signal 11 - it was really the kernel

2002-03-04 Thread Olaf Frączyk
Hi, I have spent two days to get cyrus-imapd working. I have tried everything, but I was getting signal 11, from 1 to 5 per hour, so it was impossible to use it. After searching I found in faq, that it could be caused by kernel 2.4.17. So I moved to 2.4.18, and ..., it works now 6 hours with no p

Want sieve but don't want delivery duplicate supression

2002-03-04 Thread Olaf Frączyk
Hi, Any hope to get it working? It makes trouble, especially with mailing lists. Eg. somebody posted mail to group1,group2, and to me. In result I see only one message. But I have filter in sieve, so it sorts mail into different folders. So in my inbox is no message, only in folder for group1. A

Do I need user prefix for all mail folders, eg. user.olaf ?

2002-03-05 Thread Olaf Frączyk
Hi, I want to have some shared folders in my company. Do I have to add a dummy user and build folder structure under it or I may have mailboxes like that: office.subject1 office.subject2 info.subject1 etc.? Will it break something? Mail to these boxes would be put using sieve. Regards, Olaf

Sieve doesn't catch all messages it should

2002-03-05 Thread Olaf Frączyk
Hi, Sieve doesn't catch all messages. It is probably caused , by a little malformed header, but with procmail I hadn't those problems. I include header for message that is catched, and for this is not. I think that it is ">" character before one of "Received:". Anyway I think it's sieve's fault.

cyradm not showing metadata if logged as admin

2017-04-06 Thread Olaf Frączyk
ried to give the admin full ACL rights for this mailbox but it didn't help. Is there any configuration option to change this behaviour? Best regards, Olaf Frączyk -- NAVI Sp. z o.o. Promienista 5/1 60-288 Poznań mobile: +48609769035 phone: +48616622881 fax: +48616622882 http://www.navi.pl

Set metadata (specialuse - Sent,Junk,Drafts) as admin for other user

