This is to announce the release of Pound v2.2.1. Changes in this version
(since 2.2):

Enhancements:
  - allow specific Listeners to override the gloabl LogLevel value
  - allow a default Client value to be defined at the global level
  - allow a default TimeOut value to be defined at the global level
  - added compile-time flags for file owner and group

Bug fixes:
  - fixed some problems in the installation procedure
  - fixed problem in SSL session string
  - added protocol check in need_rewrite

The software is at version 2.2.1 (beta quality). Further testing
(especially under heavy loads), improvements and suggestions are
welcome.
-- 
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-44-920 4904

> This is to announce the release of Pound v2.2.1. Changes in this version
> (since 2.2):

This is pretty minor, but I wanted to report that the '-D' option to the 
'install' binary doesn't exist on OpenBSD 4.0.  Output:

$ sudo make install
/usr/bin/install -c -o proxy -g proxy -m 555 -D pound /usr/local/sbin/pound
install: unknown option -- D
usage: install [-bCcdpSs] [-B suffix] [-f flags] [-g group] [-m mode] 
[-o owner]
                source [...] target [...]
*** Error code 64

Stop in /home/dave/src/Pound-2.2.1 (line 52 of Makefile).

I simply removed it locally.

Regards,
-- 
Dave Steinberg
http://www.geekisp.com/
http://www.steinbergcomputing.com/

On Mon, 2007-01-08 at 14:13 -0500, Dave Steinberg wrote:
> > This is to announce the release of Pound v2.2.1. Changes in this version
> > (since 2.2):
> 
> This is pretty minor, but I wanted to report that the '-D' option to the 
> 'install' binary doesn't exist on OpenBSD 4.0.  Output:
> 
> $ sudo make install
> /usr/bin/install -c -o proxy -g proxy -m 555 -D pound /usr/local/sbin/pound
> install: unknown option -- D
> usage: install [-bCcdpSs] [-B suffix] [-f flags] [-g group] [-m mode] 
> [-o owner]
>                 source [...] target [...]
> *** Error code 64
> 
> Stop in /home/dave/src/Pound-2.2.1 (line 52 of Makefile).
> 
> I simply removed it locally.

Thanks Dave, we'll try again in the next release.
-- 
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-44-920 4904

Hi Robert,

Thanks for you update on poundctl / OpenBSD working, since then I've 
been playing around to try and work out what I'm doing wrong. I've now 
managed to track down something significant, I think.

Below is my current working 'config' file.

User "nobody"
Group "nobody"
Daemon 1
LogFacility user
LogLevel 2
Alive 30

ListenHTTP
            Address 10.190.10.120
            Port    80

            Service
                BackEnd
                    Address 10.190.10.102
                    Port    80
                    HAport  1234
                    Priority 1
                End

                BackEnd
                    Address 10.190.10.103
                    Port    80
                    HAport 1234
                    Priority 2
                End
                Session
                    Type  IP
                    TTL  300
                End
            End
End

Now as previously stated if I modify the file as follows Pound stops 
forwarding to the backends but using poundctl does work.

User "nobody"
Group "nobody"
Daemon 1
LogFacility user
LogLevel 2
Alive 30
Control "/etc/ctlfile"

Ok so this we know. If I now turn off logging and leave the Control 
directive in i.e.

User "nobody"
Group "nobody"
Daemon 1
LogFacility user
LogLevel 0
Alive 30
Control "/etc/ctlfile"

Poundctl now works AND the Pound daemon forwards requests to my backend 
servers.

So it looks like I'm doing something wrong in the logging. Initially 
when 'playing' with pound I couldn't get anything to appear in the 
syslog, I had originally been using 'LogFacility daemon', changing this 
to 'user' meant I got log messages.

Following a post a couple of days ago I modified my Pound config as follows:

LogFacility pound

and my syslog.conf as follows:

#       $OpenBSD: syslog.conf,v 1.17 2005/05/25 07:35:38 david Exp $
#

!!pound
*.*                                    /var/log/pound
!*

*.notice;auth,authpriv,cron,ftp,kern,lpr,mail,user.none /var/log/messages
kern.debug;syslog,user.info                             /var/log/messages
auth.info                                               /var/log/authlog
authpriv.debug                                          /var/log/secure
cron.info                                               /var/cron/log
daemon.info                                             /var/log/daemon
ftp.info                                                /var/log/xferlog
lpr.debug                                               /var/log/lpd-errs
mail.info                                               /var/log/maillog
#uucp.info                                              /var/log/uucp

