01-28-2009
Reboots are documented in the errpt. You can be lucky and find with errpt -a which uid issued the reboot.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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
2. Solaris
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
3. HP-UX
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
4. AIX
Is there such location or command to know how many times did you reboot your server in that particular day?in AIX. (3 Replies)
Discussion started by: kenshinhimura
3 Replies
5. Linux
supermicro(dual core) server getting rebooted after "decompressing the kernel;booting the kernel" message comes.
I tried giving acpi=off to the kernel command line but same problem.It shows everything ok and no problem with memory and processors and power supplies.Wt could be the reason?
It has... (1 Reply)
Discussion started by: pankajd
1 Replies
6. Solaris
In Windows we can check the event viewer for entries 6005,6006,6009 to confirm the system down times, as in when it got down and when it came back up. Is there some similar log files in Solaris/RHEL that I can check the timings and who or what caused the system reboot. I am an absolute newbie. Need... (4 Replies)
Discussion started by: lubu
4 Replies
7. Red Hat
I am trying to figure out what might causing Production server unexpectedly reboot during last few months ..
Is auto reboot is set , I can check it is not set during the kernel panic but are they any other parameters which I am missing .
-bash-2.05b$ uname -a
Linux PD1011... (4 Replies)
Discussion started by: dba1981
4 Replies
8. Red Hat
Hi
One of our server is showing the uptime 0hr 5mints
there is no log in /var/log/messages
there is no log in command "last"
kernel version is 2.4.9 (RH2.1 AS)
What could be the reason for this. is this issue is related to uptime counter reached max
how to verify this.
Best Regards
KVK (4 Replies)
Discussion started by: venikathir
4 Replies
9. Red Hat
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
10. UNIX for Dummies Questions & Answers
I have been mounting a directory to share with a windows pc. If i reboot the AIX box the mount goes away. How can i make the mount permanent? Here is the command I use to make the mount
exportfs -i -o root=<servername> /path (1 Reply)
Discussion started by: fierfek
1 Replies
statd(1M) System Administration Commands statd(1M)
NAME
statd - network status monitor
SYNOPSIS
/usr/lib/nfs/statd
DESCRIPTION
statd is an intermediate version of the status monitor. It interacts with lockd(1M) to provide the crash and recovery functions for the
locking services on NFS. statd keeps track of the clients with processes which hold locks on a server. When the server reboots after a
crash, statd sends a message to the statd on each client indicating that the server has rebooted. The client statd processes then inform
the lockd on the client that the server has rebooted. The client lockd then attempts to reclaim the lock(s) from the server.
statd on the client host also informs the statd on the server(s) holding locks for the client when the client has rebooted. In this case,
the statd on the server informs its lockd that all locks held by the rebooting client should be released, allowing other processes to lock
those files.
lockd is started by automountd(1M), mount_nfs(1M), and share(1M) if NFS automounts are needed.
FILES
/var/statmon/sm lists hosts and network addresses to be contacted after a reboot
/var/statmon/sm.bak lists hosts and network addresses that could not be contacted after last reboot
/var/statmon/state includes a number which changes during a reboot
/usr/include/rpcsvc/sm_inter.x contains the rpcgen source code for the interface services provided by the statd daemon.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWnfscu |
+-----------------------------+-----------------------------+
SEE ALSO
svcs(1), automountd(1M), lockd(1M), mount_nfs(1M), share(1M), svcadm(1M), attributes(5), smf(5)
System Administration Guide: IP Services
NOTES
The crash of a server is only detected upon its recovery.
The statd service is managed by the service management facility, smf(5), under the service identifier:
svc:/network/nfs/status
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser-
vice's status can be queried using the svcs(1) command.
If it is disabled, it will be enabled by mount_nfs(1M), share_nfs(1M), and automountd(1M) unless its application/auto_enable prop-
erty is set to false.
SunOS 5.10 18 Nov 2004 statd(1M)