Hi,

I have just realized that one of my pound proxies stopped logging request
while still serving them without any problem. The last logged entry was
from 13:05:54, now I restarted pound and it also started logging requests
again. This is on RedHat 7.3, pound 1.5.
Although it doesn't hurt too much, I'd like to know what could be wrong
here. Any ideas?

Regards,
Simon

/var/log/messages:
--------------------------------------------------------------------
Oct 20 13:05:53 xx-01 pound: 10.206.217.62 GET
/webmail/themes/css/sans-10.css HTTP/1.1 - HTTP/1.1 200 OK (10.1.6.25:80)
Oct 20 13:05:54 xx-01 pound: 10.10.4.244 GET
/webmail/plugins/archive_mail/includes/display_inside.php HTTP/1.1 -
HTTP/1.1 200 OK (10.1.6.25:80)
Oct 20 21:18:52 xx-01 sshd(pam_unix)[5193]: session opened for user root
by (uid=0)
Oct 20 21:19:54 xx-01 pound: received signal 15 - exiting...
Oct 20 21:20:59 xx-01 pound: starting...
Oct 20 21:20:59 xx-01 pound: pound startup succeeded
Oct 20 21:21:11 xx-01 pound: 10.161.34.15 GET /webmail/src/left_main.php
HTTP/1.1 - HTTP/1.1 200 OK (10.1.6.25:80)
Oct 20 21:21:12 xx-01 pound: 10.161.34.15 GET
/webmail/themes/css/invoca-10.css HTTP/1.1 - HTTP/1.1 200 OK
(10.1.6.25:80)

Hello!

Am Montag, 20. Oktober 2003 21:36 schrieb Simon Matter:[...]

Pound is running chrooted (RootJail)? Make sure that there is a directoy 
"/dev" and a socket file called "log" in your RootJail. If you're using the 
standard syslog daemon this can achieved by starting the syslogd with the 
"-a" option.

  syslogd -a <rootjaildir>/dev/log


man 8 syslogd

       -a socket
              Using this argument you can specify additional sockets from that
              syslogd has to listen to.   This  is  needed  if you're  going
              to let some daemon run within a chroot() environment.  You can
              use up to 19 additional sockets.  If your environment needs even
              more, you have to increase the symbol MAXFUNIX within the
              syslogd.c source file.   An example  for a chroot() daemon is
              described by the people from OpenBSD at
              http://www.psionic.com/papers/dns.html.


Andi

> Hello![...][...][...]

You are right, my pound is running chrooted. But why does it work for some
time and suddenly stop?
And, is there no other way to solve this problem. I'm maintaining rpm
packages for pound and it was certainly easier if the syslog configuration
could remain as it is.

Simon
[...]

Hello!

Am Montag, 20. Oktober 2003 23:26 schrieb Simon Matter:[...]

As soon as pound is started, it can only "see" the root jail environment. But 
sometimes (in certain situations), Pound (rather the GNU C Library) has to 
reopen the /dev/log socket. You can create a hard link from /dev/log to the 
/dev/log in your root jail. Have a look at the Pound website.


Andi