Re: Win32::Daemon problems

Is there any other logging that you might be able to add to the system or error logs in order to help you diagnose the problem? What messages exactly are given? Does the service in fact show up as "started?"

Comment on Re: Win32::Daemon problems

Replies are listed 'Best First'.
Re^2: Win32::Daemon problems by o3zone (Initiate) on Oct 18, 2012 at 16:19 UTC
I apologize for the original posting being as an Anonymous Monk, I did not realize I was not logged into the Monastery. The error output is from the Windows System Event Log: "The FooBar service has reported an invalid current state 0" Event ID 7016. STDERR shows no errors reported, only that the service started: c:\FOO\FooBar.exe started Thu Oct 18 15:00:00 2012. The error shows up every time the system does a callback to FooBar to see if it is running. So my System Event Log fills up rather quickly. Humbly, Mike O	[reply]

Replies are listed 'Best First'.

Re^2: Win32::Daemon problems
by o3zone (Initiate) on Oct 18, 2012 at 16:19 UTC

I apologize for the original posting being as an Anonymous Monk, I did not realize I was not logged into the Monastery. The error output is from the Windows System Event Log: "The FooBar service has reported an invalid current state 0" Event ID 7016. STDERR shows no errors reported, only that the service started: c:\FOO\FooBar.exe started Thu Oct 18 15:00:00 2012. The error shows up every time the system does a callback to FooBar to see if it is running. So my System Event Log fills up rather quickly. Humbly, Mike O

[reply]