Re: [Help] Cyrus 2.4.17 segfault
Il 12/11/2019 22:58, ellie timoney ha scritto: On Tue, Nov 12, 2019, at 2:51 AM, Marco wrote: An user user/a has full ACL to another mailbox user/b. When the user/a SELECT a folder on user/b where he has access the imap process crashes. If you set up a couple of test accounts with the same sharing arrangement, do those crash in the same way? Or is it specific to the two original accounts? Hi Ellie, I made other tests... It's specific to the user/a account. When user/a SELECT a shared folder where it has access, the imap process crashes. I updated to cyrus-imapd-2.4.20 and the issue still happens. I also tried to rebuild mailboxes.db with ctl_mboxlist -d -u, I tried to rebuild mailboxes.db with an old backup... I tried to delete the statuscache and to delete the skipstamp db... the problem still happens. Thank you Marco Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: [Help] Cyrus 2.4.17 segfault
On Tue, Nov 12, 2019, at 2:51 AM, Marco wrote: > An user user/a has full ACL to another mailbox user/b. When the user/a > SELECT a folder on user/b where he has access the imap process crashes. If you set up a couple of test accounts with the same sharing arrangement, do those crash in the same way? Or is it specific to the two original accounts? Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: IMAP over SSL (only) handshake hangs
Hello Helder, If there is no enough random seed OpenSSL will not hang, just return an error. Even /dev/random is opened in non-blocking mode. This is true only if OpenSSL is built with non-blocking mode. https://github.com/openssl/openssl/blob/master/crypto/rand/rand_unix.c If it hangs after some time could it be a handle leak? In the past, I had a similar problem and used "lsof" and "ulimit" commands to see is it reached. This error could be a possible track to a handle leak. setrlimit: Unable to set file descriptors limit to -1: Operation not permitted Regards, Zhivko On Mon, Nov 11, 2019, at 2:53 PM, Helder Guerreiro via Info-cyrus wrote: > On 10/11/19 00:19, Helder Guerreiro via Info-cyrus wrote: > > On 09/11/2019 23.34, Patrick Boutilier wrote: > >> Almost sounds like you are running out of entropy. What does this show? > >> > >> cat /proc/sys/kernel/random/entropy_avail > > > > Right now it's at 3769 bytes. I'll monitor this. > > It happened again, the entropy available never got bellow 3600 (logged > it every minute or so). > > Cyrus Home Page: http://www.cyrusimap.org/ > List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ > To Unsubscribe: > https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus > Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
