Remove Server Sleep Mode

Hi All,

Need some help here. Can anyone tell me how to set or which start up script to edit in order not to set the server to sleep mode after a while of inactivity. My Unix server will go to sleep mode and then i always end up with a OK Prompt and have to reset the server. My Server is a V120 running Solaris 9

Thanks
Alvin

take a look into your /etc/power.conf
use: man power.conf

greetings pressy

Hi Press,

Thanks a lot .... :smiley:

If the system is a server, I'd go ahead and disable /etc/rc*/*power init daemon entries as well and then stop the daemon. Keep in mind that patching the system will sometimes re-add the disabled rc scripts and /etc/power.conf.

Cheers,

Keith

Hi,

Can u enlighten me how to do it ?

To start off, create an empty root owned file in / called noautoshutdown:

# touch /noautoshutdown; chmod 400 /noautoshutdown

Just a point of curiosity; what does your /etc/power.conf file look like?

Keith

Hi,

Actually my problem is that the v120 Server that i have is very strange. In fact i have two v120 server. The other is ok. But this particularly is very strange. When i use it during office hour. Is ok. But if i left it overnight. The next day it will be at OK prompt when i connect to it via the LOM port. I have to because i cannot telnet in nor i can ping. Does this cause by the power safe mode or the OS crash ?

Thanks
Alvin

What are you seeing in your messages file (/var/adm/messages). Do you have a dump file in your carsh directory (check location using dumpadm).

Keith

i am at home now ... so cannot check. By the way, i have created a script in a text pad. Afterthat, what should i do in order to make solaris reg it as a executable script?

Thanks again
Alvin

You can make the file you created executable; for example, if the filename you created was named somescript, you'd:

$ chmod 500 somescript

Or you could just run it via shell:

$ sh somescript

Cheers,

Keith

Hi Keith,

Thanks for the prompt reply. So meaning, i use a text pad to create a script. When i save it to a filename such as 'dbora' in /etc/init.d i need to make it executable? Otherwise it won't work? Actually this is a oracle file where by it trigger a dbstart script within the $ORACLE_HOME/bin directory. But of course i have symbolic link to /etc/rc0.d and /etc/rc3.d directory.

BTW ... was thinking of it now. I don think the server crash bcoz i use it the whole day in the office. The only thing is that the server will go into ok prompt the next day i go back to office. I believe it is in certain mode. Not sure sleep mode is good to describe it bcoz the fan is on while i am at the ok prompt. So also don know what happen to the server. The only way is to restart the server.

do the commands below and correlate the times the server goes down wih what you find in the logs ... also, you might want to keep 1 user logged in throughout the night so you can pinpoint closer to the time when the server went down by the time it logs off the user ...

  1. last | grep reboot
  2. grep -i err /var/adm/messages
  3. grep -i warn /var/adm/messages
  4. grep -i notice /var/adm/messages

Hi All,

Thanks for the advice and really appreciate. Actually this is what i need to do everyday. The server did not crashed nor in sleep mode. Now the qns is how do i avoid this.

Everyday when i come to office, i realise that this is what i need to do

  • connect to the server via LOM port using windows hyper terminal (cause cannot telnet)
  • ok prompt appear
  • use #. escape sequence to get the LOM prompt
  • enter this command LOM>console
  • Ok prompt again then type Ok go
  • then the console login apprear
  • then everything back to normal, can telnet can ping

So the qns, how do i avoid that ? thks in advance

Alvin

you cannot telnet or ping the server because it is in suspend mode ... typing go at the ok prompt causes the server to unsuspend ...

your server is at the OK prompt because something put it there ... you need to find out what that something is ... there is no script that would fix your issue without knowing what is causing the problem ... you have to investigate this ... people here have been giving you hints on how to do it but it's really up to you to follow through ...

Hi,

I have check and go through the steps and advice that some kind soul like yourself has done. It just that it does not really solve it. The system still go to sleep mode.

Anyway, here are some of the messages

