Hello everybody,
we're new to pound. Recently we set up a pound daemon with three backend
servers.
Our /var/log/messages is filled up with following errors:
Aug 25 14:59:05 Intranet-Cluster pound: (40cb1940) error flush headers to
129.201.9.21: Connection reset by peer
Aug 25 14:59:06 Intranet-Cluster pound: (40144940) error flush headers to
129.201.9.21: Connection reset by peer
Aug 25 14:59:23 Intranet-Cluster pound: (40185940) error flush headers to
129.201.9.76: Connection reset by peer
Aug 25 14:59:24 Intranet-Cluster pound: (409e6940) error copy server cont:
Connection reset by peer
Aug 25 14:59:25 Intranet-Cluster pound: (409e6940) error copy server cont:
Connection reset by peer
Aug 25 14:59:25 Intranet-Cluster pound: (409e6940) error copy server cont:
Connection reset by peer
Aug 25 14:59:25 Intranet-Cluster pound: (409e6940) error copy server cont:
Connection reset by peer
Aug 25 14:59:25 Intranet-Cluster pound: (409e6940) error copy server cont:
Connection reset by peer
Aug 25 14:59:25 Intranet-Cluster pound: (4103f940) error copy server cont:
Connection reset by peer
Aug 25 14:59:25 Intranet-Cluster pound: (4103f940) error read from
129.201.9.76: Connection reset by peer
Aug 25 14:59:31 Intranet-Cluster pound: (40c70940) error flush headers to
129.201.9.76: Connection reset by peer
Aug 25 14:59:32 Intranet-Cluster pound: (40c70940) error flush headers to
129.201.9.76: Connection reset by peer
Aug 25 14:59:41 Intranet-Cluster pound: (40185940) error flush headers to
129.201.9.76: Connection reset by peer
Aug 25 14:59:41 Intranet-Cluster pound: (40efa940) error flush headers to
129.201.9.76: Connection reset by peer
Aug 25 14:59:41 Intranet-Cluster pound: (408e2940) error flush headers to
129.201.9.76: Connection reset by peer
Aug 25 14:59:41 Intranet-Cluster pound: (40595940) error flush headers to
129.201.9.76: Connection reset by peer
Aug 25 14:59:41 Intranet-Cluster pound: (40c70940) error flush headers to
129.201.9.76: Connection reset by peer
Aug 25 14:59:41 Intranet-Cluster pound: (4034c940) error flush headers to
129.201.9.76: Connection reset by peer
Aug 25 14:59:44 Intranet-Cluster pound: (4138c940) error flush headers to
129.201.9.76: Connection reset by peer
Aug 25 14:59:46 Intranet-Cluster pound: (4034c940) error copy server cont:
Connection reset by peer
Aug 25 14:59:46 Intranet-Cluster pound: (4034c940) error copy server cont:
Connection reset by peer
Aug 25 14:59:46 Intranet-Cluster pound: (4034c940) error copy server cont:
Connection reset by peer
Aug 25 14:59:46 Intranet-Cluster pound: (4034c940) error copy server cont:
Connection reset by peer
Aug 25 14:59:46 Intranet-Cluster pound: (4034c940) error copy server cont:
Connection reset by peer
Aug 25 14:59:46 Intranet-Cluster pound: (4034c940) error copy server cont:
Connection reset by peer
Aug 25 14:59:46 Intranet-Cluster pound: (40b2b940) error flush headers to
129.201.9.76: Connection reset by peer
Aug 25 14:59:50 Intranet-Cluster pound: (40595940) error copy server cont:
Connection reset by peer
Aug 25 14:59:50 Intranet-Cluster pound: (40595940) error copy server cont:
Connection reset by peer
Aug 25 14:59:50 Intranet-Cluster pound: (40595940) error copy server cont:
Connection reset by peer
Aug 25 14:59:50 Intranet-Cluster pound: (40595940) error copy server cont:
Connection reset by peer
Aug 25 14:59:50 Intranet-Cluster pound: (402ca940) error copy server cont:
Connection reset by peer
Aug 25 14:59:50 Intranet-Cluster pound: (402ca940) error copy server cont:
Connection reset by peer
Aug 25 14:59:51 Intranet-Cluster pound: (40595940) error flush headers to
129.201.9.76: Connection reset by peer
Aug 25 14:59:54 Intranet-Cluster pound: (40595940) error flush headers to
129.201.9.76: Connection reset by peer
Aug 25 14:59:54 Intranet-Cluster pound: (409a5940) error flush headers to
129.201.9.76: Connection reset by peer
Aug 25 15:00:33 Intranet-Cluster pound: (409a5940) error flush headers to
129.201.9.76: Connection reset by peer
Aug 25 15:00:33 Intranet-Cluster pound: (40860940) error flush headers to
129.201.9.76: Connection reset by peer
Aug 25 15:00:33 Intranet-Cluster pound: (408e2940) error flush headers to
129.201.9.76: Connection reset by peer
Aug 25 15:01:20 Intranet-Cluster pound: (41143940) error flush headers to
129.201.5.122: Connection reset by peer
Aug 25 15:01:22 Intranet-Cluster pound: (40617940) error flush headers to
129.201.9.21: Connection reset by peer
Aug 25 15:01:40 Intranet-Cluster pound: (40617940) error flush headers to
129.201.9.21: Connection reset by peer
Aug 25 15:02:06 Intranet-Cluster pound: (400c2940) error flush headers to
129.201.9.21: Connection reset by peer
Aug 25 15:02:17 Intranet-Cluster pound: (407de940) error copy server cont:
Connection reset by peer
Aug 25 15:02:17 Intranet-Cluster pound: (407de940) error copy server cont:
Connection reset by peer
Here is our configuration file for pound:
################################
## POUND CONFIGURATION
################################
## global options:
User "nobody"
Group "nogroup"
# RootJail "/chroot/pound"
## Have Pound run in the foreground (if 0) or as a daemon (if 1). By default
Pound runs as a daemon (detaches
## itself from the controlling terminal and puts itself in the background).
Daemon 1
## allow extended HTTP requests (PUT, DELETE). By default, Pound only allows
GET, POST and HEAD.
# ExtendedHTTP 0
## allow WebDAV requests (LOCK, UNLOCK). By default, Pound only allows GET,
POST and HEAD.
# WebDAV 0
## Enable or disable the dynamic rescaling code (default: 0). If enabled Pound
will periodically try to modify
## the back-end priorities in order to equalise the response times from the
various back-ends. This value can
## be overridden for specific services.
DynScale 1
## 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 consume resources - so beware.
## check backend every X secs, by default 30 seconds:
Alive 5
## specify for how long Pound will wait for a client request (default: 30
seconds). Set it higher if your clients time-out
## on a slow network or over-loaded server
Client 120
## How long should Pound wait for a response from the back-end (in seconds).
Default: 15 seconds. This value
## can be overridden for specific back-ends. alex manhart php:
max_execution_time: 30 seconds, apart from disabling by script
TimeOut 600
## How long should Pound continue to answer existing connections after a
receiving and INT or HUP signal
## (default: 30 seconds). The configured listeners are closed immediately.
You can bypass this behaviour by
## stopping Pound with a TERM or QUIT signal, in which case the program exits
without any delay.
Grace 30
Control "/tmp/pound.sock"
## Logging: (goes to syslog by default)
## 0 no logging
## 1 normal
## 2 extended
## 3 Apache-style (common log format)
LogLevel 2
# Eingehende Verbindungen Port 80
ListenHTTP
Address 129.201.5.60
Port 80
## If 1 force Pound to change the Location: and Content-location:
headers in responses. If they point to the
## back-end itself or to the listener (but with the wrong protocol) the
response will be changed to show the
## virtual host in the request. Default: 1 (active). If the value is
set to 2 only the back-end address is
## compared; this is useful for redirecting a request to an HTTPS
listener on the same server as the HTTP listener.
## alex manhart: loeste callcenter problem; Portwechsel PHP4<->PHP5
RewriteLocation 0
Service
URL "/\~.*"
BackEnd
Address 129.201.5.23
Port 80
End
End
# Backend-Server
Service
BackEnd
Address 129.201.5.61
Port 80
Priority 1
End
BackEnd
Address 129.201.5.62
Port 80
Priority 1
End
BackEnd
Address 129.201.5.63
Port 80
Priority 1
End
End
End
By the way, I have to mention, that our PHP Scripts make a lot of
XMLHttpRequests (AJAX), because of a heavy use of many RIA's (Rich Internet
Applications with Javascript).
Also important to know is, we've no errors in our Apache Logs and no errors
occur in the frontend (e.g. ie/firefox/safari browsers/clients)! Strange, can
someone explain that pound produce mass errors?
Mit freundlichen Grüßen,
Alexander Manhart
--
To unsubscribe send an email with subject unsubscribe to [email protected].
Please contact [email protected] for questions.
