/var/lib/puppet/reports is filling up

RESOLVED WORKSFORME

Status

Release Engineering
Platform Support
P3
normal
RESOLVED WORKSFORME
6 years ago
4 years ago

People

(Reporter: armenzg, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [puppet][cleanup])

(Reporter)

Description

6 years ago
scl-production-puppet.build.scl1:disk - /var is WARNING: DISK WARNING - free space: / 3967 MB (10% inode=77%):
(Reporter)

Comment 1

6 years ago
I wonder if we could have a cronjob to clean this up regularly.

[root@scl-production-puppet reports]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/vda3              38G   32G  3.9G  90% /
/dev/vda1              99M   18M   77M  19% /boot
tmpfs                1006M     0 1006M   0% /dev/shm

[root@scl-production-puppet reports]# find /var/lib/puppet/reports -name "*yaml" -mtime +30 -exec rm {} \;

Filesystem            Size  Used Avail Use% Mounted on
/dev/vda3              38G   26G  9.5G  74% /
/dev/vda1              99M   18M   77M  19% /boot
tmpfs                1006M     0 1006M   0% /dev/shm

Only 4 reports in the last 30 days:
[root@scl-production-puppet reports]# find /var/lib/puppet/reports -name "*yaml"
/var/lib/puppet/reports/talos-r4-lion-059.build.scl1.mozilla.com/201202212241.yaml
/var/lib/puppet/reports/talos-r4-lion-069.build.scl1.mozilla.com/201202212237.yaml
/var/lib/puppet/reports/talos-r4-lion-067.build.scl1.mozilla.com/201202090413.yaml
/var/lib/puppet/reports/talos-r4-lion-044.build.scl1.mozilla.com/201202250200.yaml

I guess this was a side-effect of the Humpty Dumpty errors.

Updated

6 years ago
Component: Release Engineering → Release Engineering: Platform Support
OS: Mac OS X → All
Priority: -- → P3
QA Contact: release → coop
Hardware: x86 → All
Whiteboard: [puppet][cleanup]
(Assignee)

Updated

4 years ago
Product: mozilla.org → Release Engineering

Updated

4 years ago
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.