2017-04-07 Thread Olaf Frączyk
user (not using user's password)? Or maybe there is some other way to accomplish my goal? I cannot expect from users to login via telnet and set it by themselves. Best regards, Olaf Frączyk -- NAVI Sp. z o.o. Promienista 5/1 60-288 Poznań mobile: +48609769035 phone: +48616622881 fa

Replication - current status and how to do failover

2020-04-04 Thread Olaf Frączyk
Hello, 1. Is currently master-master replication possible (maybe 3.2) Is it OK to sync them two-way? If yes - how to set up such config? 2. If master-master is impossible, is there any guide how to setup failover from master to slave and possibly back? If split-brain happens - is there an e

Replication failed 3.0.5 -> 3.0.13

2020-04-20 Thread Olaf Frączyk
the old machine. Best regrads, Olaf Frączyk 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: Replication failed 3.0.5 -> 3.0.13, now 3.0.13->3.0.13

2020-04-20 Thread Olaf Frączyk
On 2020-04-20 16:11, Olaf Frączyk wrote: Hi, I'm running 3.0.5. I want to migrate to a new machine. I set up cyrus-imapd 3.0.13. The replication started but it didn't transfer all mails. The store isn't big 44GB, transferred was about 24 GB. In the logs I see: Apr 20 14:5

Re: Replication failed 3.0.5 -> 3.0.13, now 3.0.13->3.0.13

2020-04-21 Thread Olaf Frączyk
it cause problems? Maybe I should move the sync_client from START section to SERVICES, it seems that it is not automatically restarted On 2020-04-21 08:47, Michael Menge wrote: Hi Olaf Quoting Olaf Frączyk : Hi, I upgraded to 3.0.13 but it didn't help. This time it copied about 18G

Re: Replication failed 3.0.5 -> 3.0.13, now 3.0.13->3.0.13

2020-04-21 Thread Olaf Frączyk
happens, there is no activity both on the replica and on the master for some time. So maybe the imap server process is not recovering correctly in the longlock situation? On 2020-04-21 11:07, Olaf Frączyk wrote: Hi, When I run sync_client -r on the master I see the following on the replica

Re: Replication failed 3.0.5 -> 3.0.13, now 3.0.13->3.0.13

2020-04-21 Thread Olaf Frączyk
11:18, Olaf Frączyk wrote: I also found out that when I see on master: Apr 21 11:12:38 ifs sync_client[27996]: IOERROR: zero length response to MAILBOXES (idle for too long) Apr 21 11:12:38 ifs sync_client[27996]: IOERROR: zero length response to RESTART (idle for too long) Apr 21 11:12:3

Re: Replication failed 3.0.5 -> 3.0.13, now 3.0.13->3.0.13

2020-04-21 Thread Olaf Frączyk
, Michael Menge wrote: Hi, Quoting Olaf Frączyk : The current situation is: 1. Replica: stopped and started the replica no activity on replica - iotop and top show nothing the only messages on replica is incoming connection from master 2. Master: when I run sync_client -r I still get: Apr

Re: Replication failed 3.0.5 -> 3.0.13, now 3.0.13->3.0.13

2020-04-21 Thread Olaf Frączyk
n(6, SHUT_RD)    = 0 close(6)    = 0 close(5)        = 0 munmap(0x7fc6ed5bb000, 16384)   = 0 close(3)    = 0 munmap(0x7fc6ed5d, 49152)   = 0 close(4)    = 0

Re: Replication failed 3.0.5 -> 3.0.13, now 3.0.13->3.0.13

2020-04-21 Thread Olaf Frączyk
On 2020-04-21 16:00, Michael Menge wrote: Hi, Quoting Olaf Frączyk : I managed to get strace on both sides, however it doesn't make me wiser - there is nothing obvious for me. Additionally I see that replication works more or less for new messages, but older are not processed. I

Re: Replication failed 3.0.5 -> 3.0.13, now 3.0.13->3.0.13

2020-04-22 Thread Olaf Frączyk
On 2020-04-21 20:40, Michael Menge wrote: Quoting Olaf Frączyk : Yes, at the beginning I was also thinking if initial sync is necessary, but there was nothing in docs about it, something started replicating and I simply assumed it does initial resync. I'll try it this evening. :)

Re: Replication failed 3.0.5 -> 3.0.13, now 3.0.13->3.0.13

2020-04-22 Thread Olaf Frączyk
S section. The SERVICES section is for service processes (i.e. processes that listen on a socket and service client requests). sync_client is a client, not a service. Cheers, ellie On Wed, Apr 22, 2020, at 4:40 AM, Michael Menge wrote: Quoting Olaf Frączyk : Yes, at the beginning I was al

Re: Replication failed 3.0.5 -> 3.0.13

2020-04-22 Thread Olaf Frączyk
On 2020-04-22 09:16, Andrzej Kwiatkowski wrote: W dniu 20.04.2020 o 16:11, Olaf Frączyk pisze: Hi, I'm running 3.0.5. I want to migrate to a new machine. I set up cyrus-imapd 3.0.13. The replication started but it didn't transfer all mails. The store isn't big 44GB, transferr

sync_log_chain - is it always needed?

2020-04-28 Thread Olaf Frączyk
Hello, I was wondering why do we need to use this option on middle servers in replication chain? I don't use sync_server. The replication is done using IMAP protocol. Is in this case this setting also necessary? Shouldn't the middle server catch all changes that are done via IMAP protocol

Re: sync_log_chain - is it always needed?

2020-04-29 Thread Olaf Frączyk
On 2020-04-29 03:39, ellie timoney wrote: On Wed, Apr 29, 2020, at 1:12 AM, Olaf Frączyk wrote: I was wondering why do we need to use this option on middle servers in replication chain? Hope this helps, Yes it helped. Thank you. As the replication uses its own protocol even over IMAP

Re: Replication failed 3.0.5 -> 3.0.13

2020-04-29 Thread Olaf Frączyk
On 2020-04-29 16:47, Andrzej Kwiatkowski wrote: Ok. I was asking because of problem with low entropy on VM-s causing performance issues with big installations. I didn't have this issue, however as I said, my installation is really small. If I needed more entropy I would think of using a hardw

Re: sync_log_chain - is it always needed?

2020-05-01 Thread Olaf Frączyk
On 2020-05-01 01:26, ellie timoney wrote: The rolling sync_client takes care of cleaning up each sync_log file as it finishes replicating it downstream. Now consider the case where your replica is an end point, not a link in a chain: it does not have a rolling sync_client forwarding replicatio

sync_client -r stops working after several minutes

2020-05-01 Thread Olaf Frączyk
Hi, cyrus-imapd 3.0.13, CentOS 8 replication over IMAP, no sync_server I try to find out why rolling replication is failing in my case. They sync_client -A works fine. I have enabled logging for cyrus_admin in /var/lib/imap/log/cyrus_admin On the replica side /var/lib/imap/log/cyrus_admin: