gauze(at)dropdead.org wrote:[...]

I am not receiving duplicates.

On Thu, 7 Jul 2005 17:20:29 +0200 Ximon Eighteen
<ximon.eighteen(at)int.greenpeace.org> wrote:
[...]

The accepted method is to run ident on the Pound binary (or strings as
you did). There is no runtime flag.[...]

> Am I missing something here?

Well, at least one thing. I neglected to say that I've never had any problems 
running Pound and fully intend to continue using it. Sorry for the tone of my 
posts, it's been a long frustrating day (for non Pound reasons of course :D).

X

On Thu, 7 Jul 2005 17:25:08 +0200 Ximon Eighteen
<ximon.eighteen(at)int.greenpeace.org> wrote:
[...]

Funny, just to make sure I tested 1.9 again and it definitely refuses to
run with wrong arguments...[...]

Hi James,
[...]

Not exactly, but I/we just don't understand what you're talking about.
What do IIS logs and COM components have to do with Pound?

Cheers, Chris.[...]

Chris,
there is life out there... thanks for the reply.  OK to summarise the
previous three mails:
As far as I can see in /var/logs/messages pound logs stuff about
exceptions and starting and stopping, but it doesn't log web requests.
It seems to me (happy to be corrected on any of this..) that it sends
this x-forwarded-client header to the backends where the web requests
are logged.  This is fine with apache etc where you can log these
custom headers. IIS does not log custom headers unless you write code
to log them (enter the COM objects), or buy a third party logging app.
I'd be happy as a clam if I'm wrong and someone could say "Oh no you
just do <this> and you get web logs" but as far as I can see if you
use IIS and pound you can't get standard web logs.
Looking forward to your view.
cheers
JMB

On 7/8/05, James Billson <james.billson(at)gmail.com> wrote:[...]

[...]

Hi James,

Pound logs the following for me:

Jul  3 04:02:12 www3 pound: 217.14.134.36 GET
/testpages/www.google.co.uk.html HTTP/1.1 - HTTP/1.1 200 OK

This looks like an Apache log entry with a syslog header prepended. You
could strip off the syslog header with a simple perl script.

If you don't see these, reconfigure your syslogd to send all messages
from pound (including debug level) into a separate file like
/var/log/pound.

Sorry I have no idea about making IIS log the forwarded-for header, but
if it doesn't then it's fundamentally incompatible with any kind of
standard reverse proxy, which seems unlikely.

Hope this helps,

Cheers, Chris.

On Fri, 2005-07-08 at 11:55, James Billson wrote:[...][...]

Hi Chris,

IIS won't do what you would like it to right off-the-shelf.  You will 
need to do at least one of the following:

1. obtain a third-party logging plugin for IIS that understands the header.

2.  use apache rather than IIS

3.   ignore the IIS server logs, and use pounds at the load balancer. 
Logging from pound should save you from having to later combine log 
reports from all of your backend servers.

Note to all:  If anyone can tell me how to get syslogd to send messages 
from pound to another file, under stock redhat 9, I'd be *really* 
thankful.  Try as I may, I can't get it to work.

Thanks,
Ed

