root@PRD /etc/oracle/oprocd> ls -ltra
-rw-r--r-- 1 root system 304 May 22 10:05 prd.oprocd.log.2016-05-22-10:10:59
drwxrwx--- 2 root system 256 May 22 10:11 stop
-rw-r--r-- 1 root system 175 May 22 10:11 prd.oprocd.log
-rwxr--r-- 1 root system 512 May 22 10:11 prd.oprocd.lgl
drwxrwx--- 2 root system 256 May 22 10:11 fatal
drwxrwx--- 2 root system 256 May 22 10:11 check
root@PRD /etc/oracle/oprocd> cat prd.oprocd.log
May 22 10:11:00.148 | INF | monitoring started with timeout(1000), margin(500), skewTimeout(125)
May 22 10:11:00.194 | INF | fatal mode startup, setting process to fatal mode
root@PRD /etc/oracle/oprocd>
root@PRD /etc/oracle/oprocd>
root@PRD /etc/oracle/oprocd> cat prd.oprocd.log.2016-05-22-10:10:59
May 22 08:39:39.546 | INF | monitoring started with timeout(1000), margin(500), skewTimeout(125)
May 22 08:39:39.628 | INF | fatal mode startup, setting process to fatal mode
May 22 10:05:26.457 | INF | shutting down from client request
May 22 10:05:26.457 | INF | exiting current process in NORMAL mode
But, shouldn't the timestamp on the RAC logs be before the reboot, the timestamps certainly are after the reboot
if you notice AIX logs: reboot happened at 8:38 where as the RAC log is 10:11
Hi ,
My Sun Machine Rebooted by itself 2 days back . Its running fine now , But i wanted to find out wat caused it to reboot...
This is wat the var/adm/messages show .
Kern.notice:- System booting after fatal error FATAL...
Wat causes this message ...
And wat tasks should i do to ensure it... (6 Replies)
Hi All,
Since server is located at remote place so how to identify which user rebooted the server. Is there any way to identify the user.
Thanks in advance,
Reg,
Bache Gowda (1 Reply)
hi
anyone one here for helping me? plzzzzzzzzzzzzz
I would like to know how Licensing information such as the operating system revision level and license restrictions in terms of user numbers can be seen?
and When was the system last rebooted can also be seen? (3 Replies)
dear all
Iam unix administrator and yesterday the server rebooted alone and when i check the messages i find the below errors can you help me (3 Replies)
Hi,
I want to know how to find out which user has rebooted the server? I have used last command but it is not giving username though it is showing below output
reboot --------------- date
Regards,
Manoj (5 Replies)
Hi,
Not sure if this was asked in a tread already(searched but did not find anything :( )
I want to know who rebooted a system without reading through allot of /var/adm/messages
I know the command last will show me when the system was rebooted
*user* *Login Protocol* *IP address* ... (2 Replies)
Hi Team,
server rebooted happen sunddely, i check all the log files but ..i didn't find any reason...kindly share your's ideas with me...
Thanks in advace
Rajesh_Apple...:b: (1 Reply)
Hi,
Yesterday one of Red Hat Server 4.2 got rebooted.
I have checked /var/log/messages, but does not find out any serious issue related to peformance / hardware issue.
how to find out why server was rebooted? (1 Reply)
Discussion started by: manoj.solaris
1 Replies
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)