In certain cases, the "aipservice" fails to auto-start when the OS restarts

Summary

When the OS restarts, "aipservice" may not auto-start in some cases. The "Status" of "aipservice" is then 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)…

This phenomenon may occur, for instance, when using NEC’s OS install script or intentionally using "rc-local.service." It's advised not to use "rc-local.service" on RHEL7.x/CentOS7.x or later.

Workaround

In this case, there were reports that running "rc-local.service" helped "aipservice" start normally. Note that this solution may not work in every environment.

To implement, open the service file "/etc/systemd/system/aipservice.service" with a text editor. Add "After=rc-local.service" in the [Unit] section under Description and save the file.

[Unit] Description=AIP Service After=rc-local.service

If "aipservice" doesn't start after OS boot, as a temporary fix, execute the following command to manually start the service.

# systemctl start aipservice

Target Product

– ActiveImage Protector 2018 Linux Update 8

(13451175029273)