Re: Logs not being saved (/var/log/messages, etc)?
On Tue, May 09, 2006 at 12:19:12PM +, Matt Bostock wrote: > I think I fixed it guys, thanks for all of your help. > > Syslogd was choking because /var/log/messages didn't exist. I touched that, > restarted and all was working again. I did the same for the others (auth.log > etc), and things seem ok now. To stop it happening again, take a look at newsyslog.conf(5) and ensure all permissions are correct, and that newsyslog(8) will create a new log file or HUP the interested daemon as necessary. Dan -- Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: D349 B109 0EB8 2554 4D75 B79A 8B17 F97C 1622 166A _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgpNVG0uxgvdP.pgp Description: PGP signature
Re: Logs not being saved (/var/log/messages, etc)?
I think I fixed it guys, thanks for all of your help. Syslogd was choking because /var/log/messages didn't exist. I touched that, restarted and all was working again. I did the same for the others (auth.log etc), and things seem ok now. Many thanks, Matt :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Logs not being saved (/var/log/messages, etc)?
On 5/9/06, Matt Bostock <[EMAIL PROTECTED]> wrote: Hi, The usual system logs such as /var/log/messages are not being saved. /var/log/messages does not exist, but /var/log/messages.0 (the old rotated version) does. I've tried a 'tail /dev/klog' and it returns 'device busy'. syslogd -dv isn't returning anything useful either. I'd be very grateful for any suggestions :) Matt Make sure syslogd is started: ps auxw | grep syslog ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Logs not being saved (/var/log/messages, etc)?
> The usual system logs such as /var/log/messages are not being saved. > /var/log/messages does not exist, but /var/log/messages.0 > (the old rotated > version) does. if theres a rotated log, there should be a source for, too. check permissions on /var/log (eg. schg-flag) maybe there's some odd reason for syslogd not being able to write to it. also, try creating an empty file (touch /var/log/messages; chmod o-r /var/log/messages) and restarting syslogd. you can test logging with the logger-command. if your box is not private (for you only): did you check, if someone removed the file? check for logins, network sessions, strange users with uid 0 in master.passwd, change-date of files in at least /etc. if anything looks strange, change your root-pw, shutdown unnecessary daemons, and take the box off the net if it's possible ,-) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"