InTime Agents

Why are Agents not accepting the job?

74 views May 23, 2016 September 15, 2020 plunify 0

Cause:

This may be caused by various reason, with the most common reason being toolchain version mismatches. The Agent is configured with the wrong toolchain or the global toolchain has wrong path(s) such that the Agent(s) cannot find the toolchain.

Resolution:

In the Private Cloud Console, run the following commands.

user> .job
+-----+-----------------------+-------+---------+------------+-------+--------+----------------+-----------+
| NO. | CLIENTID              | JOBID | P.JOBID | USERID     | START | FINISH | TIME           | STATUS    |
+-----+-----------------------+-------+---------+------------+-------+--------+----------------+-----------+
| 1   | selftest_000C298F05BC | 470   | 0       | intimeuser | 19:14 |        | 08m:16s        | QUEUED    |
+-----+-----------------------+-------+---------+------------+-------+--------+----------------+-----------+
1. Why is job 470 still in the queue? Next, find out if the Agent is free...

user> .status
+-----+-----------------------+-------+------------+--------+-------+--------+--------+-----------------+
| NO. | CLIENTID              | JOBID | USERID     | STATUS | ALIVE | B.LIST | MARKED | LAST_HEARTBEAT  |
+-----+-----------------------+-------+------------+--------+-------+--------+--------+-----------------+
| 1   | selftest_000C298F05BC |       | intimeuser | FREE   | YES   | NO     | NIL    | 19:23 (00m:10s) |
+-----+-----------------------+-------+------------+--------+-------+--------+--------+-----------------+
2. The Agent is free, so find out the toolchain used to submit the job.

user> .job.more
+-----+-----------------------+-------+---------+------------+------+---------+-------+--------+------+---------+
| NO. | CLIENTID              | JOBID | P.JOBID | USERID     | RUNS | MAXTIME | LIMIT | VENDOR | TOOL | VERSION |
+-----+-----------------------+-------+---------+------------+------+---------+-------+--------+------+---------+
| 1   | selftest_000C298F05BC | 470   | 0       | intimeuser | 3    | 36      | 3     | Xilinx | ISE  | 14.7    |
+-----+-----------------------+-------+---------+------------+------+---------+-------+--------+------+---------+
3. The toolchain used is ISE 14.7. Next, find out the Agent's supported toolchain(s)?

user> .toolchain
+-----+-----------------------+-------+------------+--------+-------+-------+--------+-----------+-----------+
| NO. | CLIENTID              | JOBID | USERID     | STATUS | ALIVE | COUNT | VENDOR | TOOL      | VERSION   |
+-----+-----------------------+-------+------------+--------+-------+-------+--------+-----------+-----------+
| 1   | selftest_000C298F05BC |       | intimeuser | FREE   | YES   | 2     | ALTERA | QUARTUSII | 12.0.0    |
|     |                       |       |            |        |       |       | XILINX | ISE       | 14.3      |
+-----+-----------------------+-------+------------+--------+-------+-------+--------+-----------+-----------+
4. It seems that the Agent is not configured with the required toolchain.

user> .log=470
HH:mm:ss | UUID     | CLIENTID                  | STEP | MESSAGE
14:36:28 | A-2DD134 | selftest_000C298F05BC     | PASS | Submitting a new job, 470
14:36:40 | A-FE089D | selftest_000C298F05BC     | PASS | Uploading project file.
14:53:03 | B-NTC2NJ | selftest_000C298F05BC     | FAIL | Mismatching toolchain
14:53:44 | B-YZDKYW | selftest_000C298F05BC     | FAIL | Mismatching toolchain

5. Lastly, the log command has confirmed that there was a mismatch in the toolchain for job 470.

Cause:

Another cause would be the MATCHUSER_FLAG. When MATCHUSER_FLAG is YES, jobs will be assigned to the agents started by the same user who submitted the job.

Resolution:

In the Private Cloud Console, run the following commands.

admin> .server.properties
+-----+------------+-------------------------+------------------------------------+
| NO. | READ/WRITE | KEY                     | VALUE                              |
+-----+------------+-------------------------+------------------------------------+
...
| 14  | R/W        | MATCHUSER_FLAG          | YES                                |
...

1. The property value is set to YES.

admin> .server.properties.set.MATCHUSER_FLAG=NO

2. Set the property value to NO.

Applies to:

  • Linux Operating System
  • Windows Operating System

Knowledge Base ID: 4003 - Last Review: May 21, 2014 - Revision: 1.0