Greetings,
My server rebooted yesterday evening, I would like to know the reason for the same. The /var/log/message has the following lines.
Apr 9 16:08:13 newserver named[5358]: lame server resolving '189.187.106.202.in-addr.arpa' (in '106.202.in-addr.arpa'?):202.106.196.28#53 Apr 9 17:01:01 newserver su(pam_unix)[29172]: session opened for user bin by (uid=0) Apr 9 17:01:01 newserver su(pam_unix)[29172]: session closed for user bin Apr 9 17:18:08 newserver init: cannot execute "/sbin/shutdown" Apr 9 16:07:22 newserver syslogd 1.4.1: restart. Apr 9 16:07:22 newserver syslog: syslogd startup succeeded Apr 9 16:07:22 newserver syslog: klogd startup succeeded Apr 9 16:07:22 newserver kernel: klogd 1.4.1, log source = /proc/kmsg started. Apr 9 16:07:22 newserver kernel: Linux version 2.4.18-14 (bhcompile@astest.test.redhat.com) (gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)) #1 Wed Sep 4 12:13:11 EDT 2002
Before the reboot I had renamed shutdown to some other name so that by mistake I do not use the command to shutdown the server. What I noticed is that the system time was 17:18 when the shutdown was attempted by init, but when the server came online again the time in the log is shown as 16:07, is this due to a system (software) crash? The uptime gives an uptime of 9 hours right now, while it was 180+ days before.
SYSTEM INFO : RHL 8.0, AMD 1.3G 512MB RAM.
Bye.
On Thu, Apr 10, 2003 at 11:17:12AM +0530, Amish K. Munshi wrote:
The /var/log/message has the following lines. Apr 9 16:08:13 newserver named[5358]: lame server resolving '189.187.106.202.in-addr.arpa' (in '106.202.in-addr.arpa'?):202.106.196.28#53
put this in /etc/bind/named.conf
logging { category lame-servers { null; }; };
Regards
can u send ur other logs like /var/log/secure
On Thu, 10 Apr 2003, Amish K. Munshi wrote:
Apr 9 16:08:13 newserver named[5358]: lame server resolving '189.187.106.202.in-addr.arpa' (in '106.202.in-addr.arpa'?):202.106.196.28#53 Apr 9 17:01:01 newserver su(pam_unix)[29172]: session opened for user bin by (uid=0) Apr 9 17:01:01 newserver su(pam_unix)[29172]: session closed for user bin
Looks like ctrl-alt-del program is being called from somewhere
Supreet
On Thu, 2003-04-10 at 11:17, Amish K. Munshi wrote:
- GLUG Meet - 4.00pm Sun. 13th April, 2003 @ HBCSE *
Greetings,
My server rebooted yesterday evening, I would like to know the reason for the same. The /var/log/message has the following lines.
Apr 9 16:08:13 newserver named[5358]: lame server resolving '189.187.106.202.in-addr.arpa' (in '106.202.in-addr.arpa'?):202.106.196.28#53 Apr 9 17:01:01 newserver su(pam_unix)[29172]: session opened for user bin by (uid=0) Apr 9 17:01:01 newserver su(pam_unix)[29172]: session closed for user bin Apr 9 17:18:08 newserver init: cannot execute "/sbin/shutdown" Apr 9 16:07:22 newserver syslogd 1.4.1: restart. Apr 9 16:07:22 newserver syslog: syslogd startup succeeded Apr 9 16:07:22 newserver syslog: klogd startup succeeded Apr 9 16:07:22 newserver kernel: klogd 1.4.1, log source = /proc/kmsg started. Apr 9 16:07:22 newserver kernel: Linux version 2.4.18-14 (bhcompile@astest.test.redhat.com) (gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)) #1 Wed Sep 4 12:13:11 EDT 2002
Before the reboot I had renamed shutdown to some other name so that by mistake I do not use the command to shutdown the server. What I noticed is that the system time was 17:18 when the shutdown was attempted by init, but when the server came online again the time in the log is shown as 16:07, is this due to a system (software) crash? The uptime gives an uptime of 9 hours right now, while it was 180+ days before.
SYSTEM INFO : RHL 8.0, AMD 1.3G 512MB RAM.
Bye.
-- Amish K. Munshi Visit http://munshi.dyndns.org/imp for my public key.
--
On 11 Apr 2003, supreet wrote:
Looks like ctrl-alt-del program is being called from somewhere Supreet
ctrl-alt-del is not a program but a magic key sequence for x86 machines to get attention of the kernel to do something, which defaults to safe reboot on most recent linux distributions. On WinNT it is used as a Secure Attention Key during login. More on key mappings can be found in Keyboard-and-Console-HOWTO and /usr/src/linux/Documentation/SAK.txt