My current hypothesis is that something has been leaking file descriptors and we hit a hard limit. On Thu, 26 Feb 2004, Paul Winkler wrote:
On Thu, Feb 26, 2004 at 11:30:35AM -0800, Dennis Allison wrote:
In each case the target Zope was up and running and serving--which is what made it strange.
That's really odd and hard to believe, given that you say a restart fixed the problem. I have no clue.
On Thu, 26 Feb 2004, Paul Winkler wrote:
On Thu, Feb 26, 2004 at 10:22:22AM -0800, Dennis Allison wrote:
I've had a couple of instances where ZSyncer cannot find the target host(s). Restarting the Zopes seems to clear the problem. Any idea why that problem might occur?
Usually it means that the target zope really is not responding, either because zope is dead or spinning, or because there's some other network problem... e.g. a firewall has been reconfigured and is now blocking the connection from source to target, or DNS is broken, etc.
Whenever this comes up for me, my first check is always to ssh to the box that's running the "source" zope and see if I can connect to the target with a command-line web client, e.g. links, lynx, or wget.
Invariably the answer is "no".
--
Paul Winkler http://www.slinkp.com Look! Up in the sky! It's HYPER HAM-WENCH! (random hero from isometric.spaceninja.com)
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
--
Paul Winkler http://www.slinkp.com Look! Up in the sky! It's THE GAMMA EMCEE! (random hero from isometric.spaceninja.com)
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )