Logging level of ServiceGuard

[Ronelle van Niekerk]

The app_mon.log file in the package directory (/etc/cmcluster/ is getting very big, very fast.
I can't seem to find anywhere to switch the logging level of ServiceGuard down a tad.

Anyone got any any ideas for me?

[Sridhar Bhaskarla · Accepted solution]

Hi Ronelle,

It's not the serviceguard but your application itself that is generating logging messages. There isn't a serviceguard parameter, that I know, you can modify to stop the messages. You will have to modify your application startup scripts to add "> /dev/null 2>&1" to whichever steps that would produce standard out|error messages during runtime.

It is also a good idea to make /etc/cmcluster, a filesystem otherwise it can fill up root filesystem.

-Sri

[Ronelle van Niekerk]

Thanks for that. Makes a lot of sense.

[Stephen Doud]

I know this is not your problem but sometimes customers need to capture all the detail but find the file system filling up.
If such larger logs are necessary, the admin can move the package control log file to another file system and sym-link it to the /etc/cmcluster/ so that Serviceguard won't create a new one in the package directory.
Example:
# cd /etc/cmcluster/orapkg
# mv orapkg.cntl.log /misc/logs
# ln -s /misc/logs /etc/cmcluster/orapkg/orapkg.cntl.log


-StephenD.

[#5]

I know this is a bit of a digression, but you do not need to place your package scripts and log file under /etc/cmcluster. They can go anywhere and if you think about the file system layout, /etc/cmcluster is the wrong place for them to live. You might be better off placing the package stuff somewhere other than /etc/cmcluster.