server sits at ok prompt from time to time 6

[sm42]

Every few days or so I have a test solris9 server that sits at the ok prompt.

Is this server on some sort of energy saving mission?

How can I change this?

Thanks.

 

[KenCunningham]

I wonder whether 'Lights Out Management' (LOM) has anything to do with this? Sorry, I've never encountered it, but if you do a keyword search in this forum for LOM, you'll get plenty of hits that might give you a clue as to what's happening.

 

[Annihilannic]

If you're running running powerd(1M) and your system is idle overnight I believe the default action is to shut it down. Not a good idea for a server obviously!

Annihilannic.

 

[sm42]

powerd is not running

 

[huebs]

Do you have a terminal concentrator/server connected to serial port A of your server? I sometimes caught a break signal when switching off/on our good old Annex or plugging cables.

 

[sm42]

I do have a serial cable connected to the server.
This cable has come out from time to time.

 

[sm42]

Just pulled out the serial cable and the server is still up.

 

[tuka]

What type of server?
What are you using to access the console (RSC,SC,etc)?
/etc/default/kbd file show how to disable "break"

Sunsolve infodoc 27538 describe some areas to look in
while at the ok prompt

Can you type "resume" and the system actually continue?

After a reboot does the messages file indicate any reason

is the eeprom set to auto-boot? false?

 

[cndcadams]

another option is to run the last command and compare it to your var/adm/messages file to see if the system shutdown co-insides with login times of specific person.

If there is a specific person logging on at or around system shutdown see how they are exiting there login as sometimes the terminal servers keystocks can act like a stop-A which will put you at the ok prompt.

Also check to see if there are any error messages in /var/adm/messages.* or is the system going down on signal 15 which usually means someone is telling it to shutdown.


Thanks

CA

 

[marrow]

could check you root cronjobs and check who's been on root via "last" as cndcadams recommends. Look at /etc/power.conf should be
autopm default
# Auto-Shutdown Idle(min) Start/Finish(hh:mm) Behavior
autoshutdown 30 9:00 9:00 noshutdown
statefile /var/.CPR

 

[sm42]

Thanks gang.

Will get back soon.

 

[sm42]

auto-boot?=true

reboot system boot Mon Sep 19 14:08

Still can't work this one out.

ls -la /etc/power.conf
/etc/power.conf: No such file or directory

 

[marrow]

Hello sm42 - Did you ever look at "last" command as cndcadams suggested to see if any users on system at time of close down? Also how about creating the /etc/power.conf file, every Solaris 9 system I have, has this file. (Owned by root)
-rw-r--r-- 1 root sys 538 Nov 16 2004 /etc/power.conf

# Copyright (c) 1996 - 2001 by Sun Microsystems, Inc.
# All rights reserved.
#
#pragma ident "@(#)power.conf 1.16 01/03/19 SMI"
#
# Power Management Configuration File
#
# This entry keeps removable media from being powered down unless the
# console framebuffer and monitor are powered down
# (See removable-media(9P))

device-dependency-property removable-media /dev/fb


# autopm default
autopm disable
# Auto-Shutdown Idle(min) Start/Finish(hh:mm) Behavior
autoshutdown 30 9:00 9:00 noshutdown

 

[marrow]

Also check /etc/rc2.d/S85power

 

[sm42]

This is output from last command

reboot system boot Mon Sep 19 14:08

 

[sm42]

created /etc/power.conf .
thanks marrow
will see what happens

 

[gkout]

Your serial cables might cause the shutdown of the server. If you haven't turned the key of the server to the lock position if u unplug the serial cable frrom the annex concenrator, or whatever this will cause the server to go to ok, just check that ur key is turned to the "lock" position.
Hope this helps.

 

[kHz]

This is indirectly related to the ok prompt.

If you use Windows XP and hyperterm to connect to the serial for for SC access you may encounter the server reseting if you close your hyperterm connection while it is connected serially. Disconnect the serial connection BEFORE closing the hyperterm session.

This has happened to me a few times. The latest was on Saturday while doing some work and the hyperterm session was disconnected while connected to the SC, which caused the server to drop to the boot prom (ok).

 

[gkout]

KHz read above...If u turn the key to the lock position no matter what u do the server will stay up...just try it

 

[sm42]

Thanks Khz and gkout.
Will try your suggestions.

server is still going to ok prompt.
Will unplug the serial cable.


The server is an Ultra 5.
Can't remember seeing the key lock position, will check.

Thanks.