Summary: | app-admin/syslog-ng-3.1.2 - Error parsing configuration; filename='/etc/syslog-ng/syslog-ng.conf' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | ShadowCat8 <ShadowCat8> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | critical | CC: | jer, jobbara.artalmatlan, mr_bones_, weigt.mathias |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
ShadowCat8
2010-11-05 22:30:34 UTC
please upload your syslog-ng.conf logrotate sent a SIGHUP to syslog-ng and syslog-ng had been updated. Then it turned out that the new syslog-ng didn't like your configuration. It's nothing to do with cron or logrotate - it's just your syslog-ng configuration that needs updating. (In reply to comment #1) > please upload your syslog-ng.conf > Sorry about the delay on this. Been real busy lately. Here is the syslog-ng.conf: ================================================================================== @version: 3.0 # $Header: /var/cvsroot/gentoo-x86/app-admin/syslog-ng/files/syslog-ng.conf.gentoo.3,v 1.1 2010/04/06 02:11:35 mr_bones_ Exp $ # # Syslog-ng default configuration file for Gentoo Linux options { chain_hostnames(no); # The default action of syslog-ng is to log a STATS line # to the file every 10 minutes. That's pretty ugly after a while. # Change it to every 12 hours so you get a nice daily update of # how many messages syslog-ng missed (0). stats_freq(43200); }; source src { unix-stream("/dev/log" max-connections(256)); internal(); file("/proc/kmsg"); }; destination messages { file("/var/log/messages"); }; # By default messages are logged to tty12... destination console_all { file("/dev/tty12"); }; # ...if you intend to use /dev/console for programs like xconsole # you can comment out the destination line above that references /dev/tty12 # and uncomment the line below. #destination console_all { file("/dev/console"); }; log { source(src); destination(messages); }; log { source(src); destination(console_all); }; =============================================================================== And, @Jeroen Roovers: If it doesn't like the config, then there is an issue with the config that comes with the =app-admin/syslog-ng-3.1.2 package. That was the default one that etc-update had put in, without any modifications. If you want, I can get you a copy of the syslog-ng.conf file it replaced. HTH. (In reply to comment #3) > (In reply to comment #1) > > please upload your syslog-ng.conf > > > > Sorry about the delay on this. Been real busy lately. Here is the > syslog-ng.conf: > ================================================================================> There is nothing wrong with this configuration file. Syslog-ng starts fine with it. If you still experience problems with that please start syslog-ng like this and check the output for errors. syslog-ng -Fev -f /etc/syslog-ng/syslog-ng.conf > And, > @Jeroen Roovers: If it doesn't like the config, then there is an issue with the > config that comes with the =app-admin/syslog-ng-3.1.2 package. That was the > default one that etc-update had put in, without any modifications. > > If you want, I can get you a copy of the syslog-ng.conf file it replaced. > > HTH. > (In reply to comment #4) > (In reply to comment #3) > > (In reply to comment #1) > > > please upload your syslog-ng.conf > > > > > > > Sorry about the delay on this. Been real busy lately. Here is the > > syslog-ng.conf: > > ================================================================================> > > There is nothing wrong with this configuration file. Syslog-ng starts fine with > it. > If you still experience problems with that please start syslog-ng like this and > check the output for errors. > > syslog-ng -Fev -f /etc/syslog-ng/syslog-ng.conf > Sorry. I meant -d not -v syslog-ng -Fed -f /etc/syslog-ng/syslog-ng.conf > > > And, > > @Jeroen Roovers: If it doesn't like the config, then there is an issue with the > > config that comes with the =app-admin/syslog-ng-3.1.2 package. That was the > > default one that etc-update had put in, without any modifications. > > > > If you want, I can get you a copy of the syslog-ng.conf file it replaced. > > > > HTH. > > > Thanks for the reply. Here is the output from the terminal when I issue the command after stopping the daemon: ~ # syslog-ng -Fed -f /etc/syslog-ng/syslog-ng.conf Running application hooks; hook='1' Running application hooks; hook='3' syslog-ng starting up; version='3.1.2' Incoming log entry; line='<78>Dec 7 15:00:01 cron[7312]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )' Incoming log entry; line='<78>Dec 7 15:00:01 cron[7313]: (root) CMD (rm -f /var/spool/cron/lastrun/cron.hourly)' ^C^CTermination requested via signal, terminating; syslog-ng shutting down; version='3.1.2' Running application hooks; hook='4' ~ # Now, I am not sure if you wanted me to stop the daemon before issuing the command, so if that was not what was expected, let me know. Also, let me know if there is anything more you need, and TIA for your help. The SIGHUP to syslog-ng means it doesn't restart itself, so it's still the old version running and trying to read the new config, then faulting on that. Stopping the service and starting it again with the new config should be no problem. But maybe you want a second opinion... |