Re: [Dovecot] lock file
----- Original Message ----- From: "Simon Waters" simonw@zynet.net To: "Obantec Support" support@obantec.net Sent: Thursday, August 18, 2005 12:33 PM Subject: Re: [Dovecot] lock file
On Thursday 18 Aug 2005 12:19 pm, Obantec Support wrote: <snip>
What is your question?
Yes it is a lock file, by default (if you must use mbox) Dovecot overrides them in 30s I believe.
Either work out if it is genuine, and delete it if not.
You only need to use dotlock locking if you are using NFS (or similar), and using "mbox". Hopefully this only affects a small number of big mail servers, and most of them would presumably switch to maildir when deploying dovecot over NFS anyway.
Hi
not using NFS. my question is what is it, why is it happening and how do i get my users mbox working again.
as soon as i delete it it comes back with 1B contents 0
Mark
On Thu, 2005-08-18 at 13:14 +0100, Obantec Support wrote:
On Thursday 18 Aug 2005 12:19 pm, Obantec Support wrote: <snip>
What is your question?
Yes it is a lock file, by default (if you must use mbox) Dovecot overrides them in 30s I believe.
Either work out if it is genuine, and delete it if not.
You only need to use dotlock locking if you are using NFS (or similar), and using "mbox". Hopefully this only affects a small number of big mail servers, and most of them would presumably switch to maildir when deploying dovecot over NFS anyway.
Hi
not using NFS. my question is what is it, why is it happening and how do i get my users mbox working again. as soon as i delete it it comes back with 1B contents 0
mbox.lock file is created when something starts modifying the mbox file. It's deleted after the modification is finished. Are there some errors in Dovecot's logs that would explain why it doesn't delete the lock file? It should be removed in all other cases except if Dovecot crashes. If it did crash, please get a gdb backtrace as explained in http://dovecot.org/bugreport.html
----- Original Message ----- From: "Timo Sirainen" tss@iki.fi To: "Obantec Support" support@obantec.net Cc: dovecot@dovecot.org Sent: Friday, August 19, 2005 5:19 PM Subject: Re: [Dovecot] lock file
Hi Timo
Weird, i found several old pop3 PID's running under the user campusuk_002 UID. and old procmail PID's for the user. Killed the first pop3 PID and maillog shows
Aug 19 18:34:09 proteus2a dovecot: POP3(campusuk_002): file_unlock_dotlock() failed with mbox file /var/spool/mail/campusuk_002: No such file or directory Aug 19 18:34:09 proteus2a sendmail[15715]: j7HKm2Nv016768: to=uk@campusuk.com, delay=1+20:46:05, xdelay=21:48:46, mailer=local, pri=120724, dsn=2.0.0, stat=Sent Aug 19 18:34:09 proteus2a sendmail[19370]: j7HKI7c2014841: to=uk@campusuk.com, delay=1+21:14:00, xdelay=20:48:45, mailer=local, pri=120790, dsn=2.0.0, stat=Sent Aug 19 18:34:09 proteus2a dovecot: POP3(campusuk_002): Our dotlock file /var/spool/mail/campusuk_002.lock was deleted Aug 19 18:34:09 proteus2a dovecot: POP3(campusuk_002): file_unlock_dotlock() failed with mbox file /var/spool/mail/campusuk_002: No such file or directory Aug 19 18:34:09 proteus2a sendmail[4760]: j7I9FE2p029541: to=manzoor@campusuk.com, delay=1+08:18:55, xdelay=15:48:42, mailer=local, pri=122721, dsn=2.0.0, stat=Sent Aug 19 18:34:09 proteus2a dovecot: POP3(campusuk_002): Our dotlock file /var/spool/mail/campusuk_002.lock was deleted Aug 19 18:34:09 proteus2a dovecot: POP3(campusuk_002): file_unlock_dotlock() failed with mbox file /var/spool/mail/campusuk_002: No such file or directory Aug 19 18:34:09 proteus2a dovecot: POP3(campusuk_002): Our dotlock file /var/spool/mail/campusuk_002.lock was deleted Aug 19 18:34:09 proteus2a dovecot: POP3(campusuk_002): file_unlock_dotlock() failed with mbox file /var/spool/mail/campusuk_002: No such file or directory
Where it says "/var/spool/mail/campusuk_002: No such file or directory" ?? it is there i can see it an now its 1MB as there were 16 emails in the mqueue in sending state but locked out.
Mark
participants (2)
-
Obantec Support
-
Timo Sirainen