A NOTE has been added to this issue.
======================================================================
http://www.dbmail.org/mantis/view.php?id=306
======================================================================
Reported By: variable
Assigned To:
======================================================================
Project: DBMail
Issue ID: 306
Category: General
Reproducibility: always
Severity: crash
Priority: normal
Status: new
======================================================================
Date Submitted: 28-Feb-06 23:08 CET
Last Modified: 04-Mar-06 08:28 CET
======================================================================
Summary: the processes spawn infitnetly until they crash the
machine
Description:
Both on 2.0.7 and 2.0.9 all 3 processes will spawn indefinatly until the
machine crashes, I found that if you set the TRACE_LEVEL=5 it will solve
the problem, and have been running my production server like this for
http://www.dbmail.org/mantis/view.php?id=6#2
months now. Also these open processes keep opening connections to pgsql
and quickly use all the connections for pgsql.
======================================================================
----------------------------------------------------------------------
ajake - 01-Mar-06 17:14
----------------------------------------------------------------------
I can confirm same behaviour with trace_level 3, debian sid, mysql and with
dbmail 2.0.9 (using imap&lmtp). Also with older 2.0.x versions, maybe with
all of them. We just went from 5 users to 75 and now it happens few times a
day (at busy hours).
During night we run dbmail-util and after that restart dbmail services.
Sometimes root imapd or lmtpd has already died. Also there usually are a
lot of glibc errors
during restart (example follows) and during the day.
Removing IP entries older than [2006-02-22 14:36:01]...
Ok. [18] IP entries were older than [2006-02-22 14:36:01].
Vacuuming and optimizing database...
Ok. Database cleaned up.
Maintenance done. No errors found.
Stopping dbmail servers: done.
dbmail-imapd: no process killed <-- just to be sure, sometimes there are
leftovers
dbmail-lmtpd: no process killed
Starting dbmail servers: dbmail-imapd .dbmail-lmtpd .done.
*** glibc detected *** corrupted double-linked list: 0x0808a3a8 ***
*** glibc detected *** corrupted double-linked list: 0x0809a4d8 ***
*** glibc detected *** corrupted double-linked list: 0x0808a3a8 ***
*** glibc detected *** corrupted double-linked list: 0x0808a3a8 ***
*** glibc detected *** corrupted double-linked list: 0x0808a3a8 ***
*** glibc detected *** corrupted double-linked list: 0x080a1d50 ***
*** glibc detected *** corrupted double-linked list: 0x080a22c0 ***
*** glibc detected *** corrupted double-linked list: 0x0808a3a8 ***
*** glibc detected *** double free or corruption (fasttop): 0x0812f350
***
*** glibc detected *** double free or corruption (!prev): 0x081003f8 ***
*** glibc detected *** double free or corruption (fasttop): 0x080f9cb0
***
*** glibc detected *** double free or corruption (!prev): 0x080fdaa0 ***
*** glibc detected *** double free or corruption (fasttop): 0x08096cd0
***
*** glibc detected *** double free or corruption (fasttop): 0x080a4420
***
*** glibc detected *** double free or corruption (fasttop): 0x0810ad98
***
*** glibc detected *** double free or corruption (fasttop): 0x080a4330
***
*** glibc detected *** corrupted double-linked list: 0x0808a3a8 ***
*** glibc detected *** corrupted double-linked list: 0x080a4208 ***
another run:
*** glibc detected *** corrupted double-linked list: 0x0808a3d8 ***
*** glibc detected *** corrupted double-linked list: 0x0808a3d8 ***
*** glibc detected *** corrupted double-linked list: 0x0808a3d8 ***
*** glibc detected *** corrupted double-linked list: 0x08096c10 ***
*** glibc detected *** corrupted double-linked list: 0x0808a3d8 ***
*** glibc detected *** corrupted double-linked list: 0x0808a3d8 ***
*** glibc detected *** free(): invalid pointer: 0x080d8628 ***
*** glibc detected *** malloc(): memory corruption: 0x080d6b78 ***
*** glibc detected *** malloc(): memory corruption: 0x080c7370 ***
*** glibc detected *** corrupted double-linked list: 0x0808a3d8 ***
*** glibc detected *** corrupted double-linked list: 0x0808a3d8 ***
*** glibc detected *** corrupted double-linked list: 0x0808a3d8 ***
*** glibc detected *** corrupted double-linked list: 0x0808a3d8 ***
*** glibc detected *** corrupted double-linked list: 0x08096b80 ***
*** glibc detected *** corrupted double-linked list: 0x080a01d0 ***
*** glibc detected *** malloc(): memory corruption: 0x0809a740 ***
*** glibc detected *** corrupted double-linked list: 0x0808a3d8 ***
*** glibc detected *** corrupted double-linked list: 0x0808a3d8 ***
----------------------------------------------------------------------
mike - 04-Mar-06 08:28
----------------------------------------------------------------------
Late fall I upgraded a 7.x.x PGSQL to PostgreSQL 8.0.1 on a LAN file server
which does Admin mail for a dept. I upgraded Postfix and wanted to upgrade
DBMail too but *could not* get DBMail-2.0.7 to work properly. Connections
used the limit but dbmail.conf unchanged -- I upped the connections limit;
lasted an hour. Rolled back to DBMail-2.0.6: to this day. I now still have
the src folders so I checked the diff on the ChangeLog. Below is what
happened between 2.0.6 and 2.0.7 if anyone can spot something impacting
their setup. I can't see it.
2005-09-02 Paul J Stevens <[EMAIL PROTECTED]>
* ChangeLog, sql/mysql/create_tables_innoDB.mysql,
sql/postgresql/create_tables.pgsql:
added ON UPDATE CASCADE to create_table files
2005-08-31 Paul J Stevens <[EMAIL PROTECTED]>
* ChangeLog, configure, configure.in:
bump the version to 2.0.7
* debian/changelog:
updating sarge packages
* contrib/startup-scripts/debian/dbmail,
contrib/startup-scripts/debian/dbmail-imapd,
contrib/startup-scripts/debian/dbmail-lmtpd,
contrib/startup-scripts/debian/dbmail-pop3d,
contrib/startup-scripts/debian/dbmail.default:
update the included startup scripts
2005-08-24 Paul J Stevens <[EMAIL PROTECTED]>
* ChangeLog, server.c:
cleanup the signal handler in server.c
* pool.c:
add boundary check in manage_spare_children
2005-08-23 Ilja Booij <[EMAIL PROTECTED]>
* pop3.c: AUTH command no longer returns list of supported
authentication mechanisms when issued without arguments. closes
http://www.dbmail.org/mantis/view.php?id=237
2005-08-22 Paul J Stevens <[EMAIL PROTECTED]>
* debug.c:
avoid malloc in debug.c,trace by using a static buffer for debug
messages
* server.c:
reset alarm after database recovers
* pool.c:
non-blocking locking and some fixes in manage_spare_children
Issue History
Date Modified Username Field Change
======================================================================
28-Feb-06 23:08 variable New Issue
01-Mar-06 17:13 ajake Note Added: 0001016
01-Mar-06 17:14 ajake Note Edited: 0001016
04-Mar-06 08:28 mike Note Added: 0001020
======================================================================
