Shutdown not working 2

[KenCunningham]

Hi all,

I patched my E450 with the latest Sunsolve patches and tried to issue a shutdown -i6 -g0 -y command to reboot the box. The usual 'Logoff now' etc message appeared, but that seems to be as far as the shutdown actually proceeded, ie no reboot took place. Anyone else had this problem, and if so, is any solution available. Thanks in anticipation.

 

[harris79]

I've noticed that init 6 doesn't always work on my boxes (Solaris 8 with a full patch set), but reboot does.

Steve

 

[KenCunningham]

Thanks Steve, I'll give reboot a go when I get the chance. Oddly enough, the same patches applied to a Solaris 7 test box (Ultra 1) of the same system worked fine and init 6 remains available on that machine. Might be an architecture issue, I guess. Cheers.

 

[jdhinze]

Hi Ken,

I am having a simmliar problem on e450 with Solaris 8. Sometimes it works other times does not. This is a production system so we have limmeted hours to test , but was in on Sunday doing other maint. and of 3 shutdowns only one completed properly. The other two we actually had to turn off via the key , but system came back ok . Any insight or ideas would be appriciated.
Thanks,
Jack

 

[mikeclark]

I have seen the same thing with Solaris 8 after patching but, after the initian reboot shutdown mostly seems to work OK.

 

[KenCunningham]

Hi Jack,

can you do a:

which shutdown

to tell you where Solaris is looking for the command? I've not used Solaris 8, however, so things may have changed between 7 and 8.

 

[jdhinze]

Ken,

I am using /usr/sbin/shutdown

 

[notthehoople]

Hi,

I've seen this as well on Solaris 8 but have never had a chance to look closely into what was going on. I *think* what is happening is that 'shutdown' now waits for all the 'kill' scripts to exit gracefully before shutdown and that one of these scripts is sat waiting for an application to shutdown.

Next time it happens, check if any of the Kill scripts are sat trying to shutdown some part of the system. If this is the case you've got a starting point for what's going wrong. You could also try killing the kill script (!) in an attempt to get your shutdown running again.