[Dovecot] Crashes with 2.2.4 setup that worked perfectly with 2.2.2 (.2.3 also crashes)
I am not sure how to get the symbols necessary, however the following is the backtrace (this is Fedora 19 latest everything):
Jul 8 03:23:02 MX dovecot: auth: Fatal: block_alloc(2147483648): Out of memory Jul 8 03:23:02 MX dovecot: auth: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x5f437) [0x7f97a952f437] -> /usr/lib64/dovecot/libdovecot.so.0(+0x5f4fe) [0x7f97a952f4fe] -> /usr/lib64/dovecot/libdovecot.so.0(i_error+0) [0x7f97a94f070f] -> /usr/lib64/dovecot/libdovecot.so.0(+0x72ee8) [0x7f97a9542ee8] -> /usr/lib64/dovecot/libdovecot.so.0(+0x72f1f) [0x7f97a9542f1f] -> /usr/lib64/dovecot/libdovecot.so.0(sasl_client_new+0x31) [0x7f97a9526ac1] -> /lib64/libldap-2.4.so.2(ldap_int_sasl_open+0x5c) [0x7f97a62f058c] -> /lib64/libldap-2.4.so.2(ldap_int_sasl_bind+0x5c9) [0x7f97a62f0cd9] -> /lib64/libldap-2.4.so.2(ldap_sasl_interactive_bind+0x96) [0x7f97a62f3e46] -> /lib64/libldap-2.4.so.2(ldap_sasl_interactive_bind_s+0xe1) [0x7f97a62f4041] -> /usr/lib64/dovecot/auth/libauthdb_ldap.so(db_ldap_connect+0x146) [0x7f97a652f286] -> dovecot/auth(userdb_init+0x1a) [0x7f97a99e09ea] -> dovecot/auth(auths_init+0xc9) [0x7f97a99c8e29] -> dovecot/auth(main+0x335) [0x7f97a99c8225] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f97a8ae8b75] -> dovecot/auth(+0xe43d) [0x7f97a99c843d] Jul 8 03:23:02 MX dovecot: master: Error: service(auth): command startup failed, throttling for 60 secs Jul 8 03:23:02 MX dovecot: auth: Fatal: master: service(auth): child 9650 returned error 83 (Out of memory (service auth { vsz_limit=256 MB }, you may need to increase it))
Any help would be greatly appreciated.
Thank you, Trever
Am 08.07.2013 11:31, schrieb Trever L. Adams:
Jul 8 03:23:02 MX dovecot: auth: Fatal: master: service(auth): child 9650 returned error 83 (Out of memory (service auth { vsz_limit=256 MB }, you may need to increase it))
Any help would be greatly appreciated
look at the last line of your quote
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 07/08/2013 03:43 AM, Reindl Harald wrote:
Am 08.07.2013 11:31, schrieb Trever L. Adams:
Jul 8 03:23:02 MX dovecot: auth: Fatal: master: service(auth): child 9650 returned error 83 (Out of memory (service auth { vsz_limit=256 MB }, you may need to increase it))
Any help would be greatly appreciated
look at the last line of your quote
I am afraid that that doesn't fix the problem Reindl.
Jul 8 03:51:56 MX dovecot: auth: Fatal: block_alloc(2147483648): Out of memory Jul 8 03:51:56 MX dovecot: auth: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x5f437) [0x7f5774b6b437] -> /usr/lib64/dovecot/libdovecot.so.0(+0x5f4fe) [0x7f5774b6b4fe] -> /usr/lib64/dovecot/libdovecot.so.0(i_error+0) [0x7f5774b2c70f] -> /usr/lib64/dovecot/libdovecot.so.0(+0x72ee8) [0x7f5774b7eee8] -> /usr/lib64/dovecot/libdovecot.so.0(+0x72f1f) [0x7f5774b7ef1f] -> /usr/lib64/dovecot/libdovecot.so.0(sasl_client_new+0x31) [0x7f5774b62ac1] -> /lib64/libldap-2.4.so.2(ldap_int_sasl_open+0x5c) [0x7f577192c58c] -> /lib64/libldap-2.4.so.2(ldap_int_sasl_bind+0x5c9) [0x7f577192ccd9] -> /lib64/libldap-2.4.so.2(ldap_sasl_interactive_bind+0x96) [0x7f577192fe46] -> /lib64/libldap-2.4.so.2(ldap_sasl_interactive_bind_s+0xe1) [0x7f5771930041] -> /usr/lib64/dovecot/auth/libauthdb_ldap.so(db_ldap_connect+0x146) [0x7f5771b6b286] -> dovecot/auth(userdb_init+0x1a) [0x7f577501c9ea] -> dovecot/auth(auths_init+0xc9) [0x7f5775004e29] -> dovecot/auth(main+0x335) [0x7f5775004225] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f5774124b75] -> dovecot/auth(+0xe43d) [0x7f577500443d] Jul 8 03:51:56 MX dovecot: master: Error: service(auth): command startup failed, throttling for 2 secs Jul 8 03:51:56 MX dovecot: auth: Fatal: master: service(auth): child 1744 returned error 83 (Out of memory (service auth { vsz_limit=512 MB }, you may need to increase it))
I do not think that dovecot has increased its memory usage by more than 100%.
Thank you, Trever -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCgAGBQJR2oxjAAoJENEtz1LOYsiz4s4P/1g5GHweaH0L7GfZeDypYx8V 0tRTtMHkW66IpgQ9V7ZTlFO6jbrQGiqQyiaKy1s5Fx1gYbDwJ6fEgVqNqM1w1L8U hnw78a2piCFu4lOtatooAWoudtkR5/4VUSKXId9fCLayTFWRhE1TkBP74+KfAqCa CipHazwpZpYR4PShHooUPn54mxYupFmwL3GQZKP0rglIB/VUwpXXm6QJaX3+Nfnf 0jrSQEn/vbrV9kOiH7/FauzXfQl/23a1odpzgcgvaqXO0oAL0r/8OoF7CZhSTPsJ bs97T/G8PV4zFnTug1XjbvPY5xDh2F8ZbcgEE63y72c4Ncjs0njFxlAS/1rfu7cl k0URC2IfRm8dFcfa67xNpNH+aOxlaCP0/r5/0WEQg+VjzfNUNMwNq29uXjiZvYd8 ojFgfeyBtHepZkgg/YmtE39wIbLh83vizBcQVF96en4NCjvtfeUZkFdlR6F9TvY8 CiJj2eZ3sI/WHdenpv83nxGmKlIj6dg0tbmXuYrO1067L+zBbW3tcHebxqqcDQ/u PGsDKkaLZvmw+is/iJwnlvhfAyeMzbn5/r+IST24K3h4oyVv0DSyVvrXaxOG0DB0 NGMYoiNc+3oqbN4OKR9E+SZvyJDFS/oGAP0j2mbnmTiCdmKbhsBJQVy+1uoLt+sL 1WPrhMM2ElUuLT9+5J3f =luLp -----END PGP SIGNATURE-----
Hi Trever,
Actually the first line seems to suggest an attempt to allocate 2GB block. The question is why it wants to do that =)
Best wishes Eugene
-----Original Message----- From: Trever L. Adams Sent: Monday, July 08, 2013 1:55 PM To: Reindl Harald Cc: dovecot@dovecot.org Subject: Re: [Dovecot] Crashes with 2.2.4 setup that worked perfectly with 2.2.2 (.2.3 also crashes)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 07/08/2013 03:43 AM, Reindl Harald wrote:
Am 08.07.2013 11:31, schrieb Trever L. Adams:
Jul 8 03:23:02 MX dovecot: auth: Fatal: master: service(auth): child 9650 returned error 83 (Out of memory (service auth { vsz_limit=256 MB }, you may need to increase it))
Any help would be greatly appreciated
look at the last line of your quote
I am afraid that that doesn't fix the problem Reindl.
Jul 8 03:51:56 MX dovecot: auth: Fatal: block_alloc(2147483648): Out of memory Jul 8 03:51:56 MX dovecot: auth: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x5f437) [0x7f5774b6b437] -> /usr/lib64/dovecot/libdovecot.so.0(+0x5f4fe) [0x7f5774b6b4fe] -> /usr/lib64/dovecot/libdovecot.so.0(i_error+0) [0x7f5774b2c70f] -> /usr/lib64/dovecot/libdovecot.so.0(+0x72ee8) [0x7f5774b7eee8] -> /usr/lib64/dovecot/libdovecot.so.0(+0x72f1f) [0x7f5774b7ef1f] -> /usr/lib64/dovecot/libdovecot.so.0(sasl_client_new+0x31) [0x7f5774b62ac1] -> /lib64/libldap-2.4.so.2(ldap_int_sasl_open+0x5c) [0x7f577192c58c] -> /lib64/libldap-2.4.so.2(ldap_int_sasl_bind+0x5c9) [0x7f577192ccd9] -> /lib64/libldap-2.4.so.2(ldap_sasl_interactive_bind+0x96) [0x7f577192fe46] -> /lib64/libldap-2.4.so.2(ldap_sasl_interactive_bind_s+0xe1) [0x7f5771930041] -> /usr/lib64/dovecot/auth/libauthdb_ldap.so(db_ldap_connect+0x146) [0x7f5771b6b286] -> dovecot/auth(userdb_init+0x1a) [0x7f577501c9ea] -> dovecot/auth(auths_init+0xc9) [0x7f5775004e29] -> dovecot/auth(main+0x335) [0x7f5775004225] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f5774124b75] -> dovecot/auth(+0xe43d) [0x7f577500443d] Jul 8 03:51:56 MX dovecot: master: Error: service(auth): command startup failed, throttling for 2 secs Jul 8 03:51:56 MX dovecot: auth: Fatal: master: service(auth): child 1744 returned error 83 (Out of memory (service auth { vsz_limit=512 MB }, you may need to increase it))
I do not think that dovecot has increased its memory usage by more than 100%.
Thank you, Trever -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCgAGBQJR2oxjAAoJENEtz1LOYsiz4s4P/1g5GHweaH0L7GfZeDypYx8V 0tRTtMHkW66IpgQ9V7ZTlFO6jbrQGiqQyiaKy1s5Fx1gYbDwJ6fEgVqNqM1w1L8U hnw78a2piCFu4lOtatooAWoudtkR5/4VUSKXId9fCLayTFWRhE1TkBP74+KfAqCa CipHazwpZpYR4PShHooUPn54mxYupFmwL3GQZKP0rglIB/VUwpXXm6QJaX3+Nfnf 0jrSQEn/vbrV9kOiH7/FauzXfQl/23a1odpzgcgvaqXO0oAL0r/8OoF7CZhSTPsJ bs97T/G8PV4zFnTug1XjbvPY5xDh2F8ZbcgEE63y72c4Ncjs0njFxlAS/1rfu7cl k0URC2IfRm8dFcfa67xNpNH+aOxlaCP0/r5/0WEQg+VjzfNUNMwNq29uXjiZvYd8 ojFgfeyBtHepZkgg/YmtE39wIbLh83vizBcQVF96en4NCjvtfeUZkFdlR6F9TvY8 CiJj2eZ3sI/WHdenpv83nxGmKlIj6dg0tbmXuYrO1067L+zBbW3tcHebxqqcDQ/u PGsDKkaLZvmw+is/iJwnlvhfAyeMzbn5/r+IST24K3h4oyVv0DSyVvrXaxOG0DB0 NGMYoiNc+3oqbN4OKR9E+SZvyJDFS/oGAP0j2mbnmTiCdmKbhsBJQVy+1uoLt+sL 1WPrhMM2ElUuLT9+5J3f =luLp -----END PGP SIGNATURE-----
Am 08.07.2013 12:00, schrieb Eugene:
Actually the first line seems to suggest an attempt to allocate 2GB block. The question is why it wants to do that =)
sure taht there is no stupid client trying to store a some GB draft on the server? i had a year ago a apple-mail client where the user selected the wrong attachment (6 GB MP4) and apple-mail insisted to store it a draft on the server repeating this every time the server came back after crashing even after changing the password as the client found a open connection from before
if the client is inside the LAN with GBE this goes fast
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 07/08/2013 04:15 AM, Reindl Harald wrote:
Am 08.07.2013 12:00, schrieb Eugene:
Actually the first line seems to suggest an attempt to allocate 2GB
block. The question is why it wants to do that =)
sure taht there is no stupid client trying to store a some GB draft on the server? i had a year ago a apple-mail client where the user selected the wrong attachment (6 GB MP4) and apple-mail insisted to store it a draft on the server repeating this every time the server came back after crashing even after changing the password as the client found a open connection from before
if the client is inside the LAN with GBE this goes fast
The crash happens on any Kerberos login. I am the only user on the system at the moment and while I have a few drafts, they are small.
To do crash, I just do "yum upgrade; service dovecot restart" then try to login. Instant crash. If I then do a forced down grade, do the login, it works.
Trever
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCgAGBQJR2pN1AAoJENEtz1LOYsizylMP/2LDQQjzoUjk2koPmR48r/Xs 9NvmRr1xcvi4jjYic1qT1NJgOO8jHT93smV8whX0LDa49scIu4TwBxAqOcMH/lSh +zqcGo5mj1zA3Qu7e81EcV34raFXfNKPOqGRzmKf68aKO0ktMLINXlEhPzbfxeoH r3CxukFzKjzA0ZZh1XtFzgX1SdnttiqjZYVVqy7YMS5mph+pRxE7UPtLSXS9vJck cQAM75B7WGCDIT9hPW2YFz4GXEDtx8bgMrzeEXNe1MdTxXi/+jIzBDmRdsOmJ7fS lmooFETcjZBv36OGReLYipu5juG34Z0EpiWJTy1DbcnOL5XwAdoErIx2VbZ+r+Aj 5fFEhQT/bpsEo+GBb59zPRE5b22Y3LgNFBwQ1m0zie/GJTSUi89M2mKugQ5l5s0O fPEwdtQT7VYWr1iZVrDaQBA6xAqTMaz/XxH8JByE/nYAXYQflW/4PU/qeh6qCNxE VJeyVAfcuIZGKtzvepye/8ZZxKLRHVcP/dq/0um3xWozUiG6se7V3TWfQ2DhIOEj TJhN0Ygcm+iQmyUBIN82ga4j4KUvZTIJ9h6CeRTlqznuxMzXI5UH+Q38fASqUCZN nRT7bMGhYwP7w9sioRj+8nZqxkLqpT/pxwPvQpZt3HTD6VFjsvQ9RClx4Ylmztom KumkGNlet79FuLKq1MSL =GEz4 -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 07/08/2013 04:00 AM, Eugene wrote:
Hi Trever,
Actually the first line seems to suggest an attempt to allocate 2GB block. The question is why it wants to do that =)
Best wishes Eugene
And I have no reason why.
Thank you for your help, Trever
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCgAGBQJR2phXAAoJENEtz1LOYsizxKwQAJDqwTY2ooYJ9cHjrsQo6p6H xKMXBh3G+3rNkNfrdw1OKFKuTESh92lbA6wjPEEKnNl5ZAkarJZJQcR2qtp5IT3+ L/YRZiuSFNK/UKzhxMopnbp4gntE+Fq5Ch6SMNkNfm2iHgsO5YAbQAhOJadH9JI2 KICFb6SmWCVsZ4JynzioGIBRnY+ka881BUgPBtQJfjjGn2C76IWaPtJuc8cyEWGq +yPXUStCawRnV+EAeC8s/KWEND+Ys3Mm5Z5p2ad+vYI4M0FzCdqAH/v+zO/KvQNX oJsvzcecLg0zbI+O8fIXX3wD/5imzQweDaY/kOV1WayEby+GXAY1VByrVttq7H49 IIYVWlVj2uwDbw4IoTnKqBCf3/bp6isTbHiPqts/vq5dD45ssjT+fQ9qmpkE0BJQ rGdOQH2Bt+tPIu3m3C+Mm5r/1ygaHp+ZBCKZzl2wDoZUmavh7g2NG9HOKXtj0jEk s6HTDrfAIoGRRCCPOc72bJanzrCqHIs8Jg+/M9SNKCmBk0oYO1MdnShVofg8Cgx1 o+Y8NPeWmwVvmFuZ6lZflSkCKP8o3ajgqyYfyCO2Gzj+nDs6mAwo2Z0BL/AuFpUZ N+BL8NuNA26pXlLZ61Q/1q/e/Uz4+tRDGYbhSXoKs5gaKjvtm58xL2ZcxdM2QZfN /9szf1Ihr62NkbXFumSX =zyeX -----END PGP SIGNATURE-----
On 07/08/2013 04:45 AM, Trever L. Adams wrote:
On 07/08/2013 04:00 AM, Eugene wrote:
Hi Trever,
Actually the first line seems to suggest an attempt to allocate 2GB block. The question is why it wants to do that =)
Best wishes Eugene
And I have no reason why.
Thank you for your help, Trever
In 2.2.3 did mailbox handling change? I use maildir. Some of the folders do have a lot of messages, but very few large ones (I believe my postfix setup limits things to 10M per message).
Also, this happens on any login kerberos or not. I have an LDAP that is used to test for accounts (this is where it says it is crashing), Kerberos for Authentication and PAM which looks at the LDAP/Kerberos.
Nothing but dovecot software changes between working and non-working.
Trever
On 8.7.2013, at 12.31, Trever L. Adams trever@middleearth.sapphiresunday.org wrote:
I am not sure how to get the symbols necessary, however the following is the backtrace (this is Fedora 19 latest everything):
Jul 8 03:23:02 MX dovecot: auth: Fatal: block_alloc(2147483648): Out of memory [0x7f97a9526ac1] -> /lib64/libldap-2.4.so.2(ldap_int_sasl_open+0x5c) [0x7f97a62f058c] -> /lib64/libldap-2.4.so.2(ldap_int_sasl_bind+0x5c9) [0x7f97a62f0cd9] -> /lib64/libldap-2.4.so.2(ldap_sasl_interactive_bind+0x96)
There's a bug in v2.2.4 with LDAP SASL binds. http://hg.dovecot.org/dovecot-2.2/rev/2dd27b0e7e49
I'll try to get v2.2.5 out this week. Been a bit lazy these few weeks with a "vacation". :)
On 07/09/2013 10:02 PM, Timo Sirainen wrote:
On 8.7.2013, at 12.31, Trever L. Adams trever@middleearth.sapphiresunday.org wrote:
I am not sure how to get the symbols necessary, however the following is the backtrace (this is Fedora 19 latest everything):
Jul 8 03:23:02 MX dovecot: auth: Fatal: block_alloc(2147483648): Out of memory [0x7f97a9526ac1] -> /lib64/libldap-2.4.so.2(ldap_int_sasl_open+0x5c) [0x7f97a62f058c] -> /lib64/libldap-2.4.so.2(ldap_int_sasl_bind+0x5c9) [0x7f97a62f0cd9] -> /lib64/libldap-2.4.so.2(ldap_sasl_interactive_bind+0x96) There's a bug in v2.2.4 with LDAP SASL binds. http://hg.dovecot.org/dovecot-2.2/rev/2dd27b0e7e49
I'll try to get v2.2.5 out this week. Been a bit lazy these few weeks with a "vacation". :)
Thank you for the information Timo. I hope your "vacation" was great!
Thanks again, Trever
On 07/09/2013 10:02 PM, Timo Sirainen wrote:
On 8.7.2013, at 12.31, Trever L. Adams trever@middleearth.sapphiresunday.org wrote:
I am not sure how to get the symbols necessary, however the following is the backtrace (this is Fedora 19 latest everything):
Jul 8 03:23:02 MX dovecot: auth: Fatal: block_alloc(2147483648): Out of memory [0x7f97a9526ac1] -> /lib64/libldap-2.4.so.2(ldap_int_sasl_open+0x5c) [0x7f97a62f058c] -> /lib64/libldap-2.4.so.2(ldap_int_sasl_bind+0x5c9) [0x7f97a62f0cd9] -> /lib64/libldap-2.4.so.2(ldap_sasl_interactive_bind+0x96) There's a bug in v2.2.4 with LDAP SASL binds. http://hg.dovecot.org/dovecot-2.2/rev/2dd27b0e7e49
I'll try to get v2.2.5 out this week. Been a bit lazy these few weeks with a "vacation". :)
Only some basic testing so far, but I wanted to report that everything seems to be working perfectly. Thank you again, Timo.
Trever
participants (4)
-
Eugene
-
Reindl Harald
-
Timo Sirainen
-
Trever L. Adams