<Command: last | grep reboot>
reboot system boot Thu Apr 7 10:22
reboot system boot Wed Apr 6 16:18
reboot system boot Wed Apr 6 16:08
reboot system boot Wed Apr 6 13:50
reboot system boot Wed Apr 6 13:20
reboot system boot Wed Apr 6 11:18
reboot system boot Wed Apr 6 10:10
reboot system boot Tue Apr 5 09:44
reboot system boot Mon Apr 4 08:56
reboot system boot Fri Apr 1 12:20
reboot system boot Tue Mar 29 14:01
reboot system boot Tue Mar 29 13:25
reboot system boot Tue Mar 29 09:03
reboot system boot Mon Mar 28 08:59
reboot system boot Thu Mar 24 18:12
reboot system boot Thu Mar 24 11:17
reboot system boot Wed Mar 23 13:34
reboot system boot Mon Mar 21 10:38
reboot system boot Tue Mar 15 12:11
reboot system boot Mon Mar 14 17:11
reboot system boot Fri Mar 11 16:00
reboot system boot Tue Jan 18 09:29
reboot system boot Mon Jan 17 15:03
reboot system boot Mon Dec 6 10:19
reboot system boot Fri Dec 3 16:10
reboot system boot Fri Dec 3 15:06
reboot system boot Fri Dec 3 14:21
reboot system boot Fri Dec 3 13:10
reboot system boot Fri Dec 3 10:37
reboot system boot Thu Dec 2 14:36
reboot system boot Thu Dec 2 14:17

The last reboot is done by me on 7 Apr at around 10am

<Command: grep -i err /var/adm/messages>
Mar 29 14:01:07 sf120-01 unix: [ID 882636 kern.warning] WARNING: interrupt level
15 not serviced
Apr 1 12:20:27 sf120-01 unix: [ID 882636 kern.warning] WARNING: interrupt level
15 not serviced
Apr 6 11:18:11 sf120-01 unix: [ID 882636 kern.warning] WARNING: interrupt level
15 not serviced
Apr 6 12:23:53 sf120-01 /usr/dt/bin/ttsession[2060]: [ID 862433 daemon.error] c
hild (2086) exited due to signal 1
Apr 6 13:20:08 sf120-01 unix: [ID 882636 kern.warning] WARNING: interrupt level
15 not serviced
Apr 6 13:46:29 sf120-01 /usr/dt/bin/ttsession[1863]: [ID 862433 daemon.error] c
hild (1883) exited due to signal 1
Apr 6 13:50:23 sf120-01 unix: [ID 882636 kern.warning] WARNING: interrupt level
15 not serviced
Apr 6 15:00:10 sf120-01 /usr/dt/bin/ttsession[2011]: [ID 862433 daemon.error] c
hild (2535) exited due to signal 1
Apr 6 15:49:21 sf120-01 /usr/dt/bin/ttsession[2830]: [ID 862433 daemon.error] c
hild (2848) exited due to signal 1
Apr 6 16:18:47 sf120-01 unix: [ID 882636 kern.warning] WARNING: interrupt level
15 not serviced
Apr 6 18:11:18 sf120-01 /usr/dt/bin/ttsession[1858]: [ID 862433 daemon.error] c
hild (1886) exited due to signal 1
Apr 7 09:45:01 sf120-01 /usr/dt/bin/ttsession[2109]: [ID 862433 daemon.error] c
hild (2152) exited due to signal 1
Apr 7 10:02:18 sf120-01 /usr/dt/bin/ttsession[2300]: [ID 722431 daemon.error] _
Tt_iceauth::make_auth_cookie(): '/u01/app/oracle/.TTauthority' not writable, au
th entry not added.
Apr 7 10:08:02 sf120-01 /usr/dt/bin/ttsession[2415]: [ID 722431 daemon.error] _
Tt_iceauth::make_auth_cookie(): '/u01/app/oracle/.TTauthority' not writable, au
th entry not added.
Apr 7 10:22:27 sf120-01 unix: [ID 882636 kern.warning] WARNING: interrupt level
15 not serviced
Apr 7 10:24:40 sf120-01 /usr/dt/bin/ttsession[1857]: [ID 722431 daemon.error] _
Tt_iceauth::make_auth_cookie(): '/u01/app/oracle/.TTauthority' not writable, au
th entry not added.
Apr 7 10:33:05 sf120-01 /usr/dt/bin/ttsession[2062]: [ID 848021 daemon.error] _
Tt_iceauth::make_auth_cookie(): timeout in locking authority file '/export/home
/oracle/.TTauthority'
Apr 7 10:35:05 sf120-01 /usr/dt/bin/ttsession[2162]: [ID 848021 daemon.error] _
Tt_iceauth::make_auth_cookie(): timeout in locking authority file '/export/home
/oracle/.TTauthority'
Apr 7 10:36:33 sf120-01 /usr/dt/bin/ttsession[2264]: [ID 722431 daemon.error] _
Tt_iceauth::make_auth_cookie(): '/u01/app/oracle/.TTauthority' not writable, au
th entry not added.
Apr 7 10:46:31 sf120-01 /usr/dt/bin/ttsession[2424]: [ID 848021 daemon.error] _
Tt_iceauth::make_auth_cookie(): timeout in locking authority file '/u01/app/ora
cle/.TTauthority'
Apr 7 10:57:05 sf120-01 /usr/dt/bin/ttsession[2556]: [ID 848021 daemon.error] _
Tt_iceauth::make_auth_cookie(): timeout in locking authority file '/export/home
/oracle/.TTauthority'
Apr 7 11:01:32 sf120-01 /usr/dt/bin/ttsession[2656]: [ID 848021 daemon.error] _
Tt_iceauth::make_auth_cookie(): timeout in locking authority file '/u01/app/ora
cle/.TTauthority'
Apr 7 11:22:10 sf120-01 /usr/dt/bin/ttsession[2787]: [ID 722431 daemon.error] _
Tt_iceauth::make_auth_cookie(): '/u01/app/oracle/.TTauthority' not writable, au
th entry not added.