Chris Wilson wrote:
[...][...]
>>>there is life out there... thanks for the reply.  OK to summarise
the
>>>previous three mails:
>>>As far as I can see in /var/logs/messages pound logs stuff about
>>>exceptions and starting and stopping, but it doesn't log web
requests.
>>>It seems to me (happy to be corrected on any of this..) that it
sends
>>>this x-forwarded-client header to the backends where the web
requests
>>>are logged.  This is fine with apache etc where you can log these
>>>custom headers. IIS does not log custom headers unless you write
code
>>>to log them (enter the COM objects), or buy a third party logging
app.
>>>I'd be happy as a clam if I'm wrong and someone could say "Oh no
you
>>>just do <this> and you get web logs" but as far as I can see
if you
>>>use IIS and pound you can't get standard web logs.
>>>Looking forward to your view.
>>>cheers
>>>JMB
>>>
>>>On 7/8/05, Chris Wilson <chris(at)aidworld.org> wrote:
>>>
>>>>Hi James,
>>>>
>>>>
>>>>>Are my mails not getting through, or does this list not
want to discuss
>>>>>matters relating to Pound over IIS?
>>>>
>>>>Not exactly, but I/we just don't understand what you're talking
about.
>>>>What do IIS logs and COM components have to do with Pound?
>>>>
>>>>Cheers, Chris.
>>>>--
>>>>(aidworld) chris wilson | chief engineer
(chris(at)aidworld.org)
>>>>
>>>>
>>>>--
>>>>To unsubscribe send an email with subject 'unsubscribe' to
pound(at)apsis.ch.
>>>>Please contact roseg(at)apsis.ch for questions.
>>>>http://192.168.1.2:8080/Apsis/pound/pound_list/archive/2005/2005-07/1120582038000/1120813247000
>>>>
>>>
>>>
>>>--
>>>James Billson, james.billson(at)cim.com.au
>>>Managing Director
>>>Commercial Interactive Media (CIM) - www.cim.com.au
>>>Delivering smart e-solutions for real business
>>>Tel: + 61 3 9419 4900
>>>Fax: + 61 3 9419 4149
>>>
>>>The information contained in this email message may be
confidential, and
>>>may also be the subject of privileged or public interest immunity.
If you
>>>are not the intended recipient, any use, disclosure or reproduction
of this
>>>document is unauthorised. If you have received this email in error,
please
>>>notify me by email. Before opening or using attachments, check them
for
>>>viruses and defects. Our liability is limited to resupplying any
affected
>>>attachments.
>>>[...]

On Fri, 08 Jul 2005 08:14:34 -0400 Ed R Zahurak
<ezahurak(at)atlanticbb.net> wrote:
[...]

Configure Pound so that it logs to local7 (this is just an example,
use whatever fits your needs):

./configure --with-log=LOG_LOCAL7

Compile, install.

Modify your /etc/syslog.conf to include:

local7.=info        /var/log/pound.log
local7.notice      /var/log/pound.err

Also make sure your messages do NOT go anywhere else (search for .none,
add local7 as needed). Restart the syslogd. From now on the traffic (aka
log) messages go to /var/log/pound.log, everything else goes to
/var/log/pound.err

Rotating the log files is left as an exercise to the interested
reader...[...]

Chris,

On 7/8/05, Chris Wilson <chris(at)aidworld.org> wrote:[...]

I think this then is the root of my problem.  I was expecting what you
describe, instead I get:

lb# cd /var/log/
lb# tail -f messages
Jul  9 06:01:39 lb pound: BackEnd 203.32.143.32 resurrect
Jul  9 06:12:08 lb pound: bad header from 203.32.143.149
(---------------: ------------)
Jul  9 06:12:09 lb last message repeated 8 times
Jul  9 06:15:54 lb pound: bad header from 203.32.143.133
(---------------: ------------)
Jul  9 06:16:04 lb last message repeated 20 times
Jul  9 06:29:31 lb pound: BackEnd 203.32.143.32 is dead
Jul  9 06:30:11 lb pound: BackEnd 203.32.143.32 resurrect

I don't get as many bad header messages as there are web accesses, but
as you can see I get plenty.  This is at log level 3 and 4.

System is running on FreeBSD 4.4 (I think - at least that's what's in
the /COPYRIGHT file)
Am I looking in the wrong place?
thanks
JMB

Hi James,

Make sure you are not discarding messages at LOG_INFO priority in your
syslog configuration. You may also want to turn up the logging level
(LogLevel directive in configuration file) to level 3 or 4, to get more
detailed logs. You will probably still have to massage them to get them
into something like Apache log format.

Cheers, Chris.

On Fri, 2005-07-08 at 15:18, James Billson wrote:[...][...]

On Sun, 2005-07-10 at 16:00 +0200, Arkadiusz Patyk wrote:[...]

You can check the SERVER_PORT apache variable; I have this line in
httpd.conf to simulate how mod_ssl sets the HTTPS variable too:

SetEnvIf SERVER_PORT "443" HTTPS=on
[...]

On Sun, 10 Jul 2005 16:00:19 +0200 Arkadiusz Patyk <areq(at)areq.eu.org>
wrote:
[...]

See HTTPSHeaders in the man page.[...]

On Thu, 14 Jul 2005 15:11:39 +0200 Lukasz 'LCF' Jagiello
<lukasz.jagiello(at)zjednoczenie.com> wrote:
[...]

Have the back-end server log the address(es) in X-Forwarded-for rather
than originating address. How you do that depends very much on your
server - each one is different...[...]