skills.rest
liyanqing1987
liyanqing1987COMMUNITY
Explore all skills by this author →
GitHub

lsf_job_pend

Diagnose LSF/OpenLava/Volclava jobs stuck in PEND using bjobs and reason-specific commands.

66|20|Updated Jul 7, 2020
Search Tags:#dependency handling#job scheduling#lsf#pending diagnosis#HPC monitoring#queue capacity#license usage
One-click install
npx skills add https://github.com/liyanqing1987/lsfMonitor --skill lsf-job-pend
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lsf_job_pend
Source: https://github.com/liyanqing1987/lsfMonitor/tree/main/monitor/conf/skills/lsf_job_pend
Command: npx skills add https://github.com/liyanqing1987/lsfMonitor --skill lsf-job-pend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly diagnose why an LSF/OpenLava/Volclava job remains in PEND state and doesn’t start, so you can identify the real scheduling blocker and act immediately.

Core Features & Use Cases

  • PEND Root-Cause Diagnosis: Determines the underlying Pending Reason (as reported by the scheduler) and selects targeted checks for slot limits, resource mismatches, license shortages, queue/host state issues, dependency problems, and user limits.
  • Actionable Evidence Collection: Gathers the required job, queue, host, and (when applicable) license information, then summarizes the diagnosis using concrete command outputs and key fields.
  • Fix-First Reporting: Produces an output plan including immediate copy-pastable remediation steps and longer-term prevention guidance.

Quick Start

Ask the skill: “Diagnose why my LSF job is stuck in PEND and give me the exact commands to fix it, using my job’s pending reason and job id.”

Frequently Asked Questions about lsf_job_pend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my LSF job stay in PEND state and not start running?▼

LSF jobs stay PEND when the scheduler faces slot limits, resource mismatches, license shortages, queue capacity limits, or user policy constraints preventing job dispatch.

How do I diagnose why an OpenLava job is stuck in a queue for a long time?▼

To diagnose a stuck OpenLava job, map the scheduler-reported Pending Reason to targeted checks using bjobs, bqueues, busers, and bhosts to gather evidence on jobs, queues, hosts, and user limits.

Can I use this to find out if pending jobs are caused by license shortages?▼

Yes, pending diagnosis maps scheduler pending reasons to targeted evidence collection across license usage, verifying if license shortages block job dispatch.

What LSF commands do I need to check pending job reasons?▼

You need bjobs to view pending reasons, plus reason-specific commands like bqueues, busers, bhosts, lshosts, lsload, and brsvs to gather targeted evidence for remediation.

Does this pending diagnosis work with Volclava and OpenLava clusters?▼

Yes, this pending diagnosis applies to LSF, OpenLava, and Volclava clusters, mapping the reported pending reason to targeted checks across jobs, queues, hosts, and licenses.

What should I do when LSF scheduling fails to allocate resources due to policy limits?▼

When scheduling fails due to policy limits, check user limits with busers and queue policies with bqueues to identify the configuration constraint, then apply the immediate copy-pastable remediation steps provided.

Related Skills

Explore More Software Engineering Skills→
liyanqing1987liyanqing1987
66

lsf_job_slow

Diagnose LSF/OpenLava/Volclava RUN-state jobs with no output or slow progress.

Community
Advanced
reckerswartzreckerswartz

solid-queue-setup

Configure Solid Queue as the Rails 8 Active Job backend.

Community
Advanced
SciMate-AISciMate-AI
1

hpc-orchestration

Coordinate HPC job submission, monitoring, and recovery across Slurm, PBS, and LSF.

Official
Advanced
Project-HAMiProject-HAMi
4.3k

k8s_gpu_pod_troubleshooter

Diagnose GPU pod scheduling and allocation issues in Kubernetes clusters with HAMi.

Official
Advanced