01-20-2012 07:05 AM - edited 03-16-2019 09:07 AM
Hi, all.. I have a problem here,
My Publisher suddenly stoped some administratve services lice Cisco Tomcat, AMC, Phone registered Monitor, etc, so now the phones are registered but I cannot see anything (no status).
I try to enter de CLI to restar manually some services and I got this error every 2-3 minutes.
################################
Command Line Interface is starting up, please wait ...
/usr/local/platform/bin/cliscript.sh: line 137: 28857 Killed /bin/nice -n 10 java -DConsoleRows=$ROWS -DConsoleColumns=$COLS sdMain name=$name priv=$priv $master
Copyright Cisco Systems 2006-2008
################################
What do you recommend at this point?
Look at the administrative services.
#################################
System SSH [STARTED]
Cluster Manager [STARTED]
Service Manager is running
Getting list of all services
>> Return code = 0
A Cisco DB[STARTED]
A Cisco DB Replicator[STARTED]
Cisco AMC Service[STOPPED] Component is not running
Cisco AXL Web Service[STOPPED] Commanded Out of Service
Cisco Audit Event Service[STARTED]
Cisco Bulk Provisioning Service[STARTED]
Cisco CAR Scheduler[STOPPED] Component is not running
Cisco CAR Web Service[STOPPED] Commanded Out of Service
Cisco CDP[STARTED]
Cisco CDP Agent[STARTED]
Cisco CDR Agent[STARTED]
Cisco CDR Repository Manager[STOPPED] Component is not running
Cisco CTIManager[STARTED]
Cisco CallManager[STARTED]
Cisco CallManager Admin[STOPPED] Commanded Out of Service
Cisco CallManager Attendant Console Server[STOPPED] Component is not running
Cisco CallManager Cisco IP Phone Services[STOPPED] Commanded Out of Service
Cisco CallManager Personal Directory[STOPPED] Commanded Out of Service
Cisco CallManager Serviceability[STOPPED] Commanded Out of Service
Cisco CallManager Serviceability RTMT[STOPPED] Commanded Out of Service
Cisco Certificate Expiry Monitor[STARTED]
Cisco DRF Local[STARTED]
Cisco DRF Master[STOPPED] Component is not running
Cisco Database Layer Monitor[STARTED]
Cisco Dialed Number Analyzer[STOPPED] Commanded Out of Service
Cisco Extended Functions[STARTED]
Cisco Extension Mobility[STOPPED] Commanded Out of Service
Cisco Extension Mobility Application[STOPPED] Commanded Out of Service
Cisco IP Manager Assistant[STOPPED] Commanded Out of Service
Cisco License Manager[STARTED]
Cisco Log Partition Monitoring Tool[STARTED]
Cisco RIS Data Collector[STOPPED] Component is not running
Cisco RTMT Reporter Servlet[STOPPED] Commanded Out of Service
Cisco SOAP - CDRonDemand Service[STARTED]
Cisco Serviceability Reporter[STARTED]
Cisco Syslog Agent[STARTED]
Cisco Tftp[STARTED]
Cisco Tomcat[STARTING]
Cisco Tomcat Stats Servlet[STOPPED] Commanded Out of Service
Cisco Trace Collection Service[STARTED]
Cisco Trace Collection Servlet[STOPPED] Commanded Out of Service
Cisco UXL Web Service[STOPPED] Commanded Out of Service
Host Resources Agent[STARTED]
MIB2 Agent[STARTED]
Native Agent Adapter[STARTED]
SNMP Master Agent[STARTED]
SOAP -Log Collection APIs[STARTED]
SOAP -Performance Monitoring APIs[STARTED]
SOAP -Real-Time Service APIs[STARTED]
System Application Agent[STARTED]
Cisco CTL Provider[STOPPED] Service Not Activated
Cisco CallManager SNMP Service[STOPPED] Service Not Activated
Cisco Certificate Authority Proxy Function[STOPPED] Service Not Activated
Cisco DHCP Monitor Service[STOPPED] Service Not Activated
Cisco DirSync[STOPPED] Service Not Activated
Cisco IP Voice Media Streaming App[STOPPED] Service Not Activated
Cisco Messaging Interface[STOPPED] Service Not Activated
Cisco TAPS Service[STOPPED] Service Not Activated
Cisco Unified Mobile Voice Access Service[STOPPED] Service Not Activated
Cisco WebDialer Web Service[STOPPED] Service Not Activated
Primary Node =true
#############################
Could you please give me an advice?
Solved! Go to Solution.
01-20-2012 07:16 AM
Hi
Maybe take a look at your memory stats using RTMT or the server CLI.
Typically you see problems with Tomcat as a result of memory starvation - and usually this is down to a memory leak in some process or other on the server. It usually requires an upgrade to resolve.
A reboot will cure it temporarily if that's the case - if you haven't rebooted this server for a long time it will probably get you a similar amount of time to the current uptime.
Regards
Principal Engineer at Logicalis UK
Please rate helpful posts...
01-20-2012 07:16 AM
Hi
Maybe take a look at your memory stats using RTMT or the server CLI.
Typically you see problems with Tomcat as a result of memory starvation - and usually this is down to a memory leak in some process or other on the server. It usually requires an upgrade to resolve.
A reboot will cure it temporarily if that's the case - if you haven't rebooted this server for a long time it will probably get you a similar amount of time to the current uptime.
Regards
Principal Engineer at Logicalis UK
Please rate helpful posts...
03-05-2012 10:45 AM
Thanks, I roboted the server and everything os all right!
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