The Deep Security Manager (DSM) services do not start automatically when the Linux OS boots if the Deep Security Manager is installed on a network drive.
After installing the Deep Security Manager (DSM), a symbolic link /etc/rc.d/init.d/dsm_s is auto-created which points to /opt/dsm/dsm_s (or to your specific DSM installation folder). During the process at OS startup, /etc/rc.d/init.d/dsm_s is executed before /opt is mounted. The reference destination does not exist and the automatic startup fails.
In these situations, messages record the situation where /opt is mounted after the execution of /etc/rc.d/init.d/dsm_s fails. The following shows in /var/log/message:
systemd-sysv-generator [xxxx]: stat () failed on /etc/rc.d/init.d/dsm_s: No such file or directory ... systemd: Mounting / opt ...
To resolve the issue, create a script that delays the startup of dsm_s.
- Create a new script /etc/rc.d/init.d/dsm_bootup for DSM startup with the following contents.
#!/bin/sh # chkconfig: 345 10 90 # description: dsm_bootup echo "For DSM bootup only" sleep 100s ## If DSM is not installed on /opt/dsm, please change to the correct installation path sh /opt/dsm/dsm_s start
- Grant an execute permission to the created script with the command below.
chmod +x /etc/rc.d/init.d/dsm_bootup
- Add the script to the autoboot list using the following command.
cd /etc/rc.d/init.d chkconfig --add dsm_bootup chkconfig dsm_bootup on
- Reboot the OS and check that dsm_s boots deferred.