Hi Guys, Last night during scheduled maintenance I upgraded our mail cluster from 2.2.5.
Man this took longer than i budgeted for :) (~5000 mailboxes) I have a few queries regarding the migration. I'll not paste them all at once but rather one at a time. The main issue I have at the moment is IMAP is very very slow. In some cases it's timing out. Our webmail server (using overlook (modified squirrelmail)) is taking a good few minutes to render. We have two webmail servers, one is running a local imapd and the other is currently pointing to an imapd on another box, both have the same issue. Our mysql server doesn't have an higher load than normal and i've tried (dare i say it) shutting of postfix frontend so its stops processing mail and this isn't making any difference. I've set TRACE_LEVEL to 5 but cant really see anything specific. These machines are all on bonded gigabit Ethernet and i've tested network throughput to rule out any connectivity/switching problems and this is fine. These are the errors im currently getting; Jun 6 10:53:06 mail4-core-1 dbmail/imap4d[16923]: Error:[server] pool.c,set_lock(+66): Error setting lock. Trying again. Jun 6 10:53:07 mail4-core-1 dbmail/imap4d[16913]: Error:[server] pool.c,set_lock(+66): Error setting lock. Trying again. Jun 6 10:53:18 mail4-core-1 dbmail/imap4d[16859]: Error:[server] pool.c,set_lock(+66): Error setting lock. Trying again. Jun 6 10:53:28 mail4-core-1 dbmail/imap4d[16895]: Error:[server] pool.c,set_lock(+66): Error setting lock. Trying again. Jun 6 10:53:28 mail4-core-1 dbmail/imap4d[16887]: Error:[server] pool.c,set_lock(+66): Error setting lock. Trying again. Jun 6 10:54:12 mail4-core-1 dbmail/imap4d[16905]: Error:[server] pool.c,set_lock(+66): Error setting lock. Trying again. Jun 6 10:54:13 mail4-core-1 dbmail/imap4d[16905]: Error:[server] pool.c,set_lock(+66): Error setting lock. Trying again. Jun 6 10:54:20 mail4-core-1 dbmail/imap4d[16875]: Error:[server] pool.c,set_lock(+66): Error setting lock. Trying again. Jun 6 10:55:30 mail4-core-1 dbmail/imap4d[16895]: Error:[server] pool.c,set_lock(+66): Error setting lock. Trying again. Jun 6 10:55:54 mail4-core-1 dbmail/imap4d[16911]: Error:[server] pool.c,set_lock(+66): Error setting lock. Trying again. Jun 6 10:56:02 mail4-core-1 dbmail/imap4d[17684]: Error:[server] pool.c,set_lock(+66): Error setting lock. Trying again. Jun 6 10:56:32 mail4-core-1 dbmail/imap4d[17684]: Error:[server] pool.c,set_lock(+66): Error setting lock. Trying again. Jun 6 10:56:38 mail4-core-1 dbmail/imap4d[17694]: Error:[server] pool.c,set_lock(+66): Error setting lock. Trying again. Jun 6 10:56:40 mail4-core-1 dbmail/imap4d[17700]: Error:[server] pool.c,set_lock(+66): Error setting lock. Trying again. Jun 6 10:57:14 mail4-core-1 dbmail/lmtpd[14336]: Error:[server] pool.c,set_lock(+66): Error setting lock. Trying again. Jun 6 10:57:28 mail4-core-1 dbmail/imap4d[17702]: Error:[server] pool.c,set_lock(+66): Error setting lock. Trying again. Jun 6 10:57:34 mail4-core-1 dbmail/imap4d[17698]: Error:[server] pool.c,set_lock(+66): Error setting lock. Trying again. Jun 6 10:57:52 mail4-core-1 dbmail/imap4d[17680]: Error:[server] pool.c,set_lock(+66): Error setting lock. Trying again. Jun 6 11:00:52 mail4-core-1 dbmail/imap4d[17674]: Error:[server] pool.c,set_lock(+66): Error setting lock. Trying again. Jun 6 11:00:55 mail4-core-1 dbmail/imap4d[17674]: Error:[server] pool.c,set_lock(+66): Error setting lock. Trying again. Jun 6 11:01:18 mail4-core-1 dbmail/imap4d[17678]: Error:[server] pool.c,set_lock(+66): Error setting lock. Trying again. Jun 6 11:01:34 mail4-core-1 dbmail/lmtpd[14364]: Error:[server] pool.c,set_lock(+66): Error setting lock. Trying again. Jun 6 11:01:49 mail4-core-1 dbmail/imap4d[17674]: Error:[server] pool.c,set_lock(+66): Error setting lock. Trying again. I don't believe i saw these errors in 2.0.10, but perhaps they were there :) Are these normal? Can someone tell me what i should be doing to debug this? It is considerably slower than 2.0.10 on the same hardware (ive had a few complaints of imap being slow in outlook/$OTHER_CLIENTS also, but i cant guarantee these are of the same issue, although it looks likely) If anyone can give me some information that would be greatly appreciated... And thanks for a great product! Regards Jon Duggan Nuco Technologies Ltd [EMAIL PROTECTED] Tel. 0870 165 1300 _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
