My Oracle Support Banner

watcher Received request to restart ... Restarting Prevents Data Collection (Doc ID 1940656.1)

Last updated on MARCH 18, 2020

Applies to:

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

Goal

Request to Restart, without Exited Abnormally

When the watcher log file shows "Received request to restart: ..." messages like below, but without the corresponding "exited abnormally" message, it means the periodic msprobe process has called for a restart for some reason.

To determine why msprobe called for restart, you must review the default log file covering the time of the "request to restart" message.

Exited abnormally is a separate problem - look for core files

If you see "exited abnormally" followed by "request to restart", for example:

Then you should be looking for core files from the process which "exited abnormally". Also, make sure coreadm is configured properly.

 

Solution

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
Goal
 Request to Restart, without Exited Abnormally
 Exited abnormally is a separate problem - look for core files
Solution
 What requested the restart?
 How to gather more data?
 "Exited Abnormally" after the fact - don't be confused
 Why must it restart more than just the problem process?
 Sometimes restart only makes it worse
References

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