Hi Paul,
Thanks for responding. Unfortunately, I don't think the database
connection is the problem. The system has no trouble connecting to
PostgreSQL to add users. The message you are seeing mentions that dbmail
"could not connect to database", but that is because of the other
repeated log message "dbconnect(): PQconnectdb failed: FATAL: sorry,
too many clients already". Of course, if we have runaway process
spawning, PostgreSQL will stop allowing connections after just a few
seconds. In fact, since this is an underpowered test machine, My
max-connections is set at only 40.
I will be glad to try any other tests you suggest (gdb backtrace?). I am
very interested in the possibility of using dbmail on my production servers.
Best regards,
Rick Morris
Paul J Stevens wrote:
Your dbmail installation can't connect to the database. The log is
very clear about this.
If you can do 'dbmail-adduser s' and get a valid return, then you may
start the servers, if not, fix your database connection before
proceeding.
This check is build into the debian init scripts for a good reason.
But you do have a point, the daemons should exit gracefully in such a
situation, instead of going on a stampede.
Rick Morris wrote:
Hi,
I installed DBmail 1.2.9 with PostgreSQL support from the FreeBSD
ports, created the appropriate PostgreSQL database, created a user,
created the 'dbmail' user, etc... and edited
/usr/local/etc/dbmail.conf appropriately (AFAIK).
I also installed Postfix as the MTA, and it is running fine.
But when I try to run dbmail-imapd, within seconds it spawns so many
processes that the console starts showing the message "dbmail-imapd
in malloc(): warning: recursive call" repeatedly. The same thing
happens when I try dbmail-pop3d. The log fills up with messages like:
Aug 3 01:30:53 bluebox dbmail/imap4d[44728]: StartServer(): child
[45392] has exited
Aug 3 01:30:53 bluebox dbmail/imap4d[45408]: PerformChildTask():
could not connect to database
Aug 3 01:30:53 bluebox dbmail/imap4d[45410]: CreateChild(): signal
handler placed, going to perform task now
Aug 3 01:30:53 bluebox dbmail/imap4d[44728]: StartServer(): creating
new child
Aug 3 01:30:53 bluebox dbmail/imap4d[44728]: ParentSigHandler(): got
signal [20]
Aug 3 01:30:53 bluebox dbmail/imap4d[44728]: ParentSigHandler(): got
signal [20]
Aug 3 01:30:53 bluebox dbmail/imap4d[44728]: StartServer(): child
[45394] has exited
Aug 3 01:30:53 bluebox dbmail/imap4d[45412]: CreateChild(): signal
handler placed, going to perform task now
Aug 3 01:30:53 bluebox dbmail/imap4d[44728]: StartServer(): creating
new child
Aug 3 01:30:53 bluebox dbmail/imap4d[44728]: StartServer(): child
[45396] has exited
Aug 3 01:30:53 bluebox dbmail/imap4d[45414]: CreateChild(): signal
handler placed, going to perform task now
Aug 3 01:30:53 bluebox dbmail/imap4d[44728]: StartServer(): creating
new child
Aug 3 01:30:53 bluebox dbmail/imap4d[45410]: dbconnect():
PQconnectdb failed: FATAL: sorry, too many clients already
Aug 3 01:30:53 bluebox dbmail/imap4d[45410]: PerformChildTask():
could not connect to database
Aug 3 01:30:53 bluebox dbmail/imap4d[45412]: dbconnect():
PQconnectdb failed: FATAL: sorry, too many clients already
Aug 3 01:30:53 bluebox dbmail/imap4d[45416]: CreateChild(): signal
handler placed, going to perform task now
Aug 3 01:30:53 bluebox dbmail/imap4d[44728]: StartServer(): child
[45398] has exited
Aug 3 01:30:53 bluebox dbmail/imap4d[45412]: PerformChildTask():
could not connect to database
Aug 3 01:30:53 bluebox dbmail/imap4d[44728]: StartServer(): creating
new child
I am running FreeBSD 4.10. I searched the mailling list for similar
problems and only found one mention of this, in May 2004, with no
resolution. Any ideas what I can look for?
Regards,
Rick Morris
_______________________________________________
Dbmail mailing list
Dbmail@dbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail
