/ Zope / Apsis / Pound Mailing List / Archive / 2003 / 2003-09 / Pound WORKER Exit 11

[ << ] [ >> ]

[ <many bad words> spammers / "Eric S. ... ] [ simple attempts not working / "Eric S. ... ]

Pound WORKER Exit 11
"D JS" <djs-pound(at)whatcom.net>
2003-09-18 21:29:47 [ FULL ]
I'm using the FreeBSD 5.1 operating system. pound was included with the
standard included ports and packages distribution so after stumbling across it
on the CD, I decided to try it.

I've never had a ports or package in FreeBSD fail before, so I thought it would
be worth seeking advice from this mailing list.

Here is a summary of what happened right up to the trouble point:

1. I compiled and installed the pound port from the FreeBSD ports collection
successfully with no errors reported.

2. I typed man pound at the prompt and reviwed the online manual. I then tried
to execute pound and analyze the log file on my system. As expected, I noticed
that it didn't remain resident as a background process because it exited at
start up looking for a configuration file in /usr/local/etc called pound.cfg

3. I reviewed the documentation and created the following pound.cfg file
for my host which has an interface card connected to the Internet on address
a.b.c.d which has a web service process (the intented "BackEnd" for pound to
use) serving requests on any interface port 8080 that I wanted to try accessing
from the Internet on port 8070 via pound:

ListenHTTP a.b.c.d,8070
UrlGroup ".*"
BackEnd a.b.c.d,8080,1
EndGroup

4. I then try to access this website http://a.b.c.d:8070

but it fails with a connection broken message on the web browser and the
following entries are found in my /var/log file:

Sep 18 12:21:23 myhost kernel: pid 22068 (pound), uid 0: exited on signal 11
(core dumped) 
Sep 18 12:21:23 myhost pound: MONITOR: worker exited on signal 11, restarting. 

[...]

Why is the WORKER getting the segmentation error everytime it is called upon to
redirect the request from 8070 to 8080? The main pound process restarts a new
copy of WORKER everytime.

I would assume WORKER is getting an EXIT SIGNAL 11 because I made an error or
omission in the configuration file /usr/local/etc/pound.cfg but would have
thought that I would have been informed of a problem at program start up time.

I've made sure that http://a.b.c.d:8080 is an
available, living backend.

Any help would be appreciated, please.

Thank You

Re: Pound WORKER Exit 11
Andreas Roedl <andreas.roedl(at)native-instruments.de>
2003-09-19 12:03:32 [ FULL ]
Hello!

Am Donnerstag, 18. September 2003 21:29 schrieb D JS:[...]

The "release" ports collection of FreeBSD 5.1 includes a pretty old version of 
Pound (1.2). The "current" tree of the ports collection has version 1.4:

http://gatekeeper.dec.com/pub/BSD/FreeBSD/ports/i386/packages-5.1-release/www/pound-1.2.tbz
http://gatekeeper.dec.com/pub/BSD/FreeBSD/ports/i386/packages-current/www/pound-1.4.tbz

You can either switch to "current" or get the bleeding edge version of Pound 
here:

  http://www.apsis.ch/pound/Pound-current.tgz


Andi[...]

Re: Pound WORKER Exit 11
Robert Segall <roseg(at)apsis.ch>
2003-09-19 13:39:07 [ FULL ]
On Thursday 18 September 2003 21:29, you wrote:[...]

There are indeed two processes, a monitor and a worker. Should the worker 
fail the monitor would have it restarted.

I admit I never tried Pound on FreeBSD 5.1. I would suggest you have a look 
at the Makefile resulting from the autoconf - we know of problems with the 
latest version of OpenBSD due to a change in the threading library. Please 
make sure that -DNEED_STACK appears in the CFLAGS - if not please add it 
manually.

Good luck and let us know...[...]

MailBoxer