Hoping that all pound logs would be directed to a separate file, however 
this does not appear to be working. I changed my pound config to 
'daemon' then 'user' but still nothing appearing in /var/log/pound

Sorry for the long post, if someone could point me to the right place 
I'll gladly RTFM but at present I'm not sure where to begin. What do 
other OBSD users do about logging?

Many thanks

Simon

> Hoping that all pound logs would be directed to a separate file, however 
> this does not appear to be working. I changed my pound config to 
> 'daemon' then 'user' but still nothing appearing in /var/log/pound

On my OpenBSD machines, I don't even bother setting a LogFacility in the 
pound.conf file - I just have the following at the top of my syslog.conf:

!!pound
*.*                                       /var/log/pound
!*

Which you already have.  Just to establish that you're doing things 
right with syslog, be sure:

1) /var/log/pound exists and is writable
2) You've restarted syslogd

If those are true, and you still get nothing in the logs from pound, 
make a new syslog target like:

*.*         /var/log/all

And see what you get.  For completeness, my pound.conf starts with:

User        "www"
Group       "www"
RootJail    "/var/pound"
Alive       15
LogLevel    2
Daemon      0
Control     "/tmp/pound.sock"

PS - Daemon mode seems to give me some trouble.  Does it work properly 
for you?

-- 
Dave Steinberg
http://www.geekisp.com/
http://www.steinbergcomputing.com/

On Wed, 2007-01-10 at 11:31 +0000, Simon Slaytor wrote:
> Now as previously stated if I modify the file as follows Pound stops 
> forwarding to the backends but using poundctl does work.
> 
> User "nobody"
> Group "nobody"
> Daemon 1
> LogFacility user
> LogLevel 2
> Alive 30
> Control "/etc/ctlfile"

This might be problematic: user "nobody" probably has no write
permission in /etc. Try using "/tmp/ctrlfile" or similar.

> Ok so this we know. If I now turn off logging and leave the Control 
> directive in i.e.
> 
> User "nobody"
> Group "nobody"
> Daemon 1
> LogFacility user
> LogLevel 0
> Alive 30
> Control "/etc/ctlfile"
> 
> Poundctl now works AND the Pound daemon forwards requests to my backend 
> servers.
> 
> So it looks like I'm doing something wrong in the logging. Initially 
> when 'playing' with pound I couldn't get anything to appear in the 
> syslog, I had originally been using 'LogFacility daemon', changing this 
> to 'user' meant I got log messages.
> 
> Following a post a couple of days ago I modified my Pound config as follows:
> 
> LogFacility pound
> 
> and my syslog.conf as follows:
> 
> #       $OpenBSD: syslog.conf,v 1.17 2005/05/25 07:35:38 david Exp $
> #
> 
> !!pound
> *.*                                    /var/log/pound
> !*
> 
> *.notice;auth,authpriv,cron,ftp,kern,lpr,mail,user.none /var/log/messages
> kern.debug;syslog,user.info                             /var/log/messages
> auth.info                                               /var/log/authlog
> authpriv.debug                                          /var/log/secure
> cron.info                                               /var/cron/log
> daemon.info                                             /var/log/daemon
> ftp.info                                                /var/log/xferlog
> lpr.debug                                               /var/log/lpd-errs
> mail.info                                               /var/log/maillog
> #uucp.info                                              /var/log/uucp
> 
> Hoping that all pound logs would be directed to a separate file, however 
> this does not appear to be working. I changed my pound config to 
> 'daemon' then 'user' but still nothing appearing in /var/log/pound

Please use standard log facilities. "pound" and "user" are not it!

> Sorry for the long post, if someone could point me to the right place 
> I'll gladly RTFM but at present I'm not sure where to begin. What do 
> other OBSD users do about logging?
> 
> Many thanks
> 
> Simon
> 
> 
> 
-- 
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-44-920 4904

Thanks Dave,

I'll try that syslog option tomorrow, daemon seems to works 'ok' for me.


