×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

Emergency !! Major Power Failure - Publisher / Subscriber& Connection wont start...

Answered Question
Sep 27th, 2014
User Badges:

We have had a major outage, after power restored Publisher services wont start.

 

In addition Unity connection has a corrupt database and another subscriber is screwed.

 

However - first things first - I desperately need to get my publisher live.

 

I have restarted it many times now -

 

The GUI doesnt work and at the command line when I type

 

utils services list -

 

they are all in [STARTING] -

 

Uptime is now 2 hours.

 

Any ideas ?? Hopefully someone is working on a saturday !

Correct Answer by Jaime Valencia about 2 years 10 months ago

You should have involved your support team, TAC, or whoever that may be right away if this is an emergency, you cannot possibly expect the level of support required to fix something like this, and under time constrains, on a public forum. TAC is staffed 24x7 for this exact purpose.

Best I could tell you is to try the recovery CDs, or to restore from a backup, if all fails.

Correct Answer by orddie234 about 2 years 10 months ago

what version of call manager are we talking about here?

for best results...  you may want to get tac involved.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (4 ratings)
Loading.
keanej Sat, 09/27/2014 - 07:05
User Badges:

I notice this bug

 

Services Stuck in Starting after Graceful Shutdown/Restart
 
Solution seems to be ..
 

Move selinux to permissive (utils os secure permissive)

Restart the server and then after services are up

Move selinux to enforcing (utils os secure enforce)

 

 

I'll try that and let you know how it goes  !

keanej Sat, 09/27/2014 - 07:29
User Badges:

Well - that didnt work.

All services in [STARTING]

Any ideas ?

Correct Answer
orddie234 Sat, 09/27/2014 - 11:02
User Badges:

what version of call manager are we talking about here?

for best results...  you may want to get tac involved.

Chris Deren Sun, 09/28/2014 - 08:47
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,
  • Cisco Designated VIP,

    2017 IP Telephony, Contact Center, Unified Communications

I just had a customer go through similar outage where all 4 subs at failed data center needed to be rebuilt per TAC, fortunately Pub was OK, so this was quick solution, you may need to rebuild the Pub and restore from good backup, but I concur with Java engage TAC as they have root access to analyze the issue.

Chris

keanej Mon, 09/29/2014 - 09:39
User Badges:

Thanks for all the feedback -

 

I contacted TAC and raised a P1. We lost one publisher and one subscriber - we only had one working subscriber

we went down the road of SUB to PUB recovery.

At the end I downloaded the missing COP files and we were good to go.

The only 'gotcha' seems to be dial-plans - there were causing me a little heart ache and needed to be re-installed. Also MoH - but I didnt have much of that to begin with.

 

Apparently the underling Linux OS doesn't like sudden power downs !

keanej Mon, 09/29/2014 - 09:42
User Badges:

FYI

 

My recovery disk was corrupt and a download of a fresh recovery disk fixed unity connection ! That was a relief !

Correct Answer
Jaime Valencia Sat, 09/27/2014 - 11:54
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    2011

You should have involved your support team, TAC, or whoever that may be right away if this is an emergency, you cannot possibly expect the level of support required to fix something like this, and under time constrains, on a public forum. TAC is staffed 24x7 for this exact purpose.

Best I could tell you is to try the recovery CDs, or to restore from a backup, if all fails.

Manish Gogna Sun, 09/28/2014 - 21:20
User Badges:
  • Cisco Employee,

You can try to bring up the system using a recovery disk, however a rebuild may still be required as per the following doc

http://www.cisco.com/c/en/us/support/docs/unified-communications/unified...

  • Cisco Bug ID CSCth60800, "Recovery Disc warning to rebuild system after file system repair"
  • Cisco Bug ID CSCth53322, "Document the need for system rebuild after file system repair"

HTH

Manish

Actions

This Discussion