FreeBSD 13 – pkg audit cannot run because local vulnerability database is stale or locked

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Security audit checks fail, reducing vulnerability visibility.

Environment & Reproduction

Seen after interrupted pkg operations or stale DB locks.

Root Cause Analysis

Audit metadata cannot refresh due to lock or mirror access issues.

Quick Triage

Confirm no active pkg process before lock-file cleanup.

Step-by-Step Diagnosis

Inspect lock artifacts and run verbose pkg audit refresh.

Solution – Primary Fix

Safely clear stale locks, refresh repositories, then re-run audit.

Solution – Alternative Approaches

Mirror VuXML internally for restricted network environments.

Verification & Acceptance Criteria

pkg audit completes and returns actionable results.

Rollback Plan

Restore pkg DB snapshot if metadata corruption is detected.

Prevention & Hardening

Use lock-aware wrappers to avoid overlapping pkg operations.

Related Errors & Cross-Refs

Often linked with failed unattended upgrades in jails.

Related tutorial: View the step-by-step tutorial for FreeBSD 13.

View all FreeBSD 13 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

pkg audit and VuXML documentation for FreeBSD.