Displaying 10 results from an estimated 10 matches for "redispatch".
Did you mean:
sedispatch
2013 Feb 01
3
Cannot get puppetlabs-haproxy to do what I want
...tion'' => [
''httplog'',
]
},
ipaddress => "",
ports => [80],
}
}
When these run, haproxy goes down because it puts the server entry under
defaults instead of messaging00:
defaults
log global
maxconn 8000
option redispatch
retries 3
stats enable
timeout http-request 10s
timeout queue 1m
timeout connect 10s
timeout client 1m
timeout server 1m
timeout check 10s
server rabbit01 10.0.2.15:55672,10.0.2.15:5672 check
listen messaging00 10.0.2.15:55672,10.0.2.15:5672
balance roundrobin
mode...
2011 Oct 18
3
haproxy ssl
...empting to load balance SSL web servers using haproxy on centos 5.7.
I am using HA-Proxy version 1.4.18
Here is the stanza in the config regarding SSL:
listen https 192.168.1.200:443
mode tcp
balance roundrobin
option forwardfor except 192.168.1.200
option redispatch
maxconn 10000
reqadd X-Forwarded-Proto:\ https
server web1 web1.summitnjhome.com:443 maxconn 5000
server web2 web2.summitnjhome.com:443 maxconn 5000
I can connect to https on each web server and have it serve content. the IP 192.168.1.200 is a virtual IP created w...
2016 Jun 24
1
haproxy + Apache + virtual hosts -> wrong host is displayed
...xy-1.5.14-3.el7.x86_64
httpd-2.4.6-40.el7.centos.1.x86_64
The /etc/haproxy/haproxy.cfg binds HAProxy to
ports 80 and 443 and accepts HTTPS to slova.de:
defaults
mode http
option http-server-close
option forwardfor except 127.0.0.0/8
option redispatch
....
frontend public
bind 144.76.184.151:80
bind 144.76.184.151:443 ssl crt /etc/pki/tls/certs/slova.de.pem
reqidel ^X-Forwarded-Proto:
reqidel ^X-Forwarded-For:
reqadd X-Forwarded-Proto:\ https if { ssl_fc }
option forwardfor
default_backend apache
backend apache
s...
2010 Dec 01
0
[LLVMdev] RFC: Exception Handling Proposal Revised
...invoke?
> Syntax:
>
> dispatch resume to label<resumedest>
How do you say: if nothing is matched, keep unwinding out of the function?
Actually I don't see why <resumedest> is useful at all, since you can always
place a complete set of all handlers into one dispatch, so redispatching is
not needed. That said, it might be handy for reducing code duplication.
> catches [
> <type> <val>, label<dest1>
> ...
> ]
> catchall [<type> <val>, label<dest> ]
> personality [<type> <valu...
2012 Jun 28
0
[LLVMdev] One problem to discuss
...kernel will invoke SignalHandler to handle the signal, but may deadlock at mutex acquire (as kernel now is conditionally preemptied).
Maybe we can trylock (instead of lock) at the beginning of SignalHandler (the locking period should not be a concern as we running in the kernel now), if try fails, redispatch the signal and exits (try again in next time enter in); otherwise go ahead as usual.
Best Regards
Hui Wu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120628/24da9ab3/attachment.html>
2006 Sep 07
2
Running two clusters side by side
I''m happy to announce that ChaCha.com a new search engine that debuted this
week and it runs on a mongrel cluster.
Warning, promo follows. :)
ChaCha.com is unlike any other search engine since it allows you to connect
to a "guide" with experience in the field(s) of knowledge you are searching
in. (Based on your keywords) Check it out at http://www.chacha.com
Now on to my
2010 Dec 01
2
[LLVMdev] RFC: Exception Handling Proposal Revised
...t;
>> dispatch resume to label<resumedest>
>
> How do you say: if nothing is matched, keep unwinding out of the function?
> Actually I don't see why <resumedest> is useful at all, since you can always
> place a complete set of all handlers into one dispatch, so redispatching is
> not needed. That said, it might be handy for reducing code duplication.
>
The <resumedest> will have code to handling unwinding out of the function. Normally, it will just call _Unwind_Resume(). As you saw in the example, though, it may call other things (like `terminate()'...
2010 Dec 01
10
[LLVMdev] RFC: Exception Handling Proposal Revised
This is a revision of the second exception handling proposal I sent out. You can see it here:
http://lists.cs.uiuc.edu/pipermail/llvmdev/2010-November/036484.html
After much discussion, there are some changes to the proposal – some significant and some minor. One major point, this proposal does not address the issue of catching an exception thrown from a non-invoke instruction. However if done
2008 Jan 23
14
Again: Workaround found for request queuing vs. num_processors, accept/close
Hello all.
I too found out that I sometimes have some action that can take up to 10
seconds in my rails application. I''ve read all arguments Zed made about
polling/and inbox strategies, and I think I just can''t work around my feeling
that a "wrong" request that takes up too much time should be able to lock
subsequent requests in mongrels queue. That''s what
2012 Jun 20
12
Could not run Puppet configuration client: execution expired
Hello,
I''m running Puppet 2.7.6 and currently expanding the number of servers
managed by Puppet. At around the 160-170 host mark (with a 5-minute run
interval + splay), my puppetmaster server is starting to die. Is this
normal? What I''m getting in the agent logs is the following:
Wed Jun 20 12:15:08 +0200 2012 Puppet (debug): Failed to load library