Summary: | net-mail/dovecot-2.0.19: crashes every now then when a user tries to login | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Lutz Schildt <ls> |
Component: | [OLD] Server | Assignee: | Eray Aslan <eras> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | CC: | alunduil, mjo, net-mail+disabled |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
dovecot.conf
dovecot-sql.conf.ext dovecot config files Test ebuild for dovecot-2.2.alpha1 |
Description
Lutz Schildt
2012-05-12 12:31:23 UTC
It looks like the assertion failed during config file parsing, can you post your dovecot.conf? Created attachment 311555 [details]
dovecot.conf
Created attachment 311557 [details]
dovecot-sql.conf.ext
Sorry for comment-spam :( dovecot.conf and dovecot-sql.conf.ext have been attached. database name, user and password have been modified obviously. doveconf does crash every now and then as well as I just found out. Feels like it crashes once with the same output as dovecot/config in every 20 to 30 times I run it. (In reply to comment #2) > Created attachment 311555 [details] > dovecot.conf Is this really your config file, or the output of `doveconf` (one can't tell, but Timo thought it was the latter)? He also said that there were fixes to settings-parser.c in the dovecot-2.1, so if you're willing to brave the upgrade, that could either fix the problem or confirm that it still exists in 2.1. It's the output of doveconf (In reply to comment #6) > It's the output of doveconf Can you post the actual config file? If there's really a bug in the parser, it might only be triggered on the actual file. The actual config consists of roughly 20+ files, I'd have to go through all of them manually and remove passwords etc. Also do you want me to put them into an archive? (In reply to comment #8) > The actual config consists of roughly 20+ files, I'd have to go through all > of them manually and remove passwords etc. Also do you want me to put them > into an archive? Yeah, sorry. I'll set up an installation of 2.0.19 here and see if I can get it to crash, but I'll need your real config files (sans passwords) otherwise I'm sure it would work. If I can get it to crash, I can try to the 2.1.x upgrade and see what happens. Created attachment 311801 [details]
dovecot config files
(In reply to comment #10) > Created attachment 311801 [details] > dovecot config files I'm not able to reproduce this running `doveconf` a few hundred thousand times on a desktop machine. The machines look "close enough," i.e. I was able to use your CFLAGS. We're running 2.0.17 on our main IMAP server at the moment... I'm going to upgrade that now and see if those errors start to show up in the logs tomorrow. (In reply to comment #11) > > We're running 2.0.17 on our main IMAP server at the moment... I'm going to > upgrade that now and see if those errors start to show up in the logs > tomorrow. Well, I upgraded, but hit a problem. I was able to run `doveconf` without it crashing, however, sieve broke. I started seeing "...Error: sieve: failed to open script..." and messages failing to be filtered in the logs. I can't have that be broken in the morning, so I had to revert to 2.0.17 for now (which is working fine again with the same config). (In reply to comment #12) > Well, I upgraded, but hit a problem. I was able to run `doveconf` without it > crashing, however, sieve broke. I started seeing "...Error: sieve: failed to > open script..." and messages failing to be filtered in the logs. > > I can't have that be broken in the morning, so I had to revert to 2.0.17 for > now (which is working fine again with the same config). I've been having the same issues with 2.0.19 but not able to find any information on the issue. In particular it seems that 2.0.19 can't find personal includes on my setup. Same exact config runs just fine with 2.0.17. Was looking to test that again today but noticed that 2.0.17 has been removed from the tree so until that either gets added back in (not sure if that's something that happens) or I see this issue is resolved I don't feel comfortable playing around with the 2.0.19 issue. (In reply to comment #13) > (In reply to comment #12) > > Well, I upgraded, but hit a problem. I was able to run `doveconf` without it > > crashing, however, sieve broke. I started seeing "...Error: sieve: failed to > > open script..." and messages failing to be filtered in the logs. > > > > I can't have that be broken in the morning, so I had to revert to 2.0.17 for > > now (which is working fine again with the same config). > > I've been having the same issues with 2.0.19 but not able to find any > information on the issue. In particular it seems that 2.0.19 can't find > personal includes on my setup. Same exact config runs just fine with 2.0.17. > > Was looking to test that again today but noticed that 2.0.17 has been > removed from the tree so until that either gets added back in (not sure if > that's something that happens) or I see this issue is resolved I don't feel > comfortable playing around with the 2.0.19 issue. You can safely pull the 2.0.17 ebuild from CVS, though: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-mail/dovecot/dovecot-2.0.17.ebuild?revision=1.10 I've got bigger problems right now, but sooner or later I'll have to just skip 2.0.19 and see if the 2.1.x series works. I've added dovecot-2.0.17 back to the tree for now. (In reply to comment #12) > (In reply to comment #11) > > > > We're running 2.0.17 on our main IMAP server at the moment... I'm going to > > upgrade that now and see if those errors start to show up in the logs > > tomorrow. > > Well, I upgraded, but hit a problem. I was able to run `doveconf` without it > crashing, however, sieve broke. I started seeing "...Error: sieve: failed to > open script..." and messages failing to be filtered in the logs. > > I can't have that be broken in the morning, so I had to revert to 2.0.17 for > now (which is working fine again with the same config). This was due to a bug fix in 2.0.18: http://dovecot.org/list/dovecot/2012-February/063748.html I've just upgraded to 2.1.9 and things look OK after I fixed that. Ditto, everything is working fine here in 2.1.9 with the sieve changes. Closing as dovecot-2.0.19 is no longer in the tree. With dovecot 2.0.17 and 2.0.19 gone from the tree, I now had to move to 2.1.12-r1 and I'm still experiencing the exact same issue. dovecot-2.0.17 with the last version this did not happen, as of 2.0.19 this happens from time to time. I'm open for any suggestions. (In reply to comment #19) > With dovecot 2.0.17 and 2.0.19 gone from the tree, I now had to move to > 2.1.12-r1 and I'm still experiencing the exact same issue. > > dovecot-2.0.17 with the last version this did not happen, as of 2.0.19 this > happens from time to time. > > I'm open for any suggestions. Did you check my last post? There was a bugfix in sieve that was responsible for the crash (i.e., you have a slight mistake in your config, which used to work): http://dovecot.org/list/dovecot/2012-February/063748.html I'm not using sieve and the USE-flag is disabled. (In reply to comment #21) > I'm not using sieve and the USE-flag is disabled. Oh, duh, sorry. I forgot that the original wasn't what was keeping me off 2.0.19. Created attachment 334388 [details]
Test ebuild for dovecot-2.2.alpha1
I threw together this ebuild for the latest alpha (I just hard-coded the version/paths, and deleted the pigeonhole stuff). It at least starts up here.
If you still get the error with this, you should post the backtrace either to dovecot-users (where the author will see it), or back here (and I can relay it there). Crashes with backtraces are usually fixed quickly.
|