cancel
Showing results for 
Search instead for 
Did you mean: 

Wvlog error: Process stop detected. Trying to restart.

Support_Sydney
Moderator

Wvlog error: Process stop detected. Trying to restart.

You are receiving an error similar to the following:

2016-11-07 12:38:36 00001050 promgrp 05666 irpromgs 10.0.0 068684 - Process stop detected. Trying to restart. CCM50001:CCM50001

1 ACCEPTED SOLUTION

Accepted Solutions
Support_Sydney
Moderator

Re: Wvlog error: Process stop detected. Trying to restart.

You are receiving an error similar to the following:

2016-11-07 12:38:36 00001050 promgrp 05666 irpromgs 10.0.0 068684 - Process stop detected. Trying to restart. CCM50001:CCM50001

Cause: the Prognosis Process Manager irpromgs keeps a close eye on all the processes in Prognosis. When one stops than Process Manager detects it and tries to restart it. It logs this event to WVLOG and includes the Prognosis internal symbolic name of the process in the wvlog event.

Solution: Check for preceding events leading up to this one and see if the process itself logs any errors that are meaningful, and might provide a clue to the cause of the problem. Sometimes the process may log sufficiently meaningful information to help identify the root cause.

Note: If Process Manager finds the process to have stopped 5 times within 5 minutes then it will stop re-attempting to start it up and logs another error "Process is over restart limit"

View solution in original post

1 REPLY 1
Support_Sydney
Moderator

Re: Wvlog error: Process stop detected. Trying to restart.

You are receiving an error similar to the following:

2016-11-07 12:38:36 00001050 promgrp 05666 irpromgs 10.0.0 068684 - Process stop detected. Trying to restart. CCM50001:CCM50001

Cause: the Prognosis Process Manager irpromgs keeps a close eye on all the processes in Prognosis. When one stops than Process Manager detects it and tries to restart it. It logs this event to WVLOG and includes the Prognosis internal symbolic name of the process in the wvlog event.

Solution: Check for preceding events leading up to this one and see if the process itself logs any errors that are meaningful, and might provide a clue to the cause of the problem. Sometimes the process may log sufficiently meaningful information to help identify the root cause.

Note: If Process Manager finds the process to have stopped 5 times within 5 minutes then it will stop re-attempting to start it up and logs another error "Process is over restart limit"

View solution in original post