This is why you are getting so many messages. This should be *.emerg, not *.debug! You only wnat messages with pirority of emerg to show up on the console. You definitly do not want all the debugging messages sent there.Mikkel L. Ellertson wrote:
It actualy sounds like the daemons are not running. As root, run "service syslog status" and make sure both syslogd and klogd are running. If they both report that they are running, then chack /etc/syslog.conf - there should be only one entry that uses *, tty, tty0, or console for the output file. (*.emerg *)
Mikkel
Yo, Mikkel; Thanks for the suggestions. Syslogd is definitely running;
service syslog status syslogd (pid 7208) is running... klogd (pid 7217) is running...
The only thing I saw that looked a bit strange was that debug messages were set to be delivered to everyone (?), if that makes any sense.
# Everybody gets emergency messages *.debug *
>
That seems to be the sole exception which MIGHT send log events to the console, but since there aren't any emergencies,.....You should not be getting the error. You may want to run
In fact, it seems that most of the log messages going to the monitor have to do with my email server, and my PPPOE client, but instead of being emergencies, the monitor is getting every single event, such as users connecting successfully and retreiving their emails, or PPPOE re-establishing a connection - including every step of the connection process.
It's almost as if a monitoring program was sending every single server activity to the screen. But it's reporting the events as coming from syslogd.
Now here's something interesting though. When I did a restart of syslogd,
service syslog restart , I got the following,...
Shutting down kernel logger: [ OK ]
Shutting down system logger: [ OK ]
Starting system logger: /etc/init.d/syslog: line 100: 7885 Terminated $*
[FAILED]
Starting kernel logger: [ OK ]
So, I checked /etc/init.d/syslog and looked at line 100 which only states;
esac
That's it. For some reason, that line is generating an error. Even so, syslog successfully restarts;
service syslog status syslogd (pid 7886) is running... klogd (pid 7894) is running...
If I have some sort of error on line 100, and this is a default config file, then everyone should be having the same thing in their syslog init scripts, right? But they're not or there's be a lot of talk about it on the list.
See why this is getting on my nerves? GRRRR!
"rpm -V syslogd" and see what errors it reports. You may also want to run a package like chkrootkit to make sure your box wasn't "hacked". A look at the log files is also in order. The /etc/syslog.conf file got changed, and maybe the /etc/rc.d/init.d/syslog file as well.
Mikkel --
Do not meddle in the affairs of dragons, for you are crunchy and taste good with Ketchup!
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
