HP-UX startup message!

[troll_1]

hello all!
when my hp L2000 system startup and goes to the start application section, it says:configuring unconfigured software filesets...???and wait for about 10 miniutes, is it ok?

two of my servises in /sbin/rc2.d , named: S360xxx & S950XXX not started when system started, but in /var/adm/rc.log, it says the services has successfully started, why? the scipts is right, for when I excute /sbin/rc2.d/S360xxxx start, it runs ok!

thanks a lot!

[Michael Tully]

yes that's okay, your system is configuring some un-configured filesets. Did you do some patching or installing additional products?

I've seen a few times where some services have indicated that they have started, but didn't. Unless you can afford another reboot to make sure, make a note for next time this system boots.

Regards
Michael
"When I have trouble spelling, it's called fat finger syndrome"

[Christian Gebhardt]

Hi

The startup time depends on the applications you'll start at boot time, but 10 minutes seems to be ok.

"OK" in the rc.log means that return-code of the script is 0.

A possible problem is that you misses Environment settings in the startup script and you have set this environment in the loginshell.

Do you have an example of the startupscript ??

Chris

[Steven E. Protter]

All I would add is that you might want to test the services.

nslookup with the hostname being served by the dns(named) daemon.

ps -ef | grep named

You are porbably okay. There is no relationship to the configuring unconfigured filesets message and the services message.

The filesets message happens every time the system starts, and its somewhat analogous to Windows doing setup on a recently installed patch or program after a forced restart.

SEP

[Balaji N]

hi,

1. some previously installed software are not configured. and hence the system is trying to configure the same. does this happen everytime you reboot?

swlist -l fileset -a state | grep installed.

there should be no output for this and all the sw filesets should be in configured set. if not, do an swconfigure manually look for any errors in sw logs.

2. as others have pointed out, the problem is most probably with your environment variables and related configurations files in /etc/rc.config.d/. check if there are any errors in them. also, see that there are no backup copies of configuration files in /etc/rc.config.d/ directory.

my 2 paise.
-balaji

[troll_1]

First thank all for your replies!
Following is an example of my scripts!,please see what's wrong with it,why it not started! my 9000 system can't reboot arbitary for its services is important!thanks!
#!/sbin/sh
case $1 in
start)
/usr/local/sbin/sshd2 &
;;
stop)
ps -ef |grep sshd|grep -v grep|awk '{print $2}'|xargs kill
;;
esac

[Christian Gebhardt]

Hi

I had the same problem especially with sshd2 from openssh

try this:

...
case $1 in
start)
/usr/local/sbin/sshd2 &
sleep 90
;;
...

I don't know why, but it works

By the way: with your stop-command you 'll kill all sshd, so you will disconnect all users, especially yourself if you are connected via ssh

I append my sshd start-script so check what you need from it

Chris

[Bill Hassell · Accepted solution]

Your startup script is not very complete. There are always 4 (not 2) possible parameters. The other two are the start/stop messages which are important to debug problems. There is a template which is very useful in designing start/stop scripts found in /sbin/init.d (which is where the 'real' script lives). The /sbin/rc?.d directories should just contain links.

The log which shows what happened when you tried to start ssh2d is found in /etc/rc.log.
In your script, you started ssh2d as a background process but it will be terninated when the script finishes. You must add nohup to protect ssh2d.