Another hint: If i shut down with killall, hundreads of this lines are coming in var/log/warn
[....MUCH more lines like following...] Feb 10 18:27:03 linux dbmail/pop3d[3324]: dbmysql.c,db_connect: mysql_real_connect failed: Too many connections Feb 10 18:27:03 linux dbmail/pop3d[3325]: dbmysql.c,db_connect: mysql_real_connect failed: Too many connections Feb 10 18:27:03 linux dbmail/pop3d[3326]: dbmysql.c,db_connect: mysql_real_connect failed: Too many connections Feb 10 18:27:03 linux dbmail/pop3d[3318]: PerformChildTask(): could not connect to database Feb 10 18:27:03 linux dbmail/pop3d[3327]: dbmysql.c,db_connect: mysql_real_connect failed: Too many connections Feb 10 18:27:03 linux dbmail/pop3d[3328]: dbmysql.c,db_connect: mysql_real_connect failed: Too many connections Feb 10 18:27:03 linux dbmail/pop3d[3319]: PerformChildTask(): could not connect to database Feb 10 18:27:03 linux dbmail/pop3d[3329]: dbmysql.c,db_connect: mysql_real_connect failed: Too many connections Feb 10 18:27:03 linux dbmail/pop3d[3330]: dbmysql.c,db_connect: mysql_real_connect failed: Too many connections Feb 10 18:27:03 linux dbmail/pop3d[3331]: dbmysql.c,db_connect: mysql_real_connect failed: Too many connections Feb 10 18:27:03 linux dbmail/pop3d[3320]: PerformChildTask(): could not connect to database Feb 10 18:27:03 linux dbmail/pop3d[3332]: dbmysql.c,db_connect: mysql_real_connect failed: Too many connections Feb 10 18:27:03 linux dbmail/pop3d[3333]: dbmysql.c,db_connect: mysql_real_connect failed: Too many connections Feb 10 18:27:03 linux dbmail/pop3d[3322]: PerformChildTask(): could not connect to database Feb 10 18:27:03 linux dbmail/pop3d[3334]: dbmysql.c,db_connect: mysql_real_connect failed: Too many connections Feb 10 18:27:03 linux dbmail/pop3d[3335]: dbmysql.c,db_connect: mysql_real_connect failed: Too many connections Feb 10 18:27:03 linux dbmail/pop3d[3336]: dbmysql.c,db_connect: mysql_real_connect failed: Too many connections Feb 10 18:27:03 linux dbmail/pop3d[3323]: PerformChildTask(): could not connect to database Feb 10 18:27:03 linux dbmail/pop3d[3316]: pool.c,child_unregister: child [3316] unregistered Feb 10 18:27:03 linux dbmail/pop3d[3324]: PerformChildTask(): could not connect to database Feb 10 18:27:03 linux dbmail/pop3d[3325]: PerformChildTask(): could not connect to database Feb 10 18:27:03 linux dbmail/pop3d[3326]: PerformChildTask(): could not connect to database Feb 10 18:27:03 linux dbmail/pop3d[3318]: pool.c,child_unregister: child [3318] unregistered Feb 10 18:27:03 linux dbmail/pop3d[3327]: PerformChildTask(): could not connect to database Feb 10 18:27:03 linux dbmail/pop3d[3328]: PerformChildTask(): could not connect to database Feb 10 18:27:03 linux dbmail/pop3d[3319]: pool.c,child_unregister: child [3319] unregistered Feb 10 18:27:03 linux dbmail/pop3d[3329]: PerformChildTask(): could not connect to database Feb 10 18:27:03 linux dbmail/pop3d[3330]: PerformChildTask(): could not connect to database Feb 10 18:27:03 linux dbmail/pop3d[3331]: PerformChildTask(): could not connect to database Feb 10 18:27:03 linux dbmail/pop3d[3320]: pool.c,child_unregister: child [3320] unregistered Feb 10 18:27:03 linux dbmail/pop3d[3332]: PerformChildTask(): could not connect to database Feb 10 18:27:03 linux dbmail/pop3d[3333]: PerformChildTask(): could not connect to database Feb 10 18:27:03 linux dbmail/pop3d[3322]: pool.c,child_unregister: child [3322] unregistered Feb 10 18:27:03 linux dbmail/pop3d[3334]: PerformChildTask(): could not connect to database Feb 10 18:27:03 linux dbmail/pop3d[3335]: PerformChildTask(): could not connect to database Feb 10 18:27:03 linux dbmail/pop3d[3336]: PerformChildTask(): could not connect to database Feb 10 18:27:03 linux dbmail/pop3d[3323]: pool.c,child_unregister: child [3323] unregistered Feb 10 18:27:03 linux dbmail/pop3d[3324]: pool.c,child_unregister: child [3324] unregistered Feb 10 18:27:03 linux dbmail/pop3d[3325]: pool.c,child_unregister: child [3325] unregistered Feb 10 18:27:03 linux dbmail/pop3d[3326]: pool.c,child_unregister: child [3326] unregistered Feb 10 18:27:03 linux dbmail/pop3d[3327]: pool.c,child_unregister: child [3327] unregistered Feb 10 18:27:03 linux dbmail/pop3d[3328]: pool.c,child_unregister: child [3328] unregistered Feb 10 18:27:03 linux dbmail/pop3d[3337]: pool.c,child_register: register child [3337] Feb 10 18:27:03 linux dbmail/pop3d[3329]: pool.c,child_unregister: child [3329] unregistered Feb 10 18:27:03 linux dbmail/pop3d[3330]: pool.c,child_unregister: child [3330] unregistered Feb 10 18:27:03 linux dbmail/pop3d[3331]: pool.c,child_unregister: child [3331] unregistered Feb 10 18:27:04 linux dbmail/pop3d[3332]: pool.c,child_unregister: child [3332] unregistered Feb 10 18:27:04 linux dbmail/pop3d[3333]: pool.c,child_unregister: child [3333] unregistered Feb 10 18:27:04 linux dbmail/pop3d[3338]: pool.c,child_register: register child [3338] Feb 10 18:27:04 linux dbmail/pop3d[3334]: pool.c,child_unregister: child [3334] unregistered Feb 10 18:27:04 linux dbmail/pop3d[3335]: pool.c,child_unregister: child [3335] unregistered Feb 10 18:27:04 linux dbmail/pop3d[3336]: pool.c,child_unregister: child [3336] unregistered Feb 10 18:27:04 linux dbmail/pop3d[3339]: pool.c,child_register: register child [3339] Feb 10 18:27:04 linux dbmail/pop3d[3340]: pool.c,child_register: register child [3340] Feb 10 18:27:04 linux dbmail/pop3d[3341]: pool.c,child_register: register child [3341] Feb 10 18:27:04 linux dbmail/pop3d[3337]: dbmysql.c,db_connect: mysql_real_connect failed: Too many connections Feb 10 18:27:04 linux dbmail/pop3d[3342]: pool.c,child_register: register child [3342] Feb 10 18:27:04 linux dbmail/pop3d[3343]: pool.c,child_register: register child [3343] Feb 10 18:27:04 linux dbmail/pop3d[3338]: dbmysql.c,db_connect: mysql_real_connect failed: Too many connections Feb 10 18:27:04 linux dbmail/pop3d[3344]: pool.c,child_register: register child [3344] Feb 10 18:27:04 linux dbmail/pop3d[3345]: pool.c,child_register: register child [3345] [At this point Machine is DEAD / HANGS, no more log available] dbmail, postfix are working fine(!) on this system. But when killall -> Machine dead / hangs after a few seconds after killall. The same is on another machine with same configs. I dont understand why dbmail cant connect to db after killall. -----Ursprüngliche Nachricht----- > Von: <[EMAIL PROTECTED],[email protected]> > Gesendet: 10.02.2005 15:12 > An: Groh,Thomas <[email protected]> > Betreff: RE: AW: RE: [Dbmail] Problem shut down dbmail-pop3d > > > Hello, > > Interesting... never heard of that happening before, and offhand > I don't see how it would. Did you check iptables rules, to make sure > nothing is blocked/changed there? Look for any other syslog messages, > related to stuff other than dbmail, too. Anything interesting in the > output of "dmesg"? Can that machine make outgoing connections after > that happens? > > > > ---- Original Message ---- > From: <[email protected]> > To: [EMAIL PROTECTED], [email protected] > Subject: AW: RE: [Dbmail] Problem shut down dbmail-pop3d > Sent: Thu, 10 Feb 2005 17:32:10 +0100 (CET) > > > I hope i can give more info: > > > > I installed dbmail on a local system and on a dedicated server. Both > > machines > have same config (suse 9.0 etc.) > > > > The complete server gives NO RESPONDS after killall dbmail-pop3d ! > > No responds via ssh (it shuts down after i send the kill signal!). No > Webserver responds (going down when killall dbmail-pop3d). But ping is okay ! > But i must restart the server by hand. > > The last in "warn" log is many lines of > "serverchild.c,active:child_sig_handler: git signal [15]" > > > > I dont have more info. Hope its enough (?) > > > > > > > > I habe installed DBMail 2.0.3 > > > > I have a problem shutdown dbmail-pop3. If i killall dbmail-pop3 the > > > > server > > > hangs and all connections halts. Only a reboot awakes the maschine. > > > > > > By "the server," you mean the entire machine, not just the pop3 server > > > process? Is the console locked up or still working? Does it answer > > > pings? > > > If you still have console access, you can start checking stuff out there > > > (look at log files, "dmesg" output, try disabling all firewall rules and > > > make sure the policy is ACCEPT for input/output/forward chains). > > > > > > > I installed dbmail on suse 9.0 > > > > > > > > Have anybody a hint whats wrong ? > > > > > > Not really... doesn't make any sense w/o more info. > > > > > > > > > > > > > > > -- > > > Jesse Norell > > > jesse @ kci.net > > > > > > _______________________________________________ > > > Dbmail mailing list > > > [email protected] > > > https://mailman.fastxs.nl/mailman/listinfo/dbmail > > > > > > > > > > > > > _______________________________________________ > > Dbmail mailing list > > [email protected] > > https://mailman.fastxs.nl/mailman/listinfo/dbmail > > > -- End Original Message -- > > > -- > Jesse Norell > jesse @ kci.net > > _______________________________________________ > Dbmail mailing list > [email protected] > https://mailman.fastxs.nl/mailman/listinfo/dbmail > > >
