Palo Alto Networks firewalls: Job(s) stuck in pending
Notice: This blog post was originally published on Indeni before its acquisition by BlueCat.
The content reflects the expertise and perspectives of the Indeni team at the time of writing. While some references may be outdated, the insights remain valuable. For the latest updates and solutions, explore the rest of our blog
This is a real life sample alert from the indeni alert guide for Palo Alto Networks Firewalls.
Description:
One or more jobs running on this device have been stuck in “pending” state for more than 30 minutes.
Affected Jobs:
-
EBLRefresh
-
Install
Manual Remediation Steps:
Review the jobs listed above for possible issues. You may want to stop and re-issue the job if possible. For more information read DOC-2259.
How does this alert work?
indeni reviews the current list of jobs on a regular basis by running “show jobs all”. For this alert, indeni looks for jobs that have been stuck in PEND for more than 30 minutes.
Related content
Agentic AI adoption in network observability propels NetOps teams
Network observability is crucial for today’s networks and even more capable with agentic AI, according to new Omdia and BlueCat research.
Stop the ticket bottleneck: Automate DNS, DHCP, and IPAM with Quick Service
Automated DNS, DHCP, and IPAM (DDI) service delivery enables organizations to replace manual, ticket-based workflows with policy-driven, self-service…
Stay ahead of network issues with real-time metrics with BlueCat Integrity X
Get real-time DNS, DHCP, and IPAM metrics with BlueCat Integrity X. Detect issues early using native Prometheus telemetry and proactive DDI observability.
Adding business context to DDI with tagging in BlueCat Integrity X
Add business context to DNS, DHCP, and IPAM with tagging in BlueCat Integrity X. Improve visibility, automation, and governance across complex networks.