05-20-2013 01:47 PM
Hi community,
We are facing some problems with our CPI 1.3. The software suddenly stopped responding. We already tried to restart the service and the machine without success.
The following message was shown when we tried to start NCS:
gn827cb/admin# application start NCS
Purging PurgeSAMPollerRecods
{Mon May 20 11:19:20 BRT 2013} ===================================================
{Mon May 20 11:19:20 BRT 2013} =========Issuing dbadmin -v start=================
{Mon May 20 11:19:21 BRT 2013} =======executing delete sql script sam_poller_jobs_cleanup.sql====
{Mon May 20 11:30:10 BRT 2013} ==========Issuing dbadmin -v stop=================
{Mon May 20 11:30:13 BRT 2013} ===================================================
Completed purging SAMPoller Records
Starting Network Control System...
This may take a few minutes...
Failure during Network Control System startup. Check launchout.log for details.
start
gn827cb/admin#
We also got this message:
gn827cb/admin# sh application status NCS
Health Monitor is running, with an error.
initHealthMonitor(): can not start DB
Reporting Server is Stopped
Ftp Server is Stopped
Database server is stopped
Tftp Server is Stopped
Matlab Server is Stopped
NMS Server is stopped.
SAM Daemon is not running ...
DA Daemon is not running ...
Syslog Daemon is not running ...
status
gn827cb/admin#
Any idea how can I solve this?
I'm also trying to open a case with Cisco, but they ask me about SN, and I'm using a VM/OVA deployment. I don't know how to find it.
I also checked that we have a problem with space:
*****************************************
Checking Disk Space...
*****************************************
df -h output...
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/smosvg-rootvol
3.8G 285M 3.4G 8% /
/dev/mapper/smosvg-storeddatavol
9.5G 151M 8.9G 2% /storeddata
/dev/mapper/smosvg-localdiskvol
29G 173M 27G 1% /localdisk
/dev/sda2 97M 5.6M 87M 7% /storedconfig
/dev/mapper/smosvg-home
93M 5.6M 83M 7% /home
/dev/mapper/smosvg-optvol
120G 119G 0 100% /opt
/dev/mapper/smosvg-varvol
3.8G 117M 3.5G 4% /var
/dev/mapper/smosvg-usrvol
6.6G 1.2G 5.1G 19% /usr
/dev/mapper/smosvg-tmpvol
1.9G 35M 1.8G 2% /tmp
/dev/mapper/smosvg-recvol
93M 5.6M 83M 7% /recovery
/dev/mapper/smosvg-altrootvol
93M 5.6M 83M 7% /altroot
/dev/sda1 485M 18M 442M 4% /boot
tmpfs 3.9G 0 3.9G 0% /dev/shm
df -k output...
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/smosvg-rootvol
3967680 291476 3471404 8% /
/dev/mapper/smosvg-storeddatavol
9903432 153700 9238552 2% /storeddata
/dev/mapper/smosvg-localdiskvol
29741864 176224 28030460 1% /localdisk
/dev/sda2 99150 5688 88342 7% /storedconfig
/dev/mapper/smosvg-home
95195 5657 84623 7% /home
/dev/mapper/smosvg-optvol
125157140 124238476 0 100% /opt
/dev/mapper/smosvg-varvol
3967680 119396 3643484 4% /var
/dev/mapper/smosvg-usrvol
6919612 1227320 5335124 19% /usr
/dev/mapper/smosvg-tmpvol
1967952 35816 1830556 2% /tmp
/dev/mapper/smosvg-recvol
95195 5664 84616 7% /recovery
/dev/mapper/smosvg-altrootvol
95195 5664 84616 7% /altroot
/dev/sda1 495844 17643 452601 4% /boot
tmpfs 4021724 0 4021724 0% /dev/shm
df -k output for / /usr /var /opt
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/smosvg-rootvol
3967680 291476 3471404 8% /
/dev/mapper/smosvg-usrvol
6919612 1227320 5335124 19% /usr
/dev/mapper/smosvg-varvol
3967680 119396 3643484 4% /var
/dev/mapper/smosvg-optvol
125157140 124238476 0 100% /opt
*****************************************
Thank you in advance.
05-21-2013 02:07 AM
Hi,
Since it is a virtual appliance just attach them show tech-support and this should be sufficient for them. Regarding the disk space usage what you can do is:
1) Enable root access if you haven't ("root_enable" command).
2) Enter root mode.
3) Execute "du -sh /opt/*" it will list directories inside /opt which are consuming your disk space. After just analyze or find out which directories and files are causing this filling up.
P.
08-17-2016 10:49 AM
05-27-2019 08:17 AM
Hi Mady
you can resolved this iussue?
05-27-2019 09:39 AM
- You will need to fsck the corrupt filesystem manually : after entering the root password enter
fsck -y /dev/mapper/smosvg-varvol
M.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide