Environment
Situation
Unix agent is not in the startup list.
Resolution
To fix this problem, make sure there is only one nqmdaemon script and that all the system startup scripts refer to it through a symbolic link so modifications to the nqmdaemon file will affect all run levels. This keeps the environment clean by making only one nqmdaemon file, and preventing old copies from previous NetIQ AppManager for UNIX from mistakenly being run.
- Ensure that /etc/rc.d/rc2.d/S99nqmdaemon is a symbolic link to /etc/nqmdaemon by executing the command "ls -l /etc/rc.d/rc2.d/". The output should resemble:
# ls -l /etc/rc.d/rc2.d
total 48
-rwxr--r-- 3 root staff 8613 Mar 29 13:30 S99nqmdaemon - If S99nqmdaemon is not a symbolic link, create one by removing the incorrect file and creating a link:
- rm /etc/rc.d/rc2.d/S99nqmdaemon
- ln -s /etc/nqmdaemon /etc/rc.d/rc2.d/S99nqmdaemon
- Verify that it is now a symbolic link by issuing the command in step 1:
# ls -l /etc/rc.d/rc2.d
total 24
lrwxrwxrwx 1 root system 14 Apr 06 14:18 S99nqmdaemon -> /etc/nqmdaemon - Repeat these steps for all init directories your system uses: rc1.d, rc3.d, and so on.
Cause
Additional Information
If you are running Red Hat Linux, see NETIQKB51719 at https://www.netiq.com/kb/esupport/consumer/esupport.asp?id=NETIQKB51719.
For information on the startup lists for various operating systems, see NETIQKB13345: "Where is the AppManager for Unix startup script located?" at https://www.netiq.com/kb/esupport/consumer/esupport.asp?id=NETIQKB13345.