I've still over 200 mails unread in the mailing list, and important things left in TODO. This release is an improvement over rc7 anyway, hopefully I'll have time to fix the rest soon.
http://dovecot.org/releases/dovecot-1.0.rc8.tar.gz http://dovecot.org/releases/dovecot-1.0.rc8.tar.gz.sig
* GSSAPI: Changed POP3 service name to "pop", which is what the
standard says
* "mbox:/var/mail/%u" no longer works as the mail location. You'll
have to specify the mail root explicitly, just like the examples
always have: "mbox:~/mail:INBOX=/var/mail/%u"
+ SHA1, LDAP-MD5, PLAIN-MD5, PLAIN-MD4: The password can be now either
hex or base64 encoded. The encoding is detected automatically based
on the password string length.
+ Allow running only Dovecot master and dovecot-auth processes with
protocols=none setting
+ deliver: -f <envelope sender> parameter can be used to set mbox
From_-line's sender address
+ deliver: Log all mail saves and failures
+ Tru64 SIA passdb support. Patch by Simon L Jackson.
- INBOX was listed twice in mailbox list if namespace prefix was used
- INBOX-prefixed namespaces were a bit broken
- kqueue: Fix 100% CPU usage
- deliver: Duplicate storage was a bit broken
- dictionary code was broken (ie. dict quota)
- SIGHUP caused crashes sometimesHi,
On Mon, Oct 09, 2006 at 09:33:18PM +0300, Timo Sirainen wrote:
I've still over 200 mails unread in the mailing list, and important things left in TODO. This release is an improvement over rc7 anyway, hopefully I'll have time to fix the rest soon.
http://dovecot.org/releases/dovecot-1.0.rc8.tar.gz http://dovecot.org/releases/dovecot-1.0.rc8.tar.gz.sig
I updated the packages at http://ATrpms.net/name/dovecot/
- GSSAPI: Changed POP3 service name to "pop", which is what the standard says
- "mbox:/var/mail/%u" no longer works as the mail location. You'll have to specify the mail root explicitly, just like the examples always have: "mbox:~/mail:INBOX=/var/mail/%u"
- SHA1, LDAP-MD5, PLAIN-MD5, PLAIN-MD4: The password can be now either hex or base64 encoded. The encoding is detected automatically based on the password string length.
- Allow running only Dovecot master and dovecot-auth processes with protocols=none setting
- deliver: -f <envelope sender> parameter can be used to set mbox From_-line's sender address
- deliver: Log all mail saves and failures
- Tru64 SIA passdb support. Patch by Simon L Jackson.
- INBOX was listed twice in mailbox list if namespace prefix was used
- INBOX-prefixed namespaces were a bit broken
- kqueue: Fix 100% CPU usage
- deliver: Duplicate storage was a bit broken
- dictionary code was broken (ie. dict quota)
- SIGHUP caused crashes sometimes
-- Axel.Thimm at ATrpms.net
On Mon, October 9, 2006 20:33, Timo Sirainen wrote:
I've still over 200 mails unread in the mailing list, and important things left in TODO. This release is an improvement over rc7 anyway, hopefully I'll have time to fix the rest soon.
Upgraded from RC2 to RC8, and for the first time since I installed RC2 - dovecot crashed with the following line:
dovecot: Oct 11 08:38:08 Error: Login process died too early - shutting down
// Tom
On Wed, 2006-10-11 at 08:46 +0200, Tom Sommer wrote:
On Mon, October 9, 2006 20:33, Timo Sirainen wrote:
I've still over 200 mails unread in the mailing list, and important things left in TODO. This release is an improvement over rc7 anyway, hopefully I'll have time to fix the rest soon.
Upgraded from RC2 to RC8, and for the first time since I installed RC2 - dovecot crashed with the following line:
dovecot: Oct 11 08:38:08 Error: Login process died too early - shutting down
Immediately at startup or sometimes later? What about the reason why the login process crashed? If it's not shown it's because there's a bug that sometimes the last logging messages are lost.. If you run dovecot through strace -f you should see the messages (probably in log, or at least in the strace log).
On Wed, October 11, 2006 12:22, Timo Sirainen wrote:
On Wed, 2006-10-11 at 08:46 +0200, Tom Sommer wrote:
On Mon, October 9, 2006 20:33, Timo Sirainen wrote:
I've still over 200 mails unread in the mailing list, and important things left in TODO. This release is an improvement over rc7 anyway, hopefully I'll have time to fix the rest soon.
Upgraded from RC2 to RC8, and for the first time since I installed RC2
dovecot crashed with the following line:
dovecot: Oct 11 08:38:08 Error: Login process died too early - shutting down
Immediately at startup or sometimes later? What about the reason why the login process crashed? If it's not shown it's because there's a bug that sometimes the last logging messages are lost.. If you run dovecot through strace -f you should see the messages (probably in log, or at least in the strace log).
It was running fine for ~24 hours, then it crashed.
There wasn't anything else in the log besides what I posted - I'll try and run logging with full debug enabled, that might provide more details, should it happen again.
I'm not familiar with running strace though :)
On Wed, 2006-10-11 at 13:11 +0200, Tom Sommer wrote:
Immediately at startup or sometimes later? What about the reason why the login process crashed? If it's not shown it's because there's a bug that sometimes the last logging messages are lost.. If you run dovecot through strace -f you should see the messages (probably in log, or at least in the strace log).
It was running fine for ~24 hours, then it crashed.
There wasn't anything else in the log besides what I posted - I'll try and run logging with full debug enabled, that might provide more details, should it happen again.
I'm not familiar with running strace though :)
This patch should fix the logging:
http://dovecot.org/list/dovecot-cvs/2006-October/006473.html
On Wed, October 11, 2006 14:21, Timo Sirainen wrote:
On Wed, 2006-10-11 at 13:11 +0200, Tom Sommer wrote:
Immediately at startup or sometimes later? What about the reason why the login process crashed? If it's not shown it's because there's a bug that sometimes the last logging messages are lost.. If you run dovecot through strace -f you should see the messages (probably in log, or at least in the strace log).
It was running fine for ~24 hours, then it crashed.
There wasn't anything else in the log besides what I posted - I'll try and run logging with full debug enabled, that might provide more details, should it happen again.
I'm not familiar with running strace though :)
This patch should fix the logging:
http://dovecot.org/list/dovecot-cvs/2006-October/006473.html
Thanks, it just crashed again - I've applied the patch, will report back with results next time it does so :)
On Wed, October 11, 2006 15:47, Tom Sommer wrote:
On Wed, October 11, 2006 14:21, Timo Sirainen wrote:
On Wed, 2006-10-11 at 13:11 +0200, Tom Sommer wrote:
Immediately at startup or sometimes later? What about the reason why the login process crashed? If it's not shown it's because there's a bug that sometimes the last logging messages are lost.. If you run dovecot through strace -f you should see the messages (probably in log, or at least in the strace log).
It was running fine for ~24 hours, then it crashed.
There wasn't anything else in the log besides what I posted - I'll try and run logging with full debug enabled, that might provide more details, should it happen again.
I'm not familiar with running strace though :)
This patch should fix the logging:
http://dovecot.org/list/dovecot-cvs/2006-October/006473.html
Thanks, it just crashed again - I've applied the patch, will report back with results next time it does so :)
Just crashed again, same stuff in log - nothing more, nothing less
Reverting back to RC2, let me know if you want me to do further
On Wed, 2006-10-11 at 18:35 +0200, Tom Sommer wrote:
There wasn't anything else in the log besides what I posted - I'll try and run logging with full debug enabled, that might provide more details, should it happen again.
I'm not familiar with running strace though :)
This patch should fix the logging:
http://dovecot.org/list/dovecot-cvs/2006-October/006473.html
Thanks, it just crashed again - I've applied the patch, will report back with results next time it does so :)
Just crashed again, same stuff in log - nothing more, nothing less
Reverting back to RC2, let me know if you want me to do further
Hmh. Maybe the logging patch didn't fix it completely then. How about this then, it just slows down creating login new login processes instead of killing the whole dovecot:
http://dovecot.org/list/dovecot-cvs/2006-October/006475.html
On Thu, October 12, 2006 11:13, Timo Sirainen wrote:
On Wed, 2006-10-11 at 18:35 +0200, Tom Sommer wrote:
There wasn't anything else in the log besides what I posted - I'll try and run logging with full debug enabled, that might provide more details, should it happen again.
I'm not familiar with running strace though :)
This patch should fix the logging:
http://dovecot.org/list/dovecot-cvs/2006-October/006473.html
Thanks, it just crashed again - I've applied the patch, will report back with results next time it does so :)
Just crashed again, same stuff in log - nothing more, nothing less
Reverting back to RC2, let me know if you want me to do further
Hmh. Maybe the logging patch didn't fix it completely then. How about this then, it just slows down creating login new login processes instead of killing the whole dovecot:
http://dovecot.org/list/dovecot-cvs/2006-October/006475.html
Ok, running the patch now
Funny thing is, the crash only happens on one of the server, I got 5 others which doesn't have any problems
On Thu, October 12, 2006 11:23, Tom Sommer wrote:
On Thu, October 12, 2006 11:13, Timo Sirainen wrote:
On Wed, 2006-10-11 at 18:35 +0200, Tom Sommer wrote:
There wasn't anything else in the log besides what I posted - I'll try and run logging with full debug enabled, that might provide more details, should it happen again.
I'm not familiar with running strace though :)
This patch should fix the logging:
http://dovecot.org/list/dovecot-cvs/2006-October/006473.html
Thanks, it just crashed again - I've applied the patch, will report back with results next time it does so :)
Just crashed again, same stuff in log - nothing more, nothing less
Reverting back to RC2, let me know if you want me to do further
Hmh. Maybe the logging patch didn't fix it completely then. How about this then, it just slows down creating login new login processes instead of killing the whole dovecot:
http://dovecot.org/list/dovecot-cvs/2006-October/006475.html
Ok, running the patch now
Funny thing is, the crash only happens on one of the server, I got 5 others which doesn't have any problems
Hrm, I read the other thread about this issue - do you think the cause is that max connections are reached?
The server with the problem is perhaps the busiest server we have, the others don't have nearly that many logins.
On Thu, 2006-10-12 at 11:51 +0200, Tom Sommer wrote:
Hrm, I read the other thread about this issue - do you think the cause is that max connections are reached?
It's not at least that simple, because I can't reproduce it by setting max login processes to 2 and then trying to log in with more than 2 clients in different ways.
On Thu, October 12, 2006 14:13, Timo Sirainen wrote:
On Thu, 2006-10-12 at 11:51 +0200, Tom Sommer wrote:
Hrm, I read the other thread about this issue - do you think the cause is that max connections are reached?
It's not at least that simple, because I can't reproduce it by setting max login processes to 2 and then trying to log in with more than 2 clients in different ways.
Latest log entry:
dovecot: Oct 13 00:19:15 Error: Temporary failure in creating login processes, slowing down for now dovecot: Oct 13 00:19:15 Info: Created login processes successfully, unstalling
On Fri, 2006-10-13 at 10:25 +0200, Tom Sommer wrote:
On Thu, October 12, 2006 14:13, Timo Sirainen wrote:
On Thu, 2006-10-12 at 11:51 +0200, Tom Sommer wrote:
Hrm, I read the other thread about this issue - do you think the cause is that max connections are reached?
It's not at least that simple, because I can't reproduce it by setting max login processes to 2 and then trying to log in with more than 2 clients in different ways.
Latest log entry:
dovecot: Oct 13 00:19:15 Error: Temporary failure in creating login processes, slowing down for now dovecot: Oct 13 00:19:15 Info: Created login processes successfully, unstalling
What else related to it? I was hoping now there would be an actual error message written by an imap-login process.
On Wed, October 11, 2006 12:22, Timo Sirainen wrote:
On Wed, 2006-10-11 at 08:46 +0200, Tom Sommer wrote:
On Mon, October 9, 2006 20:33, Timo Sirainen wrote:
I've still over 200 mails unread in the mailing list, and important things left in TODO. This release is an improvement over rc7 anyway, hopefully I'll have time to fix the rest soon.
Upgraded from RC2 to RC8, and for the first time since I installed RC2
dovecot crashed with the following line:
dovecot: Oct 11 08:38:08 Error: Login process died too early - shutting down
Immediately at startup or sometimes later? What about the reason why the login process crashed? If it's not shown it's because there's a bug that sometimes the last logging messages are lost.. If you run dovecot through strace -f you should see the messages (probably in log, or at least in the strace log).
No it runs for several hours before it crashes, there is no pattern before it happens.
I'm running with the patches you gave me, and --enable-debug and *_debug to yes.
I'm sorry, I'm not familiar with strace.
participants (3)
-
Axel Thimm
-
Timo Sirainen
-
Tom Sommer