Hi all,
When trying to set up dovecot, I somehow managed to get a segfault. Trying to launch dovecot from command line (simply execute 'dovecot') results in the error message: Segmentation fault (core dumped)
Trying dovecot -n results in pretty much the same: # 2.2.9: /etc/dovecot/dovecot.conf Segmentation fault (core dumped)
Looking at syslog, I see doveconf[3676]: segfault at 200 ip 00007fbb93c4fcb3 sp 00007fff005b4c10 error 4 in libc-2.19.so[7fbb93c04000+1bc000]
I tried but couldn't find the core dump anywhere on the server. Any help on this would be appreciated too.
I (trying to ) run it with postfix, on an Ubuntu 14.04 (Linux mail2.arturia.com 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux), brand new server. What troubles me even more is that I just set up successfully another mail server a week ago, with the same configuration (diffing the conf folders) except for log or mailbox paths (driver and stuff are the same).
In the google search I've done, I saw some stuff about openssl: both servers are running 1.0.1f, since one is running fine, I guess this is not the culprit.
One difference I noticed between the two servers is that on the failing one, there is no /var/run/dovecot. I presume this folder and its files are created once dovecot is launched, so that's why it's not present, and is only a symptom of the failure, not a cause?
Thanks for your help, and please tell me what other information I could provide to help.
Simon
Am 28.07.2014 09:44, schrieb Simon Gareste:
When trying to set up dovecot, I somehow managed to get a segfault. Trying to launch dovecot from command line (simply execute 'dovecot') results in the error message: Segmentation fault (core dumped)
Trying dovecot -n results in pretty much the same: # 2.2.9: /etc/dovecot/dovecot.conf Segmentation fault (core dumped)
Looking at syslog, I see doveconf[3676]: segfault at 200 ip 00007fbb93c4fcb3 sp 00007fff005b4c10 error 4 in libc-2.19.so[7fbb93c04000+1bc000]
current is 2.2.13
so don't report problems with a outdated version instead just upgrade - there where bugfixes between 2.2.9 and 2.2.13 in context of segfaults here and there
Le 28/07/2014 12:14, Reindl Harald a écrit :
Am 28.07.2014 09:44, schrieb Simon Gareste:
When trying to set up dovecot, I somehow managed to get a segfault. Trying to launch dovecot from command line (simply execute 'dovecot') results in the error message: Segmentation fault (core dumped)
Trying dovecot -n results in pretty much the same: # 2.2.9: /etc/dovecot/dovecot.conf Segmentation fault (core dumped)
Looking at syslog, I see doveconf[3676]: segfault at 200 ip 00007fbb93c4fcb3 sp 00007fff005b4c10 error 4 in libc-2.19.so[7fbb93c04000+1bc000] current is 2.2.13
so don't report problems with a outdated version instead just upgrade - there where bugfixes between 2.2.9 and 2.2.13 in context of segfaults here and there
Thank you. This outdated version is the one packaged in Ubuntu LTS 14.04.1, which I believe I'm not the only one using. Updating the dovecot packages provided by Ubuntu would certainly help. I understand that the version I'm using is roughly 9 months old, but then the LTS was released 3 months ago, why doesn't it include the 2.2.11 or 2.2.12?
And I found the solution in the end, the problem comes from auth_debug_passwords=yes being the right thing, and auth_debug_passwords=plain being source of segfault. I don't know where I got the "plain" value in the first place, but I certainly should have read more carefully some docs. I also don't know if this was fixed later, but shouldn't there be a verification on some values of some variables, when there are limited values to which they can be defined?
Anyway, dovecot is running, all my apologizes for the unwanted spam.
Simon
Am 28.07.2014 12:33, schrieb Simon Gareste:
Le 28/07/2014 12:14, Reindl Harald a écrit :
Am 28.07.2014 09:44, schrieb Simon Gareste:
When trying to set up dovecot, I somehow managed to get a segfault. Trying to launch dovecot from command line (simply execute 'dovecot') results in the error message: Segmentation fault (core dumped)
Trying dovecot -n results in pretty much the same: # 2.2.9: /etc/dovecot/dovecot.conf Segmentation fault (core dumped)
Looking at syslog, I see doveconf[3676]: segfault at 200 ip 00007fbb93c4fcb3 sp 00007fff005b4c10 error 4 in libc-2.19.so[7fbb93c04000+1bc000] current is 2.2.13
so don't report problems with a outdated version instead just upgrade - there where bugfixes between 2.2.9 and 2.2.13 in context of segfaults here and there
Thank you. This outdated version is the one packaged in Ubuntu LTS 14.04.1, which I believe I'm not the only one using
that's the problem with all that LTS packages
nobody knows what fixes they may have backported and what are missing, so the version number no longer says anything which makes it also impossible for the upstream developer to know the patchlevel
that's why i build packages for server software the last 7 years on my own infrastructure from upstream sources
Updating the dovecot packages provided by Ubuntu would certainly help. I understand that the version I'm
using is roughly 9 months old, but then the LTS was released 3 months ago, why doesn't it include the 2.2.11 or 2.2.12?
And I found the solution in the end, the problem comes from auth_debug_passwords=yes being the right thing, and auth_debug_passwords=plain being source of segfault. I don't know where I got the "plain" value in the first place, but I certainly should have read more carefully some docs. I also don't know if this was fixed later, but shouldn't there be a verification on some values of some variables, when there are limited values to which they can be defined?
Simon Gareste wrote:
This outdated version is the one packaged in Ubuntu LTS 14.04.1, which I believe I'm not the only one using. Updating the dovecot packages provided by Ubuntu would certainly help.
If Ubuntu packages segfault, you should file a bug report at Ubuntu Launchpad:
https://help.ubuntu.com/community/ReportingBugs
Regards Daniel
Am 28.07.2014 09:44, schrieb Simon Gareste:
One difference I noticed between the two servers is that on the failing one, there is no /var/run/dovecot. I presume this folder and its files are created once dovecot is launched, so that's why it's not present, and is only a symptom of the failure, not a cause?
no, it is supposed to be created by package install and on modern systems where /var/run is a symlink to /run which is a tmpfs everytime at boot
[root@mail:~]$ cat /usr/lib/tmpfiles.d/dovecot.conf d /run/dovecot 0755 root dovecot -
participants (3)
-
Daniel Parthey
-
Reindl Harald
-
Simon Gareste