You can test the connection to the agent by using telnet or using a test from the Management Console.
Testing from the command line:
telnet hostname 5555You should see the following response:
200 HELLO - BuildForge Agent v7.0.1.buildnumber
telnet localhost 5555 username <user name> password <password> cmd ping goYou should see a message like the following:
AUTH: set user account to <user name>If the above tests work but builds are failing, and a test of your server shows a user authentication error, check the pluggable authentication modules (PAM) configuration. If you see a message like the following, proceed to the next step.
AUTH: unable to set user account to <user name>: unknown account (1)
cmd ping goThe output of the telnet session should look similar to this. In particular it should end with RESULT 0 (success). This test was on an agent running on Windows.
300 DATA s 67 AUTH: Running as: [SYSTEM] in domain [NT AUTHORITY] SID Type [User] 300 DATA s 52 AUTH: Running with Privilege: [Lock pages in memory] 300 DATA s 66 AUTH: Running with Privilege: [Adjust memory quotas for a process] 300 DATA s 63 AUTH: Running with Privilege: [Create permanent shared objects] 300 DATA s 46 AUTH: Running with Privilege: [Debug programs] 300 DATA s 56 AUTH: Running with Privilege: [Bypass traverse checking] 300 DATA s 61 AUTH: Running with Privilege: [Back up files and directories] 300 DATA s 54 AUTH: Running with Privilege: [Change the system time] 300 DATA s 68 AUTH: Running with Privilege: [Remove computer from docking station] 300 DATA s 73 AUTH: Running with Privilege: [Impersonate a client after authentication] 300 HEARTBEAT 1 300 DATA s 16 PLAT: Windows XP 250 RESULT 0 PING: internal loopback test complete 260 EOR
Testing from the Management Console:
After the test, the results are available in the Test Results tab.
Could not open a connection to host on port 5555Either the Management Console is unable to connect to the host or the agent is not functioning.