Re: Squatter after upgrade

Hi Simon.
At the beginning this year I migrated from ubuntu 12.10+cyrus2.4.16 to centos7+cyrus2.4.17. All it have worked fine, but month and half after migration I start to notice something was going wrong:  time to time I see lots of  imap-processes, users complain to access to their mboxes, mail delivery problems, squatter holds at bad mbox and etc.I managed to find who faced to the same problem https://github.com/cyrusimap/cyrus-imapd/issues/1599. 
In my case I caught the bug exactly as described in link above. I decided to look for more new cyrus version for centos7 and found in kolab repository http://obs.kolabsys.com/repositories/Kolab:/16/CentOS_7/x86_64

Also about how to control squatter task via system scheduler CRON or in-build one - Cyrus EVENS Section. I think it depends on habits and sysadmin style. For example, I like starting cyrus routine tasks via EVENTS Section in order to cyrus-master controls its tasks. 

> 1 мая 2017 г., в 10:39 ДП, Simon Wilson <[email protected]> написал(а):
> 
> ----- Message from Anton <[email protected]> ---------
>   Date: Fri, 28 Apr 2017 21:22:04 +0700
>   From: Anton <[email protected]>
> Subject: Re: Squatter after upgrade
>     To: [email protected]
>     Cc: "info-cyrus lists.andrew.cmu.edu" <[email protected]>
> 
> 
>> Hi Simon!
>> Just put your squatter at the same place in EVENT section in new server. Actually I recommend you don't use stock cyrus version in centos 7 due to IDLE bugs. Jump to 2.5.10 from kolab repo.
>> 
>> 
> 
> Thanks. I've added squatter and it seems to be running OK.
> 
> I've not been able to find any information about IDLE bugs in the CentOS 7 packaged Cyrus. The whole intent of running CentOS is for package stability - it would need to be a major issue to get me to break out of that and sideload a newer Cyrus. Do you have more info on the IDLE bugs you mention?
> 
>>> 28 апр. 2017 г., в 8:13 ПП, Simon Wilson <[email protected]> написал(а):
>>> 
>>> Hi list,
>>> 
>>> I have just upgraded from Cyrus 2.3.7 on a CentOS 5 server to 2.4.17. on a new CentOS 7 server.
>>> 
>>> On the old one events was:
>>> 
>>> EVENTS {
>>> # this is required
>>> checkpoint    cmd="ctl_cyrusdb -c" period=30
>>> 
>>> # this is only necessary if using duplicate delivery suppression,
>>> # Sieve or NNTP
>>> delprune      cmd="cyr_expire -E 3" at=0400
>>> 
>>> # this is only necessary if caching TLS sessions
>>> tlsprune      cmd="tls_prune" at=0400
>>> 
>>> # running squatter
>>> squatter cmd="/usr/lib/cyrus-imapd/squatter -r user" period=1440
>>> }
>>> 
>>> On the new one it's:
>>> 
>>> EVENTS {
>>> # this is required
>>> checkpoint    cmd="ctl_cyrusdb -c" period=30
>>> 
>>> # this is only necessary if using duplicate delivery suppression,
>>> # Sieve or NNTP
>>> delprune      cmd="cyr_expire -E 3" at=0400
>>> 
>>> # this is only necessary if caching TLS sessions
>>> tlsprune      cmd="tls_prune" at=0400
>>> }
>>> 
>>> 
>>> I notice there is no SQUATTER entry in the new one - is it required, or is the functionality no longer needed? Should I put a SQUATTER entry in the new server's cyrus.conf?
>>> 
>>> Thanks
>>> Simon.
>>> 
>>> --
>>> Simon Wilson
>>> M: 0400 12 11 16
>>> 
>>> ----
>>> 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
> 
> 
> ----- End message from Anton <[email protected]> -----
> 
> 
> 
> -- 
> Simon Wilson
> M: 0400 12 11 16
> 
> ----
> 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