nable to set user account to unknown account error
We get the following error on a recurring, but irregular basis. Rerunning the job a few minutes later resolves the problem. However, the issue generates a lot of help calls. Anyone have a clue as to what the cause and/or resolution might be?
10 10/12/10 11:46AM AUTH Unable to set user account to unknown account (bfadmin) Please note that the "unknown account" referred to in by the BuildForge error message is indeed known to the buildforge console and the buildforge server. Thanks, Jonas |
4 answers
Is "bfadmin" an OS user on the agent system? Are you starting the agent with the root ID so it can auth "bfadmin" to the OS? The error is some kind of Auth error on the agent system so make sure that OS identity is correct.
Regards, Pete Build Forge/Team Build Developer We get the following error on a recurring, but irregular basis. Rerunning the job a few minutes later resolves the problem. However, the issue generates a lot of help calls. Anyone have a clue as to what the cause and/or resolution might be? |
|
bfadmin is on OS user on the agent system, and the agent is starting with the root ID. Most times, there are no problems, but somewhere between 1 and 2 percent of the time a user will get this error.
It is a commonly run job that we have written to deploy applications to our WAS test environment, so we have multiple users running it multiple times per day. Thus, even 1% creates several trouble tickets per week. Is "bfadmin" an OS user on the agent system? Are you starting the agent with the root ID so it can auth "bfadmin" to the OS? The error is some kind of Auth error on the agent system so make sure that OS identity is correct. We get the following error on a recurring, but irregular basis. Rerunning the job a few minutes later resolves the problem. However, the issue generates a lot of help calls. Anyone have a clue as to what the cause and/or resolution might be? |
|
Jonas,
Here's some info from one of our Agent experts. The agent uses PAM to authenticate to the OS. It could be that a setting in PAM is causing it to refuse authentications past a certain rate or to only allow a certain number of concurrent instances of a given application to authenticate. PAM should be logging its information somewhere, but the location depends on the OS. Generally it will be in something like /var/log/auth /var/log/security /var/log/messages /var/log/system or somesuch. Once you find it, the reason for the problem will probably show up there. In any case, the agent wouldn't decide for itself to disallow the login; it has to be the OS that's telling us "no." Hope this helps. Regards, Pete bfadmin is on OS user on the agent system, and the agent is starting with the root ID. Most times, there are no problems, but somewhere between 1 and 2 percent of the time a user will get this error. Is "bfadmin" an OS user on the agent system? Are you starting the agent with the root ID so it can auth "bfadmin" to the OS? The error is some kind of Auth error on the agent system so make sure that OS identity is correct. We get the following error on a recurring, but irregular basis. Rerunning the job a few minutes later resolves the problem. However, the issue generates a lot of help calls. Anyone have a clue as to what the cause and/or resolution might be? |
|
Thanks Pete,
I will look for the PAM logs. Jonas We get the following error on a recurring, but irregular basis. Rerunning the job a few minutes later resolves the problem. However, the issue generates a lot of help calls. Anyone have a clue as to what the cause and/or resolution might be? |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.