F5 Localdbmgr Down Site

If /var or /tmp is at 100%, remove old backup files (UCS), tech-support files (qkviews), or logs.

Check F5 Solution IDs (e.g., SOL44872, SOL16453) for version-specific issues.

tmsh create sys alarm volume-filling-high threshold 80 f5 localdbmgr down

ps aux | grep localdbmgr

tmsh run cm failover standby

If any of these are at 90% capacity or higher (especially /var ), disk space is your culprit. The /var/log directory is the usual suspect, filling up with massive audit or ltm logs.

# Stop localdbmgr bigstart stop localdbmgr If /var or /tmp is at 100%, remove

df -h /var df -i /var

| Command | Purpose | |---------|---------| | bigstart status localdbmgr | Verify service status (shows “running” or “down”) | | ps aux | grep localdbmgr | Look for running PID | | tail -200 /var/log/ltm | Search for “localdbmgr” or “sqlite” errors | | tail -200 /var/log/messages | Same as above | | df -h /shared / df -i /shared | Check disk space/inodes (full disk = DB corruption) | The /var/log directory is the usual suspect, filling

If you see “ok” → not corrupted. If you see errors → database is corrupt.