Solaris

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 ...