I'm running Pound 1.8.2 on FreeBSD 5.3 against OpenSSL 0.9.7g.

All I'd like to do is proxy to a Zope instance through port 80. Our
Zope instance runs on port 8180 and this cannot be changed, nor
accessed from the outside world.

I've setup my simple configuration file for pound, but when I execute
(as root) `/usr/local/pound/sbin/pound -f
/usr/local/pound/etc/pound.conf`, syslog reports: "pound: bad
argument(s)". Here is my configuration file:

$ cat /usr/local/pound/etc/pound.conf

###
### *Pound* Configuration for Rosetta Project
###

User pound
Group pound

LogLevel 3

# This Client entry is required for sane operations with MS browers
Client 1

ListenHTTP  64.81.54.81,80

UrlGroup    ".*"
HeadRequire Host    ".*preview.rosettaproject.org.*"
BackEnd     192.168.1.5,8180,1
EndGroup

########

Something isn't right but I'm not sure what. I do a `sockstat -l`
(similar to GNU/Linux's `netstat -atup`) and there is now listening
64.81.54.81:80. I've made sure I can ping this IP, it's up and
running.

DNS entries are also in place to point preview.rosettaproject.org. to
this public IP.

Assuming things were right, does this config match: "when I point my
web browser to http://preview.rosettaproject.org,
*Pound* picks up the
request on 64.81.54.81:80 and forwards requests to 127.0.0.1:8180"?

If there isn't a well commented sample config file (i can't find one)
there should be.

Any tips or suggestions would be greatly appreciated.
- bpk

see below, for some questions on your configuration, and reporting.

On 4 May 2005, at 23:30, Benjamin P. Keating wrote:
[...]
ok. i presume you're behind a firewall which is only letting port 80 
traffic through? and that the zope instance port can't be changed (eg 
to port 80) because you already have something on port 80 on the ip 
address in question?

[...]
this error message comes from config.c, line 774 (pound 1.8.2) and 
indicates that you're supplying incorrect arguments to pound. are you 
sure that's exactly what you typed? after the error statement is given, 
pound will exit. how many times did you attempt to execute pound?

[...]
is pound running? (what does ps show?) this doesn't agree with your 
initial problem.

[...]
ok. i presume you've changed things now as dns reports:

preview.rosettaproject.org. 3579 IN     A       64.81.54.51

[...]
no. you haven't specified 127.0.0.1 anywhere in the configuration, but 
you do have:

BackEnd     192.168.1.5,8180,1

so it would connect to 192.168.1.5 on port 8180

[...]
the default (sample) configuration file used by a debian pound 
installation is given at the end of this email. further commenting 
isn't really required as this would be replicating information from the 
man page and the FAQ, which would undesirable, requiring updating 
information in more than one location whenever changes are made to the 
documentation.

[...]

looking at http://preview.rosettaproject.org/
currently shows that the 
html contains, for example:

<base href="http://64.81.54.51:8180/rosetta/A1/"
/>

it's unclear, however, what you do and don't have working so far, 
according to your report above. can you clarify what your current 
status is?

best regards
andrew



------------------- pound.cfg

######################################################################
## global options:

User            www-data
Group           www-data
#RootJail       /chroot/pound

## allow PUT and DELETE also (by default only GET, POST and HEAD)?:
ExtendedHTTP    0

WebDAV          0

## Logging: (goes to syslog by default)
##      0       no logging
##      1       normal
##      2       extended
##      3       Apache-style (common log format)
LogLevel        1

## check backend every X secs:
Alive           30

## use hardware-accelleration card supported by openssl(1):
#SSLEngine      <hw>


######################################################################
## listen, redirect and ... to:

## redirect all requests on port 8888 ("ListenHTTP") to the local 
webserver see "UrlGroup" below):
ListenHTTP 127.0.0.1,8080

##
UrlGroup ".*"
BackEnd 127.0.0.1,80,1
EndGroup

Hey Andrew, Thanks for your reply.

I've spent some more time in the pound manual, I've changed my
configuration accordingly:

### Global Directives ###

ListenHTTP 64.81.54.81,80

User pound
Group pound

LogLevel 3

### Group Directives ###

UrlGroup ".*"
BackEnd 127.0.0.1,8180,1
EndGroup

########

Now, I got it to work *but* there is a weird issue which I forgot to
explain earlier.

There are two public IP's on this machine, 64.81.54.51 (IP1) and
64.81.54.81 (IP2). Since Apache is using port 80 on IP1, to make
migration easier/faster I aliased IP2 to the same hardware NIC as IP1.
When I tried starting pound with my new config syslog reported "pound:
64.81.54.81:80 already in use - skipped" when really it was
64.81.54.51 using port 80. Perhaps I should have Apache listen on an
odd port and proxy it through *Pound* as well. What would you
recommend? Freeing up a Public IP would be nice.

To test this, I switched my ListenHTTP to port 88 and things are
running beautifully. So this is a problem outside of *Pound*.
Apologize for posting here but at least it's another one for the
archives.

Also, as you've noticed, the Zope instance is at :8180/rosetta/A1/, is
there anyway for *Pound* to point to that and not root of Zope (just
8180)? Or would this be a VHM issue? The manul doesn't explain
anything like this, or I'm just clearly confused.

Thanks again Andrew,
- bpk


On 5/4/05, Andrew Nimmo <andrew.nimmo+apsis.ch(at)email.sh> wrote:[...]