Dave Steinberg wrote:
>> Hoping that all pound logs would be directed to a separate file, 
>> however this does not appear to be working. I changed my pound config 
>> to 'daemon' then 'user' but still nothing appearing in /var/log/pound
>
> On my OpenBSD machines, I don't even bother setting a LogFacility in 
> the pound.conf file - I just have the following at the top of my 
> syslog.conf:
>
> !!pound
> *.*                                       /var/log/pound
> !*
>
> Which you already have.  Just to establish that you're doing things 
> right with syslog, be sure:
>
> 1) /var/log/pound exists and is writable
> 2) You've restarted syslogd
>
> If those are true, and you still get nothing in the logs from pound, 
> make a new syslog target like:
>
> *.*         /var/log/all
>
> And see what you get.  For completeness, my pound.conf starts with:
>
> User        "www"
> Group       "www"
> RootJail    "/var/pound"
> Alive       15
> LogLevel    2
> Daemon      0
> Control     "/tmp/pound.sock"
>
> PS - Daemon mode seems to give me some trouble.  Does it work properly 
> for you?
>

Hi Robert,

Thanks again for the reply, I've tried root/wheel as the user/group 
unfortunately it makes no difference.

What is a 'standard' log facility? I've tried daemon but as I say this 
results in no output in syslog.

I'll try the suggestion of removing 'LogFacility' from my pound config 
altogether and redirecting pound output in syslog.conf

Thanks

Simon


Robert Segall wrote:
> On Wed, 2007-01-10 at 11:31 +0000, Simon Slaytor wrote:
>   
>> Now as previously stated if I modify the file as follows Pound stops 
>> forwarding to the backends but using poundctl does work.
>>
>> User "nobody"
>> Group "nobody"
>> Daemon 1
>> LogFacility user
>> LogLevel 2
>> Alive 30
>> Control "/etc/ctlfile"
>>     
>
> This might be problematic: user "nobody" probably has no write
> permission in /etc. Try using "/tmp/ctrlfile" or similar.
>
>   
>> Ok so this we know. If I now turn off logging and leave the Control 
>> directive in i.e.
>>
>> User "nobody"
>> Group "nobody"
>> Daemon 1
>> LogFacility user
>> LogLevel 0
>> Alive 30
>> Control "/etc/ctlfile"
>>
>> Poundctl now works AND the Pound daemon forwards requests to my backend 
>> servers.
>>
>> So it looks like I'm doing something wrong in the logging. Initially 
>> when 'playing' with pound I couldn't get anything to appear in the 
>> syslog, I had originally been using 'LogFacility daemon', changing this 
>> to 'user' meant I got log messages.
>>
>> Following a post a couple of days ago I modified my Pound config as follows:
>>
>> LogFacility pound
>>
>> and my syslog.conf as follows:
>>
>> #       $OpenBSD: syslog.conf,v 1.17 2005/05/25 07:35:38 david Exp $
>> #
>>
>> !!pound
>> *.*                                    /var/log/pound
>> !*
>>
>> *.notice;auth,authpriv,cron,ftp,kern,lpr,mail,user.none /var/log/messages
>> kern.debug;syslog,user.info                             /var/log/messages
>> auth.info                                               /var/log/authlog
>> authpriv.debug                                          /var/log/secure
>> cron.info                                               /var/cron/log
>> daemon.info                                             /var/log/daemon
>> ftp.info                                                /var/log/xferlog
>> lpr.debug                                               /var/log/lpd-errs
>> mail.info                                               /var/log/maillog
>> #uucp.info                                              /var/log/uucp
>>
>> Hoping that all pound logs would be directed to a separate file, however 
>> this does not appear to be working. I changed my pound config to 
>> 'daemon' then 'user' but still nothing appearing in /var/log/pound
>>     
>
> Please use standard log facilities. "pound" and "user" are not it!
>
>   
>> Sorry for the long post, if someone could point me to the right place 
>> I'll gladly RTFM but at present I'm not sure where to begin. What do 
>> other OBSD users do about logging?
>>
>> Many thanks
>>
>> Simon
>>
>>
>>
>>     

Hi Dave / Robert / Folks,

Based on your advice I now have pound / poundctl working with pound 
logging to it's own logfile, great many thanks.

But....

As you say now running pound in 'Daemon' mode no longer works, or rather 
it does but the pound process dies a quick death, we use the 'HAport' 
option, checking our 'ha' app on the www servers show pound never tries 
to connect to the ha port. However I run my boxes headless so tying up 
the console with pound at boot isn't a biggy for me.

