Checks not running

ataubeataube
edited November 2012 in Monitoring Software v12 and lower
We just recently upgraded to the latest version of Serverscheck (9.1.0). Since we upgraded, the checks have not been running. What should I look at first to investigate the issue?

Comments

  • ataubeataube
    Also, when I try to run Serverscheck in debug mode as described in the WIKI, I receive the following error message:



    Free to wrong pool 7c65d658 not 1fc3dd0 during global destruction.



    This error occurs after launching monitoring_manager.exe>debug.txt from an administrative command prompt
  • AdministratorAdministrator
    Run following command

    monitoring_thread2.exe > debug.txt and reply with the content of the debug file
  • ataubeataube
    I get the same error message:



    Free to wrong pool 7c6056a0 not 1fb3cf8 during global destruction.



    START LOG:



    # S-X Mon Nov 12 12:49:09 2012 Starting Monitoring SThread

    # S-X Mon Nov 12 12:49:09 2012 monitoring_thread2 instances allowed: 1

    # S-X Mon Nov 12 12:49:09 2012 monitoring_thread2 instances counted: 1

    # S-X Mon Nov 12 12:49:09 2012

    # S-X Mon Nov 12 12:49:09 2012 Confirmed running alone

    killapp: 0

    # S-X Mon Nov 12 12:49:29 2012 BUSINESS 500 9.0.17 (40 / 500)

    # S-X Mon Nov 12 12:49:29 2012 database logging inactive

    # S-X Mon Nov 12 12:49:29 2012 threads: 49

    # S-X Mon Nov 12 12:49:29 2012 Time out for rules set to: 60

    # S-X Mon Nov 12 12:49:29 2012 creating thread 0 ->

    # S-X Mon Nov 12 12:49:29 2012 creating thread 1 ->

    # S-X Mon Nov 12 12:49:29 2012 creating thread 2 ->

    # S-X Mon Nov 12 12:49:30 2012 creating thread 3 ->

    # S-X Mon Nov 12 12:49:30 2012 creating thread 4 ->

    # S-X Mon Nov 12 12:49:30 2012 creating thread 5 ->

    # S-X Mon Nov 12 12:49:30 2012 creating thread 6 ->

    # S-X Mon Nov 12 12:49:30 2012 creating thread 7 ->

    # S-X Mon Nov 12 12:49:31 2012 creating thread 8 ->

    # S-X Mon Nov 12 12:49:31 2012 creating thread 9 ->

    # S-X Mon Nov 12 12:49:31 2012 creating thread 10 ->

    # S-X Mon Nov 12 12:49:31 2012 creating thread 11 ->

    # S-X Mon Nov 12 12:49:31 2012 creating thread 12 ->

    # S-X Mon Nov 12 12:49:31 2012 creating thread 13 ->

    # S-X Mon Nov 12 12:49:32 2012 creating thread 14 ->

    # S-X Mon Nov 12 12:49:32 2012 creating thread 15 ->

    # S-X Mon Nov 12 12:49:32 2012 creating thread 16 ->

    # S-X Mon Nov 12 12:49:32 2012 creating thread 17 ->

    # S-X Mon Nov 12 12:49:32 2012 creating thread 18 ->

    # S-X Mon Nov 12 12:49:33 2012 creating thread 19 ->

    # S-X Mon Nov 12 12:49:33 2012 creating thread 20 ->

    # S-X Mon Nov 12 12:49:33 2012 creating thread 21 ->

    # S-X Mon Nov 12 12:49:33 2012 creating thread 22 ->

    # S-X Mon Nov 12 12:49:33 2012 creating thread 23 ->

    # S-X Mon Nov 12 12:49:33 2012 creating thread 24 ->

    # S-X Mon Nov 12 12:49:34 2012 creating thread 25 ->

    # S-X Mon Nov 12 12:49:34 2012 creating thread 26 ->

    # S-X Mon Nov 12 12:49:34 2012 creating thread 27 ->

    # S-X Mon Nov 12 12:49:34 2012 creating thread 28 ->

    # S-X Mon Nov 12 12:49:34 2012 creating thread 29 ->

    # S-X Mon Nov 12 12:49:34 2012 creating thread 30 ->

    # S-X Mon Nov 12 12:49:35 2012 creating thread 31 ->

    # S-X Mon Nov 12 12:49:35 2012 creating thread 32 ->

    # S-X Mon Nov 12 12:49:35 2012 creating thread 33 ->

    # S-X Mon Nov 12 12:49:35 2012 creating thread 34 ->

    # S-X Mon Nov 12 12:49:35 2012 creating thread 35 ->

    # S-X Mon Nov 12 12:49:35 2012 creating thread 36 ->

    # S-X Mon Nov 12 12:49:36 2012 creating thread 37 ->

    # S-X Mon Nov 12 12:49:36 2012 creating thread 38 ->

    # S-X Mon Nov 12 12:49:36 2012 creating thread 39 ->

    # S-X Mon Nov 12 12:49:36 2012 creating thread 40 ->

    # S-X Mon Nov 12 12:49:36 2012 creating thread 41 ->

    # S-X Mon Nov 12 12:49:37 2012 creating thread 42 ->

    # S-X Mon Nov 12 12:49:37 2012 creating thread 43 ->

    # S-X Mon Nov 12 12:49:37 2012 creating thread 44 ->

    # S-X Mon Nov 12 12:49:37 2012 creating thread 45 ->

    # S-X Mon Nov 12 12:49:37 2012 creating thread 46 ->

    # S-X Mon Nov 12 12:49:38 2012 creating thread 47 ->

    # S-X Mon Nov 12 12:49:38 2012 creating thread 48 ->



    Received KILL signal
  • ataubeataube
    I've just noticed that in the log I just posted, the version is reported as 9.0.17 when it should be 9.1.0.
  • AdministratorAdministrator
    The debug log has been stopped too soon to see any errors.



    You can download the 9.1.0 directly from following url:

    http://upgrade.serverscheck.net/monitoring_software/monitoring_thread2.exe


  • ataubeataube
    I have downloaded the file and now the log shows the new version, but the error is still the same.



    START LOG:



    # S-X Mon Nov 12 13:16:55 2012 Starting Monitoring SThread

    # S-X Mon Nov 12 13:16:55 2012 monitoring_thread2 instances allowed: 1

    # S-X Mon Nov 12 13:16:56 2012 monitoring_thread2 instances counted: 1

    # S-X Mon Nov 12 13:16:56 2012

    # S-X Mon Nov 12 13:16:56 2012 Confirmed running alone

    killapp: 0

    # S-X Mon Nov 12 13:17:15 2012 BUSINESS 500 9.1.0 (40 / 500)

    # S-X Mon Nov 12 13:17:15 2012 database logging inactive

    # S-X Mon Nov 12 13:17:15 2012 threads: 49

    # S-X Mon Nov 12 13:17:15 2012 Time out for rules set to: 60

    # S-X Mon Nov 12 13:17:16 2012 creating thread 0 ->

    # S-X Mon Nov 12 13:17:16 2012 creating thread 1 ->

    # S-X Mon Nov 12 13:17:16 2012 creating thread 2 ->

    # S-X Mon Nov 12 13:17:16 2012 creating thread 3 ->

    # S-X Mon Nov 12 13:17:16 2012 creating thread 4 ->

    # S-X Mon Nov 12 13:17:16 2012 creating thread 5 ->

    # S-X Mon Nov 12 13:17:17 2012 creating thread 6 ->

    # S-X Mon Nov 12 13:17:17 2012 creating thread 7 ->

    # S-X Mon Nov 12 13:17:17 2012 creating thread 8 ->

    # S-X Mon Nov 12 13:17:17 2012 creating thread 9 ->

    # S-X Mon Nov 12 13:17:17 2012 creating thread 10 ->

    # S-X Mon Nov 12 13:17:17 2012 creating thread 11 ->

    # S-X Mon Nov 12 13:17:17 2012 creating thread 12 ->

    # S-X Mon Nov 12 13:17:18 2012 creating thread 13 ->

    # S-X Mon Nov 12 13:17:18 2012 creating thread 14 ->

    # S-X Mon Nov 12 13:17:18 2012 creating thread 15 ->

    # S-X Mon Nov 12 13:17:18 2012 creating thread 16 ->

    # S-X Mon Nov 12 13:17:18 2012 creating thread 17 ->

    # S-X Mon Nov 12 13:17:19 2012 creating thread 18 ->

    # S-X Mon Nov 12 13:17:19 2012 creating thread 19 ->

    # S-X Mon Nov 12 13:17:19 2012 creating thread 20 ->

    # S-X Mon Nov 12 13:17:19 2012 creating thread 21 ->

    # S-X Mon Nov 12 13:17:19 2012 creating thread 22 ->

    # S-X Mon Nov 12 13:17:19 2012 creating thread 23 ->

    # S-X Mon Nov 12 13:17:19 2012 creating thread 24 ->

    # S-X Mon Nov 12 13:17:20 2012 creating thread 25 ->

    # S-X Mon Nov 12 13:17:20 2012 creating thread 26 ->

    # S-X Mon Nov 12 13:17:20 2012 creating thread 27 ->

    # S-X Mon Nov 12 13:17:20 2012 creating thread 28 ->

    # S-X Mon Nov 12 13:17:20 2012 creating thread 29 ->

    # S-X Mon Nov 12 13:17:20 2012 creating thread 30 ->

    # S-X Mon Nov 12 13:17:21 2012 creating thread 31 ->

    # S-X Mon Nov 12 13:17:21 2012 creating thread 32 ->

    # S-X Mon Nov 12 13:17:21 2012 creating thread 33 ->

    # S-X Mon Nov 12 13:17:21 2012 creating thread 34 ->

    # S-X Mon Nov 12 13:17:21 2012 creating thread 35 ->

    # S-X Mon Nov 12 13:17:21 2012 creating thread 36 ->

    # S-X Mon Nov 12 13:17:22 2012 creating thread 37 ->

    # S-X Mon Nov 12 13:17:22 2012 creating thread 38 ->

    # S-X Mon Nov 12 13:17:22 2012 creating thread 39 ->

    # S-X Mon Nov 12 13:17:22 2012 creating thread 40 ->

    # S-X Mon Nov 12 13:17:22 2012 creating thread 41 ->

    # S-X Mon Nov 12 13:17:23 2012 creating thread 42 ->

    # S-X Mon Nov 12 13:17:23 2012 creating thread 43 ->

    # S-X Mon Nov 12 13:17:23 2012 creating thread 44 ->

    # S-X Mon Nov 12 13:17:23 2012 creating thread 45 ->

    # S-X Mon Nov 12 13:17:23 2012 creating thread 46 ->

    # S-X Mon Nov 12 13:17:23 2012 creating thread 47 ->

    # S-X Mon Nov 12 13:17:24 2012 creating thread 48 ->



    Received KILL signal





    If the monitoring_thread2.exe file was not the correct version, maybe there are others that did not update properly?
  • AdministratorAdministrator
    so after 13:17 nothing else happened?
  • ataubeataube
    With previous versions, I had the monitoring performance set at FULL SPEED. With the new version, it will not run at the 49 thread full speed. I have set it to 45 threads and it is working as expected. Can you tell me what might cause this?
  • ataubeataube
    After 13:17, a windows box comes up saying that the application has experienced a problem and must close. The application error previously listed comes up in the command prompt window.



    Free to wrong pool 7c6056a0 not 1fb3cf8 during global destruction.



    After that, nothing gets added to the log unless I click the close application button, which adds "Received KILL Signal".
  • AdministratorAdministrator
    Just to clarify: After the update, all your checks now won't work?
This discussion has been closed.