Failed to start Symantec Data Center Security Server Agent AP module on upgrade or install of DCS 6.9 RHEL 7.x agent

book

Article ID: 211003

calendar_today

Updated On:

Products

Data Center Security Server Advanced Data Center Security Server

Issue/Introduction

After install or upgrade to DCS 6.9.0 agent on RHEL 7.x server, sisap-init.service appears to not start up, causing the following error (or similar errors) to be populated: 


[[email protected] tools]
# systemctl status sisap-init.service -l
  • sisap-init.service - Symantec Data Center Security Server Agent AP module
   Loaded: loaded (/etc/systemd/system/sisap-init.service; enabled; vendor preset: disabled)

   Active: failed (Result: exit-code) since Mon 2021-02-08 16:05:01 EST; 32min ago

  Process: 645 ExecStart=/etc/init.d/sisap.init start (code=exited, status=6)

Main PID: 645 (code=exited, status=6)

Feb 08 16:05:01 machine1 sisap.init[645]: /etc/symantec/sis/rc.functions: line 139: /var/log/sdcsslog/sisap_init.log: No such file or directory
Feb 08 16:05:01 machine1 sisap.init[645]: /etc/symantec/sis/rc.functions: line 570: /var/log/sdcsslog/sisap_init.log: No such file or directory
Feb 08 16:05:01 machine1 sisap.init[645]: /etc/symantec/sis/rc.functions: line 571: /var/log/sdcsslog/sisap_init.log: No such file or directory
Feb 08 16:05:01 machine1 sisap.init[645]: Error: sisap.init: error loading Symantec Data Center Security Server Agent AP driver
Feb 08 16:05:01 machine1 sisap.init[645]: /etc/symantec/sis/rc.functions: line 139: /var/log/sdcsslog/sisap_init.log: No such file or directory
Feb 08 16:05:01 machine1 root[834]: sisap.init: sisap.init: error loading Symantec Data Center Security Server Agent AP driver
Feb 08 16:05:01 machine1 systemd[1]: sisap-init.service: main process exited, code=exited, status=6/NOTCONFIGURED
Feb 08 16:05:01 machine1 systemd[1]: Failed to start Symantec Data Center Security Server Agent AP module.
Feb 08 16:05:01 machine1 systemd[1]: Unit sisap-init.service entered failed state.
Feb 08 16:05:01 machine1 systemd[1]: sisap-init.service failed.

Cause

These errors can be ignored since upon reboot of the server, all of the agent's daemons are running as expected.

[[email protected] tools]# ps -ef |grep sis
root       1283      1  1 16:05 ?        00:00:25 /opt/Symantec/sdcssagent/AMD/bin/sisamddaemon
root       1871      1  0 16:05 ?        00:00:10 /opt/Symantec/sdcssagent/IDS/bin/sisidsdaemon
sisips     2015      1  0 16:05 ?        00:00:01 /opt/Symantec/sdcssagent/IPS/bin/sisipsdaemon
sisips     2097      1  0 16:05 ?        00:00:00 /opt/Symantec/sdcssagent/IPS/bin/sisipsutildaemon

Environment

Release : 6.9.0 & 6.8.2

Component : DCS RHEL 7.x agent

Resolution

The errors can be ignored as long as all of the expected daemons are running after the server is rebooted.