The wiki machine has currently 2.4GB of available space but earlier
today a cron job found that space to be unavailable while doing man
pages maintainance.
I don't know what made that space go away (bacula, maybe?).
In any case, analizying disk usage I found 2 mysql backups from
August 2014 which take 3GB in total.
Does anyone know of any reason why we should keep them ?
--strk;
On Jul 25, 2017 4:05 PM, “Sandro Santilli” <strk@kbt.io> wrote:
The wiki machine has currently 2.4GB of available space but earlier
today a cron job found that space to be unavailable while doing man
pages maintainance.I don’t know what made that space go away (bacula, maybe?).
Isn’t bacula on a separate machine? Would be somewhat useless otherwise…
In any case, analizying disk usage I found 2 mysql backups from
August 2014 which take 3GB in total.Does anyone know of any reason why we should keep them ?
AFAIK they are not needed.
Markus
–strk;
On Tue, Jul 25, 2017 at 07:42:08PM +0200, Markus Neteler wrote:
On Jul 25, 2017 4:05 PM, "Sandro Santilli" <strk@kbt.io> wrote:
>
> The wiki machine has currently 2.4GB of available space but earlier
> today a cron job found that space to be unavailable while doing man
> pages maintainance.
>
> I don't know what made that space go away (bacula, maybe?).Isn't bacula on a separate machine? Would be somewhat useless otherwise...
Bacula is on a separate machine, but it can run scripts on the
machine being backed up to "prepare" files to be then transferred
(and removed). I hadn't checked the configuration for this specific
machine, but for others (tracsvn) I'm sure there's a preparation
script that creates local PostgreSQL backups...
> In any case, analizying disk usage I found 2 mysql backups from
> August 2014 which take 3GB in total.
>
> Does anyone know of any reason why we should keep them ?AFAIK they are not needed.
Ok, I moved them under /var/lib/trashme, so next person that needs
to clean things up will know what to do with them...
--strk;
Sandro Santilli wrote:
The wiki machine has currently 2.4GB of available space but earlier
today a cron job found that space to be unavailable while doing man
pages maintainance.
I just realized you already took care of removing the package cache. I
still consider this as being my duty (as I still regularly apply
updates), thus thanks for jumping in.
From my perspective the old DB dumps can go away, anyhow I must admit
that I didn't real all of the recent list traffic and might have missed
important notices.
If we decide to preserve these old dumps, I can store them off-site.
Best regards,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------
On Wed, Jul 26, 2017 at 10:43:29AM +0000, Martin Spott wrote:
Sandro Santilli wrote:
> The wiki machine has currently 2.4GB of available space but earlier
> today a cron job found that space to be unavailable while doing man
> pages maintainance.I just realized you already took care of removing the package cache. I
still consider this as being my duty (as I still regularly apply
updates), thus thanks for jumping in.
I was looking for a log of such updates, as wiki recently broke
due to a (default?) misconfiguration of the php apache module.
Was that module updated recently ? Or can you tell where
/etc/php5/apache/php.ini came from ?
From my perspective the old DB dumps can go away, anyhow I must admit
that I didn't real all of the recent list traffic and might have missed
important notices.If we decide to preserve these old dumps, I can store them off-site.
They are now in /var/lib/trashme, if you want to take them elsewhere.
Can you think of other possible ways those 2.4GB were consumed
temporarly, enough for the cron job updating mandb would fail ?
--strk;