About the status of Queue records

bonsai
Mega Sage

‎07-17-2022 07:35 PM

I run a powershell that resides on the MID server in a UI action.

I am creating a record in the "ecc_queue" table for execution on the MID server.

After creating the record, the powershell of the MID server runs normally.

However, the status remains "processing".
Is the way to solve this a standard feature?

I'm thinking of running a REST API from the MID server's powershell to change the status, but how do other "ecc_queue" records change to "processed"?

 

find_real_file.png

Preview file
64 KB
0 Helpfuls
  • 961 Views
3 REPLIES 3

Tom Sienkiewicz
Mega Sage

‎07-17-2022 11:41 PM

Is this an output or input record? I assume output.

The state should automatically change to processed, one the script has been run. If this is not happening, I would suggest to review the script and the MID server logs for any errors.

You can increase the logging level by adding the parameter to your MID server config in SN: mid.log.level, value: debug. Then go to the agent folder on remote server and check the log file. Also ensure your command does not prompt for a passowrd etc.

You can also check any custom business rules running on the ecc_queue table, something could be preventing the update.

bonsai
Mega Sage
In response to Tom Sienkiewicz

‎07-18-2022 08:07 AM

It is "output".

The following contents were recorded in the log file "agent0.log.0" of the MID server.
Can you see the cause by looking at this?

 

07/18/22 23:59:01 (469) Worker-Interactive:HeartbeatProbe-478cb20197701110e772b846f053afd2 Worker starting: HeartbeatProbe
07/18/22 23:59:01 (469) Worker-Interactive:HeartbeatProbe-478cb20197701110e772b846f053afd2 Probing heartbeatprobe
07/18/22 23:59:01 (469) Worker-Interactive:HeartbeatProbe-478cb20197701110e772b846f053afd2 Finished firing the heartbeatprobe
07/18/22 23:59:01 (469) Worker-Interactive:HeartbeatProbe-478cb20197701110e772b846f053afd2 Enqueuing: C:\ServiceNow MID Server test_mid\agent\work\monitors\ECCSender\output_0\ecc_queue.478cb20197701110e772b846f053afd2.xml
07/18/22 23:59:01 (483) Worker-Interactive:HeartbeatProbe-478cb20197701110e772b846f053afd2 Worker completed: HeartbeatProbe time: 0:00:00.000
07/18/22 23:59:01 (530) ECCSender.1 Sending ecc_queue.478cb20197701110e772b846f053afd2.xml
07/18/22 23:59:51 (714) LogStatusMonitor.60 2022-07-18T14:59:51.714Z, stats threads: 122, memory max: 910.0mb, allocated: 328.0mb, used: 59.0mb, standard.queued: 0 probes, standard.processing: 15 probes, expedited.queued: 0 probes, expedited.processing: 0 probes, interactive.queued: 0 probes, interactive.processing: 0 probes
0 Helpfuls

Tom Sienkiewicz
Mega Sage
In response to bonsai

‎07-18-2022 11:32 PM

Hi, in the log you posted I do not see any messages related to the actual command you are running, just the heartbeat.

There seems to be a rather big delay after the ECCSender, so perhaps there is some timeout happening. But from the logs above  I'm not sure, sorry...

0 Helpfuls