It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×6,020
×1,192

question asked: Sep 17 '13, 3:23 a.m.
question was seen: 5,469 times
last updated: Sep 17 '13, 8:19 a.m.

Related questions

build forge CRRBF0101I error message. Any attempt to run a job gives a error message job completed-failed-died

0
pratibha gupta (15●1●12●15) | asked Sep 17 '13, 3:23 a.m.

output of catalia.out

Sep 17, 2013 9:21:20 AM com.buildforge.services.server.api.AuthContext login
WARNING: Login failed - user account is locked
Sep 17, 2013 9:21:20 AM com.buildforge.services.server.api.APIServerConnection process
WARNING: !!!
Throwable occurred: com.buildforge.services.common.api.APIException: API: Authentication Error.
        at com.buildforge.services.server.api.AuthContext.login(AuthContext.java:786)
        at com.buildforge.services.server.api.commands.AuthCommands.doLoginUser(AuthCommands.java:168)
        at com.buildforge.services.server.api.commands.AuthCommands.doLoginImpl(AuthCommands.java:339)
        at com.buildforge.services.server.api.commands.AuthCommands.doLogin(AuthCommands.java:296)
        at com.buildforge.services.server.api.commands.AuthCommands.invoke(AuthCommands.java:95)
        at com.buildforge.services.server.api.APICommandProcessor.process(APICommandProcessor.java:290)
        at com.buildforge.services.server.api.APIServerConnection.handleRequest(APIServerConnection.java:258)
        at com.buildforge.services.server.api.APIServerConnection.process(APIServerConnection.java:172)
        at com.buildforge.services.server.dispatch.callback.BufferedConnection.run(BufferedConnection.java:246)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919)
        at java.lang.Thread.run(Thread.java:736)
Sep 17, 2013 9:21:20 AM com.buildforge.services.server.manager.SessionManager getAuthContext
WARNING: Login failed - token is for an external session
Sep 17, 2013 9:21:20 AM com.buildforge.services.server.api.APIServerConnection process
WARNING: !!!
Throwable occurred: com.buildforge.services.common.api.APIException: API: Authentication Error.
        at com.buildforge.services.server.api.APIServerConnection.setAuthToken(APIServerConnection.java:484)
        at com.buildforge.services.server.api.commands.AuthCommands.doLoginImpl(AuthCommands.java:317)
        at com.buildforge.services.server.api.commands.AuthCommands.doLogin(AuthCommands.java:296)
        at com.buildforge.services.server.api.commands.AuthCommands.invoke(AuthCommands.java:95)
        at com.buildforge.services.server.api.APICommandProcessor.process(APICommandProcessor.java:290)
        at com.buildforge.services.server.api.APIServerConnection.handleRequest(APIServerConnection.java:258)
        at com.buildforge.services.server.api.APIServerConnection.process(APIServerConnection.java:172)
        at com.buildforge.services.server.dispatch.callback.BufferedConnection.run(BufferedConnection.java:246)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919)
        at java.lang.Thread.run(Thread.java:736)
Sep 17, 2013 9:21:20 AM com.buildforge.services.server.api.AuthContext login
WARNING: Login failed - user account is locked
Sep 17, 2013 9:21:20 AM com.buildforge.services.server.api.APIServerConnection process
WARNING: !!!
Throwable occurred: com.buildforge.services.common.api.APIException: API: Authentication Error.
        at com.buildforge.services.server.api.AuthContext.login(AuthContext.java:786)
        at com.buildforge.services.server.api.commands.AuthCommands.doLoginUser(AuthCommands.java:168)
        at com.buildforge.services.server.api.commands.AuthCommands.doLoginImpl(AuthCommands.java:339)
        at com.buildforge.services.server.api.commands.AuthCommands.doLogin(AuthCommands.java:296)
        at com.buildforge.services.server.api.commands.AuthCommands.invoke(AuthCommands.java:95)
        at com.buildforge.services.server.api.APICommandProcessor.process(APICommandProcessor.java:290)
        at com.buildforge.services.server.api.APIServerConnection.handleRequest(APIServerConnection.java:258)
        at com.buildforge.services.server.api.APIServerConnection.process(APIServerConnection.java:172)
        at com.buildforge.services.server.dispatch.callback.BufferedConnection.run(BufferedConnection.java:246)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919)
        at java.lang.Thread.run(Thread.java:736)

Comments
pratibha gupta commented Sep 17 '13, 5:59 a.m.

CRRBF1388I: 5162: Services: Error Connecting to Build Forge Services [BuildForge::Ex::IOException: Unable to connect to sdlc3.online.vodafone.com:3966: Connection refused

Error message in db.log

One answer

Most liked answers ↑|Newest answers|Oldest answers

2
permanent link
Ryan Ruscett (1.0k●4●13) | answered Sep 17 '13, 8:19 a.m.
Hello,


An API user creates a session within Build Forge. This use is also subject to being locked out. I would log in as root, switch to the API user and change the password by typing in a new password, verifying that new password and saving the user. This should work for you. If not, please let us know. Also make sure the user is an API user selected form the User preferences page.

As far as the connection refused. Many types of connections can be refused for many different reasons. Here are some of the common reasons a connection is refused.

- The current port is not available, whether because it's already being used or not being reached. You can nestat -o | findstr <port> to determine port availability.

- There is a firewall that does not have a rule set up for the desired port and is refusing the connection.

If BF was working before, it could have been that it was restarted, and one or more of the process did not fully shut down causing a port to still be in use.

I would restart the system, ensure all BF process have shut down including bfproject, httpd etc.  Double check all the ports on the system for availability, and you could go as far as to turn off the fire wall just for test purposes. Then log in as root, switch to the user in question and reset the password.

Let us know if that helps.

Thanks!

Your answer

Register or to post 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.