Solved! Go to Solution.
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?
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.