Re^2: Win32::Daemon service doesn't reach RUNNING state

For the one that does run with the duplicated line but will not resume after pause:

The Test Service (TestService) service entered the running state.
The Test Service (TestService) service entered the paused state.
The Test Service (TestService) service has reported an invalid current
+ state 0.
[download]

Last message repeats over and over again after attempt to resume, until stopped.

Will check the other system where running is never triggered as soon as possible.

Comment on Re^2: Win32::Daemon service doesn't reach RUNNING state Download Code

Replies are listed 'Best First'.
Re^3: Win32::Daemon service doesn't reach RUNNING state by SwaJime (Scribe) on May 30, 2019 at 15:25 UTC
On yet another system, same code gives a different error: `Undefined subroutine &Win32::Daemon::SERVICE_STOPPED called at ... and + is pointing to this code in the initial startup:` [download] `my %Context = ( last_state => SERVICE_STOPPED, start_time => time(), );` [download]	[reply] [d/l] [select]
Re^4: Win32::Daemon service doesn't reach RUNNING state by SwaJime (Scribe) on May 30, 2019 at 17:22 UTC
More info: On this system it turns out there are two copies of Win32::Daemon. When I get a chance I will confirm which one is active, but I am pretty sure at the moment it is the newer one. So I have been programming for and testing with a copy of the older version. But this system we deployed to appears to be trying to load the newer and erroring out. Version coded for: $VERSION = 20131206; Version erroring out: $VERSION = '20181025';	[reply]
Re^5: Win32::Daemon service doesn't reach RUNNING state by SwaJime (Scribe) on May 31, 2019 at 12:57 UTC
So for this I'm obviously going to have to change the service so that it can detect the version and compile whether it is 20131206 or 20181025/higher ... That should be an interesting task. If anybody has already done this please let me know! The issues reported so far in this thread rg 20131206 are still unresolved. :-( On one system, Callback_Running is never called. On another system, Callback_Running is called but Win32::Daemon::State() never returns SERVICE_RUNNING when queried by Callback_Running, even though it is set by Callback_Start. I have not been able to confirm that doubling the line mentioned earlier resolves this issue. Thanks for all the help so far. This has been difficult to coordinate client screentime with Monk availability.	[reply]
Re^6: Win32::Daemon service doesn't reach RUNNING state by SwaJime (Scribe) on May 31, 2019 at 20:18 UTC
Re^7: Win32::Daemon service doesn't reach RUNNING state by SwaJime (Scribe) on Jun 03, 2019 at 14:11 UTC
Some notes below your chosen depth have not been shown here


The stupid question is the question not asked
	PerlMonks