System does not boot after 5.0 MP1 upgrade due to two conflicting rc2.d startup scripts - S50isisd and S73isisd

Problem

System does not boot after 5.0 MP1 upgrade due to two conflicting rc2.d startup scripts - S50isisd and S73isisd

Error Message

System does not boot after 5.0 MP1 upgrade due to two conflicting rc2.d startup scripts - S50isisd and S73isisd

Solution


Conditions

This issue occurs only after Storage Foundation (SF) 5.0 MP1 upgrade on Solaris.

  Cause
   
SF 5.0 creates /etc/rc2.d/S73isisd startup script. Installation of SF 5.0 MP1 creates /etc/rc2.d/S50isisd startup script.
However, MP1 installation does not remove /etc/rc2.d/S73isisd script.
 
During reboot, S50isisd script starts isis process. Redundant startup script S73isisd script attempts to start isis process again. Prior to starting the process, the script checks the current status of 'vxsvc' daemon. If the mode of vxsvc is in STARTPENDING state, then the script goes into indefinite loop until the mode changes to RUNNING state.
This may prevent the system from completing the boot sequence.
 
If debugging is set on the startup script, then the output would be like as mentioned below:
 
+ /opt/VRTSob/bin/vxsvc -m
CURRENT_RUNSTATE= START PENDING  
+ [  RUNNING !=  START PENDING -a  NOT RUNNING !=  START PENDING -a  !=  
+ START PENDING ] sleep 2 printf .
.+ nawk -F: { print $2 }  
+ /opt/VRTSob/bin/vxsvc -m
CURRENT_RUNSTATE= START PENDING  
+ [  RUNNING !=  START PENDING -a  NOT RUNNING !=  START PENDING -a  !=  
+ START PENDING ] sleep 2 printf .
.+ nawk -F: { print $2 }  
+ /opt/VRTSob/bin/vxsvc -m



  Answer/Resolution
 
Manually remove /etc/rc2.d/S50isisd startup script from the system.

Symantec etrack incident # 1037988 tracks this issue, which is fixed in 5.0 MP3.


Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)