Date: Fri, 27 Jun 2003 14:41:18 -0500 From: Sing Song <song@isot.com> To: "Scot W. Hetzel" <hetzels@westbend.net> Cc: freebsd-isp@freebsd.org Subject: Re: FBSD5 syslogd not logging Message-ID: <1056742878.3efc9ddecde2a@webmail.isot.com> In-Reply-To: <002a01c33aa6$28734150$11fd2fd8@westbend.net> References: <1056158489.3ef3b319e5313@webmail.isot.com> <00a701c339a7$3251d010$11fd2fd8@westbend.net> <1056467228.3ef8691c3b65a@webmail.isot.com> <002a01c33aa6$28734150$11fd2fd8@westbend.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting "Scot W. Hetzel" <hetzels@westbend.net>: > From: "Sing Song" <song@isot.com> > > Quoting "Scot W. Hetzel" <hetzels@westbend.net>: > > > From: "Sing Song" <song@isot.com> > > > How are you stoping/starting syslogd? (reboot, /etc/rc.d/syslogd, ...) > > > > > > If your using /etc/rc.d/syslogd, make sure that /etc/rc.conf has > > > syslogd_flags defined to the correct value. > > > > > > Is the FBSD 5.x system using the same IP address as the old FBSD 4.x > > > system? > > > If it's not you may need to either change the FBSD 5.x IP address to > the > > > old > > > 4.x IP address or change the syslog address on the routers. > > > > > > Scot > > > > I stop and restart with 'killall -HUP syslogd' > > I'm using '/usr/sbin/syslogd' > > The IP address and the port is same. > > > > When you were giving syslogd the HUP signal, all it did was tell the > currently running syslogd to re-read its configuration file > (/etc/syslogd.conf), no flag changes were made to the running syslogd. And > if you try to start a second syslogd daemon you should have gotten an > error: > > # /usr/sbin/syslogd -s -a westbend.net > syslogd: child pid 4423 exited with return code 1 > > You should have given syslogd the TERM signal, and then started syslogd > with > the correct flags. > > > What's funny is the logfiles to turn over as set in syslog.conf. > > > You should be using /etc/rc.d/syslogd to stop/start syslogd when changing > the flags for syslogd. You should be adding your changes to /etc/rc.conf, > specifically add the following to rc.conf: > > syslogd_flags="-a *.isot.com" > > NOTE: you may of may not > Then stop and start syslogd with: > > /etc/rc.d/syslogd stop > /etc/rc.d/syslogd start > > Scot Actually I did stop with 'killall syslogd' to kill it, and then started manually '/usr/sbin/syslogd -a *.isot.com'. Yesterday, I tried your recomendation to use rc.conf. Looked at the log file, still nothing. I added 'syslogd_flags="-a *.isot.com" to the rc.conf and used '/etc/rc.d/syslogd start' after killing the old syslogd process. I sure am getting frustrated as not getting any diag info from the routers. Maybe I need to put back my old radius box. ------------------------------------------------- This mail sent through ISOT. To find out more about ISOT, visit http://isot.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1056742878.3efc9ddecde2a>