IMPORTANT ANNOUNCEMENT

These forums will be permanently set to read-only mode on July 18, 2022. From that day on, no new posting or comment will be allowed on the site, but the historical content will remain intact and searchable.

A new location for posting questions about PlanetPress Suite is now available:

OL Learn - PlanetPress Classic (opens in new tab)

Topic Options
#58289 - 06/24/22 12:25 PM PP workflow Watch service in stopping state
De12345 Offline
OL Newbie

Registered: 09/14/18
Posts: 17
Hi,
On one of the PP server after deployment while sending the configuration locally the PP watch service is not responding and going in “Stopping” state and doesn’t start.

Log file entries as below:

START: 2022/06/24 15:54:02
INFO : PlanetPress LPR Client v7.6.2.9999
INFO : Host: XXX-AAA-FFF-U03; User: SYSTEM
INFO : PlanetPress LPR Client has started

INFO : PlanetPress LPR Client has stopped
STOP : 2022/06/24 16:21:01
=================================================

DEBUG: Process "Forevermark GR BL English" is still running...
DEBUG: Process "Forevermark GR BL" is still running...
DEBUG: Process "Forevermark IR BL English" is still running...
DEBUG: Process "Forevermark IR BL" is still running...
INFO : Waiting for Processes to terminate (4 process left)...
DEBUG: Process "Forevermark GR BL English" is still running...
DEBUG: Process "Forevermark GR BL" is still running...
DEBUG: Process "Forevermark IR BL English" is still running...
DEBUG: Process "Forevermark IR BL" is still running...
INFO : Waiting for Processes to terminate (4 process left)...
---------------------------------------------------------

Note: The server is a VM and couple of days back the host became unresponsive and had to hard boot. After that the above issue started occurring.

Thank You

Top
#58291 - 06/25/22 08:34 AM Re: PP workflow Watch service in stopping state [Re: De12345]
Jean-Cédric Offline
OL Expert

Registered: 10/03/16
Posts: 681
Loc: Québec, Canada
When sending your Workflow (Watch) configuration, the service ask all process to terminate what they are currently doing and then stops. It (the service) waits until all processes have confirmed they're done and then will stop. If one process is hanging, it will hold the restart until that process is done.

When that occurs next, if you know that all processes should have finished by then, in your Workflow console window, right click the Workflow (Watch) first item in the left side list and select Kill.... that will force the service to stop but the hanging process will loose the file it was currently working on. At least, you will know which process was the culprit and look into it to figure out why that particuliar process was hanging.

If you are unable to figure it out, I suggest you open a technical support ticket via our website and a technician will be able to remote in and help you with it.
_________________________
♪♫♪♫
99 frigging bugs in my code
99 frigging bugs
Take one down
Code around
127 frigging bugs in my code
♪♫♪♫

Top