99Installing UNIX agents
Troubleshooting agent issues
0 * * * * /etc/init.d/sisidsagent health_check
0 * * * * /etc/init.d/sisipsutil health_check
(Solaris and Linux Only)
Use the appropriate crontab file for the UNIX platform:
■ AIX
Crontab: /var/spool/cron/cronttabs/root
Scripts: /etc/rc.sisidsagent, /etc/rc.sisipsagent
■ HP-UX
Crontab: /var/spool/cron/crontab.root
Scripts: /sbin/init.d/sisidsagent, /sbin/init.d/sisipsagent
■ Linux
Crontab: /var/spool/cron/tabs/root
Scripts: /etc/init.d/sisidsagent, /etc/init.d/sisipsagent, /etc/init.d/sisipsutil
■ Solaris
Crontab: /var/spool/cron/crontabs/root
Scripts: /etc/init.d/sisidsagent, /etc/init.d/sisipsagent, /etc/init.d/sisipsutil
■ Tru64
Crontab: /var/spool/cron/crontabs/root
Scripts: /sbin/init.d/sisidsagent, /sbin/init.d/sisipsagent
Note: The scripts keep the last five core files generated in the agent’s respective
home directory (/opt/Symantec/scspagent/IDS/bin and /opt/Symantec/
scspagent/IPS). To change this setting, modify the MAX_CORES=5 value in the
scripts.
Troubleshooting agent issues
ISSUE: An NFS server that does not respond on an agent computer causes the
agent installation to hang.
SOLUTION: Press Ctrl+C to exit the installation, and then run df -k. If this
causes the agent computer to hang, and you are sure that a mounted share is
causing the problem, forcefully unmount the share that is not responding by
typing and running the following command:
umount -f <mount-point>
To Next Page
Loading...