[horde] Cannot write to cache directory /tmp

Simon B simon.buongiorno at gmail.com
Tue Jun 4 10:29:43 UTC 2013

On 3 June 2013 15:20, Michael J Rubinsky <mrubinsk at horde.org> wrote:
> Quoting Simon B <simon.buongiorno at gmail.com>:
>> On 3 June 2013 09:51, Ole Wolf <ole at naturloven.dk> wrote:
>>>  Quoting Simon B <simon.buongiorno at gmail.com>:
>>>> The browser says
>>>> Cannot write to cache directory /tmp
>>>> But /tmp is owned by www-data
>>> Last time I had that error (incidentally, it was after a Horde update,
>>> too)
>>> it was because the disk was full.
>> Great spot.  That's the second time a git pull has left me with a full
>> disk - 500GB!..  After a reboot, I'm back to 12% or just under 50GB..
> http://bugs.horde.org/ticket/12265

Yes and no.  I'm sure you're right as you know much more about IMAP
than I do, but my concerns are:

1) As you say in the ticket - it's amazing how many people are running
around with "broken" imap servers - given the number of different IMAP
servers that were mentioned, makes me concerned that it's not the IMAP
server - but rather the way it's being spoken to.
2) Corroborating that my IMAP server has been running without an issue
for 2 years without filling the disk with log files - and now all of a
sudden since Horde5.1 it's done it twice?  That doesn't feel kosher.
3) in fact my log files are not over-sized.  Running du /var | sort
-rh | head -10 didn't show a single file in the /var/log path, and
after a reboot, my disk is back to 16% full.  Google seems to think
this is a unclosed file handle.  If that's a Dovecot bug, I find it
strange that I'm only discovering it now an b) that Timo hasn't fixed
it yet..


More information about the horde mailing list