Hi pound users and developers.
I just want to know if there is a acive development on the pound project. Or is
the last Date in 2.6 (2010) the last and final commit?
is this grub active? and may i get help if i ran my production farm with pound.
Thanx al lot,
ps
--
To unsubscribe send an emai
Hi Peter,
Welcome to Pound.
I'm sure that Joe will jump in at some stage with more details but we use
Pound ourselves and you can find that the community is quite active and
supportive.
Patches and fixes are normally found being posted to this list which if you
know some basic Unix commands and
Hi,
Joe stated the links to updated 2.6 and 2.7 branches in this thread:
http://www.apsis.ch/pound/pound_list/archive/2013/2013-04/136765000/index_html
Cheers, Andreas.
On 18.06.2013 14:55, Scott McKeown wrote:
> Hi Peter,
>
> Welcome to Pound.
>
> I'm sure that Joe will jump in at som
Thanks Andreas now bookmarked.
Don't know how I didn't see that before.
~Scott
On 18 June 2013 14:08, Andreas Hilboll wrote:
> Hi,
>
> Joe stated the links to updated 2.6 and 2.7 branches in this thread:
>
>
>
> http://www.apsis.ch/pound/pound_list/archive/2013/2013-04/136765000/index_
I'm trying to use the -b option for poundctl to disable a backend.
The command runs with the three fields listener service and backend. The
command appears to work.
But when I list out the -X option it says all backends are enabled... even
though I just disabled it. So the options for poundctl
It would appear I'm not the only one to run into and document this exact
problem:
https://groups.google.com/forum/#!msg/pound_proxy/s_OZhTcznRc/nq_HqNMjFwcJ
On Tue, Jun 18, 2013 at 9:37 AM, Brad Allison wrote:
> I'm trying to use the -b option for poundctl to disable a backend.
>
> The command
From the man page:
Alive value
Specify how often Pound will check for resurected back-end
hosts (default: 30 seconds). In general, it is a good idea to set this as low
as possible - it will find resurected
hosts faster. However, if you set it too low it will
Try using -1 as the listener.
>From your XML output it appears you use global services. (Services not
>contained within the Listener block itself)
Joe
From: Brad Allison [mailto:brad.alli...@gmail.com]
Sent: Tuesday, June 18, 2013 9:37 AM
To: pound@apsis.ch
Subject: [Pound Mailing List] poundc
Hi Roberto,
I'm sure its just a case of sending an eMail to pound@apsis.ch with the
subject of 'unsubscribe'
On 18 June 2013 14:52, Roberto Geraldo Pimenta Ribeiro Junior <
rpime...@senado.gov.br> wrote:
> ** **
>
--
With Kind Regards.
Scott McKeown
Loadbalancer.org
http://www.loadbalan
Pcidss/v2.6 branch also appears to work fine. (without any additional commits)
Joe
From: Joe Gooch
Sent: Tuesday, June 18, 2013 11:18 AM
To: 'pound@apsis.ch'
Subject: RE: [Pound Mailing List] poundctl command simply do not work
I just checked with my installed pound 2.5 branch and enabling/disab
Seems like I didn't have to chime in. :)
Robert Segall is the maintainer... I haven't heard from him in awhile; I know
his life is very busy. He has put out v2.7b which is the next beta branch.
I maintain a github project with the source code at
http://github.com/goochjj/pound/ Branches of no
I just checked with my installed pound 2.5 branch and enabling/disabling
backends for both global and listener specific services work for me. And I
know it works, because I have a perl based web interface wrapped around it.
However my poundctl looks more than a little different, because I’m run
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 still pointed to that server. I also see in the pound.log that it's
still sending request to that "DI
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 connections. (connections not in our session
database)
Disabled means it cannot receive new conn
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 pound. So all new
Requests should be forwaded to the non-disabled backends.
Kind regards
David
Am 18.
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 it to BE_KILL.
Once upon a time I wrote a perl script to parse the xml output from poundctl
and
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
Zip:
https://github.com/goochjj/pound/archive/stage_for_upstream/v2.7b.zip
Patch:
https://github.
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 existing sessions may still
cause requests to be sent their way.
We do the same like Joe said: shut
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 is marked as "DISABLED" does pound still
check it for availability? Meaning does pound still ping
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 accomplish the same result.
As for checking for availability, are you talking about HAPort or Alive? Al
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 don't want pound constantly checking for
them if I know they are offline.
If I set them to DISABLED
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.alli...@gmail.com]
Sent: Tuesday, June 18, 2013 2:56 PM
To: pound@apsis.ch
Subject: [Pound Mailing List] DISABLED backend checked by pound for al
23 matches
Mail list logo
