Good idea.. I'll check that software out. I used to use something called NetSaint back in the day.. dont know if its still around or still as hard to configure as it used to be.
Thanks, - Brent > -----Original Message----- > From: Upayavira [mailto:[EMAIL PROTECTED] > Sent: Friday, May 21, 2004 4:24 AM > To: [EMAIL PROTECTED] > Subject: Re: Broken Pipes w/ Production Site > > [EMAIL PROTECTED] wrote: > > >Thanks - Ill try upgrading to 2.1.4 and see if that helps. > >Yeah I wasnt sure whether those exceptions were the problem > (since they > >do appear in other parts of the log file) but that was all I found > >around the time the problem occurred. > > > >I also increased the pool size in the cocooon.xconf file > after having > >problems with Cocoon/Tomcat returning blank pages (as in > actual blank > ><body> tags). I've been working on a side project called Webgate > >(webgate.sourceforge.net) and I had the blank page problem and > >increasing pool sizes seemed to fix that.. so I tried it on the > >production site and that seems to have worked (so far). > > > >But this new issue with the whole webserver no longer responding has > >started to worry me quite a bit. It's not good to have your > boss (the > >owner of the company) call me because the website isnt responding :( > > > > > Not an answer to your immediate problem, but... > > Have you got any monitoring on your server? > > I've started using Nagios (www.nagios.org) an OS monitoring > tool, Unix based, and it is great. (Up until now, all my > monitoring was hand crafted). You can set it up to test your > server every five minutes (say), and send you an > email/text/pager message whenever it (a) doesn't respond (b) > doesn't give a response you'd expect (e.g. page must contain > a specific phrase). > > With something like this, at least you can be sure you'll > find out before your boss! > > HTH. Upayavira > > >Luckily restarting seemed to fix it for now. > > > >This seems to only happen after the site has been running > for a month > >or so.. so a memory leak may definitely be the problem. I'll try > >upgrading.. and also setting up a new cron job to reboot the server > >every couple weeks just in case. > > > >Thanks, > > > >- Brent > > > > > > > >>-----Original Message----- > >>From: Askild Aaberg Olsen [mailto:[EMAIL PROTECTED] > >>Sent: Thursday, May 20, 2004 6:28 PM > >>To: [EMAIL PROTECTED] > >>Subject: RE: Broken Pipes w/ Production Site > >> > >>It seems like the client aborted the connection, like when the user > >>pressed "Stop" in the browser when the page loaded. > >>I'm using Jetty, but I get a similar message here. > >> > >>Try that yourself, by pressing "Stop" when the page loads, > and see if > >>you get the same message. > >> > >>If this is the case, I don't know if this is the cause of your > >>problem. > >> > >>There were some memory-leaks in Cocoon versions before 2.1.4. > >>Maybe this is the cause? > >>Then upgrading would certanly help. > >> > >>Have been running 2.1.4 for 40 days straight now, but it's > not a wery > >>high level of traffic on my sites, though. > >> > >>Playing with the pools in the sitemap and the store-settings in > >>cocoon.xconf helped me a lot in terms of performance, > especialy since > >>my site seemed to respond slower and slower before i did these > >>changes. > >> > >>Not much, but hopefully some of the more experienced users > will have > >>other ideas when they wake up in the morning (The > Cocoon-lists seems > >>to follow European times in terms of activity ;) > >> > >>Good luck! > >> > >>Askild > >>- > >> > >> > >>------------------------------------------------------------ > --------- > >>To unsubscribe, e-mail: [EMAIL PROTECTED] > >>For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > >> > >> > >> > >> > > > > > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
