User1: jbailey: what determines what modules are loaded into the initrd?
User2: lamont : Did you clean up ross?
User2: lamont : I got a message from elmo last night that it was out of disk space; seems (more than) fine now..
User3: [01-08-2005 09:46:18]  SERVICE ALERT: ross;Disk Space of /;CRITICAL;HARD;3;DISK CRITICAL [39041 kB (3%) free on /dev/sda3]
User3: I wasn't making it up :-P
User2: I assume not. :)
User2: Also, speaking of ross, it seems confused about SSH keys... Hrm.
User3: yeah, it will be, it's hostname is fucked
User2: I have 4 keys in LDAP (all show up in /var/lib/misc just fine, so ud-ldap is syncing okay), but I can only auth from one host, not the other.
User3: try now
User2: Oo.  Much better.
User2: Was it authenticating against the hdb.com stuff?
User3: actually ross has done this for like the last 5 or 6 days in a row
User3: i.e. dropped to 2-5% free at ~9am local
User3: so whatever's happening then is Bad(tm)
User2: Evil cronjob?
User3: User2 yah, if you find a buildd not called .buildd (in hostname -f), yell
User2: Yeah, I think there are a few others that hate me.  I'll loop through all 12 and see.
User2: crested and floe seem to be the only other two.
User2: 9am local, you say?  Hrm.
User3: fixed
User2: The only possibly nasty cronjob I can see if the DI build (which shouldn't be nasty anyway) at 6:15...
User2: I guess if it's going out of control, it could take 3 hours to fill the disks.
User2: s/if the/is the/
User3: I'm fairly sure the d-i daily build is finished well before then
User3: is ross not live CD image builder?
User2: Nope.
User3: damn, that was my first thought
User2: The LiveCD builds are commented out on ross.
User3: acct's useless for this sort of thing - unless lamont knows, I guess we should cron some ps auxfw's
User4: ross is d-i
* lamont goes digging
User4: hrm.. clearly someone cleaned it up
User4: royal is livecd
User2: Not I, and not elmo.  That doesn't leave many options.
User4: ross is d-i
User4: hrm... is 23% atm
User2: Yes, I noticed. :)
User3: yeah, but somethings using 20% of 150Gb and it's not a package
User3: and it's not d-i
User2: So, there's a mystery process that eats the disk at 9am every day, and then happily cleans up after itself.
User4: at 39MB, gcc-4.0 wins for logfile size
User4: oh, joy.
User4: 9AM DC time?
User2: Yeah.
User2: elmo : I would assume the majority of that 20% of 150GB is ccache.
User2: We do have ungodly large caches.
User3: ccache doesn't clean upitself ?
User3: oh 23% USED?
User2: Yes, 23% used.
User3: so something is using 100Gb ... W_T_F?
User2: Yeah, at 9am, something is eating 110GB.
User2: Yum.
User2: It is really at the same time every day, or just coincidentally rather close?
User3: all between 9am and 10am
User4: did tdb-dev finally show up (migrate to main)?  or did bogofilter just pick a diff machine to annoy after 9:40?
User4: User3 that's bizare!  and about 0300 for me.
* lamont will be in and out for much of the evening, need to get ready and go fetch my niece from the airport in about 3 hours, etc.
User2: Infinite loop in the find or checksecurity cron.daily jobs, perhaps?
User2: They clean up after themselves, and couldtake 3 hours to build a 110 gig log file.
* infinity whimpers when he realises that the $sshcmd{$dist} thing means some serious fiddling with backporting sshsocket stuff.
User2: Oh well, halfway there.
User5: User4 hppa is lacking libdb4.3, so python cannot be installed
User4: User2 yeah, I guess it would.
User4: User5 correct
User5: laminity: please requeue: sigc jabberoo libgnomemm2.0
User5: lamont, User2 ^^^
User4: User5 on ppc?
User5: User4 all
User4: I only have logs for sigc/ppc and jabberoo/ppc.
User4: I'll kick the others in a bit, when my meeting hits a break and I can type faster...
ubuntu-toolchain
Ubuntu IRC