Re: user-added planet script

2008-05-13 Thread Karsten 'quaid' Wade
On Thu, 2008-05-08 at 12:44 -0400, seth vidal wrote: > On Thu, 2008-05-08 at 19:20 +0300, Nicu Buculei wrote: > > > Add here probably a "language" for when/if we will have language based > > sub-planets. It is possible to have multiple values, like > > language = english, french > > for the case

Disk Space Issues - cvs-int/build hosts - (includes general note on Nagios Disk notifications)

2008-05-13 Thread Nigel Jones
Hey guys, I seem to have deleted the nagios notification that I want to mention in particular, but as I noted in SOP/Nagios the %ages noted in the e-mails are what is left, so inode=99% doesn't mean that 99% of the inodes are used, it means 99% are still free. Anyway, what this means, is tha

Re: Disk Space Issues - cvs-int/build hosts - (includes general note on Nagios Disk notifications)

2008-05-13 Thread Nigel Jones
Jeremy Katz wrote: On Tue, 2008-05-13 at 23:55 +1200, Nigel Jones wrote: Anyway, what this means, is that when nagios has been complaining about cvs-int recently, in particular the fact that /git has reached WARNING. After a bit of hunting around, I found /repo/pkgs using 168GiB of the 192

Re: Disk Space Issues - cvs-int/build hosts - (includes general note on Nagios Disk notifications)

2008-05-13 Thread Jeremy Katz
On Wed, 2008-05-14 at 00:39 +1200, Nigel Jones wrote: > Jeremy Katz wrote: > > On Tue, 2008-05-13 at 23:55 +1200, Nigel Jones wrote: > >> Anyway, what this means, is that when nagios has been complaining about > >> cvs-int recently, in particular the fact that /git has reached WARNING. > >> Afte

Re: Disk Space Issues - cvs-int/build hosts - (includes general note on Nagios Disk notifications)

2008-05-13 Thread Jeremy Katz
On Tue, 2008-05-13 at 23:55 +1200, Nigel Jones wrote: > Anyway, what this means, is that when nagios has been complaining about > cvs-int recently, in particular the fact that /git has reached WARNING. > After a bit of hunting around, I found /repo/pkgs using 168GiB of the > 192GiB available, w

Re: Disk Space Issues - cvs-int/build hosts - (includes general note on Nagios Disk notifications)

2008-05-13 Thread Nigel Jones
Jeremy Katz wrote: On Wed, 2008-05-14 at 00:39 +1200, Nigel Jones wrote: Jeremy Katz wrote: On Tue, 2008-05-13 at 23:55 +1200, Nigel Jones wrote: Anyway, what this means, is that when nagios has been complaining about cvs-int recently, in particular the fact that /git has reache

Re: Disk Space Issues - cvs-int/build hosts - (includes general note on Nagios Disk notifications)

2008-05-13 Thread Bill Nottingham
Nigel Jones ([EMAIL PROTECTED]) said: > Problem here, is that there are a LOT of old tarballs in that folder, which > leaves me wondering if we should do a spring clean ~1 mo after release. Until we get something like correspondingsource up and running, we don't have a good mechanism for weeding

Re: Disk Space Issues - cvs-int/build hosts - (includes general note on Nagios Disk notifications)

2008-05-13 Thread Mike Bonnet
On Tue, 2008-05-13 at 08:58 -0500, Dennis Gilmore wrote: > On Tuesday 13 May 2008, Nigel Jones wrote: > > Hey guys, > > > > I seem to have deleted the nagios notification that I want to mention in > > particular, but as I noted in SOP/Nagios the %ages noted in the e-mails > > are what is left, so i

Re: Disk Space Issues - cvs-int/build hosts - (includes general note on Nagios Disk notifications)

2008-05-13 Thread Dennis Gilmore
On Tuesday 13 May 2008, Nigel Jones wrote: > Hey guys, > > I seem to have deleted the nagios notification that I want to mention in > particular, but as I noted in SOP/Nagios the %ages noted in the e-mails > are what is left, so inode=99% doesn't mean that 99% of the inodes are > used, it means 99%

Change Request/Notification: FAS server problems

2008-05-13 Thread Toshio Kuratomi
I just noticed that fas was having issues and found that fas was using over a GB of memory on fas2.fedora.phx.redhat.com. No problem, I restarted fas and expected everything to be fine. 14 minutes later, memory was over a GB again. Another restart took care of the problem but I looked at the