CAcert System Admins discussion list

[Ian G <iang AT iang.org>]

Switching across to sysadm list.  Story so far:  test1 got messed up 
because it ran out of space.

On 10/01/2010 15:51, Jan Dittberner wrote:

> > /chroot/var/lib/php4:
> >
> > root@muley:/chroot/var/lib#
> >  ls -la
> > total 80916
> > drwxr-xr-x 3 root root     4096 Jul 21  2006 .
> > drwxr-xr-x 6 root root     4096 Aug 14  2008 ..
> > drwxrwxrwx 2 root root 82763776 Jan  5 14:18 php4
>
> looks like a LOT of old session data. Something like tmpreaper or a job which
> uses find to cleanup old unused files from php's session store would be a good
> idea.

Last night, Jan cleaned out the directory, first with a find and then 
with a rename/mkdir.  Reduced space to 52% used :-)  Big thanks!

Philipp G confirms that this directory is for session data only.  I 
suspect the old one can be safely removed (although maybe we need to 
look at the sessions in there to see if there was some sort of repeated 
attack).

Jan has a potential cron job.  PG suggests that any cron job to clean it 
out is a sysadm issue not a software issue.

I suggest we make Jan a test1 sysadm.  Any objections?  Who else is on 
the list?

For all test1 sysadms:  it seems that both Apache and Mysql do not start 
up properly on reboot.  Maybe as a result of chroot and run level 
changes made in the past?  Perhaps we need another go at this, some 
reboot testing?

For critical team:  this is the sort of thing where test1 and other test 
machines should be aligned with the critical setup, and there should be 
some sort of doco we could follow from them?

Wytze, do we have any writings in place that talks about cron jobs and 
process start ups on reboots?



iang