In an effort to try to speed along our conversion process I've been testing out running many simultaneous scripts for creating mailboxes and doing reconstructs on mail folders. So far I'm up to about 100 simultaneous scripts (logins) either doing IMAP mailbox creations or running reconstruct. I've been seeing these errors in the syslog: Jun 13 10:30:51 cyrus imapd[4373]: [ID 866726 local6.error] DBERROR db3: 5 lockers Jun 13 10:30:51 cyrus imapd[4376]: [ID 866726 local6.error] DBERROR db3: 6 lockers Jun 13 10:30:51 cyrus imapd[4381]: [ID 866726 local6.error] DBERROR db3: 6 lockers Jun 13 10:30:51 cyrus imapd[4381]: [ID 866726 local6.error] DBERROR db3: Aborting locker 80004fbc Jun 13 10:30:51 cyrus imapd[4373]: [ID 866726 local6.error] DBERROR db3: 7 lockers I think I've seen the one about "lockers" in the cyrus archives, and it is supposedly harmless but it seems that the ones that say "abort", do just that. Is there a way to tune the Sleepy DB for better performance or longer wait times for locks? I also got this error which seems more severe: Jun 13 10:31:01 cyrus imapd[4124]: [ID 866726 local6.error] DBERROR db3: Unable to allocate memory for transaction detail Jun 13 10:31:01 cyrus imapd[4124]: [ID 391271 local6.error] DBERROR: error beginning txn: Not enough space Jun 13 10:31:01 cyrus imapd[4124]: [ID 335833 local6.error] DBERROR: error fetching user.barfoot: cyrusdb error Is this memory space or disk space? ... both of which should be ample on this system. I'm running Cyrus 2.0.14 + SASL 1.5.24 + DB 3.1.17 on Solaris 8. The machine is pretty hefty, so it should be able to handle this (SunFire 280R w/dual UltraSPARC III, 4GB RAM, external HW RAID and internal fibre channel drives). -- Shawn Sivy, Associate Director of Networking Information Technology The College of New Jersey
