Solaris 2.5.1 -- syslogd - syslog.conf and /var/adm/messages

[pneely]

First let me say this is on Solaris 2.5.1 and cannot be upgraded.

No messages are being written to /var/adm/messages, except for the initial messages when syslogd is starting.

1. syslog.conf file has been checked. (used one from another machine)

2. syslogd has been bounced.

3. I have run syslogd in debug mode (-d) and have not seen any bad messages in it as well. In this file I did notice entries stating; "Logging to FILE /var/adm/messages", but then there would be no entry after that.

4. I have run logger as shown below with no results.
# logger -p user.err "Test Message"

5. Currently the following facility and priority levels are configured to write to /var/adm/messages;
*.err;kern.debug;daemon.notice;mail.crit;user.none
syslog.crit
*.alert

6. The only thing written to the messages file is; (And only when syslogd is bounced)
disk information: ie:
Jun 18 11:03:54 simsplae1 unix: <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>

network port information: ie:
Jun 18 11:03:54 simsplae1 unix: SUNW,hme2: FEPS (Rev Id=22) Found


I don't know what else to try. Any ideas' ????

 

[fuqun]

Did you have &quot;loghost&quot; defined in your /etc/hosts file for syslog to know where to log the system messages/errors?

example:
# Internet host table
127.0.0.1 localhost
192.168.x.x Severname loghost
#if this is the server you want to get the syslog


Hope it help.

 

[pneely]

Yes, I have that defined in my /etc/hosts file.

Thanks though,

P@

 

[NavinB]

Hi,
Did u make any changes in /etc/syslog.conf.If yes,then did u restart the syslog daemon for changes to take effect?
Furthermore,there is an entry related to user.none ....that is why, when u issue the logger command it doesn't send message to u'r log file.
One more thing,what do u mean by syslogd has been bounced?
If u cud provide the info ,maybe we can further investigate the cause of the problem......

 

[pneely]

Previous to me fiddling with it the /etc/syslog.conf was last changed 2/98. I have copied another from our test environment server. And yes actually stopped (killed) syslogd, did not use -HUP.

This listing in syslog.conf;
*.err;kern.debug;daemon.notice;mail.crit;user.none /var/adm/messages

And this command;
# logger -p user.err &quot;Test&quot;

Does not write out the message

 

[NavinB]

Hi,
U follow these steps:
Instead of user.none entry,write user.err in /etc/syslog.conf
Then restart the syslog daemon by stopping and then starting it from /etc/init.d directory(Filename is syslog)
Then issue the logger command and see if logging is enabled or not...
If u still face any problem then post it here....

 

[pneely]

I thought it would be picked up with *.err and also there is another entry in my syslog.conf that reads;
# non-loghost machines will use the following lines to cause &quot;user&quot;
# log messages to be logged locally.
#
ifdef(`LOGHOST', ,
user.err /dev/console
user.err /var/adm/messages
user.alert `root, operator'
user.emerg *
)

 

[NavinB]

Hi,
If this is the case then just remove the user.none entry and follow from step 2......

 

[pneely]

I see it now I think, user.none was overwriting user.err

I remove user.none and the logger command works now.

I'll check with the DBA to see if he's getting the information he needs. I may back.

Thanks,
P@

 

[NavinB]

U got it right man!!!
I hope u found all this helpful....
Navin