The following bug has been ASSIGNED. ====================================================================== http://www.dbmail.org/mantis/bug_view_advanced_page.php?bug_id=0000114 ====================================================================== Reported By: seanc Assigned To: paul ====================================================================== Project: DBMail Bug ID: 114 Category: Database layer Reproducibility: always Severity: crash Priority: normal Status: resolved Resolution: fixed ====================================================================== Date Submitted: 02-Nov-04 21:35 CET Last Modified: 28-Dec-04 15:04 CET ====================================================================== Summary: Crash/core when unable to connect to PostgreSQL... Description: When firing up dbmail-imapd and dbmail-pop3d, both daemons exit/abort with a recursive malloc(3) call when they're unable to connect to the specified database. In my case, I used an empty name field in dbmail.conf. ======================================================================
---------------------------------------------------------------------- aaron - 02-Nov-04 22:58 CET ---------------------------------------------------------------------- Doesn't seem to be a problem with MySQL, but I don't know if I'm breaking my dbmail.conf in the same way your are... Could you post the offending sections of your dbmail.conf? ---------------------------------------------------------------------- seanc - 02-Nov-04 23:14 CET ---------------------------------------------------------------------- Everything in my config was default: [DBMAIL] host= # host for database, set to localhost if database is om sqlport= # if you want to use TCP/IP for connecting to the database, sqlsocket= # when using a local socket connection to the database, fill user=dbmail # user to connect as to database pass=pass # password for user to database db= # name of database [EMAIL PROTECTED] # postmaster's email address. TRACE_LEVEL=2 except for the above settings. Once I added the right line to db, everything worked correctly. Was a pain to track down though because the stack had been clobbered it looked like and I wasn't getting any messages. Can you try with PostgreSQL? ---------------------------------------------------------------------- aaron - 02-Nov-04 23:25 CET ---------------------------------------------------------------------- Sorry, no PostgreSQL on my server :-\ Anybody else got a machine to test this with? I think the two questions are: 1) is the looping malloc within DBMail, and 2) if not, is there a specific input that reliably kills PostgreSQL, and therefore should be checked before calling into the PG API? ---------------------------------------------------------------------- ilja - 24-Nov-04 16:15 CET ---------------------------------------------------------------------- I'm not able to reproduce this on PostgreSQL. Still... it's trying to make the connection over and over again... annoying. That should really be fixed. ---------------------------------------------------------------------- paul - 27-Dec-04 22:36 CET ---------------------------------------------------------------------- Fixed by testing the database connection in StartServer, prior to forking children. Bug History Date Modified Username Field Change ====================================================================== 02-Nov-04 21:35seanc New Bug 02-Nov-04 22:58aaron Bugnote Added: 0000339 02-Nov-04 23:14seanc Bugnote Added: 0000340 02-Nov-04 23:25aaron Bugnote Added: 0000341 24-Nov-04 16:15ilja Bugnote Added: 0000372 24-Nov-04 16:15ilja Status new => feedback 27-Dec-04 22:36paul Bugnote Added: 0000473 28-Dec-04 15:04paul Assigned To => paul 28-Dec-04 15:04paul Projection none => minor fix 28-Dec-04 15:04paul Resolution open => fixed 28-Dec-04 15:04paul Status feedback => resolved ======================================================================
