10-21-2008
no worries.
what are you intentions for this??? the reason i ask is if you are simply trying to monitor these devices... use opennms or openview. these can help spot when a server goes down as a result of a panic/fault or a human initiated reboot/shutdown. but just because a panic happens does not mean the system will reboot. just recently we had a system reboot itself (it was seen on OV). the system did not panic. in fact it was a kern.info. and then the system came down on signal 15 (a simple exit and no core dump). on another box we actually rebooted it. again, signal 15. so i think it might be hard to differentiate between a human reboot and a fault induced reboot. also, if the signal permits, a core dump will be generated giving you a good idea that the system just crashed.
also, i believe a proper shutdown should terminate syslogd correctly. this will say its coming down on signal 15. if you look in your logs and find the output of `uname -a` in the log files and a gap in your log files... most likely it was a crash/reboot or something a long those lines.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I couldnt get my hands on my solaris 2.6 cd soo i used solaris 7 cd to boot to single user mode. I typed
boot cdrom -s
it bought me to my root prompt , but when i typed fsck.....nothing happened. It was as though it couldnt go ahead with fscking. it just bought up the prompt again,... (1 Reply)
Discussion started by: lealyz
1 Replies
2. Solaris
Hi,
I've just bought an Ultra 60 running solaris 9 (or so I've been led to believe). When I start up, it looks for a (presumably) domain/network to hook up to and the following messages are displayed:
Boot device: net file and args:
Network link setup failed
Please check cable and try... (3 Replies)
Discussion started by: alarmcall
3 Replies
3. Solaris
When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error.
cannot find mis/krtld
boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies
4. Solaris
Hi all ,
I am trying to isntallsolaris 10 using a DVD , But when i try to boot from the OB Prompt i am getting this error :
Rebooting with command: boot cdrom -install
Boot device: /pci@1f,700000/pci@0/pci@1/pci@0/ide@1f/cdrom@0,0:f File and args: -install
Can't read disk label.
Can't open... (2 Replies)
Discussion started by: ppass
2 Replies
5. Shell Programming and Scripting
I am running a daemon program that sends texts via a connected mobile phone. I run this daemon via CLI, and it loops a few commands (checking to see if there are any new texts).
It runs perfectly, the problem is, when I leave this to run on my Ubuntu Desktop, and come back to it hours later it... (2 Replies)
Discussion started by: daydreamer
2 Replies
6. Solaris
My current situation is like this, I have a v440 connected to a netapp central storage 3140 via fiber channel, my OS and oracle is installed in the internal drive of the v440.
What I would like to do is to advertise another LUN in netapp to the v440 and let my v440 boot from it so I can start... (3 Replies)
Discussion started by: q8devilish
3 Replies
7. Solaris
I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD... (9 Replies)
Discussion started by: hemalsid
9 Replies
8. Solaris
Hi,
I am running into a some problems creating a dual boot system of 2 solaris instances using ZFS file system and I was wondering if someone can help me out.
First some back ground. I have been asked to change the file system of our server from UFS to ZFS. Currently we are using Solaris... (3 Replies)
Discussion started by: estammis
3 Replies
9. Solaris
Hello Everyone,
I'm new to Solaris, less than a week to give an idea how green I am.:eek: Although new to UNIX, I've been running Linux (i.e. OpenSUSE, Ultimate Edition, Arch, and obviously Ubuntu) for many years, so, I decided to put Solaris 11 on my 12 core opteron. I had a bit of difficulty... (23 Replies)
Discussion started by: Nostradamus1973
23 Replies
10. Solaris
Hello,
I have a problem with my machine that won't boot properly.
The story is that I installed a software called apcupsd, which is a control application for my APC battery UPS. I have used version 3.14.10 earlier, but as part of restoring my previously crashed os harddrive I wanted to... (18 Replies)
Discussion started by: Zorken
18 Replies
LEARN ABOUT ULTRIX
savecore
savecore(8) System Manager's Manual savecore(8)
Name
savecore - save a core dump of the operating system
Syntax
/etc/savecore [ options ] dirname [ system ] [ corename ]
Description
The command is meant to be called near the end of the file. The command saves the core dump of the system (assuming one was made) and
writes a reboot message in the shutdown log.
The command checks the core dump to be certain it corresponds with the current running ULTRIX. If it does, it saves the core image in the
file dirname/vmcore.n and saves the namelist in the file dirname/vmunix.n. The trailing .n in the pathnames is replaced by a number which
increments each time is run in that directory.
After saving the core and namelist images, will save the error logger buffer into a predetermined file. The error logger buffer contains
information about why the crash occurred. After completes, the daemon will extract the error logger file and translate its contents into a
form familiar to the program.
Before writes out a core image, it reads a number from the file dirname/minfree. If there are fewer free blocks on the filesystem that
contains dirname than the number obtained from the file, a core dump is not done. If the file does not exist, savecore always writes out
the core file (assuming that a core dump was taken).
The command also writes a reboot message in the shut down log. If the system crashed as a result of a panic, also records the panic string
in the shut down log.
For partial crash dumps, creates a sparse core image file in dirname/vmcore.n. If this sparse core image file is copied or moved to
another location, the file expands to its true size which can take too much file system space. Hence, to copy or move sparse core image
files, you must use the command. The command has a conversion option to create sparse output files.
Options
-c Clears the core dump. This option is useful when the core dump is corrupted in a way that will not allow to save it safely. Use the
option with caution, because once it clears the core dump, the core dump cannot be retrieved.
-d dumpdev dumplo
Specifies the dump device and the dump offset when running on a system image other than the currently running system image. The pro-
gram assumes that the running system image is and it reads the dump device and dump device offset are different in the system image
that crashed, the option provides the correct dump device and dump device offset.
-e Saves only the error logger buffer into a file. If used, core or namelist images are not saved.
-f corename
Takes the i corefile name as the file from which to extract the the crash dump data instead of the default dump device. This option
is used only for diskless workstations.
If the core dump was from a system other than /vmunix, the name of that system must be supplied as system. The program assumes that the
running image is
After successful completion, the core dump is cleared. Also, a message is written in the file which tells whether the dump succeeded or
failed.
Files
Shut down log
Current running ULTRIX system
See Also
dd(1), uerf(8)
savecore(8)