BuildForge job is always going into Waiting state even after setting all the system queue and project parameters
We have defined a project with appropriate steps in it and also a selector in BuildForge but when we are running that project it always goes in to waiting state.
We have also written dot command to allocate and release semaphore in project step's command line section and also run queue size has been set to 10.
Please suggest how to proceed ? |
7 answers
Try a test project with the selector. See if it runs, that would rule out a problem with the selector waiting for a inaccessible server.
If the job is in the waiting state, then it can't be a semaphore problem since it has to run first to attempt to get the token. The run queue size is not important here unless you have 10 other projects running at the same time, but the Run Limit on the project could be if there is another instance of the project that is running. ~Spencer
|
Hi Spencer,
Project's step contains a simple "touch file" command and that too not running, job is still going in Waiting state.
Any idea what we can do to proceed ?
Thanks, Mangesh |
Actually now that I think about it, its more likely that the engine is not running. Verify that your engine process is running. If the app server is hosted separately, then you would be able to test the server and queue the build, but it wouldn't run without the engine running.
~Spencer
|
Hi Spencer,
But I am able to start the management console and able to login to console, doesnt that mean engine is running ? Is there any another way to check whether engine is running or not.
Thanks, Mangesh |
Seeing and logging into the console is not affected by the engine running or not. It only means that the web application is running. Check if the buildforge.pl or .exe is present on the server. Alternatively try starting the engine in the foreground and running the build again and see if the build is picked up.
~Spencer
|
Yes, BF management console is on Windows Server and buildforge.exe is present there. I have started the engine in foreground and its giving me below error :
Throwable occurred: com.buildforge.services.common.api.APIException: Engine license count exceeded (or missing license)
It looks to be license issue and thats why engine is not properly coming up, but we have license server which is serving the license we have imported in it and also refered the license server name in BF management console(Administration -> system -> license server).
Please let me know whether jobs may go in waiting state because of this reason ? If yes, then how to fix this license issue ?
Thanks, Mangesh |
Your foreground should have something like:
7/13/2012 9:43:06 AM: CRRBF0579I: 6808: LicMgr: Defect Adaptors are enabled.
7/13/2012 9:43:06 AM: CRRBF1102I: 6808: LicMgr: Packaging Adaptors are enabled.
7/13/2012 9:43:06 AM: CRRBF1992I: 6808: LicMgr: Test Adaptors are enabled.
7/13/2012 9:43:06 AM: CRRBF0378I: 6808: LicMgr: Multiple database support is ena
bled.
7/13/2012 9:43:06 AM: CRRBF0507I: 6808: LicMgr: Server clusters are enabled.
7/13/2012 9:43:06 AM: CRRBF0801I: 6808: LicMgr: Enterprise license found.
7/13/2012 9:43:06 AM: CRRBF0997I: 6808: LicMgr: Multiplatform support is enabled
.
7/13/2012 9:43:06 AM: CRRBF0428I: 6808: LicMgr: BOM generation is enabled.
7/13/2012 9:43:06 AM: CRRBF1255I: 6808: LicMgr: Production mode server.
7/13/2012 9:43:06 AM: CRRBF1009I: 6808: LicMgr: Manifests are enabled.
7/13/2012 9:43:06 AM: CRRBF1349I: 6808: LicMgr: Reports are enabled.
7/13/2012 9:43:06 AM: CRRBF1564I: 6808: LicMgr: Reflectors are enabled.
7/13/2012 9:43:06 AM: CRRBF0573I: 6808: LicMgr: [916] days remaining on license.
That will state that the license has been accepted. If that does not exist, then you will need to open a PMR to address the license issue.
|
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.