PI 1.4 can't start automatically after reboot

[tira li]

Hi All,

       Our client has UCS server and installed PI 1.4 virtual appliance as vm on it.  UCS Array Card has issued and all vm including PI have shut down. After replacing Array Card with RMA, every vm can run normally except for PI.  After starting PI vm and waiting for halt an hour, we still can't log in Web and implement command(ncs status) via SSH, we found all service stopped or isn't running. After running ncs start, we can log in Web and PI can collect device information normally. 

        When reloading the PI again via SSH,  we can't log in Web again and have to implement ncs start command manually. The process of NCS can't automatically start to run.

         How to check or fix it , thx in advance!

Regards,

Tira

[tira li]

Hi All,

         Have any idea about this? Thx very much!

[ngoldwat]

1st thing to check is if /etc/init.d/NCS file is missing or currupt. 

ade # stat NCS
  File: `NCS'
  Size: 1571            Blocks: 8          IO Block: 4096   regular file
Device: fd00h/64768d    Inode: 129329      Links: 1
Access: (0755/-rwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2014-10-17 09:22:12.000000000 -0400
Modify: 2014-05-29 13:33:21.000000000 -0400
Change: 2014-05-29 13:33:21.000000000 -0400

[tira li]

Hi ngoldwat,

       The file has existed in this directory and the output as below:

       ade # stat NCS
 File: `NCS'
 Size: 1571            Blocks: 8          IO Block: 4096   regular file
Device: fd00h/64768d    Inode: 257693      Links: 1
Access: (0755/-rwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2014-10-17 22:03:54.000000000 +0800
Modify: 2014-10-17 17:26:40.000000000 +0800
Change: 2014-10-17 17:26:40.000000000 +0800

[ngoldwat]

There is a high likelyhood you are running up against CSCum39942

If you think otherwise please provide the below information.

Change: 2014-10-17 17:26:40.000000000 +0800

Please attach the file for comparison along with the output of

chkconfig --list

cat /etc/inittab

ls -lh /etc/rc.d/rc3.d/

ls -lh /etc/rc.d/rc5.d/

What patch level are you running?

Thanks.

[tira li]

Hi Ngoldwat,

       I have checked the bug description and it apply to my situation.

       Our PI system version 1.4 with path PI_1.4_0_45_Update_1-39 which is used to manage WLC 7.6 has running so long and don't try to reboot to test the bug.

        In addition, I have updated one path PI_1.4_0_45_Update_2-45 to manage AP2700 on 17th Oct . So the output displayed "Change: 2014-10-17 17:26:40.000000000 +0800"

        I have uploaded the file you asked us and the path level as given below, thx in advance!

        If we want to start ncs application automatically, do we have to uninstall the path PI_1.4_0_45_Update_1-39? Thank you very much!

CNDGIDCPI01/admin# show version

Cisco Application Deployment Engine OS Release: 2.0
ADE-OS Build Version: 2.0.1.038
ADE-OS System Architecture: x86_64

Copyright (c) 2005-2010 by Cisco Systems, Inc.
All rights reserved.
Hostname: CNDGIDCPI01

Version information of installed applications
---------------------------------------------

Cisco Prime Network Control System
------------------------------------------
Version : 1.4.0.45
Patch: Cisco Prime Network Control System Version: Update-1_39_for_version_1_4_0_45
Patch: Cisco Prime Network Control System Version: Update-2_45_for_version_1_4_0_45
Patch: Cisco Prime Network Control System Version: CSCui77571_2

[ngoldwat · Accepted solution]

Well the bug indicates that the work around is

Manually start the PI server using the command "ncs start"

The recommendation here is to upgrade to 2.x

Thanks