Server status = "Checking"

[Guest]

All my agents' status is checking. This has been going on for over 4 hours. Any idea what would cause this?

Product: BuildMaster
Version: 4.2.8

[Guest]

The most likely cause is that there's a problem with multiple agents that is unfortunately halting the agent information request. Since this is done in parallel, the failure could happen at any time.

Since the "Checking" status is simply stored in a database field and does not represent the immediate live status, it's worth verifying if the agents are actually in a checking state. If you select the server and see a green icon for the live status, then it may just be a display issue on the overview page. You can verify this also by querying the ServerStatus_Code column in the BuildMaster database directly (SELECT * FROM Servers).

Other steps to try:

• restart the BuildMaster Windows service
• restart the web application, i.e. either restart the INEDOBMWEBSRV service or recycle the IIS application pool that is hosting BuildMaster

If those don't appear to help, try de-activating all the servers and enabling them one-by-one to determine which one is causing the issue. You should also verify that the agent versions match the BuildMaster server version. Agents that are newer than the server version will result in an ERROR status.

[Guest]

Thanks for the info. I think our issue is coming from having SSL running.

I was able to resolve the continuous "checking" issue by doing the following:

1. ended the agent service on all servers
2. remove the SSL line in the agent config (I had 3 agents running SSL)
3. made all agents inactive in server admin
4. unchecked SSL on the agent in server admin
   This stopped all agents.

Then I started 1 agent at a time:

1. started the agent service on the server
2. made agent active in server admin
   I repeated this for each agent/server, now all agents are at a "ready" status.

There must be something going on with my certs... I will be digging into that aspect next.

[Guest]

For reference, this also happened on another user's machine, and the following entry was found in the event log around the same time:

Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.

DETAIL - 
 3 user registry handles leaked from \Registry\User\S-1-5-21-1409082233-789336058-1343024091-27055:
Process 2940 (\Device\HarddiskVolume3\BuildMasterAgent\Agent\_tmp\bmtcpagent.exe) has opened key \REGISTRY\USER\S-1-5-21-1409082233-789336058-1343024091-27055
Process 4388 (\Device\HarddiskVolume2\Windows\System32\conhost.exe) has opened key \REGISTRY\USER\S-1-5-21-1409082233-789336058-1343024091-27055\Control Panel\International
Process 2940 (\Device\HarddiskVolume3\BuildMasterAgent\Agent\_tmp\bmtcpagent.exe) has opened key \REGISTRY\USER\S-1-5-21-1409082233-789336058-1343024091-27055\Control Panel\International