shutdown hangs during installation of 119578-09
Ive recently noticed a problem with the shutdown process hanging during patch installation.
I do a "shutdown -y -g0 -i6" as usual.
The box remails usable, but the shutdown never completes.
I bit of investigation reveals its related to patch 119578-09.
The prepatch attempts to disable the fmd service. But this is hanging during a "svcadm disable fmd" command.
If you manually shutdown fmd yourself, before trying to do the patching, things work ok. When the prepatch comes to shut fmd down, it realises theres nothing to do and continues.
I'm guessing that by the stage of the shutdown process wherepatches are installed, some part of the svc system that is needed to be able to disable facilities has already been killed.
# 1
The svc system is not started or shutdown from a runlevel script but started by init when the system boots (via the sysinit action for the command in the /etc/initab) so should always be running.
How long did you wait as the svcadm command does have a timeout while waiting for services and their dependencies to change state?
# 2
I got into work this morning at 8.30am to find a server hung that had been shut down (with init -6) at 3.15am. 5 hours in this case. 119578-09 was the culprit.
# 3
I've contacted the patch team and asked them to have a look at this as it sounds like an issue with the patch itself and not with Update manager/connection.
# 4
I think its some combination of the 2.The patch seems to run ok when patchadd is invoked manually.Ive only only from inside updatemanager that Ive seen the problem.
# 5
I might be having similar updatemanager problems when I tried to apply the latest patches:
119689-06
119012-03
119578-09
Patch 119579-09 might be problematic. To get out of the inconsistent "smcpatch analyze" setup problem, I am going to manually apply the patches one at a time in single-user mode. I thought that applying 119578-09 and then rebooting would clear up the remaining patches that would not apply. It did not work.
# 6
Your probably hitting another one of the known update manager problems caused by installing 121086-01.
This causes it to not install the patches that were delayed until a reboot.
To work around it do a
ln /etc/init.d/installupdates /etc/rc0.d/K51installupdates
ln /etc/init.d/installupdates /etc/rcS.d/K51installupdates
and shutdown/restart.
# 7
Did this ln bit work for you? I am having the same issue but making the links has not helped....
# 8
How are you rebooting.A reboot command will not work.I normally do ashutdown -y -g0 -i6
# 9
I got it to work on my sb1k but the e450 is still stuck (more of a production machine so I dont want to mess with it and will wait for the sun patch).
I do shutdown -i 6 or sync;sync;init 6 depending (on mood?).
Is your version better? I am a linux person normally, just picked up solaris in the past year, lots of reaching around in the dark here. Reading Sobell and Waters wasnt much of a help for that kind of thing...
Suppose I could read the man page, but I have a dissertation to write...
Dan
# 10
No those restart forms should be equivalent.
# 11
I think this is more a patch than an update connection issue although I'm a little confused. I tried installing this patch on my Blade 100 using the update connection manager and noticed that it simply seemed to do nothing during a reboot. The packages kept being displayed with the '-' status ("setup and ready to be installed during reboot").
So this weekend I installed these patches manually. The result is exactly the same as you described, my box also hanged during the reboot phase (shutdown -y -g 5 -i 6) and it was only the next morning (I shut it down around 22:00 and noticed something to be odd at 14:00 the next day) that I took action. Because I don't have a monitor/keyboard attached I simply forcidly turned it off and on again, and the logs didn't show any big filesystem issues.
The fun part however is that now that I look at this again I can see the patch being installed (/var/sadm/patch/119578-09 exists and the 'log' file tells me as much) but the update connection manager displays this patch as being available for installation (so a checkbox in front of it).
Personally I'm >< close to quit using the connection manager alltogether, even on my regular boxes, and only make it display the available patches. I'm nearly finished with a script which fully takes over which will once again make my life a lot easier on my servers which all happen to run several zones. Something which is a nightmare to manage otherwise.
LionO at 2007-7-6 13:30:37 >
# 12
I have a couple of scripts to install patches on zoned boxes.
I posted a version of the script a while back. But I have an improved version now which splits the safe/dangerous patches into 2 phases so you can stop services before applying the dangerous patches.
I can post them here if there is demand.
# 13
The problem is this patch should have been labeled as an interactive patch. Do not install this patch with Update Manager / Sun Update Connection or smpatch. To safely install this patch, drop down to singleuser mode and install manually.
To unhang the client
remotely login to the box and kill this process
svcadm disable -t -s svc:/system/fmd:default
It will cause some of the patch installs to fail but it will unhang restart.
We are working to get this patch labeled correctly which in turn will make it work correctly with update manager.
