My Oracle Support Banner

ims_svc_start start-msg watcher Failed To Stay Up (Doc ID 1553703.1)

Last updated on MARCH 07, 2018

Applies to:

Oracle Communications Messaging Server - Version 6.0.0 and later
Information in this document applies to any platform.

Symptoms

Trying to fail over a Messaging Server resource from one node of the cluster to another fails with the following key error message:

This shows watcher finally started about 31 seconds after "start-msg watcher" began.

So in this case, watcher started soon enough that the cluster software did not declare that it "failed to say up", but it took long enough that the rest of the Messaging Server processes were unable to start.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
 A slightly different example
Changes
Cause
Solution
 Workaround
 Debugging to determine why watcher takes so long to start
 Otherwise, more debugging from cluster
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.