[NTLUG:Discuss] RH7 not writing /var/log/messages

[Kyle Davenport]

Here's what a normal start up looks like:
hedron:~#  syslogd -d
Allocated parts table for 1024 file descriptors.
Starting.
Called init.
Called allocate_log, nlogs = -1.
cfline(*.info;mail.none;authpriv.none                   /var/log/messages)
symbolic name: info ==> 6
symbolic name: none ==> 16
symbolic name: mail ==> 16
symbolic name: none ==> 16
symbolic name: authpriv ==> 80
leading char in action: /
filename: /var/log/messages
Called allocate_log, nlogs = 0.
cfline(authpriv.*                             /var/log/secure)
symbolic name: * ==> 255
symbolic name: authpriv ==> 80
leading char in action: /
filename: /var/log/secure

...and so on thru the various logs and facilities...

Opened UNIX socket `/dev/log'.
 0: 7F 7F  X 7F 7F 7F 7F 7F 7F 7F  X 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F
FILE: /var/log/messages
 1:  X  X  X  X  X  X  X  X  X  X FF  X  X  X  X  X  X  X  X  X  X  X  X  X  X
FILE: /var/log/secure
 2:  X  X FF  X  X  X  X  X  X  X  X  X  X  X  X  X  X  X  X  X  X  X  X  X  X
FILE: /var/log/maillog
 3:  1  1  1  1  1  1  1  1  1  1  1  1  1  1  1  1  1  1  1  1  1  1  1  1  1
WALL:
 4:  X  X  X  X  X  X  X  7  7  X  X  X  X  X  X  X  X  X  X  X  X  X  X  X  X
FILE: /var/log/spooler
 5:  X  X  X  X  X  X  X  X  X  X  X  X  X  X  X  X  X  X  X  X  X  X  X FF  X
FILE: /var/log/boot.log
logmsg: syslog.info<46>, flags 4, from hedron, msg syslogd 1.3-3: restart.
Called fprintlog, logging to FILE /var/log/messages
syslogd: restarted.
Debugging disabled, SIGUSR1 to turn on debugging.

Soooo, yours looks broken.   Did the /etc/services fix work?  Check these:
ls -l /dev/log -> srw-rw-rw-    1 root     root            0 Mar  6 10:33
/dev/log
logger "this is a test" should write a message to /var/log/messages
enable the kern.* facility and restart - maybe see what is happening on the
console.
It's very suspicious that nothing in your output seems to reference the
syslog.conf file - I would start with a simple one line conf and add to it from
there.  The output is trying to tell you it's misconfigured.

_________________________________________________________




Neil Aggarwal <neil at jammconsulting.com> on 03/05/2001 05:59:41 PM

Please respond to discuss at ntlug.org

To:   discuss at ntlug.org
cc:    (bcc: Kyle Davenport/Is/Corporate/CompUSA)
Subject:  Re: [NTLUG:Discuss] RH7 not writing /var/log/messages



Kyle:

> As a rule, when you have daemon problems, just run them in debug mode.  It's
> usually easy spotting what the problem is from the output.
> For syslogd, kill it, then run "syslogd -d".  I suspect an /etc/syslog.conf
> parsing error.

OK, I ran syslogd with the debug mode turned one, but
I dont think I understand the output:

# /sbin/syslogd -d
Allocated parts table for 1024 file descriptors.
Starting.
Called logerr, msg: network logging disabled (syslog/udp service
unknown).
logmsg: syslog.err<43>, flags 4, from server2, msg syslogd: network
logging disabled (syslog/udp service unknown).
Called fprintlog, logging to CONSOLE /dev/console
Called logerr, msg: see syslogd(8) for details of whether and how to
enable it.
logmsg: syslog.err<43>, flags 4, from server2, msg syslogd: see
syslogd(8) for details of whether and how to enable it.
Called fprintlog, logging to CONSOLE /dev/console
Debugging disabled, SIGUSR1 to turn on debugging.

Do you know what this means?
Does it mean that the syslogd is writing messages to the console?

Thanks,
     Neil.

--
Neil Aggarwal
JAMM Consulting, Inc. -- (972) 612-6056, http://www.JAMMConsulting.com
Custom Internet Development -- Java, JSP, servlets, databases
_______________________________________________
http://ntlug.org/mailman/listinfo/discuss