Quoth Moritz Willers on Thu, Sep 21, 2006 at 10:46:10PM +0100: > The culprit that kept re-enabling svc:/network/rpc/meta was /var/svc/ > profile/upgrade (as setup by the flash install post deployment > processing). > > An error in the upgrade script (added by JASS, bug fixed in patch > 122608-02) caused the upgrade script to fail and the subshell > executing /var/svc/profile/upgrade in /lib/svc/method/manifest-import > to terminate before the upgrade script was renamed. It was re- > running and failing on every reboot. > > Shouldn't the upgrade script be renamed even if it failed executing?
Yes, probably. I filed 6473940 manifest-import should handle upgrade-file failure better for you. > Would it not be wise at this point to set the state of svc:/system/ > manifest-import to something other than "online"? Surely the user > should get an indication that something went wrong during the > manifest import? It would certainly have helped me to track this > problem down a lot faster! Yes, I think maintenance would be reasonable. Obviously, this is too late, but a technique which would have helped would have been to compare the time that the service was enabled with the time that other services ran. This should have turned manifest-import up, which would point to the upgrade file. Perhaps this should be on the FAQ (where is it, anyhow?). David
