When restarting OS, “aipservice” does not auto-start in some cases. Then, “Status” of “aipservice” is indicated as follows.
# systemctl status aipservice ● apiservice.service - AIP Service Loaded: loaded (/etc/systemd/aipservice.service; enabled; vendor preset: disabled Active: failed (Result: core-dump) since 木 2021-08-19 10:26:38 JST; 1min 44s ago Process: 3390 ExecStart=/opt/Actiphy/aipservice start (code=dumped, signal=SEGV) Main PID: 3390 (code=dumped, signal=SEGV)…
As an example of this phenomenon, when using NEC’s OS install script or in the environment where “rc-local.service” is intentionally used, this phenomenon occurred.
* “rc-local.service” is recommended not to use on RHEL7.x/CentOS7.x or later.
With this example, we were reported that after running “rc-local.service”, “aipservice” normally started. Please be aware this phenomenon is not applicable to every environment.
Open the service file “/etc/systemd/system/aipservice.service” by using text editor, and add “After=rc-local.service” in [Unit] section under Description and save the file.
[Unit] Description=AIP Service After=rc-local.service
In case that “aipservice” is not started after booting up OS, as a temporary workaround, please run the following command and start the service.
# systemctl start aipservice
– ActiveImage Protector 2018 Linux Update 8