>last debug step was: servicecheck!

There are no changes in the code related to this for a very long time.

The debug step indicates, that the Windows service manager takes too long 
to answer assp about the windows service state.

Thomas




Von:    Scott MacLean <a...@hollsco.com>
An:     ASSP Development Mailing List <assp-test@lists.sourceforge.net>
Datum:  16.03.2016 14:12
Betreff:        [Assp-test] Stuck thread



A couple of builds ago, this started happening on my server on a fairly
regular basis.

logged error on host mail.xxxxx.com:

Mar-15-16 23:44:11 error: MainThread stuck for 65 seconds after: MainLoop 
get the best worker = 3 (0 sockets) - last debug step was: servicecheck!

And then three minutes later:

information on host mail.xxxxx.com:

MainThread has returned to normal state after stuck


I don't see any other behavior in the logs nearby that might explain a
cause. Any idea what might be going on?

Here's a grep from yesterday's log:

Mar-15-16 00:08:45 [Worker_10000] Error: MainThread stuck for 63 seconds
after: MainLoop get the best worker = 3 (0 sockets) - last debug step
was: servicecheck!
Mar-15-16 01:11:55 [Worker_10000] Error: MainThread stuck for 65 seconds
after: MainLoop get the best worker = 3 (0 sockets) - last debug step
was: servicecheck!
Mar-15-16 01:53:41 [Worker_10000] Error: MainThread stuck for 89 seconds
after: MainLoop get the best worker = 1 (0 sockets) - last debug step
was: servicecheck!
Mar-15-16 02:26:48 [Worker_10000] Error: MainThread stuck for 64 seconds
after: MainLoop get the best worker = 2 (0 sockets) - last debug step
was: servicecheck!
Mar-15-16 02:29:00 [Worker_10000] Error: MainThread stuck for 62 seconds
after: MainLoop get the best worker = 1 (0 sockets) - last debug step
was: servicecheck!
Mar-15-16 02:56:45 [Worker_10000] Error: MainThread stuck for 66 seconds
after: MainLoop get the best worker = 2 (0 sockets) - last debug step
was: servicecheck!
Mar-15-16 04:09:54 [Worker_10000] Error: MainThread stuck for 61 seconds
after: MainLoop get the best worker = 4 (0 sockets) - last debug step
was: servicecheck!
Mar-15-16 04:28:54 [Worker_10000] Error: MainThread stuck for 61 seconds
after: MainLoop get the best worker = 1 (0 sockets) - last debug step
was: servicecheck!
Mar-15-16 04:37:50 [Worker_10000] Error: MainThread stuck for 62 seconds
after: MainLoop get the best worker = 3 (0 sockets) - last debug step
was: servicecheck!
Mar-15-16 04:44:28 [Worker_10000] Error: MainThread stuck for 65 seconds
after: MainLoop get the best worker = 2 (0 sockets) - last debug step
was: servicecheck!
Mar-15-16 05:02:38 [Worker_10000] Error: MainThread stuck for 65 seconds
after: MainLoop get the best worker = 4 (0 sockets) - last debug step
was: servicecheck!
Mar-15-16 05:31:03 [Worker_10000] Error: MainThread stuck for 61 seconds
after: MainLoop get the best worker = 3 (0 sockets) - last debug step
was: servicecheck!
Mar-15-16 06:29:42 [Worker_10000] Error: MainThread stuck for 62 seconds
after: MainLoop get the best worker = 1 (0 sockets) - last debug step
was: servicecheck!
Mar-15-16 06:43:49 [Worker_10000] Error: MainThread stuck for 62 seconds
after: MainLoop get the best worker = 3 (0 sockets) - last debug step
was: servicecheck!
Mar-15-16 09:33:12 [Worker_10000] Error: MainThread stuck for 64 seconds
after: MainLoop get the best worker = 2 (0 sockets) - last debug step
was: servicecheck!
Mar-15-16 10:42:58 [Worker_10000] Error: MainThread stuck for 65 seconds
after: MainLoop get the best worker = 2 (0 sockets) - last debug step
was: servicecheck!
Mar-15-16 11:49:26 [Worker_10000] Error: MainThread stuck for 62 seconds
after: MainLoop get the best worker = 4 (1 sockets) - last debug step
was: servicecheck!
Mar-15-16 12:15:31 [Worker_10000] Error: MainThread stuck for 64 seconds
after: MainLoop get the best worker = 2 (0 sockets) - last debug step
was: servicecheck!
Mar-15-16 12:20:24 [Worker_10000] Error: MainThread stuck for 64 seconds
after: MainLoop get the best worker = 1 (0 sockets) - last debug step
was: servicecheck!
Mar-15-16 19:27:08 [Worker_10000] Error: MainThread stuck for 62 seconds
after: MainLoop get the best worker = 3 (0 sockets) - last debug step
was: servicecheck!
Mar-15-16 20:57:22 [Worker_10000] Error: MainThread stuck for 61 seconds
after: MainLoop get the best worker = 1 (0 sockets) - last debug step
was: servicecheck!
Mar-15-16 22:16:55 [Worker_10000] Error: MainThread stuck for 64 seconds
after: MainLoop get the best worker = 2 ( sockets) - last debug step
was: servicecheck!
Mar-15-16 22:59:52 [Worker_10000] Error: MainThread stuck for 62 seconds
after: MainLoop get the best worker = 4 (0 sockets) - last debug step
was: servicecheck!
Mar-15-16 23:19:02 [Worker_10000] Error: MainThread stuck for 62 seconds
after: MainLoop get the best worker = 2 (0 sockets) - last debug step
was: servicecheck!
Mar-15-16 23:22:49 [Worker_10000] Error: MainThread stuck for 65 seconds
after: MainLoop get the best worker = 1 (0 sockets) - last debug step
was: servicecheck!
Mar-15-16 23:33:24 [Worker_10000] Error: MainThread stuck for 64 seconds
after: MainLoop get the best worker = 3 (0 sockets) - last debug step
was: servicecheck!
Mar-15-16 23:44:11 [Worker_10000] Error: MainThread stuck for 65 seconds
after: MainLoop get the best worker = 3 (0 sockets) - last debug step
was: servicecheck!




------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test






DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally 
privileged and protected in law and are intended solely for the use of the 

individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no 
known virus in this email!
*******************************************************

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to