Sponsored Content
Operating Systems AIX System rebooted itself but errpt did not catch Post 302973987 by Scott on Tuesday 24th of May 2016 03:35:30 PM
Old 05-24-2016
Could a power outage not explain the lack of logging in the matter?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Sun Machine Rebooted

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)
Discussion started by: DPAI
6 Replies

2. UNIX for Dummies Questions & Answers

How to identify who rebooted the linux server

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)
Discussion started by: bache_gowda
1 Replies

3. Shell Programming and Scripting

how can I know when system last rebooted?

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)
Discussion started by: nokia1100
3 Replies

4. Solaris

server rebooted by user

Hi, how can i know who has rebooted the server? even last command is not displaying the user, wheather any way to track the user. (2 Replies)
Discussion started by: manoj.solaris
2 Replies

5. Solaris

rebooted alone

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)
Discussion started by: murad.jaber
3 Replies

6. HP-UX

How can we know that the server was rebooted by which user in hp unix

Hi , Plz some one can help me ... How can we know that the server was rebooted by which user in hp unix and linux. Regards Venkata Jeevan (1 Reply)
Discussion started by: jeevanbv
1 Replies

7. AIX

server rebooted

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)
Discussion started by: manoj.solaris
5 Replies

8. Solaris

Checking Who rebooted a Host

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)
Discussion started by: Amr1ta
2 Replies

9. Linux

Rebooted suddenly

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)
Discussion started by: Rajesh_Apple
1 Replies

10. Red Hat

Server rebooted.

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
POWERD(8)						      System Manager's Manual							 POWERD(8)

NAME
powerd - UPS monitoring daemon SYNOPSIS
/sbin/powerd [tty] DESCRIPTION
powerd monitors the serial port connected to an UPS device and will perform an unattended shutdown of the system if the UPS is on battery longer than a specified number of minutes. powerd needs to watch a tty with modem control properties. Please refer to the powerd documen- tation for further information. powerd also has the capabilities of notifying other clients on the network that may have a UPS but not be connected to the serial line that there is a power outage, and id configured through the powerd.conf file CONFIGURATION FILE
Here is the configuration format: Lines beginning with '#' are ignored. MODE <mode> specifies the mode the UPS should be in. Valid arguements are MONITOR and PEER MONITOR being the mode to actually watch a UPS serial port, and PEER being to listen for a connection from a machine in MONITOR mode MONITOR <device> Specifies which device to monitor while in MONITOR mode. Specify an actual device file. Example: /dev/ttyS0 POWERFAIL <line> <high|low> Specifies which lines on the serial ports indicate that the power is out. Valid arguements are DCD, CAR, CTS, and RNG. Also specify if the line being HIGH or LOW indicates a power failure. Since most people may not know this arguement, Please use the enclosed upsdetect program to automatically find this line. NOTIFY <hostname[:port]> <password> Specified in MONITOR mode to notify a client running in PEER mode. Specify the hostname of the machine, and optional port the daemon is running on, And the password as specified by their LISTEN command. See below for more details. LISTEN <hostname> <password> Specified in PEER mode, specifies a hostname that is allowed to notify us of when the power is out, and the password they shall give us to authenticate themselves. The 2 passwords should match on the MONITOR mode machines NOTIFY password, and the PEER modes LISTEN password. LISTENPORT <port> Specified in PEER mode, specifies the port that powerd should listen on. If you use this arguement, powerd shall not default to using port 532, and the machine in MONITOR mode must specify the port you use in their NOTIFY command. DELAY <delayinseconds> Specifies how many seconds before notifying init of a power outage. Note that this doesnt mean that the system will shut down in that many seconds, as it depends on how init is configured. Init usually issues a 2 min shutdown. USER <username> Specifies which username to drop to from root. The program will reobtain root access only when it needs to, Like when notifying init that the power is out. This is simply a security feature, and not needed for powerd to operate. Note: powerd must still be run ini- tially as root. It will then drop to the user if, and only if, a username is specified. ARGUMENTS
None: Please use the configuration file /etc/powerd.conf which can be generated with detectups. See detectups(8) for more information FILES
/etc/powerd.conf powerd configuration file /etc/powerstatus indicates line power status /etc/inittab init is what actually issues the shutdown SEE ALSO
powerd(8), shutdown(8), wall(1), init(8), inittab(5). AUTHOR
James Brents <James@nistix.com> (with parts of this man page borrowed from all over the Linux community) POWERD(8)
All times are GMT -4. The time now is 11:12 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy