HelloWorld Project Job sits on waiting status
I am new to BF, and trying to get the HelloWorld project working.
We are using two Windows 2003 servers, one has the BF mgmt console while the other has the BF agent. We are running BF MGMT console using WebSphere App Server. Anyhow, when I try to run the HelloWorld project, the Job sits on waiting status forever. I cant seem to see anything in the WebSphere logs to suggest any exceptions or complications with the setup. Also, I am able to successfully do a "Test Connection" on the agent server. So, I am not sure where the problem is or where to look/debug. Any help would be appreciated. |
8 answers
generally this is because there isn't a console license available. Without a license, the job will just sit in "waiting".
If you have a valid console license on your license server (check the administration/users page to see if it reports the correct number of licensed users) then open a PMR to resolve the issue. |
generally this is because there isn't a console license available. Without a license, the job will just sit in "waiting". The License server runs on the same server as the MGMT console. I checked the license server to see what it has: 1 - floating Standard Edition Server license 15 - floating Standard Edition User licenses When I go to the Administration/Users page, it shows on the top of the page, 1 of 15 licenses used. This seams to be working. Anything else that this could be related to? |
generally this is because there isn't a console license available. Without a license, the job will just sit in "waiting". The License server runs on the same server as the MGMT console. I checked the license server to see what it has: 1 - floating Standard Edition Server license 15 - floating Standard Edition User licenses When I go to the Administration/Users page, it shows on the top of the page, 1 of 15 licenses used. This seams to be working. Anything else that this could be related to? Hi, Since you are using WebSphere for the services layer, I'm wondering if there is a chance that the buildforge process is not getting started properly. For Windows 2003, you should see a buildforge.exe process in the task list. It is the buildforge process that polls the database for jobs that are ready to be processed and starts them. One other thing to check would be that the system configuration 'Pause Build Forge Engine' is set to 'No'. Brent Ulbricht Developer/Lead - RTC Build |
generally this is because there isn't a console license available. Without a license, the job will just sit in "waiting". The License server runs on the same server as the MGMT console. I checked the license server to see what it has: 1 - floating Standard Edition Server license 15 - floating Standard Edition User licenses When I go to the Administration/Users page, it shows on the top of the page, 1 of 15 licenses used. This seams to be working. Anything else that this could be related to? Hi, Since you are using WebSphere for the services layer, I'm wondering if there is a chance that the buildforge process is not getting started properly. For Windows 2003, you should see a buildforge.exe process in the task list. It is the buildforge process that polls the database for jobs that are ready to be processed and starts them. One other thing to check would be that the system configuration 'Pause Build Forge Engine' is set to 'No'. Brent Ulbricht Developer/Lead - RTC Build I checked for the buildforge.exe process, could not find it in the task list. How can I troubleshoot this further? As for 'Pause Build Forge Engine', the value is 'No'. |
Hi, I have a couple of additional questions related to install/start that may help further troubleshooting. 1) How did you install Build Forge - did you choose the option to install your own application server? 2) Did you choose to install as a service? 3) How are you starting Build Forge? Brent Ulbricht Developer/Lead - RTC Build |
Hi, I have a couple of additional questions related to install/start that may help further troubleshooting. 1) How did you install Build Forge - did you choose the option to install your own application server? 2) Did you choose to install as a service? 3) How are you starting Build Forge? Brent Ulbricht Developer/Lead - RTC Build I got it to work now. All I did was launch the BF engine from the command line "BFEngine.exe -d", and then all pending jobs completed and any new ones I created. Then, I shutdown the command line session, and re-tried to start the Windows service, and this time it worked. Really weird, but perhaps the command line approach primed or tweaked something in the environment that the Service couldnt. |
I have installed Build Forge console manager and agent on the same linux box. I created a sample Hello World project, created the server authentication, defined the server, could successfully test the connection but when I run the project, I noticed the console message 'job started...' on the let window but the status is always Waiting.
I started the build Forge by using this, /opt/buildforge/server/start start and agent is running as service netstat -anpe | grep 5556 tcp 0 0 :::5556 :::* LISTEN 0 36733 16685/xinetd I have valid license to the builds. Please let me know what could be the possible issues. I could not find any log file that I can use to trace the problem. |
|
I found the problem myself. I had started the build forge console by running this,
/opt/buildforge/server/start start whereas I did not run this (guess engine was not running) I did this to resolve the issue /opt/buildforge/rc/buildforge start and this resolved the problem. Thanks Praveen |
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.