Log Files not being updated

[markl]

I'm running SunOS5.8.

The messages log file (/var/adm/messages) is not being updated with anything.

The server is being used as a mailserver and we would like the log file to be updated with general smtp info, i.e. sendmail basic info of messages coming/going.

What do I need to do to get the messages file to update? It currently has a size of 0 bytes?

Any ideas?


Thanks in advance,


Mark.

 

[bigscouse]

If you need to see the most current messages then use the command dmesg.
/var/adm/messages is maintained by syslogd, do a ps and see if it is running.

Ged Jones

Top man

 

[markl]

The syslogd is running and when I do a dmesg, there's nothing in it.


I'm well and truly stumped as to whats going on now!


Mark

 

[pmckeehan]

Have you checked your /var/log directory to see if the messages are being written to the syslog file?

Paula

 

[rkjha]

Hello Mark,

I guess you should better check your /etc/default/login file and remove the comment line before SYSLOG = YES or if it is set to NO make it yes. Hope this solves your problem.
Good luck.

RK

 

[markl]

I've checked the /etc/default/login file, and the entry is fine for SYSLOG.

I can't find anything obvious as to why it should be doing this...

 

[grega]

Just another thought .. have you checked the /etc/syslog.conf file?

Greg.

 

[markl]

I've had a look but couldn't find anything obvious.

This is the main part of the syslog.conf:

*.err;kern.notice;auth.notice /dev/sysmsg
*.err;kern.debug;daemon.notice;mail.crit;*.alert /var/adm/messages

*.alert;kern.err;daemon.err root
*.emerg *

# if a non-loghost machine chooses to have authentication messages
# sent to the loghost machine, un-comment out the following line:
#auth.notice ifdef(`LOGHOST', /var/log/authlog, @loghost)

mail.debug ifdef(`LOGHOST', /var/log/syslog, @loghost)
mail.info ifdef(`LOGHOST', /var/log/syslog, @loghost)

#
# non-loghost machines will use the following lines to cause "user"
# log messages to be logged locally.
#
user.err /dev/sysmsg
user.err /var/adm/messages
user.alert root, operator
user.emerg *


Any of this stand out as being wrong? If the above is chaged, do you need to restart anything to get it to work?


Cheers,


Mark.

 

[grega]

Nothing springs to mind ... did you change /etc/hosts recently? For syslog.conf to function properly, you should have your machines IP address in the hosts file, and have one of it's nicknames set to loghost, i.e. there will be a line in /etc/hosts ...
[tt]
100.100.100.100 myserver loghost
[/tt]

Does this make sense?

Greg ... clutching at straws now!