Sponsored Content
Operating Systems Linux SuSE How to check Server reboot reason Post 302282266 by Neo on Friday 30th of January 2009 12:09:51 PM
Old 01-30-2009
The trouble is that when a server has problems, it often is not able to write to a log file.

There are a number of logs in /var/log , including

Code:
/var/log/boot

or

Code:
/var/log/boot.log

Did you search there or the other syslog files?
 

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... (1 Reply)
Discussion started by: Sushesh
1 Replies

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

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... (1 Reply)
Discussion started by: matrixmadhan
1 Replies

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 (1 Reply)
Discussion started by: giriplug
1 Replies

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

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,... (1 Reply)
Discussion started by: KailasB
1 Replies

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... (24 Replies)
Discussion started by: VenkatReddy786
24 Replies

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 (6 Replies)
Discussion started by: gema.utama
6 Replies

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}... (3 Replies)
Discussion started by: admin_db
3 Replies
nislog(1M)						  System Administration Commands						nislog(1M)

NAME
nislog - display the contents of the NIS+ transaction log SYNOPSIS
/usr/sbin/nislog [-h num | -t num] [-v] [directory...] DESCRIPTION
nislog displays the contents of the NIS+ server transaction log on the standard output. This command can be used to track changes in the namespace. The /var/nis/trans.log file contains the transaction log maintained by the NIS+ server. When updates occur, they are logged to this file and then propagated to replicas as log transactions. When the log is checkpointed, updates that have been propagated to the replicas are removed. The nislog command can only be run on an NIS+ server by superuser. It displays the log entries for that server only. If directory is not specified, the entire log is searched. Otherwise, only those logs entries that correspond to the specified directories are displayed. OPTIONS
-h num Display num transactions from the ``head'' of the log. If the numeric parameter is 0, only the log header is displayed. -t num Display num transactions from the ``tail'' of the log. If the numeric parameter is 0, only the log header is displayed. -v Verbose mode. FILES
/var/nis/trans.log transaction log ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWnisu | +-----------------------------+-----------------------------+ SEE ALSO
nis+(1), rpc.nisd(1M), nisfiles(4), attributes(5) NOTES
NIS+ might not be supported in future releases of the SolarisTM Operating Environment. Tools to aid the migration from NIS+ to LDAP are available in the Solaris 9 operating environment. For more information, visit http://www.sun.com/directory/nisplus/transition.html. SunOS 5.10 12 Dec 2001 nislog(1M)
All times are GMT -4. The time now is 03:00 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy