From: joe s. <jo...@mo...> - 2003-10-11 05:35:49
|
I finally have a clue why my httpd maxes out sometimes when I come home. This means it's churning out cpu cycles after leaving my server and linux box running exposed to internet. I notice that it happens when: 1 -- lots of search engine hits in a short amount of time 2 -- about twice a week 3 -- stopping postmaster or https and restarting clears up problem 4 -- (new!) a message in the error log: OpenInteract::Request::lookup_conductor (226) >> Info for action: $VAR1 = { 'template_processor' => 'OpenInteract::Template::Process', 'conductor' => 'main', 'name' => 'page', 'security' => 'yes', 'method' => 'handler', 'package_name' => 'base_page', 'class' => 'oi::Handler::Page', 'package_version' => '1.24', 'key' => 'page' }; OpenInteract::find_action_handler (232) >> Found OpenInteract::UI::Main // handler for conductor DBI connect('dbname=oi1','oi',...) failed: FATAL: Non-superuser connection limit exceeded at /usr/lib/perl5/site_perl/5.8.0 //OpenInteract/DBI.pm line 39 Upping this limit will vastly improve the stability of the package for me. I am using postgres module without any special configuration done for connections on my part. Line in question from OpenInteract/DBI.pm: my $db = eval { DBI->connect( $dsn, $username, $password ) }; next time, I'll attach gdb to it as it is running to find out where it's happening. But, does anybody know, should I start looking for a solution in httpd.conf or in my server.ini file, or somewhere in the DBI settings elsewhere? Maybe the cache settings in server.ini? thanks. _____________________________________________________________ Can you survive the horror? http://www.morbidmortuary.com |