Am 06.03.2017 um 14:36 schrieb Götz Reinicke - IT Koordinator
([email protected]):
> Hi,
> 
> Am 06.03.17 um 14:29 schrieb Christian Mack ([email protected]):
>> Am 06.03.2017 um 10:53 schrieb Götz Reinicke - IT Koordinator
>> ([email protected]):
>>> Hi,
>>>
>>> I see a lot of up to 1GB big files in /tmp like OGo49B058BD278A0B.tmp
>>>
>>> As they consumed all disk space we had some problems, so i was searching
>>> for an answer what are the files for and can they removed at some point?
>>>
>> Those files will be created, when someone uploads files to SOGo.
>> Which means when someone attaches a file to her email or imports address
>> books or calendars those files will be created.
>> Normally those will be removed after usage.
>> But sometimes they will be left behind.
>> Therefore we at the University of Konstanz have added the following to
>> /etc/cron.daily/sogo-tmpwatch
>>
>> # Remove files in /tmp which are older than 7 days and starting with "OGo".
>> # Those are uploaded attachments not already send.
>> find /tmp -maxdepth 1 -type f -atime +7 -name 'OGo*' -delete
>>
>>
>> Be aware, that installing a new sogo version, will overwrite that file.
>> Because of that you have to add that again after updates, or you could
>> add it to /etc/cron.d/sogo
>>
> Thanks Christian, I'll check my cron settings.
> 
> For curiosity, why might a file get 1GB big? Are our students trying to 
> upload 
> so big files? I hope not :)
> 

Yes, they are uploading even full iso images with 4,7 GB as email
attachments. :-/
Which means, that SOGo will use up to 8 GB for MIME/base64 encoding it
in RAM!
We had several of those already.
When on a slow line, those uploads will break before finished and leave
those OGo* files behind.

Because of that we asked Inverse for upload limits.
Check WOMaxUploadSize and SOGoMaximumMessageSizeLimit.



Kind regards,
Christian Mack

-- 
Christian Mack
Universität Konstanz
Kommunikations-, Informations-, Medienzentrum (KIM)
Abteilung Basisdienste
78457 Konstanz
+49 7531 88-4416

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to