Topic: syslogd not listening

[Dub Dublin]

It appears that my SME v5.5 server is not doing anything at all with syslog messages thrown its way over the network.  

I can easily create messages and send them to the correct port (514/UDP), but nothing gets written into any of the log files, regardless of the "facility" I select.  (Most facilities are redirected to "messages" - see /etc/syslog.conf to see how things are pointed.  Yes, I know that's a templated file, and no, I haven't made any changes to it.  It still doesn't work, even when it clearly should.)

Am I doing something wrong?  Is there some magic SME-ism that's keeping it from listening to the network for syslog messages?  Surely we have someone out there using their SME server as a loghost for other systems, right?

[Shad Lords]

edit the following file:

/etc/e-smith/templates/etc/sysconfig/syslog/10NoMARKs

change the following line:

SYSLOGD_OPTIONS="-m 0"

to read as follows:

SYSLOGD_OPTIONS="-m -r 0"

expand the file:

/sbin/e-smith/expand-template /etc/sysconfig/syslog

and restart syslog:

service syslog restart

Hope this helps,

-Shad

[Glen]

Hi,  I have just had the same issue, I think it was caused by installing 'dshield' as it plays with the message logs and renames them.
Anyway I found my SME 5.5U6 was no longer sending to the 'messages' log it was actually sending to a messages.200311xxxxxx  file instead..
An ls -ltr mess*  showed no messages file without an extension.

I performed the following:-
/sbin/e-smith/expand-template /etc/syslog.conf
then
service syslog restart

and all is back to normal.

Hope this helps !