Syslog logging failure only at boot (Mac OS X)
List, I tried my best to search the archives for this information but I came up with no real answers. I've got three Mac OS X Panther servers running syslog-ng, and they run it very well. The only problem I have is when I reboot the servers syslog-ng starts from rc but fails to start logging. It's running, but it's not logging. I have to kill it and run it manually and then it runs. It's like it's choking on something by coming up too early in the boot process...? I've tried compiling 1.9.x to see if that fixes it, but I end up running into dependency problems down the line somewhere. (is 1.9.x that portable yet?). This is a drag when you go to check the logs from ssh, sudo, portsentry, mail, etc... and you find that syslog-ng never started logging after you rebooted 2 weeks ago. Yikes. Thanks for any insight, -- Alan Orth Upward Bound - Systems Administrator User Services - Field Technician California State University, Chico x6000
* Orth, Alan <AOrth@exchange.csuchico.edu>
I've got three Mac OS X Panther servers running syslog-ng, and they run it very well. The only problem I have is when I reboot the servers syslog-ng starts from rc but fails to start logging. It's running, but it's not logging. I have to kill it and run it manually and then it runs. It's like it's choking on something by coming up too early in the boot process...?
Try creating a custom /Library/StartupItems entry for syslog-ng, and set the StartupParameters.plist to require the Resolver, but use a high OrderPreference to start loggin as soon as possible. For examples, see: grep -r Requires /System/Library/StartupItems On Tiger, launchd could also be used to manage syslog-ng.
Jeremy, Great suggestion... here's what I came up with and it's been working out awesome. ;) [root@server: /Library/StartupItems/syslog-ng]# ls -l total 16 -rw-r--r-- 1 root wheel 135 17 Feb 09:32 StartupParameters.plist -rwxr-xr-x 1 root wheel 444 17 Feb 09:45 syslog-ng [root@server: /Library/StartupItems/syslog-ng]# cat StartupParameters.plist { Description = "syslog-ng"; Provides = ("Logging"); Requires = ("Resolver"); Uses = ("Disks"); OrderPreference = "Early"; } [root@server: /Library/StartupItems/syslog-ng]# cat syslog-ng #!/bin/sh ## # syslog-ng logging daemon ## . /etc/rc.common StartService () { ConsoleMessage "Starting syslog-ng" /usr/local/sbin/syslog-ng -f /etc/syslog-ng/syslog-ng.conf -p /var/run/syslog-ng.pid } StopService () { ConsoleMessage "Stopping syslog-ng" kill `cat /var/run/syslog-ng.pid` } RestartService () { ConsoleMessage "Restarting syslog-ng" StopService StartService } RunService "$1" -- Alan Orth Upward Bound - Systems Administrator User Services - Field Technician California State University, Chico x6000 -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu on behalf of Jeremy Mates Sent: Wed 2/15/2006 8:15 PM To: Syslog-ng users' and developers' mailing list Subject: [syslog-ng] Re: Syslog logging failure only at boot (Mac OS X) * Orth, Alan <AOrth@exchange.csuchico.edu>
I've got three Mac OS X Panther servers running syslog-ng, and they run it very well. The only problem I have is when I reboot the servers syslog-ng starts from rc but fails to start logging. It's running, but it's not logging. I have to kill it and run it manually and then it runs. It's like it's choking on something by coming up too early in the boot process...?
Try creating a custom /Library/StartupItems entry for syslog-ng, and set the StartupParameters.plist to require the Resolver, but use a high OrderPreference to start loggin as soon as possible. For examples, see: grep -r Requires /System/Library/StartupItems On Tiger, launchd could also be used to manage syslog-ng. _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
participants (2)
-
Jeremy Mates
-
Orth, Alan