05-27-2010 02:06 PM
|
|||||||||||||||
Solved! Go to Solution.
06-01-2010 10:36 AM
05-27-2010 11:54 PM
05-28-2010 01:41 AM
05-28-2010 06:12 AM
The error messages are comming from my monitor script, /usr/local/bin/slstatus. I've included the script below. This script is ran by VCS to test whether a syslog-ng process is running or not. The question is, why is it running on the inactive node at all?
/usr/local/bin/slstatus
#!/bin/sh
CONFIGDIR=/fwsm-logs/conf
LD_LIBRARY_PATH=/usr/sfw/lib:/usr/local/lib
DAEMON=/usr/local/sbin/syslog-ng
LOGGER=/usr/bin/logger
export LD_LIBRARY_PATH
05-28-2010 06:32 AM
05-28-2010 06:55 AM
05-28-2010 06:58 AM
05-28-2010 07:18 AM
Here is my main.cf. Basically, what the cluster is doing is running a number of syslog-ng processes that listen on different network ports (usually one syslog-ng per network device) all of which write to the same file, fwsm.log. I took the simple approach and set up 1 service group with many syslog-ng application resources.
05-28-2010 07:19 AM
05-28-2010 07:20 AM
05-30-2010 02:46 AM
05-30-2010 06:47 PM
05-30-2010 06:59 PM
05-31-2010 02:46 AM
06-01-2010 10:23 AM
06-01-2010 10:36 AM