<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body><div style="font-family:Arial;">I also replied personally. Those mailboxes are a clear case of creating folders with 'user.foo.bar' without checking the value of unixhierarchysep, which changed defaults in 3.0.<br></div>
<div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;">mailbox: longlock user^6581^130041194 for 5.2 seconds<br></div>
<div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;">So EVERY SINGLE MAILBOX is in the one number space, global/shared. We don't have a great story for shared mailboxes anway now, and I suspect there is contention on a global lock which would be a user-level lock if the folders were correctly named.<br></div>
<div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;">Bron.<br></div>
<div><br></div>
<div><br></div>
<div>On Thu, 20 Apr 2017, at 20:42, Nicola Nye wrote:<br></div>
<blockquote type="cite"><div>Anyone know what might be going on here causing these errors on 3.0 under red hat?<br></div>
<div><br></div>
<div><br></div>
<div>----- Original message -----<br></div>
<div>From: momoren <<a href="mailto:962747695@qq.com">962747695@qq.com</a>><br></div>
<div>Subject: 回复： Fwd: Imapd unusual memory usage<br></div>
<div>Date: Thu, 20 Apr 2017 17:47:31 +0800<br></div>
<div><br></div>
<div>Hi Dilian & Nicolan,<br></div>
<div> Follow your instruction, we built cyrus3.0 in our redhat7 enironment. So far we didn't get memory leak report from Valgrind. But we're still working on this in case we use it in a wrong way. But we ran into another problem. We got a lot of below error info from imap 3.0 (our build). Could you help to tell if we configured something wrongly?<br></div>
<div><div>Apr 20 04:38:21 NEMS_BE0_Stabi imap[15564]: mailbox: longlock user^6581^130041194 for 5.2 seconds<br></div>
<div>Apr 20 04:38:21 NEMS_BE0_Stabi imap[15676]: mailbox: longlock user^9961^130089235 for 16.6 seconds<br></div>
<div>Apr 20 04:38:21 NEMS_BE0_Stabi imap[15609]: mailbox: longlock user^23012^130055727 for 6.5 seconds<br></div>
<div>Apr 20 04:38:21 NEMS_BE0_Stabi imap[15591]: mailbox: longlock user^11151^130056096 for 11.2 seconds<br></div>
<div>Apr 20 04:38:21 NEMS_BE0_Stabi imap[15562]: mailbox: longlock user^12100^130014830 for 9.5 seconds<br></div>
<div>Apr 20 04:38:23 NEMS_BE0_Stabi imap[15559]: mailbox: longlock user^14969^130053647 for 1.6 seconds<br></div>
<div>Apr 20 04:38:23 NEMS_BE0_Stabi imap[15671]: mailbox: longlock user^4851^130079741 for 1.6 seconds<br></div>
<div>Apr 20 04:38:23 NEMS_BE0_Stabi imap[15608]: mailbox: longlock user^14037^130027560 for 1.2 seconds<br></div>
<div>Apr 20 04:38:23 NEMS_BE0_Stabi imap[15556]: mailbox: longlock user^26533^130054188 for 1.7 seconds<br></div>
<div>Apr 20 04:38:23 NEMS_BE0_Stabi imap[15674]: mailbox: longlock user^8561^130029817 for 7.2 seconds<br></div>
<div>Apr 20 04:38:23 NEMS_BE0_Stabi imap[15636]: mailbox: longlock user^4269^130007938 for 16.6 seconds<br></div>
<div>Apr 20 04:38:23 NEMS_BE0_Stabi imap[15648]: mailbox: longlock user^5812^130029896 for 4.7 seconds<br></div>
<div>Apr 20 04:38:23 NEMS_BE0_Stabi imap[15662]: mailbox: longlock user^16380^130010357 for 10.4 seconds<br></div>
<div>Apr 20 04:38:23 NEMS_BE0_Stabi imap[15588]: mailbox: longlock user^21460^130094740 for 10.4 seconds<br></div>
<div>Apr 20 04:38:23 NEMS_BE0_Stabi imap[15667]: mailbox: longlock user^2793^130085801 for 4.7 seconds<br></div>
<div>Apr 20 04:38:23 NEMS_BE0_Stabi imap[15670]: mailbox: longlock user^3817^130096542 for 6.9 seconds<br></div>
<div>Apr 20 04:38:23 NEMS_BE0_Stabi imap[15544]: mailbox: longlock user^8001^130012057 for 7.4 seconds<br></div>
</div>
<div> <br></div>
<div>Look forward for your help!<br></div>
<div>Nikki<br></div>
<div><div><br></div>
<div><br></div>
<div style="font-size:12px;font-family:"Arial Narrow";padding-bottom:2px;padding-top:2px;padding-left:0px;padding-right:0px;">------------------ 原始邮件 ------------------<br></div>
<div style="font-size:12px;background-image:initial;background-size:initial;background-attachment:initial;background-origin:initial;background-clip:initial;background-color:rgb(239, 239, 239);padding-bottom:8px;padding-top:8px;padding-left:8px;padding-right:8px;"><div><b>发件人:</b> "Дилян Палаузов";<dilyan.palauzov@aegee.org>;<br></div>
<div><b>发送时间:</b> 2017年4月17日(星期一) 晚上6:37<br></div>
<div><b>收件人:</b> "Nicola Nye"<nicolan@fastmail.com>; <wbr><br></div>
<div><b>抄送:</b> "momoren"<962747695@qq.com>; <wbr><br></div>
<div><b>主题:</b> Re: Fwd: Imapd unusual memory usage<br></div>
</div>
<div><br></div>
<div>Hello,<br></div>
<div><br></div>
<div>compile cyrus with debug information, and run it under valgrind:<br></div>
<div><br></div>
<div>valgrind --num-callers=30 --leak-check=full --track-origins=yes <br></div>
<div>--read-var-info=yes --show-leak-kinds=all --trace-children=yes <br></div>
<div>--track-fds=yes /usr/local/cyrus/bin/master -D<br></div>
<div><br></div>
<div>Once the processes starts consuming a lot of memory, terminate them <br></div>
<div>cleanly. If you have luck, in the stderr of valgrind there will be <br></div>
<div>"definitely lost" sections. Share the output of valgrind.<br></div>
<div><br></div>
<div>If it is something trivial, I can find the problem. But 2.4 is not <br></div>
<div>developed any more, you shall lift your version. On the other side the <br></div>
<div>problem might not be fixed in 2.5, if you have done something very special.<br></div>
<div><br></div>
<div>Greetings<br></div>
<div> Dilian<br></div>
<div><br></div>
<div>On 04/17/2017 12:04 PM, Nicola Nye wrote:<br></div>
<div>> Hi all,<br></div>
<div>><br></div>
<div>> I'm sure someone knows the answer to Nikki's question about memory usage<br></div>
<div>> on 2.4.<br></div>
<div>><br></div>
<div>> Is 2.5 more reliable or should they go to 3.0?<br></div>
<div>><br></div>
<div>> Cheers,<br></div>
<div>><br></div>
<div>> Nicola<br></div>
<div>><br></div>
<div>><br></div>
<div>> ----- Original message -----<br></div>
<div>> From: momoren <962747695@qq.com <mailto:962747695@qq.com>><br></div>
<div>> To: nicolan <nicolan@fastmail.com <mailto:nicolan@fastmail.com>><br></div>
<div>> Subject: Imapd unusual memory usage<br></div>
<div>> Date: Mon, 17 Apr 2017 16:44:03 +0800<br></div>
<div>><br></div>
<div>> Dear nicolan,<br></div>
<div>> Now we met a critical issue. Looking forward to your help!<br></div>
<div>> We upgraded from Cyrus imap 2.3.7 to 2.4.17. But the memory of each<br></div>
<div>> single imapd keep increasing. 2.3.7 is total ok. This issue only came<br></div>
<div>> after upgraded to 2.4.17. Do you happen to know some memory leak issue<br></div>
<div>> related to imapd? Or do you know if it's due to the behavior change in<br></div>
<div>> new version? If so, how to stop the memory rise?<br></div>
<div>> BTW, if we change to 3.0, do you know if it works on Redhat 7?<br></div>
<div>><br></div>
<div>> Best Regards!<br></div>
<div>> Nikki<br></div>
<div>> <br></div>
<div><br></div>
</div>
<div><br></div>
</blockquote><div style="font-family:Arial;"><br></div>
<div id="sig567075"><div class="signature">--<br></div>
<div class="signature"> Bron Gondwana<br></div>
<div class="signature"> brong@fastmail.fm<br></div>
<div class="signature"><br></div>
</div>
<div style="font-family:Arial;"><br></div>
</body>
</html>