My Oracle Support Banner

Msprobe Causes Watcher To Erroneously Restart Dispatcher (Doc ID 1510990.1)

Last updated on DECEMBER 05, 2019

Applies to:

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

Symptoms

The dispatcher process is being restarted and then watcher stops monitoring it. In the default log file:

[date/time] <hostname> msprobe[<pid>]: General Error: cannot read banner from port 587: Connection timed out
[date/time] <hostname> msprobe[<pid>]: General Critical: SMTP_SUBMIT server is not responding
[date/time] <hostname> msprobe[<pid>]: General Critical: dispatcher restart requested

And the in the watcher log, you eventually get:

[date/time] (Notice) Received request to restart: dispatcher
[date/time] (Notice) Connecting to watcher ...
[date/time] (Error) dispatcher failed twice in 600 seconds, will not perform restart

 

Changes

The SMTP_SUBMIT service has been disabled - msprobe should not be trying to test it.

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
Changes
Cause
Solution


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