[Dovecot] errors after 1.0a3 -> 1.0a4
Hi,
somebody else seeing these?
Oct 21 09:14:06 ymmv dovecot: imap-login: Login: user=<xxxx>, method=CRAM-MD5, rip=84.162.151.124, lip=85.214.25.134, TLS Oct 21 09:14:07 ymmv dovecot: imap-login: epoll_ctl(): No such file or directory Oct 21 09:14:07 ymmv dovecot: child 11419 (login) returned error 89
mailbox access fails after that.
Had this already yesterday, then downgraded to alpha3 and it worked again, upgraded again and it kept working.
Strange thing is, access through squirrelmail works perfect, but using Thunderbird gives these errors.
I'm using maildir with epoll and inotify, if that matters.
Jakob Hirsch wrote:
somebody else seeing these?
it seems not.
FWIW, there are other issues. alpha3 had a lot less errors/warnings.
This is still coming all the time: Oct 22 00:03:02 ymmv dovecot: imap(nici): inotify_rm_watch() failed: Invalid argument
This seems to be related to lock_method flock, with fcntl it's gone. Deleting the index-files doesn't help.
Oct 22 00:03:03 ymmv dovecot: imap(nici): Lost transaction log file /var/spool/vmail/nici/./Maildir/dovecot.index.log seq 2 Oct 22 00:03:03 ymmv dovecot: imap(nici): Lost transaction log file /var/spool/vmail/nici/./Maildir/dovecot.index.log seq 2 Oct 22 00:19:01 ymmv dovecot: imap(jh): Corrupted transaction log file /var/spool/vmail/jh/./Maildir/dovecot.index.log: Append with UID 5323, but next_uid = 5324 ...
On Sat, 2005-10-22 at 00:40 +0200, Jakob Hirsch wrote:
Jakob Hirsch wrote:
somebody else seeing these?
it seems not.
FWIW, there are other issues. alpha3 had a lot less errors/warnings.
This is still coming all the time: Oct 22 00:03:02 ymmv dovecot: imap(nici): inotify_rm_watch() failed: Invalid argument
I've heard I've broken at least epoll. Maybe inotify went with it?
This seems to be related to lock_method flock, with fcntl it's gone. Deleting the index-files doesn't help.
Oct 22 00:03:03 ymmv dovecot: imap(nici): Lost transaction log file /var/spool/vmail/nici/./Maildir/dovecot.index.log seq 2 Oct 22 00:03:03 ymmv dovecot: imap(nici): Lost transaction log file /var/spool/vmail/nici/./Maildir/dovecot.index.log seq 2 Oct 22 00:19:01 ymmv dovecot: imap(jh): Corrupted transaction log file /var/spool/vmail/jh/./Maildir/dovecot.index.log: Append with UID 5323, but next_uid = 5324 ...
You mean this "Append with UID .. but next_uid" error happens constantly with flock, but not with fcntl? And this isn't NFS-mounted or anything? The error sounds like the locking wouldn't work, but flock should work just as well as fcntl, and with NFS give an error..
Timo Sirainen wrote:
FWIW, there are other issues. alpha3 had a lot less errors/warnings. This is still coming all the time: Oct 22 00:03:02 ymmv dovecot: imap(nici): inotify_rm_watch() failed: Invalid argument I've heard I've broken at least epoll. Maybe inotify went with it?
It seems not that borken, as things work fine. Maybe dovecot tries to remove a watch that is already removed?
Oct 22 00:19:01 ymmv dovecot: imap(jh): Corrupted transaction log file /var/spool/vmail/jh/./Maildir/dovecot.index.log: Append with UID 5323, but next_uid = 5324 You mean this "Append with UID .. but next_uid" error happens constantly with flock, but not with fcntl? And this isn't NFS-mounted or anything?
Yes. Right after switching from flock to fcntl, I get this again:
dovecot: imap(jh): Corrupted transaction log file /var/spool/vmail/jh/./Maildir/dovecot.index.log: Append with UID 5479, but next_uid = 5480
No NFS here, simple ReiserFS with Fedora kernel 2.6.13-1.1532_FC4. Bugzilla doesn't show any problem with flock.
The error sounds like the locking wouldn't work, but flock should work just as well as fcntl, and with NFS give an error..
And it works, just tested with a little C code. It blocks if a file is locked or returns with errno==11 (Resource temporarily unavailable) if called with LOCK_NB. Very strange, I seem to be the only one having this issue.
On Sat, 2005-10-29 at 11:55 +0200, Jakob Hirsch wrote:
Oct 22 00:03:02 ymmv dovecot: imap(nici): inotify_rm_watch() failed: Invalid argument I've heard I've broken at least epoll. Maybe inotify went with it?
It seems not that borken, as things work fine.
You wouldn't really notice if inotify didn't work, or did you specifically test notifications in IDLE?
I don't really have time to look at this right now, the test is easy: make a stupid maildir somewhere, run MAIL=... /path/to/imap and then A SELECT INBOX B IDLE
and now copy some mail files into your maildir's new/ folder. If you get a message on the imap session, all is fine. If not, it's broken.
johannes
Johannes Berg wrote:
Oct 22 00:03:02 ymmv dovecot: imap(nici): inotify_rm_watch() failed: Invalid argument I've heard I've broken at least epoll. Maybe inotify went with it? It seems not that borken, as things work fine. You wouldn't really notice if inotify didn't work, or did you specifically test notifications in IDLE?
I assumed it works, because I get immediate notification in my IMAP client when new mail arrives. But I tested this now specifically and it shows the intended behaviour:
...
1 OK User logged in 2 select INBOX
- FLAGS (\Answered \Flagged \Deleted \Seen \Draft $MDNSent)
- OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft $MDNSent \*)] Flags permitted.
- 19 EXISTS
- 0 RECENT
- OK [UNSEEN 17] First unseen.
- OK [UIDVALIDITY 1112486837] UIDs valid
- OK [UIDNEXT 5491] Predicted next UID 2 OK [READ-WRITE] Select completed. 3 idle
- idling
- 20 EXISTS
Last line comes just after a 'touch Maildir/cur/bla1'.
On Sat, 2005-10-29 at 12:43 +0200, Jakob Hirsch wrote:
I assumed it works, because I get immediate notification in my IMAP client when new mail arrives. But I tested this now specifically and it shows the intended behaviour:
Last line comes just after a 'touch Maildir/cur/bla1'.
Seems to work then. No idea why the error.
johannes
Timo Sirainen wrote:
I've heard I've broken at least epoll. Maybe inotify went with it?
epoll seems really to be broken. At least I get this errors:
Oct 31 17:18:35 ymmv dovecot: imap-login: epoll_ctl(): No such file or directory Oct 31 17:18:35 ymmv dovecot: child 7643 (login) returned error 89
dovecot compiled --with-iopool=epoll and using SSL (imaps). Without SSL everything is fine. So there must be some difference when using SSL.
using --with-ioloop=poll dovecot works fine, whether I use SSL or not.
participants (3)
-
Jakob Hirsch
-
Johannes Berg
-
Timo Sirainen