spamd: cannot create /tmp/spamd-724-init: No space left on device at /
Issue #568
closed
Hello, please help me, I cannot resolve this issue, tried this 5 hours now
Jan 13 15:19:20 12e838b199b3 mail.err spamd[724]: spamd: cannot create /tmp/spamd-724-init: No space left on device at /usr/sbin/spamd line 3038.
Comments (11)
-
-
Big question is that, how the hell this happened even I still have more than 60% storage and it is not even critical, does it have limits that triggered the system to have this error appear? 60% of the drive is pretty much useless if this keeps happening.
-
repo owner
How do you run poste.io? You need to have volume for /data directory mounted somewhere with enough space
-
Running it with docker, with the documents I just followed from your page. And yes all the logs are on /data ,when the issue appears I was worried because I have enough DISK, which is 50% at that time. But still getting the error, now upon deleting the logs and cleaning, it worked fine now.
-
SH.. are there any limits imposed on /tmp or /usr/sbin from within your docker container?
Alfred, what size is your disk? How big are your log files?
-
Scott, Unfortunately, I didn't checked how big it was, but I installed it since 2017, so maybe it was too big, but my disk has enough storage to handle it since I am only using poste.io as the server, and nothing else until I wasn't able to login on roundcube then I checked the logs seeing this error but like I said I have enough storage but still the error showed up, it was weird, I can even still write something on /tmp, but to avoid the issue, I just created a little bash script to delete logs everyday, since I don't check logs anyway.
-
Certainly an odd issue. I've been running Poste.io for about 1yr and not encountered anything like what you're seeing. If SH doesn't limit anything from the docker container side then I'm at a loss for root cause without more details.
-
Scott, yeah, freshly provisioned vps doesn't have /your-data-dir/data, meaning it was created since poste.io was installed, which our data was installed as well as the logs, my provider does not have to do on this, why would they impose limit on your own VPS right? I even purchased additional storage just to be sure, but with these limitations happening, storage are useless, if I can see the system was unable to write more logs :/ and some functions may not work which makes us worried.
-
repo owner
There is no limits at all. Are you sure you have "data" directory out of your containers fs? I can only imagine scenarion where data directory is still in container which is mostly at system partition at dockers directory. Common practice is to make system partition small and partition with /home large. Is it your case?
-
Yes, this was my next question. That the data directory is on (or not) the correct partition and not off root if the VM is partitioned as such.
-
repo owner
- changed status to closed
Closing this one. Feel free to reopen if that happen again
- Log in to comment
Solved by deleting log files.