Scott, If Mod_Perl was built (and in your case it probably was) with PERL_TRACE=1 then it generates significantly more logging than otherwise. I expect that's what you're seeing. All you need to do to correct this is, as root: perl Makefile.PL USE_APXS=1 \ WITH_APXS=/usr/local/apache/bin/apxs EVERYTHING=1 Note: without the PERL_TRACE=1 then: make make install and restart apache. The other possibility (depending on the type of errors) is, one of your hosted sites had a box that's generating errors above the normal logging, in which case you'd need to track down the problem box and correct it. -- Colin -- Scoophost.com - a service of Pinnacle Digital Scoop consulting and hosting services > Message: 1 > Date: Wed, 05 Sep 2007 12:25:32 -0500 > From: Scott Lockwood <scott at guppylog.com> > Subject: Re: [Scoop-help] Scoop filling my logs > To: Rusty Foster <rusty at kuro5hin.org> > Cc: scoop-help at lists.kuro5hin.org > Message-ID: <1189013132.6354.4.camel at scott-640m> > Content-Type: text/plain > > I should have replied to this much, much sooner - but, this didn't solve > the problem. Any other ideas? I've had to turn logging off, it kept > filling the drive up and DoS'ing the server. :-) heh > > On Wed, 2007-06-06 at 10:46 -0400, Rusty Foster wrote: >> Check that the site control use_db_cache exists and is off. That >> error comes out of a short-lived experimental database caching scheme >> that shouldn't be used by anyone ever. You'd get that error if the >> site was returning Scoop::Statement db statement handles instead of >> regular DBI handles, and the calling code was trying to do a >> fetchrow_array on them, which doesn't exist in Scoop::Statement. >> >> >> --R