Subscriber server restart

1 Reply

We have been experiencing issues with the Cisco Call Manager servers resulting is some failures. Working with Cisco Technical Support we have made changes which require a restart of both servers. We have already restarted one with no effect on the end point phones, the next restart has a greater potential to cause disruption.
We will be restarting the second server at 10:05

Jamie Voyles

1 thought on “Subscriber server restart”

  1. Jamie Post author

    Hi Jamie,

    I would like summarize our call today.

    Problem Description: Sub is not reachable via GUI. CLI is very slow. It takes almost 15 min to get output of any command.

    Troubleshooting Done:

    ++ restarted servers several times.
    ++ show status shows IOWAIT to 90%
    ++ cu has upgraded f/w on MCS box.
    ++ you have also run recovery CD and rebuild server
    ++ db replication seems fine but utils diagnose test shows “test – validate_network : Error, intra-cluster communication is broken, unable to connect” ON both servers.

    ++ I noticed a DNS issue which could cause the above error and configured same DNS servers on Pub also. Rebooted Pub. Same issue.
    ++ I engaged escalation engineer to check db replication and he found that it was fine.
    ++ In catalina logs, we see following errors for Tomcat which confirm Tomcat file corruption:

    Dec 6, 2012 10:14:27 AM org.apache.catalina .startup.HostConfig deployDescriptor
    INFO: Deploying configuration descriptor SNMPService.xml
    Dec 6, 2012 10:14:27 AM org.apache.catalina .startup.HostConfig deployDescriptor
    WARNING: A docBase /usr/local/thirdparty/apache-tomcat-6.0.29/webapps/SNMPService.war inside the host appBase has been specified, and will be ignored
    Dec 6, 2012 10:14:27 AM org.apache.catalina .startup.HostConfig deployDescriptor
    INFO: Deploying configuration descriptor dna.xml
    Dec 6, 2012 10:14:27 AM org.apache.catalina .startup.HostConfig deployDescriptor
    WARNING: A docBase /usr/local/thirdparty/apache-tomcat-6.0.29/webapps/dna.war inside the host appBase has been specified, and will be ignored
    Dec 06, 2012 10:14:46 AM Tomcat HTTP connector status: 1
    …

    Dec 06, 2012 10:36:13 AM Tomcat HTTP connector status: 1
    Dec 06, 2012 10:36:13 AM Tomcat HTTPS connector status: 1
    Dec 06, 2012 10:36:13 AM Tomcat failed to start in 240 seconds
    Dec 06, 2012 10:36:13 AM — Shutdown —
    Dec 06, 2012 10:36:16 AM Stopping Tomcat based on existing process names
    Dec 06, 2012 10:36:21 AM Killing 15098

    Action Plan: Subscriber rebuild appears to be the necessary step moving forward, as catalina.out log is indicating an issue during Tomcat WAR file deployment, resulting in the system shutting down Cisco Tomcat after failure to initialize in the 240 second threshold.

    NOTE: Please do a media check before you install it on the server. I will contact you at 10 AM EST as requested by you.

    Have a good day ahead.

    Thanks & Regards,

    Tejendra Negi
    Engineer – Customer Support (Cisco Unified Communications Manager)
    Phone: , Email ID:
    Working Days: | Working hours:
    Mon to Fri|08:00 AM to 05:00 PM (EST)

    ↓

Leave a Reply