How to check Server reboot reason Post: 302282246

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

mount: failed, reason given by server: Permission denied

Hi , I have a filesystem on AIX 4.3.3 which i need to share with other clients who use Windows NT and Redhat linux 7.3. I use samba to share this with Windows NT Clients. Now i was to share this with Linux clients. When i try to nfs mount this on Linux i get "mount: failed, reason given by...

2. Shell Programming and Scripting

Server Reboot Alert

I want to get an email alert from a cronjob when a server got rebooted unexpectedly. Please help. Thanks! :confused:

3. UNIX for Advanced & Expert Users

server reboot

hi all, :) for a reboot of sun box for patch installation i would like to know where do the reboot logs apart from /var/adm/messages and patch run messages would be available, i would like to know the sequence of messages logged in the file like requesting the users to log out sending a...

4. AIX

How to check who/which id perform a system reboot?

Hi Guys, I would like to know is there a way to find out who or which id performed the system reboot?Uptime only shows the last date the system was reboot but no userid or ip add.Need to investigate something due to some reboot issues. Thanks Giri

5. Red Hat

Server usually restart not reason

Hi everyone, - I have CentOs server 5.4 , I usually remote by ssh. - My problem is server usually restart but I don't reason. I check log in file /var/log/messages: I don't see "signal 15" which kernel have to receive before restart. Everyone can see in attach. - I try to restart with command...

6. Shell Programming and Scripting

Help to check uptime post 30 min or so after every reboot

Hi, Please help me to cross verify the post reboot time. I want to execute some script after every reboot, which will happen only post 20-30 mins of reboot. If uptime is >24hrs, script should not execute. I tried with below command, but seems no luck. >> uptime | sed 's/^.*up//' | awk -F,...

7. Solaris

Validate mountpoints on solaris server after server reboot

Hi, anyone please let us know how to write shell script to find the missing mountpoints after server reboot. i want to take the mountpount information before server reboot, and validate the mountpoints after server reboot if any missing.please let us know the shell script from begining to end as...

8. Solaris

How to check last unexpected reboot time Solaris 10?

Dear all can you give me command to show me last unexpected reboot time the date, month, and the year on solaris 10 i've tried uptime who-b last reboot but nothing give me the year last reboot only the date , month and time

9. Red Hat

Server reboot

Hi, The server got rebooted and below messages can be seen in /var/log/messages Sep 7 10:49:12 minersville kernel: Call Trace: <IRQ> <ffffffff80167420>{__alloc_pages+796} Sep 7 10:49:12 minersville kernel: <ffffffff80182814>{kmem_getpages+106} <ffffffff80183c16>{fallback_alloc+304}...

LEARN ABOUT MINIX

reboot

REBOOT(8)						      System Manager's Manual							 REBOOT(8)

NAME

       reboot - reboot the system immediately

SYNOPSIS

       reboot [-f]

DESCRIPTION

       Reboot  can  be	used  to  reboot  the  system  after  installing a new kernel.	It does not inform the users, but does log it's actions in
       /usr/adm/wtmp and /usr/adm/authlog.  The system is then rebooted with the reboot(2) systemcall.

       If the -f flag is not given then all processes are sent terminate signals to give them a chance to die peacefully before the reboot() call.

       If the wtmp file exists, reboot logs itself as if it were a shutdown.  This is done to prevent last(1) from talking  about  system-crashes.
       Reboot is registered as is in the authlog file.

       Reboot can only be executed by the super-user.  Any other caller will be refused, either by reboot(8) or by reboot(2).

SEE ALSO

       reboot(2), shutdown(8), halt(8), boot(8).

BUGS

       The  error message's given by reboot are not always useful.  There are several routines that can fail, but which are not fatal for the pro-
       gram.

AUTHOR

       Edvard Tuinder (v892231@si.hhs.NL)

																	 REBOOT(8)