Closed Bug 952083 Opened 11 years ago Closed 11 years ago

tp-socorro01-master02.phx1 Disk space Critical

Categories

(Socorro :: General, task)

Product:
Socorro
Component:
General
Platform:
x86
macOS
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: rwatson, Assigned: mpressman)

References

Details

Have been alerted on #sysadmins of critical disk:
Thu 04:56:21 PST tp-socorro01-master02.phx1.mozilla.com is DOWNTIMEEND (UP) :PING OK - Packet loss = 0%, RTA = 1.82 ms

Thu 04:59:55 PST [1191] tp-socorro01-master02.phx1.mozilla.com:Disk - All is CRITICAL: DISK CRITICAL - free space: / 0 MB (0% inode=53%):

I believe this machine is down timed so not sure how "critical" this is.
This was due to /wal being expanded. After it came back up, the WAL from socorro1.db.phx1 was filling up / since the postgresql server wasn't running.
Assignee: nobody → mpressman
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
/wal is 90% full again and alerting.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
The recovery.conf archive cleanup variable was pointing to the previous location /var/lib/pgsql/wal_archive and not the new one: /wal/9.2 - I have reset and now it's being cleaned up

/dev/mapper/vg_dbsoc-lv_wal
               xfs    224G   65M  224G   1% /wal
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.