topic server booting problem in Operating System - HP-UX

server booting problem

Noble Sebastian — Fri, 29 Dec 2006 02:41:15 GMT

Hi ,all

my L class server starting time ,That is comeing single user mode , then i puting init 3 then it start multi user mode but now i given init 3 , now it is not starting

any one can help

Re: server booting problem

Peter Godron — Fri, 29 Dec 2006 03:03:37 GMT

Hi,
have you changed anything in /etc/inittab ?

You would need this file correct to change init level. If it missing or corrupted that machine would remain at single user mode.

Re: server booting problem

Noble Sebastian — Fri, 29 Dec 2006 04:19:56 GMT

Hi peter
i never change /etc/inittab value
how it come mutiuser mode init 3 is not working ...

Re: server booting problem

Mridul Shrivastava — Fri, 29 Dec 2006 04:26:51 GMT

Hi Noble,

Could you please post the error message when you execute init 3....

regards

Re: server booting problem

rariasn — Fri, 29 Dec 2006 05:07:10 GMT

Hi Noble,

# man init

WARNINGS
Boot init assumes that processes and descendants of processes spawned by boot init remain in the same process group that boot init originally created for them. When changing init states, special care should be taken with processes that change their process group affiliation, such as csh and ksh.

One particular scenario that often causes confusing behavior can occur when a child csh or ksh is started by a login well. When boot init is asked to change to a run level that would cause the original login shell to be killed, the shell's descendant csh or ksh process does not receive a hangup signal since it has changed its process group affiliation and is no longer affiliated with the process group of the original shell. Boot init cannot kill this csh or ksh process (or any of its children).

If a getty process is later started on the same tty as this previous shell, the result may be two processes (the getty and the job control shell) competing for input on the tty.

To avoid problems such as this, always be sure to manually kill any job control shells that should not be running after changing init states. Also, always be sure that user init is invoked from the lowest level (login) shell when changing to an init state that may cause your login shell to be killed.

# cd /
# reboot -r

rgs,