To troubleshoot an agent on UNIX, Linux, or MacOS, try these procedures:
- Run bfagent from a shell. The correct response is similar
to this message:
200 HELLO - Build Forge Agent v7.0.1.122
If
you receive a message similar to the example and there are shared
library problems, you will receive messages regarding those problems.
You can resolve most shared library problems by setting the path correctly.
- Check that the agent is listening. Use the following command (assuming
that the port is the default, 5555):
telnet localhost 5555
A
200 HELLO response indicates that the agent is listening. If you do
not get this response, check your systems network configuration. Verify
that the inetd configuration is correct, or check with your
Linux or UNIX system administrator.
- Check authentication. Issue the following commands, using your
login credentials:
telnet localhost 5555
username <user name>
password <password>
cmd ping
go
A message similar to the following message indicates
that the authentication is working correctly: AUTH: set user account to <user name>
If
the previous 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 similar to the following
message, proceed to the next procedure. AUTH: unable to set user account to user name: unknown account (1)
- Check the PAM configuration. Problems with the PAM configuration
are common issues on AIX platforms. Depending on your operating system,
PAM is configured in one of two ways: with a line in the pam.conf file
or with a file in the pam.d directory.
Tip: Solaris
10 is an exception in the following procedure: Delete any lines that
specify a module of
pam_dial_auth, for example
pam_dial_auth.so.1.
Agent authentication does not work if that module is included.
- Verify that /etc/pam.conf exists. If it does not, go to the instructions
for pam.d later in this topic. If the file does exist, continue to
the next step.
- In the file, create an entry for bfagent.
- Copy the lines for another application, for example, sshd or login,
and then substitute bfagent for the [application] field.
[application] [when] [mode] [module]
The
fields are as follows:
- After you set up the PAM entries, try to log in again as described
in step 3.
- For more information, see PAM documentation at http://www.sun.com/software/solaris/pam.
- To troubleshoot PAM which is configured in pam.d:
- Find the /etc/pam.d directory and note that it contains several
fills, each named for an application. Within each file, each line
is formatted this way:
[when] [mode] [module]
- Copying a file from another application, such as sshd or login,
and rename it bfagent.
- After you set up the PAM entries, try to log in again as described
in step 3.
- For more information, see PAM documentation at http://www.sun.com/software/solaris/pam/ .