cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2041
Views
0
Helpful
1
Replies

Cisco prime services not starting

Hello,

I run into an incident where Cisco Prime NCDS is not running even after a stop/start from the services. A cleanup is also not necessary seen that there is enough space. The lauchout.log doesn't make a difference and the startup.log doesn't exist

This is the error I get when I try to restart the service

AHAS-PRIME01/admin# ncs stop

Stopping Network Control System...

This may take a few minutes...
Stopping remoting: Ftp Server
Remoting 'Ftp Server' stopped successfully.
Database is not running.
Stopping remoting: Tftp Server
Remoting 'Tftp Server' stopped successfully.
Stopping remoting: Matlab Server
Remoting 'Matlab Server' stopped successfully.
NMS Server is not running!.

Network Control System successfully shutdown.


Plug and Play Gateway is being shut down..... Please wait!!!

Stop of Plug and Play Gateway Completed!!
SAM daemon process id does not exist
DA daemon process id does not exist
DA syslog daemon process id does not exist

AHAS-PRIME01/admin# ncs start

Starting Network Control System...

This may take a few minutes...

Failure during Network Control System startup.  Check launchout.log for details.

AHAS-PRIME01/admin# sho version

Cisco Application Deployment Engine OS Release: 2.0
ADE-OS Build Version: 2.0.6.003-px-build
ADE-OS System Architecture: x86_64

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


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

Cisco Prime Infrastructure
------------------------------------------
Version : 2.0.0.0.294-2

Disk space is enough because:

ade # df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/smosvg-rootvol
                      3.8G  284M  3.4G   8% /
/dev/mapper/smosvg-altrootvol
                       93M  5.6M   83M   7% /altroot
/dev/mapper/smosvg-home
                       93M  5.6M   83M   7% /home
/dev/mapper/smosvg-recvol
                       93M  5.6M   83M   7% /recovery
/dev/mapper/smosvg-tmpvol
                      1.9G   38M  1.8G   3% /tmp
/dev/mapper/smosvg-localdiskvol
                      122G  8.2G  107G   8% /localdisk
/dev/mapper/smosvg-storeddatavol
                      9.5G  151M  8.9G   2% /storeddata
/dev/mapper/smosvg-varvol
                      3.8G  874M  2.8G  24% /var
/dev/mapper/smosvg-optvol
                      647G   88G  526G  15% /opt
/dev/mapper/smosvg-usrvol
                      6.6G  873M  5.5G  14% /usr
/dev/sda2              97M  5.6M   87M   7% /storedconfig
/dev/sda1             485M   18M  443M   4% /boot
tmpfs                 7.8G     0  7.8G   0% /dev/shm
ade # df -k
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mapper/smosvg-rootvol
                       3967680    290064   3472816   8% /
/dev/mapper/smosvg-altrootvol
                         95195      5664     84616   7% /altroot
/dev/mapper/smosvg-home
                         95195      5668     84612   7% /home
/dev/mapper/smosvg-recvol
                         95195      5664     84616   7% /recovery
/dev/mapper/smosvg-tmpvol
                       1967952     38784   1827588   3% /tmp
/dev/mapper/smosvg-localdiskvol
                     127250060   8509796 112171920   8% /localdisk
/dev/mapper/smosvg-storeddatavol
                       9903432    153704   9238548   2% /storeddata
/dev/mapper/smosvg-varvol
                       3967680    894316   2868564  24% /var
/dev/mapper/smosvg-optvol
                     677780752  91682376 551113624  15% /opt
/dev/mapper/smosvg-usrvol
                       6919612    893124   5669320  14% /usr
/dev/sda2                99150      5689     88341   7% /storedconfig
/dev/sda1               495844     17558    452686   4% /boot
tmpfs                  8139408         0   8139408   0% /dev/shm

Anyone any idea ?

1 Reply 1

Marvin Rhoads
Hall of Fame
Hall of Fame

When did it last work? what changed?

You will probably need to open a TAC case to get it running. They will almost certainly advise you to migrate off of this very old "dot 0" release. (Prime Infrastructure 3.1.3 is the current release right now.)