We have an appliance which is using pound 2.7 as an sslizer in front of a Jetty
instance. It presents a http and https listener.
It showed an anomaly this morning where:
root: # poundctl -c /tmp/pound
Requests in queue: 0
0. http Listener :::80 a
0. Service "HTTP" active (0)
0. Backend 127.0.0.1:8080 active (5 0.000 sec) DEAD
1. HTTPS Listener :::443 a
0. Service "HTTPS" active (5)
0. Backend 127.0.0.1:8080 active (5 0.000 sec) alive
-1. Global services
so, the http port returned a 503, and the https did return the actual page. It
goes to the same backend port on the same box.
What could have caused this? The http port did not recover...
Kind regards,
Maurice
----------------------------------------------------------------------
The information contained in this transmission may be confidential. Any
disclosure, copying, or further distribution of confidential information is not
permitted unless such privilege is explicitly granted in writing by Quantum.
Quantum reserves the right to have electronic communications, including email
and attachments, sent across its networks filtered through anti virus and spam
software programs and retain such messages in order to comply with applicable
data security and retention requirements. Quantum is not responsible for the
proper and complete transmission of the substance of this communication or for
any delay in its receipt.
