11-29-2013
What is in the logs?
You seem to have memory issue...
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello.
System is a HP Visualize C3600 running X11 and after a power failure machine will not boot (see error messages below)
From what I've read, this may be caused by a corrupted etc/inittab file. Solution suggested on other websites is to boot in single user mode and edit file inittab... (2 Replies)
Discussion started by: westcoast
2 Replies
2. Linux
Hi all
I used a dual boot operating system and it works fine for me. Now , i install a Ati radeon 9250 Agp card on my system and this results in boot failure of fedora 6. The graphics card is working fine with windows XP , i.e i have no compatibility issues.The system also refuses to boot when i... (2 Replies)
Discussion started by: joshighanshyam
2 Replies
3. Solaris
I installed solaris virtually and tried to format the partitions .. I dont know what went wrong, It got rebooted and hangs in the screen "No partitions" and after pressing Enter button it goes to "INT18 boot failure" and hangs there once again . Could any one of you suggest why this has happened... (3 Replies)
Discussion started by: priky
3 Replies
4. Solaris
I have installed Solaris 10 OS in Sun Virtual Box that uses x86 32 bit system. After an abnormal shutdown i'm getting the following message on the console when i try to boot.
SunOS Release 5.10 Version Generic_127128_11 32-bit
Copyright 1983-200 Sun Microsystems, Inc. All rights reserrved.
Use... (3 Replies)
Discussion started by: Sesha
3 Replies
5. SCO
hi
SCO Unix 5.0.6 doesn't boot due to this problem:
not a directory
boot not found
cannot open
stage 1 boot failure: error loading hd (40)/boot
Knows someone howto solve it? (16 Replies)
Discussion started by: ccc
16 Replies
6. Debian
I'm trying to run clusterKnoppix live cd from a couple machines but it only works from one computer. The other three, my toshiba laptop, emachine, and hp machine can't find the filesystem.. the live cd stops booting and gives me a error saying it couldn't find knoppix filesystem and then gives me a... (0 Replies)
Discussion started by: iamhe
0 Replies
7. HP-UX
HPUX running in D-Class (L1000), pretty old HPUX version - hpux 11.00
Attempt 1 -- To boot from normal (primary)
Unable to boot - system complains failure
SYSTEM ALERT System Name : uninitialized DATE : 10/22/2011 Time : 03/41:12 Alert Level 15 = Fatal hardware or configuration... (12 Replies)
Discussion started by: ckwan
12 Replies
8. Solaris
Hi Guys,
I have a small problem with a v445 which I have been informed will only boot with the reconfigure option enabled.
It is attached to HP SAN storage using qla2300 FCA's with a Veritas encapsulated rootvoldg (No Laughing here please) when I try a reboot I get the following error.
... (5 Replies)
Discussion started by: gull04
5 Replies
9. UNIX for Dummies Questions & Answers
hi power went out. next day unix sco wont boot up error code 303. any help appreciated as we are clueless. (11 Replies)
Discussion started by: fredthayer
11 Replies
LEARN ABOUT HPUX
diaglogd
diaglogd(1M) diaglogd(1M)
NAME
diaglogd - Support Tools Manager logging daemon
SYNOPSIS
/usr/sbin/stm/uut/bin/sys/diaglogd
DESCRIPTION
The Support Tools Manager (STM) uses a logging daemon ( diaglogd ) to read diagnostic events from the kernel via diag2 (diagnostic pseudo
driver) and logs them in the system log files.
diaglogd is launched automatically at boot by the STM daemon diagmond. The STM User Interface, xstm , mstm , or cstm , Daemon commands can
also be used to launch the daemon as well as shut it down and view the daemon's activity log.
The log files created by diaglogd can be viewed using the STM utility logtool.
Application Usage
This daemon will be deprecated on new server models. Please use System Management Homepage (see hpsmh(1M)).
WARNINGS
The following message will appear on the system console when the diagnostic logging facility determines that the I/O subsystem has started
logging excessive I/O errors. This message will appear only once and I/O errors will be lost until the diagnostic subsystem can recover
from this condition.
DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility has started receiving excessive
errors from the I/O subsystem. I/O error entries will be lost
until the cause of the excessive I/O logging is corrected.
If the diaglogd daemon is not active, use the Daemon Startup
command in stm to start it. If the diaglogd daemon is active, use
the logtool utility in stm to determine which I/O subsystem is
logging excessive errors.
The following message will appear on the system console when the cause of the excessive I/O error logging is corrected. The total number
of I/O errors that were dropped will be placed in "XX".
DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility is no longer receiving excessive
errors from the I/O subsystem. XX I/O error entries were lost.
OTHER FILES
/dev/diag/diag0 - Series 800 Diagnostic pseudo driver device file
/dev/diag/diag1 - Series 700 Diagnostic pseudo driver device file
/dev/diag/diag2 - Series 700/800 Diagnostic pseudo driver device file
/var/stm/logs/sys/activity_log_diaglogd - Activity log of diaglogd
/var/stm/logs/os/log##.raw - OS system log files
/var/stm/logs/os/log##.raw.cur - Current OS system log file
/var/stm/config/sys/diaglogd.cfg - Diagmond configuration
/var/stm/data/daemon_list - List of daemons installed
/var/stm/data/key_file - OS resource key file
COPYRIGHT
(c) Copyright 1995, Hewlett-Packard Company
ORIGIN
diaglogd was developed by Hewlett-Packard Company.
SEE ALSO
stm(1M), diagmond(1M)
diaglogd(1M)