Am 13.05.20 um 21:46 schrieb Jose David Bravo A (jbr...@colombiahosting.com.co): > Hi guys, > > Sorry for flooding you with errors, but I'm not able to find any solution in > the list o elsewhere... > > This is another problem that we got today: > > > ======= Memory map: ======== < ... > > *** Error in `/usr/sbin/sogod': malloc(): memory corruption: > 0x000055b9e3e294c0 *** > May 13 10:59:17 sogod [23136]: 181.58.119.22 "GET > /SOGo/so/geren...@ipsisolwayuu.com.co/Mail/0/folderINBOX/folderCOOMEVA_SP_AUTORIZACIONES/92/2/aros.jpg > HTTP/1.0" 200 4671/0 0.354 - - 0 < ...> > May 13 10:59:17 sogod [23135]: <0x0x55b9bde1f080[WOWatchDogChild]> child > 28465 exited > May 13 10:59:17 sogod [23135]: <0x0x55b9bde1f080[WOWatchDogChild]> > (terminated due to signal 6) > May 13 10:59:17 sogod [23135]: <0x0x55b9bde6f840[WOWatchDog]> child spawned > with pid 18044 >
That is a dying worker because of memory corruption. It was respawned by the SOGo WatchDog. "signal 6" is usually used by the Kernel for killing invalid processes. That worker was trying to open an attachment "aros.jpg" from email with ID 92 in Folder "INBOX.COOMEVA_SP_AUTORIZACIONES" of user "geren...@ipsisolwayuu.com.co" If you can reproduce that error with that email, you should open a bug report with it at https://sogo.nu/bugs/ If not, then you eventually have a problem with your RAM. Kind regards, Christian Mack -- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre 78457 Konstanz +49 7531 88-4416
smime.p7s
Description: S/MIME Cryptographic Signature
