Almond skrev den 2014-12-22 13:43:
this was the situation on /tmp before tmpwatch installation:
[root@myhostname ~]# du -lh /tmp
11M /tmp/systemd-private-jr1YKi/tmp
11M /tmp/systemd-private-jr1YKi
is this 11M mail ?
[root@myhostname ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/md2 1.8T 56G 1.7T 4% /
devtmpfs 16G 0 16G 0% /dev
tmpfs 16G 0 16G 0% /dev/shm
tmpfs 16G 57M 16G 1% /run
tmpfs 16G 0 16G 0%
/sys/fs/cgroup
tmpfs 16G 57M 16G 1%
/etc/machine-id
/dev/md1 488M 280M 179M 61% /boot
check bash profile, and or systemmd that change how and where temp files
are stored, is dovecot started via systemmd ?
export | grep tmp
1) user mail quota 50 MB
2) spamd and clamscan together
3) ...spamd[28040]: plugin: eval failed: error writing to
/tmp/.spamassassin28040V31F7ftmp: Disk quota exceeded at
/usr/share/perl5/vendor_perl/Mail/SpamAssassin/Message.pm line 965,
what is the homedir of user running this ?
note /tmp/.spa....
hided dirs is imho not cleared in tmpwatch if not instucted to it
possible you have set spamd / spamc scan limit bigger then what it have
room for in fs quotas ?, i cant see here if you have it enabled
but 1.7TB free tmp should imho be fine :=)
as i see it something is forceing all tmp files to be in /tmp including
what really just should be maildir tmp dir
if you use dovecot move the question over there, since its not a
spamassassin issue, any chance of you run something in chroot ?
