I have a few bugs open by support and other developers due to the ganglia daemon error messages spamming the syslog. The developer's aren't happy about this since it prevents them from seeing messages they need in that log file to help them track down customer issues in other areas. We are currently using syslog version 1.3 (from Linux SLES 11.3) and I'm told that this version does not have the capability to direct output to another file. Also, we are using Ganglia version 3.5.0
One message that can fill up the syslog is "rrdcached: illegal attempt to update using time". (I have a note in that bug to run "ntpq -np" to make sure each node in the cluster is synced to the specified ntp server and not the local clock.) The debug_level is 0 in both the gmond.conf and gmetad.conf files, but that just seems to affect bringing the daemons to the foreground to be able to log messages to the terminal when the value is > 0. Is there any way I can just turn off logging to syslog until we upgrade to a kernel that supports a later version of syslog in order to be able to redirect the output to another file? We're several months out from upgrading to CentOS 7.
------------------------------------------------------------------------------
_______________________________________________ Ganglia-general mailing list Ganglia-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-general
