Hey guys, After many trials and tribulations I have now got some fairly stable NFS clients serving dovecot-lda and pop3/imap. Over a 9 hour postal/rabid stress test only saw 5 errors for the 4 servers. Wondering if anyone can shed a bit more light on what they mean exactly. I have tried to find "Resource temporarily unavailable" and "No locks available" in the src to get some understanding - however it appears these messages are from a lower level.
With pop3:
Feb 22 03:36:32 mailget01 dovecot: POP3(test992@mailtest06.com): fcntl() failed with file /mnt/mailstore/mailtest06.com/8/test992/dovecot.index.log: Resource temporarily unavailable Feb 22 03:36:32 mailget01 dovecot: POP3(test992@mailtest06.com): mail_index_wait_lock_fd() failed with file /mnt/mailstore/mailtest06.com/8/test992/dovecot.index.log: Resource temporarily unavailable Feb 22 04:16:45 mailget01 dovecot: POP3(test445@mailtest03.com): fcntl() failed with file /mnt/mailstore/mailtest03.com/4/test445/dovecot.index.log: Resource temporarily unavailable Feb 22 04:16:45 mailget01 dovecot: POP3(test445@mailtest03.com): mail_index_wait_lock_fd() failed with file /mnt/mailstore/mailtest03.com/4/test445/dovecot.index.log: Resource temporarily unavailable
Feb 22 13:07:27 mailget01 dovecot: POP3(test999@mailtest06.com): fcntl() failed with file /mnt/mailstore/mailtest06.com/8/test999/dovecot.index: Resource temporarily unavailable Feb 22 13:07:27 mailget01 dovecot: POP3(test999@mailtest06.com): fcntl() failed with file /mnt/mailstore/mailtest06.com/8/test999/dovecot.index: Resource temporarily unavailable Feb 22 13:07:27 mailget01 dovecot: POP3(test999@mailtest06.com): Couldn't open INBOX: Internal error occurred. Refer to server log for more information. [2007-02-22 13:07:27] Feb 22 13:07:27 mailget01 dovecot: POP3(test999@mailtest06.com): No INBOX for user top=0/0, retr=0/0, del=0/0, size=0
Does this mean that pop3 was waiting for a lock, but timed out ? What are the likely affects of this on a client POPing - session times out and they need to reconnect? The "No INBOX" error is little more odd, the same user had successful login 90 minutes earlier.
With deliver:
Feb 22 01:42:03 mailfilter01 deliver(test680@mailtest04.com): fcntl() failed with file /mnt/mailstore/mailtest04.com/10/test680/dovecot.index: No locks available Feb 22 01:42:06 mailfilter01 deliver(test265@mailtest03.com): fcntl() failed with file /mnt/mailstore/mailtest03.com/1/test265/dovecot.index: No locks available Feb 22 03:25:42 mailfilter02 deliver(test454@mailtest03.com): fcntl() failed with file /mnt/mailstore/mailtest03.com/2/test454/dovecot.index: No locks available Feb 22 03:25:45 mailfilter02 deliver(test397@mailtest03.com): fcntl() failed with file /mnt/mailstore/mailtest03.com/7/test397/dovecot.index: No locks available
I assume this means deliver tried to obtain a lock on the index file (probably many times) but failed. Are the likely affects that the message still gets saved to the maildir but the index doesn't get updated?
Regards
Dean Manners