ESP jobs status "Agent notified"
search cancel

ESP jobs status "Agent notified"

book

Article ID: 420527

calendar_today

Updated On:

Products

ESP Workload Automation

Issue/Introduction

ESP jobs that are going to agent stay in "Agent notified" state. The agent is shown active from the agent monitor or page mode command (OPER AGENT agent_name LIST) and does the interval check every 5 minutes. 

OPER AGENT agent_name LIST

agent_name                                                            
 Address ###.##.##.##                                           
 Port 7520                                                            
 OS (AIX for ppc64)                                                   
 Release (12.1)                                                       
 Build (7092, Service Pack 00, Maintenance Level 00)                  
 CommType TCP/IP, Charcode ASCII                                      
 Encryption(AES), Keyname(#####)                                
 Retry Interval 12000                                                 
 Owned by  ###.##.##.##                                             
 Active                                                               
  Last send at 03.20.12 on TUESDAY DECEMBER 2ND, 2025                 
  Messages sent 7, queued 0          

R for Resubmit of the job does not help and with every next try the "Messages sent" counter is increasing but the ESP jobs are still in the "Agent notified" status.

How do we get the jobs out of agent notified status?

Cause

The agent suddenly stopped working.

According to the "runner_os_component.log" file from the agent, it is visible that the task has been received and executed by the agent, but nothing has been sent to the "transmitter.log" and to the WA ESP. 

 

Resolution

The problem appears to be that the agent cannot create spool files, most likely because its spool directory is full or the Operating System is preventing the creation of more files.

Currently, spool cleanup is disabled in the agentparm.txt file (runnerplugin.spool.clean.enable=false).

To fix this and prevent future occurrences, please enable spool cleanup in the agentparm.txt file and restart the agent. For example, update the agentparm.txt with these parameters:

runnerplugin.spool.clean.enable=true
runnerplugin.spool.expire=10D
runnerplugin.spool.sleep=24H
 
This configuration will automatically delete spool files older than 10 days, with the cleanup check performed every 24 hours. You can modify the spool file expiration time as needed.
 
For further details on spool cleanup and other related parameters, please refer to the Agent documentation - Configure the Agent to Clear Spool Files Automatically.