Re: reboot record information
On Fri, 13 Feb 2004 11:39:28 -0500 "JJB" <[EMAIL PROTECTED]> probably wrote: > When an FBSD system crooks, and It reboots it's self, very seldom > does any of issued problem messages have time to be posted > completely before the rug is pulled out from under the log write > process by the reboot occurring. All you can find out from the logs > is yes indeed it did reboot. You are SOL, just like the rest of us > when this happens to us. Probably a loose chance, but `last' could come up with something... Anyway it still just reads the logs... If you're afraid this may happen again, and you're on a network, you might want to use the remote logging feature of syslog. Then, all messages will make it to the destination, right up to the reboot. HTH, -- DoubleF Truth is the most valuable thing we have -- so let us economize it. -- Mark Twain pgp0.pgp Description: PGP signature
RE: reboot record information
--- JJB <[EMAIL PROTECTED]> wrote: > When an FBSD system crooks, and It reboots it's self, very seldom > does any of issued problem messages have time to be posted > completely before the rug is pulled out from under the log write > process by the reboot occurring. All you can find out from the logs > is yes indeed it did reboot. You are SOL, just like the rest of us > when this happens to us. That's unfortunate and hard to believe, but I have little choice but to believe it. I was hoping for a better mechanism of tracing what happened. But as you say, once a reboot is called for and the processes are stopped, I suppose there's nothing left running to write to a log. Thanks, ~John > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of John > DeStefano > Sent: Friday, February 13, 2004 10:57 AM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: RE: reboot record information > > > JJB <[EMAIL PROTECTED]> wrote: > >All reboot messages go to /var/log/messages. The message file is > >archived, so just go the /var/log directory and look at your > message > >files and look for msgs before the boot msgs of that date. > > That's what I thought too. However, according to my system status > message this morning: > "Local system status: > 3:13AM up 3 days, 11 mins, 0 users, load averages: 0.00, 0.00, > 0.00" > > My /var/log/messages still contains messages older than 3 days ago; > it's from where I pulled the log lines from my original post. As > you > can see, there's no sign of a cause for reboot there. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of John > DeStefano > Sent: Friday, February 13, 2004 10:17 AM > To: [EMAIL PROTECTED] > Subject: reboot record information > > I was interested to find from a system mail this morning that my > system had been rebooted three days ago. As far as I was aware, the > last reboot was about two months ago. > The following lines in /var/log/messages give me a clue that the > reboot happened after "Feb 10 02:51:52": > > Feb 10 02:51:52 zurg inetd[608]: netbios-ns/udp: bind: Address > already > in use > [note: the "netbios-ns/udp" line is a system message that I get > every 10 minutes... haven't been able to figure that one out either] > Feb 10 03:02:37 zurg syslogd: kernel boot file is > /boot/kernel/kernel > Feb 10 03:02:37 zurg kernel: Copyright (c) 1992-2003 The FreeBSD > Project > > But there's no sign of what happened to cause the reboot, or how it > was done. Is there another log file that would store this > information? I am mostly concerned because I'm fairly certain this > reboot was not performed at the console: it was either a system > reaction to a problem, or somebody poking around where they > shouldn't be... > Thanks, > ~John __ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: reboot record information
When an FBSD system crooks, and It reboots it's self, very seldom does any of issued problem messages have time to be posted completely before the rug is pulled out from under the log write process by the reboot occurring. All you can find out from the logs is yes indeed it did reboot. You are SOL, just like the rest of us when this happens to us. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of John DeStefano Sent: Friday, February 13, 2004 10:57 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: reboot record information JJB <[EMAIL PROTECTED]> wrote: >All reboot messages go to /var/log/messages. The message file is >archived, so just go the /var/log directory and look at your message >files and look for msgs before the boot msgs of that date. That's what I thought too. However, according to my system status message this morning: "Local system status: 3:13AM up 3 days, 11 mins, 0 users, load averages: 0.00, 0.00, 0.00" My /var/log/messages still contains messages older than 3 days ago; it's from where I pulled the log lines from my original post. As you can see, there's no sign of a cause for reboot there. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of John DeStefano Sent: Friday, February 13, 2004 10:17 AM To: [EMAIL PROTECTED] Subject: reboot record information I was interested to find from a system mail this morning that my system had been rebooted three days ago. As far as I was aware, the last reboot was about two months ago. The following lines in /var/log/messages give me a clue that the reboot happened after "Feb 10 02:51:52": Feb 10 02:51:52 zurg inetd[608]: netbios-ns/udp: bind: Address already in use [note: the "netbios-ns/udp" line is a system message that I get every 10 minutes... haven't been able to figure that one out either] Feb 10 03:02:37 zurg syslogd: kernel boot file is /boot/kernel/kernel Feb 10 03:02:37 zurg kernel: Copyright (c) 1992-2003 The FreeBSD Project But there's no sign of what happened to cause the reboot, or how it was done. Is there another log file that would store this information? I am mostly concerned because I'm fairly certain this reboot was not performed at the console: it was either a system reaction to a problem, or somebody poking around where they shouldn't be... Thanks, ~John - Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" __ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: reboot record information
JJB <[EMAIL PROTECTED]> wrote: >All reboot messages go to /var/log/messages. The message file is >archived, so just go the /var/log directory and look at your message >files and look for msgs before the boot msgs of that date. That's what I thought too. However, according to my system status message this morning: "Local system status: 3:13AM up 3 days, 11 mins, 0 users, load averages: 0.00, 0.00, 0.00" My /var/log/messages still contains messages older than 3 days ago; it's from where I pulled the log lines from my original post. As you can see, there's no sign of a cause for reboot there. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of John DeStefano Sent: Friday, February 13, 2004 10:17 AM To: [EMAIL PROTECTED] Subject: reboot record information I was interested to find from a system mail this morning that my system had been rebooted three days ago. As far as I was aware, the last reboot was about two months ago. The following lines in /var/log/messages give me a clue that the reboot happened after "Feb 10 02:51:52": Feb 10 02:51:52 zurg inetd[608]: netbios-ns/udp: bind: Address already in use [note: the "netbios-ns/udp" line is a system message that I get every 10 minutes... haven't been able to figure that one out either] Feb 10 03:02:37 zurg syslogd: kernel boot file is /boot/kernel/kernel Feb 10 03:02:37 zurg kernel: Copyright (c) 1992-2003 The FreeBSD Project But there's no sign of what happened to cause the reboot, or how it was done. Is there another log file that would store this information? I am mostly concerned because I'm fairly certain this reboot was not performed at the console: it was either a system reaction to a problem, or somebody poking around where they shouldn't be... Thanks, ~John - Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" __ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: reboot record information
All reboot messages go to /var/log/messages. The message file is archived, so just go the /var/log directory and look at your message files and look for msgs before the boot msgs of that date. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of John DeStefano Sent: Friday, February 13, 2004 10:17 AM To: [EMAIL PROTECTED] Subject: reboot record information I was interested to find from a system mail this morning that my system had been rebooted three days ago. As far as I was aware, the last reboot was about two months ago. The following lines in /var/log/messages give me a clue that the reboot happened after "Feb 10 02:51:52": Feb 10 02:51:52 zurg inetd[608]: netbios-ns/udp: bind: Address already in use [note: the "netbios-ns/udp" line is a system message that I get every 10 minutes... haven't been able to figure that one out either] Feb 10 03:02:37 zurg syslogd: kernel boot file is /boot/kernel/kernel Feb 10 03:02:37 zurg kernel: Copyright (c) 1992-2003 The FreeBSD Project But there's no sign of what happened to cause the reboot, or how it was done. Is there another log file that would store this information? I am mostly concerned because I'm fairly certain this reboot was not performed at the console: it was either a system reaction to a problem, or somebody poking around where they shouldn't be... Thanks, ~John - Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
reboot record information
I was interested to find from a system mail this morning that my system had been rebooted three days ago. As far as I was aware, the last reboot was about two months ago. The following lines in /var/log/messages give me a clue that the reboot happened after "Feb 10 02:51:52": Feb 10 02:51:52 zurg inetd[608]: netbios-ns/udp: bind: Address already in use [note: the "netbios-ns/udp" line is a system message that I get every 10 minutes... haven't been able to figure that one out either] Feb 10 03:02:37 zurg syslogd: kernel boot file is /boot/kernel/kernel Feb 10 03:02:37 zurg kernel: Copyright (c) 1992-2003 The FreeBSD Project But there's no sign of what happened to cause the reboot, or how it was done. Is there another log file that would store this information? I am mostly concerned because I'm fairly certain this reboot was not performed at the console: it was either a system reaction to a problem, or somebody poking around where they shouldn't be... Thanks, ~John - Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
