BuildForge job is always going into Waiting state even after setting all the system queue and project parameters

Hi Spencer,

I am trying to run the test project itself with a simple selector which is having the accessible server. I have tested the server connectivity from management console and it passes successfully without any issue so ultimately selector also shouldn't have any problem running a command on that server.

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

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

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)
 at com.buildforge.services.server.api.auth.EngineCredentials.use(EngineCredentials.java:139)
 at com.buildforge.services.server.api.auth.EngineCredentials.get(EngineCredentials.java:87)
 at com.buildforge.services.server.api.AuthContext.becomeEngine(AuthContext.java:1117)

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