The last entry is i do not have sufficient right given to one user to the directory

<Command: grep -i warn /var/adm/messages>
Mar 29 14:01:07 sf120-01 unix: [ID 882636 kern.warning] WARNING: interrupt level
15 not serviced
Apr 1 12:20:27 sf120-01 unix: [ID 882636 kern.warning] WARNING: interrupt level
15 not serviced
Apr 6 11:18:11 sf120-01 unix: [ID 882636 kern.warning] WARNING: interrupt level
15 not serviced
Apr 6 13:20:08 sf120-01 unix: [ID 882636 kern.warning] WARNING: interrupt level
15 not serviced
Apr 6 13:50:23 sf120-01 unix: [ID 882636 kern.warning] WARNING: interrupt level
15 not serviced
Apr 6 16:18:47 sf120-01 unix: [ID 882636 kern.warning] WARNING: interrupt level
15 not serviced
Apr 7 10:22:27 sf120-01 unix: [ID 882636 kern.warning] WARNING: interrupt level
15 not serviced

Any useful information ?

<Command: grep -i notice /var/adm/messages>
Mar 28 08:59:37 sf120-01 genunix: [ID 540533 kern.notice] ^MSunOS Release 5.9 Ve
rsion Generic_112233-12 64-bit
Mar 28 08:59:37 sf120-01 genunix: [ID 943905 kern.notice] Copyright 1983-2003 Su
n Microsystems, Inc. All rights reserved.
Mar 29 09:03:34 sf120-01 genunix: [ID 540533 kern.notice] ^MSunOS Release 5.9 Ve
rsion Generic_112233-12 64-bit
Mar 29 09:03:34 sf120-01 genunix: [ID 943905 kern.notice] Copyright 1983-2003 Su
n Microsystems, Inc. All rights reserved.
Mar 29 13:24:39 sf120-01 genunix: [ID 672855 kern.notice] syncing file systems..
.
Mar 29 13:24:39 sf120-01 genunix: [ID 904073 kern.notice] done
Mar 29 13:25:23 sf120-01 genunix: [ID 540533 kern.notice] ^MSunOS Release 5.9 Ve
rsion Generic_112233-12 64-bit
Mar 29 13:25:23 sf120-01 genunix: [ID 943905 kern.notice] Copyright 1983-2003 Su
n Microsystems, Inc. All rights reserved.
Mar 29 13:36:57 sf120-01 genunix: [ID 672855 kern.notice] syncing file systems..
.
Mar 29 13:36:57 sf120-01 genunix: [ID 904073 kern.notice] done
Mar 29 14:00:43 sf120-01 genunix: [ID 540533 kern.notice] ^MSunOS Release 5.9 Ve
rsion Generic_112233-12 64-bit
Mar 29 14:00:43 sf120-01 genunix: [ID 943905 kern.notice] Copyright 1983-2003 Su
n Microsystems, Inc. All rights reserved.
Apr 1 12:20:03 sf120-01 genunix: [ID 540533 kern.notice] ^MSunOS Release 5.9 Ve
rsion Generic_112233-12 64-bit
Apr 1 12:20:03 sf120-01 genunix: [ID 943905 kern.notice] Copyright 1983-2003 Su
n Microsystems, Inc. All rights reserved.
Apr 4 08:55:56 sf120-01 genunix: [ID 540533 kern.notice] ^MSunOS Release 5.9 Ve
rsion Generic_112233-12 64-bit
Apr 4 08:55:56 sf120-01 genunix: [ID 943905 kern.notice] Copyright 1983-2003 Su
n Microsystems, Inc. All rights reserved.
Apr 5 09:44:02 sf120-01 genunix: [ID 540533 kern.notice] ^MSunOS Release 5.9 Ve
rsion Generic_112233-12 64-bit
Apr 5 09:44:02 sf120-01 genunix: [ID 943905 kern.notice] Copyright 1983-2003 Su
n Microsystems, Inc. All rights reserved.
Apr 6 10:09:48 sf120-01 genunix: [ID 540533 kern.notice] ^MSunOS Release 5.9 Ve
rsion Generic_112233-12 64-bit
Apr 6 10:09:48 sf120-01 genunix: [ID 943905 kern.notice] Copyright 1983-2003 Su
n Microsystems, Inc. All rights reserved.
Apr 6 11:13:13 sf120-01 genunix: [ID 672855 kern.notice] syncing file systems..
.
Apr 6 11:13:13 sf120-01 genunix: [ID 904073 kern.notice] done
Apr 6 11:17:47 sf120-01 genunix: [ID 540533 kern.notice] ^MSunOS Release 5.9 Ve
rsion Generic_112233-12 64-bit
Apr 6 11:17:47 sf120-01 genunix: [ID 943905 kern.notice] Copyright 1983-2003 Su
n Microsystems, Inc. All rights reserved.
Apr 6 12:26:10 sf120-01 genunix: [ID 672855 kern.notice] syncing file systems..
.
Apr 6 12:26:10 sf120-01 genunix: [ID 904073 kern.notice] done
Apr 6 13:19:44 sf120-01 genunix: [ID 540533 kern.notice] ^MSunOS Release 5.9 Ve
rsion Generic_112233-12 64-bit
Apr 6 13:19:44 sf120-01 genunix: [ID 943905 kern.notice] Copyright 1983-2003 Su
n Microsystems, Inc. All rights reserved.
Apr 6 13:48:20 sf120-01 genunix: [ID 672855 kern.notice] syncing file systems..
.
Apr 6 13:48:20 sf120-01 genunix: [ID 904073 kern.notice] done
Apr 6 13:49:59 sf120-01 genunix: [ID 540533 kern.notice] ^MSunOS Release 5.9 Ve
rsion Generic_112233-12 64-bit
Apr 6 13:49:59 sf120-01 genunix: [ID 943905 kern.notice] Copyright 1983-2003 Su
n Microsystems, Inc. All rights reserved.
Apr 6 16:01:27 sf120-01 genunix: [ID 672855 kern.notice] syncing file systems..
.
Apr 6 16:01:27 sf120-01 genunix: [ID 904073 kern.notice] done
Apr 6 16:08:20 sf120-01 genunix: [ID 540533 kern.notice] ^MSunOS Release 5.9 Ve
rsion Generic_112233-12 64-bit
Apr 6 16:08:20 sf120-01 genunix: [ID 943905 kern.notice] Copyright 1983-2003 Su
n Microsystems, Inc. All rights reserved.
Apr 6 16:11:20 sf120-01 genunix: [ID 672855 kern.notice] syncing file systems..
.
Apr 6 16:11:20 sf120-01 genunix: [ID 904073 kern.notice] done
Apr 6 16:18:23 sf120-01 genunix: [ID 540533 kern.notice] ^MSunOS Release 5.9 Ve
rsion Generic_112233-12 64-bit
Apr 6 16:18:23 sf120-01 genunix: [ID 943905 kern.notice] Copyright 1983-2003 Su
n Microsystems, Inc. All rights reserved.
Apr 7 10:12:52 sf120-01 genunix: [ID 672855 kern.notice] syncing file systems..
.
Apr 7 10:12:52 sf120-01 genunix: [ID 904073 kern.notice] done
Apr 7 10:22:03 sf120-01 genunix: [ID 540533 kern.notice] ^MSunOS Release 5.9 Ve
rsion Generic_112233-12 64-bit
Apr 7 10:22:03 sf120-01 genunix: [ID 943905 kern.notice] Copyright 1983-2003 Su
n Microsystems, Inc. All rights reserved.

Does it ring a bell ??

Thanks again
Alvin

hi kduffin,

As requested, this is how power.conf look like

# 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
# Auto-Shutdown Idle(min) Start/Finish(hh:mm) Behavior
autoshutdown 30 9:00 9:00 noshutdown
statefile //.CPR

Enjoy
Alvin

if you look at your last output and then look at the messages log ... there are several instances where warnings were logged around the time the reboots were happening ... you might want to look at processes running at that time and see what they're doing to your system ...

reboot system boot Wed Apr 6 16:18
Apr 6 16:18:47 sf120-01 unix: [ID 882636 kern.warning] WARNING: interrupt level 15 not serviced

reboot system boot Wed Apr 6 13:50
Apr 6 13:50:23 sf120-01 unix: [ID 882636 kern.warning] WARNING: interrupt level 15 not serviced