agent v0.4.0.129 fails to automatically start after reboot

[mikep]

I am running 0.4.0.129x64. It works great and I can start it from the service control panel successfully. The service is set to automatically start. I have not changed the service settings from the way it was installed by the installer.

When I reboot the server, the agent fails to start successfully. I get an error message that it timed out. I also verified that I'm experiencing the same issue on a 32-bit server with the 32-bit agent.

Log Name: System
Source: Service Control Manager
Date: 2/6/2012 4:49:22 PM
Event ID: 7009
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: XXXXXXXXX
Description:
A timeout was reached (30000 milliseconds) while waiting for the NSClient++ (x64) service to connect.
Event Xml:
<Event xmlns="​http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName?="Service Control Manager" />
<EventID Qualifiers="49152">7009</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated? SystemTime?="2012-02-07T00:49:22.296875000Z" />
<EventRecordID>60139</EventRecordID>
<Correlation />
<Execution ProcessID="464" ThreadID="468" />
<Channel>System</Channel>
<Computer>XXXXXXXXXXXXXX</Computer>
<Security />

</System>
<EventData?>

<Data Name="param1">30000</Data>
<Data Name="param2">NSClient++ (x64)</Data>

</EventData?>

</Event>

Log Name: System
Source: Service Control Manager
Date: 2/6/2012 4:49:22 PM
Event ID: 7000
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: XXXXXXXXXXXXXXXXXXXX
Description:
The NSClient++ (x64) service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
Event Xml:
<Event xmlns="​http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName?="Service Control Manager" />
<EventID Qualifiers="49152">7000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated? SystemTime?="2012-02-07T00:49:22.296875000Z" />
<EventRecordID>60140</EventRecordID>
<Correlation />
<Execution ProcessID="464" ThreadID="468" />
<Channel>System</Channel>
<Computer>XXXXXXXXXXXXXXXX</Computer>
<Security />

</System>
<EventData?>

<Data Name="param1">NSClient++ (x64)</Data>
<Data Name="param2">%%1053</Data>

</EventData?>

</Event>

[mickem]

This was due to invalid service defenition if I recall correctly,m please try this with latest RC and reopen if it is still an issue...

[mikep]

Using the 64-bit version of build 150, I am still seeing the same behavior. The starting and stopping of the service works great in the service control manager. But when the server is restarting, I recieve the same two error messages that were listed above.

Is nscp dependent on another service that may not have been started already?

[mickem]

No, the problem seems to have been boost and the message_queue library.
I was using it (as I was lazy) for implementing log syncronization.

The problem though was that the library seems to do some strange voodoo the symptoms I had locally was NOTHING process failes to start I added logging to the main()... nothing... extremely frustrating...

Regardless I have cranked out a temporary "fix" which I would like you(?) to try and make sure this fixes the issue. NOTICE this version is crap so DO NOT install this in production. It has a broken log implementation (which is not configurable and not really thread safe (meaning it shouldn't crash but log might got multiple statements on the same line).

I will try to write a new non boost message_queue version in the next few days which should resolve this in a proper fashion after which a new RC will be released.

Michael Medin

[mickem]

x64 build of nscp.exe

[mickem]

BTW, how to install:

install regular build of 0.4.0 and make backup of nscp.exe and place this in and reboot... Verify that it starts and a log is created <exe-folder>/nsclient.log.
Then restore previous backedup version...

[mikep]

This appears to have resolved the autostart issue. I unzipped the nscp.exe and copied it to the nsclient++ directory. After a server reboot, I verified the service was running and providing passive checks as well as handling active check requests. I didn't validate all of the other functionality, but the autostart appears to be resolved.

Thanks!

mikep

[mickem]

Sweeet... Then I will go home and fix the logging and hopefully tomorrow or day after we will have a new build...

Thanks very much for all help in testing things!!!

[mickem]

Whoops, abit to trigger happy there... reset to reopened :)

[mickem]

Fixed in latest build with a new one coming soon which also removes the old fileLogger which is no longer used...

Michael Medin