/ Zope / Apsis / Pound Mailing List

• Archive
• 2013
• 2012
• 2011
• 2010
• 2009
• 2008
• 2007
• 2006
• 2005
• 2004
• 2003

Recent Posts

• 2013-06-18 21:58:19 RE: [Pound Mailing List] DISABLED backend checked by pound for alive/dead? / Joe Gooch <mrwizard(at)k12system.com>
  I don’t know for sure. But it looks like enabled/disabled has no bearing at all on alive/dead status, or checking. Joe From: Brad Allison [mailto:brad.allison(at)gmail.com] Sent: Tuesday, June 18, 2013
  
  
• 2013-06-18 20:56:12 DISABLED backend checked by pound for alive/dead? / Brad Allison <brad.allison(at)gmail.com>
  If a backed is tagged as "DISABLED" does pound continue to check it for alive/dead status? I want to put a bunch of IP's in there for possible webservers, and just leave them physically off. But I d
  
  
• 2013-06-18 20:53:42 RE: [Pound Mailing List] poundctl command simply do not work / Joe Gooch <mrwizard(at)k12system.com>
  Poundctl doesn’t let you mark something as dead,unless you change the line I mentioned in the last email. However, marking a backend as disabled and using the flush patch I just posted would accompli
  
  
• 2013-06-18 19:52:03 RE: [Pound Mailing List] poundctl command simply do not work / Joe Gooch <mrwizard(at)k12system.com>
  My stage for upstream branch now contains a patch to add –f to poundctl to flush all sessions for a backend. Feel free to test! Branch https://github.com/goochjj/pound/tree/stage_for_upstream/v2.7b
  
  
• 2013-06-18 19:50:18 Re: [Pound Mailing List] poundctl command simply do not work / Brad Allison <brad.allison(at)gmail.com>
  I was looking at the options and I can't see a way to mark a backend server as dead. For now I've just been stopping apache on the server to make pound see it as dead. Another question: If a server
  
  
• 2013-06-18 19:38:29 Re: [Pound Mailing List] poundctl command simply do not work / "D. R." <daveyx(at)gmx.de>
  Brad, for example look here: http://linux.die.net/man/8/poundctl *-B/-b n m r* Enable/disable a back-end. A disabled back-end will not be passed requests to answer. Note however that existin
  
  
• 2013-06-18 19:38:00 RE: [Pound Mailing List] poundctl command simply do not work / Joe Gooch <mrwizard(at)k12system.com>
  Or you could implement a HAPort script to mark the backend dead. Or you could use poundctl to delete the sessions. Or you could edit svc.c… Search for BE_DISABLE in the CTRL_DE_BE block, and change
  
  
• 2013-06-18 19:32:39 Re: [Pound Mailing List] poundctl command simply do not work / "D. R." <daveyx(at)gmx.de>
  Hi Brad, according to the pound documentation you are facing the correct behaviour. pound still directs Requests to the disabled backend, but only if this client is still in the routing table of poun
  
  
• 2013-06-18 19:32:10 RE: [Pound Mailing List] poundctl command simply do not work / Joe Gooch <mrwizard(at)k12system.com>
  Because you’re using session affinity, and you still have active sessions attached to that host. A backend can be Alive or Dead. It can also be Enabled or Disabled. Enabled means it can receive new
  
  
• 2013-06-18 19:21:58 Re: [Pound Mailing List] poundctl command simply do not work / Brad Allison <brad.allison(at)gmail.com>
  Okay. Now using -1 for the listener I see the backend server is listed as status="DISABLED". So that part worked. But I also see traffic is still being sent to that server and hostname keys are sti