I haven't seen that error message before, so I googled around. According to various mod_perl mailing lists, that message should only show up if the user presses the "stop" button before the page is finished loading. Is the scoop page taking so long to display that you're cancelling the request in frustration? If that's the case, then that error message isn't the problem with Scoop, and we just have to figure out why Scoop is taking so long. I'd suggest, first, setting apache's log level back to "warn" and turning on Scoop's debug feature - at the top of many of the .pm files, there's a line that says: my $DEBUG = 0; If you change that 0 to 1, all of the debugging messages in that .pm file will print in the apache error log. I suggest starting with scoop/lib/Scoop.pm and scoop/lib/Scoop/ApacheHandler.pm as those are the early stages of the program and show the code being initialized and the handoff to the specific page handlers once Scoop has figured out what page you're looking for. -janra On 9-Jun-07, at 3:09 AM, Wallace Winfrey wrote: > Hello > > We recently moved our server to a new datacenter, and after the move, > Scoop no longer renders pages properly. > > The apache instance itself seems to be working just fine -- it's > returning imagines and CSS files, passing off requests to mod_proxy > and > interacting with our Twiki FCGI server just fine, and our mailman cgi > scripts are also working. It's just that none of the Scoop-generated > pages are rendering. > > I've set apache's LogLevel to debug, but the problem appears to be > confined entirely to the Scoop mod_perl thread, and thus, I'm not > seeing > very helpful messages from mod_perl in the log instance. The only > thing > I'm seeing is this: > > [Sat Jun 9 04:04:22 2007] [info] [client 74.6.73.82] (32)Broken pipe: > client stopped connection before rwrite completed > [Sat Jun 9 04:04:22 2007] [debug] Apache.c(364): (32)Broken pipe: > mod_perl: rwrite returned -1 (fd=3, B_EOUT=8)\n > > FWIW, we're running Scoop with RHEL ES 3, using Apache 1.3.34 and > Scoop > rev. 1.697, although we did do a cvs update on 10/10/2006. > > Does anyone have any ideas about where I could start to debug this > problem? Where I might possibly put some debugging messages in a > module > file to give me a better idea of where it's hanging? > > Apologies for the somewhat desperate tone of this message -- but > this is > a wholly unexpected circumstance. > > cheers > > w > > _______________________________________________ > Scoop-help mailing list > Scoop-help at lists.kuro5hin.org > http://lists.kuro5hin.org/mailman/listinfo/scoop-help