10-13-2010
The exit code 96 in SMF means there is some configuration error (SMF_EXIT_ERR_CONFIG).
This error might be the fact, that an attempt is made to start DCS (a daemon for dynamic reconfiguration), which is only supported on the larger enterprise class servers, but not the V240.
The watchdog reset could also be caused by an architecture mismatch. Is it possible, that on the boot disks there is a image taken from a DR-capable server?
This User Gave Thanks to hergp For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hey guys,
I had a Sunfire V240 with Solaris 10 preinstalled but replaced the original 2 -73g harddrives with 2 146g drives now I'm trying to install Solaris 9 which I want to use not 10.
Now I keep getting this error:
Rebooting with command: boot
Boot device: disk0:a File and args:
The... (2 Replies)
Discussion started by: kingdbag
2 Replies
2. UNIX for Dummies Questions & Answers
Hello all,
Does anyone know how to reset the ALOM password for Sun fire V240 or the OBP password? I was given a V240 without any password or hard drive.
Thanks (3 Replies)
Discussion started by: larryase
3 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I trying to jumpstart SunFire V240 Solaris 10, 2006_01. All the jumpstart files on jumpstart install and boot server are ok (tested on another machine Sun Ultra 10). But this system comes out with: "The file just loaded does not appear to be executable." after "boot net - install" and setting... (0 Replies)
Discussion started by: jump
0 Replies
4. Solaris
Hi,
we are having one sun v240 server, now this server is performing very slow,
checked using top, iostat and vmstat commands, output is looking normal, but the performance is very slow and generating more traffic in network,
how can we resolve this.
Regards
RJS (5 Replies)
Discussion started by: rajasekg
5 Replies
5. Hardware
I recently acquired a sunfire v240 and I'm trying to get into it so I can install linux on it. Right now I'm still trying to get a monitor connected so I can do this.
I've tried connecting to it with a crossover cable to my laptop (vista and linux equipped). I was able to get a connection... (2 Replies)
Discussion started by: QuadRunner750
2 Replies
6. Solaris
hallo anybody know how to set alom mail alerty server with yahoomail ?
thank u?where i can find mail server address for yahoomail?thank (1 Reply)
Discussion started by: yanto85
1 Replies
7. Solaris
after shutting down the server and the ILOM/ALOM,
its date seems to go back to 1977..rather than current date..
problem with battery on ILOM/ALOM ??:( (1 Reply)
Discussion started by: ppchu99
1 Replies
8. Solaris
had a v240 pre-configured and running the OS and alom, for about 3 months good, no issues.
All of sudden, I can't see the IP address of the OS and the alom..
There is nothing wrong with thet network...
I suspect the ALOM crashed and/or something bad happened to it..
Is there anyway... (3 Replies)
Discussion started by: ppchu99
3 Replies
9. Solaris
Hey guys,
I recently replaced the heatsinks on two different V240's. Repasted and replaced them myself. After attempting to bring them back up, there was no display coming from the KVM. I figured it was a matter of environment in OBP and attempted to get to the OK prompt from the... (20 Replies)
Discussion started by: DanielSluder
20 Replies
10. Solaris
Hi Guys,
I have performed OBP & ALOM upgrade on V240 system. One of my system, running Solaris 10, having issue to identify flash rom during ALOM 1.6.10 version upgrade (OBP upgraded to latest one).
May I know what the reason of this error and how can I fix it so I can upgrade ALOM using... (0 Replies)
Discussion started by: myrpthidesis
0 Replies
LEARN ABOUT DEBIAN
wd_keepalive
WD_KEEPALIVE(8) System Manager's Manual WD_KEEPALIVE(8)
NAME
wd_keepalive - a simplified software watchdog daemon
SYNOPSIS
wd_keepalive [-c filename|--config-file filename]
DESCRIPTION
This is a simplified version of the watchdog daemon. If configured so it only opens
.IR /dev/watchdog , and keeps writing to it often enough to keep the kernel from resetting, at least once per minute. Each write delays
the reboot time another minute. After a minute of inactivity the watchdog hardware will cause a reset. In the case of the software watchdog
the ability to reboot will depend on the state of the machines and interrupts.
The wd_keepalive daemon can be stopped without causing a reboot if the device /dev/watchdog is closed correctly, unless your kernel is com-
piled with the CONFIG_WATCHDOG_NOWAYOUT option enabled.
Under high system load wd_keepalive might be swapped out of memory and may fail to make it back in in time. Under these circumstances the
Linux kernel will reset the machine. To make sure you won't get unnecessary reboots make sure you have the variable realtime set to yes in
the configuration file watchdog.conf. This adds real time support to wd_keepalive: it will lock itself into memory and there should be no
problem even under the highest of loads.
On system running out of memory the kernel will try to free enough memory by killing process. The wd_keepalive daemon itself is exempted
from this so-called out-of-memory killer.
OPTIONS
Available command line options are the following:
-c config-file, --config-file config-file
Use config-file as the configuration file instead of the default /etc/watchdog.conf.
FILES
/dev/watchdog
The watchdog device.
/var/run/wd_keepalive.pid
The pid file of the running wd_keepalive.
SEE ALSO
watchdog.conf(5)
watchdog(8)
4th Berkeley Distribution January 2005 WD_KEEPALIVE(8)