Description of problem in RHS 3.0 Early Access release: I've noticed that the glusterpmd.log repeats the same message every minute, resulting in unnecessary log space utilization. I'm not sure the meaning of this error, as my test install has the hostname configured, with DNS A and PTR records correct. [root@rhs1 ~]# tail /var/log/glusterpmd.log 2014-07-17 14:26:53,439 - GlusterProcLog - WARNING - Hostname is not configured 2014-07-17 14:27:53,499 - GlusterProcLog - WARNING - Hostname is not configured 2014-07-17 14:28:53,559 - GlusterProcLog - WARNING - Hostname is not configured 2014-07-17 14:29:53,627 - GlusterProcLog - WARNING - Hostname is not configured 2014-07-17 14:30:53,684 - GlusterProcLog - WARNING - Hostname is not configured 2014-07-17 14:31:53,743 - GlusterProcLog - WARNING - Hostname is not configured 2014-07-17 14:32:53,803 - GlusterProcLog - WARNING - Hostname is not configured 2014-07-17 14:33:53,864 - GlusterProcLog - WARNING - Hostname is not configured 2014-07-17 14:34:53,924 - GlusterProcLog - WARNING - Hostname is not configured 2014-07-17 14:35:53,977 - GlusterProcLog - WARNING - Hostname is not configured [root@rhs1 ~]# hostname rhs1.demo.local
This error is thrown because 'hostname_in_nagios' is not filled in '/etc/nagios/nagios_server.conf' file. This will be populated automatically once discovery.py completed successfully.
Also this will consume more space, it has log rotate implemented already.
(In reply to Kanagaraj from comment #2) > This error is thrown because 'hostname_in_nagios' is not filled in > '/etc/nagios/nagios_server.conf' file. > > This will be populated automatically once discovery.py completed > successfully. This log could be more meaningful. "Hostname not configured" creates a confusion as though the local hostname is not configured kind of sense. It would be better, if log says as, 'hostname_in_nagios' is not configured in '/etc/nagios/nagios_server.conf'
Lets fix it as suggested by Satheesaran.
Modified the log message to "'hostname_in_nagios' is not configured in '/etc/nagios/nagios_server.conf'" as suggested by Satheesaran. Fix link: http://review.gluster.org/#/c/8920/
Verified and works fine with build gluster-nagios-addons-0.1.12-1.el6rhs.x86_64. When glusterpmd is started and discovery.py is not run on RHS nodes, the following would be logged in /var/log/glusterpmd.log. 2014-11-12 16:50:16,558 - GlusterProcLog - WARNING - 'hostname_in_nagios' is not configured in /etc/nagios/nagios_server.conf User will be able to see this issue when he adds RHS nodes to Console and enable external monitoring and not running discovery.py script. This issue will not be seen during upgrades.
please ignore comment 8. Please Read as below : Verified and works fine with build gluster-nagios-addons-0.1.12-1.el6rhs.x86_64. When glusterpmd is started and discovery.py is not run on RHS nodes, the following would be logged in /var/log/glusterpmd.log. 2014-11-12 16:50:16,558 - GlusterProcLog - WARNING - 'hostname_in_nagios' is not configured in /etc/nagios/nagios_server.conf If discovery.py is not run, User will be able to see the issue when he adds RHS nodes to Console and enable external monitoring.
Hi Darshan, Can you please review the edited doc text for technical accuracy and sign off?
Looks good.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-0039.html