In the genesis image rsyslogd is started with the -c4 option in
/bin/doxcat without any syslog servers configured (before any network is
available). However, /sbin/dhclient-script inserts any syslog addresses
gathered during DHCP into the rsyslogd.conf and performs a *HUP* of the
previously started rsyslogd process. This logic fails with version 4
because a full restart (re-read of the config) is not performed upon HUP
as it was in version 3 and therefore the messages are never directed to
the syslog server.

Although there is a configuration change that is possible, a full
restart HUP is deprecated and remove in version 5. I believe the correct
fix is to actually perform a full restart of rsyslog in dhclient-script.
A simple proposed patch is attached, however, it does not perform any
error checking in the event that the restart fails in some way.

-- 
Daniel M. Weeks
Systems Administrator
Computational Center for Nanotechnology Innovations
Rensselaer Polytechnic Institute
Troy, NY 12180
518-276-4458
--- dhclient-script.orig	2013-03-15 12:35:59.262853543 -0400
+++ dhclient-script	2013-03-15 12:36:52.603862581 -0400
@@ -43,7 +43,7 @@
         for ls in $new_log_servers; do
 		echo *.* @$ls >> /etc/rsyslog.conf
 	done
-	kill -1 `cat /var/run/syslogd.pid`
+	kill `cat /var/run/syslogd.pid`; rsyslogd -c4
 
 	if [ ! -z "$new_tcode" -a -r "/usr/share/zoneinfo/posix/$new_tcode" ]; then
 		cp "/usr/share/zoneinfo/posix/$new_tcode" /etc/localtime
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user

Reply via email to