On Wed, Mar 10, 2010 at 6:20 PM, (private) HKS <[email protected]> wrote: > I'm moving my Pound servers from OpenBSD to FreeBSD 8.0 AMD64. > > I've compiled Pound 2.5 from source --with-maxbuf384 and included > PCRE. Each instance of Pound is throwing this error at its first > request: > > pound: MONITOR: worker exited on signal 11, restarting > > Subsequent requests are serviced normally. I'm using the same > configurations that I was using on the OpenBSD boxes (albeit with > relevant paths corrected). I've pasted my config below. Anybody seen > this before? > > > -HKS > > > User "pound" > Group "pound" > Control "/var/run/pound-ctl.socket" > LogFacility daemon > LogLevel 5 > Alive 30 > Client 30 > TimeOut 900 > Grace 30 > > # HTTP goes to HTTPS redirect > ListenHTTP > Address 10.2.1.72 > Port 80 > RewriteLocation 2 > Service > Backend > Address 10.2.1.11 > Port 8080 > End > Backend > Address 10.2.1.21 > Port 8080 > End > Backend > Address 10.2.1.22 > Port 8080 > End > End > End > > ListenHTTPS > Address 10.2.1.72 > Port 443 > Cert "/usr/local/etc/pound/private/cert.pem" > Client 30 > RewriteLocation 2 > > # Mercurial requests get big timeouts > Service > HeadRequire "[Aa][Cc][Cc][Ee][Pp][Tt]: > .*application\/mercurial.*" > HeadRequire "[Uu][Ss][Ee][Rr]-[Aa][Gg][Ee][Nn][Tt]: > .*mercurial.*" > Backend > Address 10.2.1.24 > Port 80 > # 12 hours > Timeout 43200 > End > Backend > Address 10.2.1.30 > Port 80 > # 12 hours > Timeout 43200 > End > End > > Service > Backend > Address 10.2.1.24 > Port 80 > End > Backend > Address 10.2.1.30 > Port 80 > End > End > End > > # Uh-Oh page in case everything else is hosed > Service > Backend > Address 127.0.0.1 > Port 8181 > End > End >
This seems to be related to configuring with --with-maxbuf384 on a 64-bit box (I don't have any 64-bit non-FreeBSD boxes, so I can't test that). If I leave that out or use --with-maxbuf92, there is no initial segfault. Any idea what's going on here? -HKS -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