Many thanks for the advice, I'll play around with the daemon problem but 
if you make any headway remember your fellow OBSD users :-)

Thanks

Simon


Dave Steinberg wrote:
>> Hoping that all pound logs would be directed to a separate file, 
>> however this does not appear to be working. I changed my pound config 
>> to 'daemon' then 'user' but still nothing appearing in /var/log/pound
>
> On my OpenBSD machines, I don't even bother setting a LogFacility in 
> the pound.conf file - I just have the following at the top of my 
> syslog.conf:
>
> !!pound
> *.*                                       /var/log/pound
> !*
>
> Which you already have.  Just to establish that you're doing things 
> right with syslog, be sure:
>
> 1) /var/log/pound exists and is writable
> 2) You've restarted syslogd
>
> If those are true, and you still get nothing in the logs from pound, 
> make a new syslog target like:
>
> *.*         /var/log/all
>
> And see what you get.  For completeness, my pound.conf starts with:
>
> User        "www"
> Group       "www"
> RootJail    "/var/pound"
> Alive       15
> LogLevel    2
> Daemon      0
> Control     "/tmp/pound.sock"
>
> PS - Daemon mode seems to give me some trouble.  Does it work properly 
> for you?
>

This is to announce the release of Pound v2.2.2. Changes in this version
(since 2.2.1):

Enhancements:
  - changes in the dynamic rescaling, hopefully with better results.
  - doubled the session key size (for those people with insanely long
cookies)
  - added "LogFacility -" for logging to stdout/stderr instead of syslog
  - added optional Service names. The names are shown in poundctl output

Bug fixes:
  - fixed bug in multiple HeadRemove matching
  - fixed problem with extra large session keys
  - fixed problem for OpenBSD - a workaround for a possible bug in the
OpenBSD threads library

The software is at version 2.2.2 (beta quality). Further testing
(especially under heavy loads), improvements and suggestions are
welcome.

We have also made a Pound logo available (on the Pound main page) to be
included in your web sites. I'd like to stress that this is a request on
our part, rather than an obligation on yours.
-- 
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-44-920 4904

> This is to announce the release of Pound v2.2.2. Changes in this version
> (since 2.2.1):

Hi Robert, nice work on this release.  Some feedback from my upgrade:

- When not running in daemon mode, if I ctl-c the pound process, I get 
this error:

pid 31756: Fatal error '_thread_tag_init' at line 54 in file 
/usr/src/lib/libpthread/thread/thread_tag.c (errno = 0)

- As before, OpenBSD's 'install' binary doesn't support the -D option.
- I don't seem to get _any_ log output unless I specify 'LogFacility -'. 
  I tried leaving it unset, or setting it as 'LogFacility daemon'.

I'm running a mostly stock OpenBSD 4.0 install on i386, with a threaded 
build of openssl-0.9.8d.

Are there other relevant details I've omitted?

Regards,
-- 
Dave Steinberg
http://www.geekisp.com/
http://www.steinbergcomputing.com/

> This is to announce the release of Pound v2.2.2. Changes in this version
> (since 2.2.1):
>
> Enhancements:
>   - changes in the dynamic rescaling, hopefully with better results.
>   - doubled the session key size (for those people with insanely long
> cookies)
>   - added "LogFacility -" for logging to stdout/stderr instead of syslog

Hi,

Thanks for the new release. Unfortunately with the new code I don't get
anything logged via syslog anymore. Shouldn't the default logging work the
same way than before? I also tried to set "LogFacility daemon" in
pound.cfg with no success. Any ideas?

Thanks,
Simon

My apologies to everybody - it seems some wrong files ended up in the
release (-D flag for install in the Makefile, "LogFacility -" as default
in the man page, opening the syslog). We'll correct this tomorrow and
replace the distribution files.
-- 
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-44-920 4904

Pound 2.2.3 is now released. No new features, just fixes for the botched
2.2.2 release.
-- 
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-44-920 4904

> Pound 2.2.3 is now released. No new features, just fixes for the botched
> 2.2.2 release.

Hi Robert,

