[Dovecot] Problems after upgrade (0.99.x -> 1.0.x)
Hello :)
I had a working Dovecot 0.99.x with the following dovecot.conf: ### ssl_disable = yes disable_plaintext_auth = no login = imap verbose_proctitle = yes default_mail_env = maildir:%h/Maildir auth = default auth_mechanisms = plain auth_userdb = passwd /etc/passwd auth_passdb = shadow /etc/shadow auth_user = root protocols = imap pop3 ###
Then I've downloaded, compiled and installed Doveot 1.0.rc6, I tried lot of "possibilities" in the new dovecot.conf but I always get :
dovecot: Dovecot v1.0.rc6 starting up dovecot: Login process died too early - shutting down dovecot: child 15288 (login) killed with signal 11 dovecot: child 15289 (login) killed with signal 11 dovecot: child 15290 (login) killed with signal 11
Some add. info:
# dovecot -n # /usr/local/etc/dovecot.conf ssl_disable: yes login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login auth default: passdb: driver: shadow args: /etc/shadow userdb: driver: passwd
How can I get the new Dovecot acting as the old one? I don't use pam (which seems to be default now), simply shadow passwords (Slackware). http://wiki.dovecot.org/UpgradingDovecot did not help me.
TIA, websafe
* On 15/08/06 16:50 +0200, fazer69@o2.pl wrote:
| Hello :)
|
| I had a working Dovecot 0.99.x with the following dovecot.conf:
1.0rc6 crashes with the errors you mention. Try the nightly snapshot
instead. To be honest, I am still watching the unfolding events while
running 1.0rc2, which my customers haven't complained about.
-Wash
http://www.netmeister.org/news/learn2quote.html
DISCLAIMER: See http://www.wananchi.com/bms/terms.php
--
+======================================================================+
|\ _,,,---,,_ | Odhiambo Washington
Odhiambo WASHINGTON wrote::
- On 15/08/06 16:50 +0200, fazer69@o2.pl wrote: 1.0rc6 crashes with the errors you mention. Try the nightly snapshot instead. To be honest, I am still watching the unfolding events while running 1.0rc2, which my customers haven't complained about.
Thanks for Your reply :) I've tried with the latest nightly, but it didn't help. I think it was a problem in my config and some real chaos ]:-> with libz on this server.
Dovecot was compiled:
#
make clean
./configure
--prefix=/usr
--localstatedir=/var
--sysconfdir=/etc
--enable-debug
--enable-shared
--enable-dependency-tracking
&& make
&& make install
#
Now I run dovecot using:
LD_LIBRARY_PATH=/usr/lib/dovecot/:/usr/lib/dovecot/imap/ dovecot
and everything works fine, even Postfix with Dovecot SASL :))) with this simple /etc/dovecot.conf:
# # /etc/dovecot.conf protocols = pop3 imap disable_plaintext_auth = no ssl_disable = yes protocol imap { } protocol pop3 { } protocol lda { postmaster_address = postmaster@mydomain.tld } auth default { mechanisms = plain login passdb shadow { } userdb passwd { } socket listen { client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } user = root } ###
Maybe someone will find it useful ;-)
-- websafe
On Tue, 2006-08-15 at 22:22 +0200, websafe wrote:
./configure
--prefix=/usr
--localstatedir=/var
--sysconfdir=/etc
--enable-debug \
--enable-debug is a bad idea to use in production. It just slows things down and may flood your log files with useless information.
--enable-shared \
Usually better if you don't change these from defaults. Although I suppose this is the default.
fazer69@o2.pl writes:
dovecot: Dovecot v1.0.rc6 starting up dovecot: Login process died too early - shutting down dovecot: child 15288 (login) killed with signal 11 dovecot: child 15289 (login) killed with signal 11 dovecot: child 15290 (login) killed with signal 11
How can I get the new Dovecot acting as the old one?
Does this reproduce after a reboot? If so, get a stack backtrace from the core file or by attaching a debugger such as GDB and post it.
-- Matthias Andree
Matthias Andree wrote::
dovecot: Dovecot v1.0.rc6 starting up dovecot: Login process died too early - shutting down dovecot: child 15288 (login) killed with signal 11 dovecot: child 15289 (login) killed with signal 11 dovecot: child 15290 (login) killed with signal 11 How can I get the new Dovecot acting as the old one? Does this reproduce after a reboot? If so, get a stack backtrace from
fazer69#o2.pl writes: the core file or by attaching a debugger such as GDB and post it.
Yes, after reboot it was the same. When I now start Dovecot, simply by typing:
dovecot
Aug 15 23:45:30 phazer dovecot: Dovecot v1.0.rc6 starting up Aug 15 23:45:32 phazer dovecot: Login process died too early - shutting down Aug 15 23:45:32 phazer dovecot: imap-login: Panic: Leaked file fd 5: dev 0.10 inode 5 Aug 15 23:45:32 phazer last message repeated 2 times Aug 15 23:45:32 phazer dovecot: pop3-login: Panic: Leaked file fd 5: dev 0.10 inode 5 Aug 15 23:45:32 phazer dovecot: pop3-login: Panic: Leaked file fd 5: dev 0.10 inode 5 Aug 15 23:45:32 phazer dovecot: auth(default): Panic: Leaked file fd 5: dev 0.10 inode 5 Aug 15 23:45:32 phazer dovecot: child 10139 (auth) killed with signal 6 Aug 15 23:45:32 phazer dovecot: child 10140 (login) killed with signal 6 Aug 15 23:45:32 phazer dovecot: child 10142 (login) killed with signal 6 Aug 15 23:45:32 phazer dovecot: child 10143 (login) killed with signal 6 Aug 15 23:45:32 phazer dovecot: child 10144 (login) killed with signal 6 Aug 15 23:45:32 phazer dovecot: child 10141 (login) killed with signal 6 Aug 15 23:45:32 phazer dovecot: child 10145 (login) killed with signal 6
Still this error, but :> that's why I run it for now using:
LD_LIBRARY_PATH=/usr/lib/dovecot/:/usr/lib/dovecot/imap/ dovecot
Aug 15 23:48:44 phazer dovecot: Dovecot v1.0.rc6 starting up
Aug 15 23:48:53 phazer dovecot: imap-login: Login: user=<websafe>, method=plain,
rip=*, lip=*
(see my previus posting)
So IMHO sth is wrong with "my" libz :-) But a I mentioned, it works fine prefixed with LD_LIBRARY_PATH...
:)
websafe wrote:
So IMHO sth is wrong with "my" libz :-)
Does dovecot even use libz? Is the compressed mbox support not a plugin?
But a I mentioned, it works fine prefixed with LD_LIBRARY_PATH...
Which begs the question: what's in your usual library search path that Dovecot is finding before its own files?
What IS your current search path, and are there possibly stale dovecot files (from your previous build) lurking about?
Has anyone else done a migration from 0.99 -> 1.0 on Slackware?
-- Curtis Maloney cmaloney@cardgate.net
Curtis Maloney wrote::
Which begs the question: what's in your usual library search path that Dovecot is finding before its own files?
You mean this: # cat /etc/ld.so.conf /usr/X11R6/lib /usr/i486-slackware-linux/lib /usr/local/ssl/lib /usr/lib /usr/local/lib
?
What IS your current search path, and are there possibly stale dovecot files (from your previous build) lurking about?
Yes, there is really chaos on this machine, most new things are checked on it, so its possible, that there are some new/old, even very old files and different versions etc. ;) (10.2/2.6.16.14)
participants (6)
-
Curtis Maloney
-
fazer69＠o2.pl
-
Matthias Andree
-
Odhiambo WASHINGTON
-
Timo Sirainen
-
websafe