swap parition ran full

[uwe@…]

I think my swap partition was full because of excessively large log files. Zentyal-login was impossible. Yesterday I checked the Zentyal log settings and the default settings were never to delete any log files! I shortened one file manually and then I was able to login again and change the settings.

Today I have the same problem again! After cleaning up again, I can login, but still get some database connection errors (see attached ebox.log). Can you help?

Best regards Uwe Stelzer

[uwe@…]

I found the problem which has eaten the most disk space: duplicity cache. The backup job doesn't finish and leaves a huge cache file on disk.

I used the standard partitioning scheme which was suggested during installation. Maybe the 6.5 GB for / is too small?

adminbs@bsserver:/$ df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/bsserver-root

6,5G 2,5G 3,6G 41% /

none 2,0G 208K 2,0G 1% /dev none 2,0G 0 2,0G 0% /dev/shm none 2,0G 3,5M 2,0G 1% /var/run none 2,0G 0 2,0G 0% /var/lock none 2,0G 0 2,0G 0% /lib/init/rw none 6,5G 2,5G 3,6G 41% /var/lib/ureadahead/debugfs /dev/sda1 228M 51M 166M 24% /boot /dev/sdb1 459G 258G 178G 60% /media/backup-usb /dev/mapper/bsserver-home

900G 103G 751G 13% /home

[jamor@…]

Hello,

in most cases duplicit clear this after a successful backup. You can also delete it manually without any harm (except duplicity speed).

I haven't find any way to discriminate between correct and incorrect cache directories so we cannot remove rhis directories automatically. Also check your duplicity version just to make sure you don't have an outdated version.