It took me some time now to find out why logging to syslog still doesn't
work for me.
Since 2.0-something, logging to syslog was easy even with a RootJail
because syslog has been opened before the chrooting. This breaks now
because pound starts initial logging to stdout and switches to syslog too
late for chrooted configurations.

I added the patch below to my rpms which fixes the issue for me. I
understand that another solution is to make /dev available in the root
jail via tricks like bind mount (at least on Linux) but I prefer to start
loggin to syslog and stop it later if the user wants it.

What do you think?

Simon

--- Pound-2.2.3/pound.c.orig    Fri Jan 19 21:29:10 2007
+++ Pound-2.2.3/pound.c Sat Jan 20 14:55:26 2007
(at)(at) -142,7 +142,7 (at)(at)
     print_log = 0;
     (void)umask(077);
     control_sock = -1;
-    log_facility = -1;
+    log_facility = LOG_DAEMON;
     logmsg(LOG_NOTICE, "starting...");

     signal(SIGTERM, h_term);

On Sat, 2007-01-20 at 15:19 +0100, Simon Matter wrote:
> > Pound 2.2.3 is now released. No new features, just fixes for the botched
> > 2.2.2 release.
> 
> Hi Robert,
> 
> It took me some time now to find out why logging to syslog still doesn't
> work for me.
> Since 2.0-something, logging to syslog was easy even with a RootJail
> because syslog has been opened before the chrooting. This breaks now
> because pound starts initial logging to stdout and switches to syslog too
> late for chrooted configurations.
> 
> I added the patch below to my rpms which fixes the issue for me. I
> understand that another solution is to make /dev available in the root
> jail via tricks like bind mount (at least on Linux) but I prefer to start
> loggin to syslog and stop it later if the user wants it.
> 
> What do you think?
> 
> Simon
> 
> --- Pound-2.2.3/pound.c.orig    Fri Jan 19 21:29:10 2007
> +++ Pound-2.2.3/pound.c Sat Jan 20 14:55:26 2007
> (at)(at) -142,7 +142,7 (at)(at)
>      print_log = 0;
>      (void)umask(077);
>      control_sock = -1;
> -    log_facility = -1;
> +    log_facility = LOG_DAEMON;
>      logmsg(LOG_NOTICE, "starting...");
> 
>      signal(SIGTERM, h_term);

Not really. What you probably want is

	openlog("pound", LOG_CONS | LOG_NDELAY, LOG_DAEMON);

The LOG_NDELAY will force the opening of the device early.
-- 
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-44-920 4904

> On Sat, 2007-01-20 at 15:19 +0100, Simon Matter wrote:
>> > Pound 2.2.3 is now released. No new features, just fixes for the
>> botched
>> > 2.2.2 release.
>>
>> Hi Robert,
>>
>> It took me some time now to find out why logging to syslog still doesn't
>> work for me.
>> Since 2.0-something, logging to syslog was easy even with a RootJail
>> because syslog has been opened before the chrooting. This breaks now
>> because pound starts initial logging to stdout and switches to syslog
>> too
>> late for chrooted configurations.
>>
>> I added the patch below to my rpms which fixes the issue for me. I
>> understand that another solution is to make /dev available in the root
>> jail via tricks like bind mount (at least on Linux) but I prefer to
>> start
>> loggin to syslog and stop it later if the user wants it.
>>
>> What do you think?
>>
>> Simon
>>
>> --- Pound-2.2.3/pound.c.orig    Fri Jan 19 21:29:10 2007
>> +++ Pound-2.2.3/pound.c Sat Jan 20 14:55:26 2007
>> (at)(at) -142,7 +142,7 (at)(at)
>>      print_log = 0;
>>      (void)umask(077);
>>      control_sock = -1;
>> -    log_facility = -1;
>> +    log_facility = LOG_DAEMON;
>>      logmsg(LOG_NOTICE, "starting...");
>>
>>      signal(SIGTERM, h_term);
>
> Not really. What you probably want is
>
> 	openlog("pound", LOG_CONS | LOG_NDELAY, LOG_DAEMON);
>
> The LOG_NDELAY will force the opening of the device early.

Thanks, I just tried it and it fixes the problem.

Simon

On Jan 19, 2007, at 1:25 PM, Robert Segall wrote:

> Pound 2.2.3 is now released. No new features, just fixes for the  
> botched
> 2.2.2 release.

The website still only shows 2.2.2

-Blake