Last Comment Bug 731992 - /var/lib/puppet/reports is filling up
: /var/lib/puppet/reports is filling up
Status: RESOLVED WORKSFORME
[puppet][cleanup]
:
Product: Release Engineering
Classification: Other
Component: Platform Support (show other bugs)
: other
: All All
: P3 normal (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
: Chris Cooper [:coop]
Mentors:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-03-01 06:34 PST by Armen Zambrano [:armenzg] (EDT/UTC-4)
Modified: 2013-11-08 13:21 PST (History)
0 users
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---


Attachments

Description Armen Zambrano [:armenzg] (EDT/UTC-4) 2012-03-01 06:34:24 PST
scl-production-puppet.build.scl1:disk - /var is WARNING: DISK WARNING - free space: / 3967 MB (10% inode=77%):
Comment 1 Armen Zambrano [:armenzg] (EDT/UTC-4) 2012-03-01 07:06:49 PST
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.

Note You need to log in before you can comment on or make changes to this bug.