trafficserver-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeremy Utley <>
Subject Problems with Squid format logging
Date Thu, 14 Jun 2012 19:37:21 GMT
Good afternoon everyone!

We're having some issues with Traffic server's squid format log files,
and I'm wondering if anyone else has ever encountered this type of
situation yet.  First off, a little background on how we have things
set up:

We're running trafficserver 3.0.4 on CentOS 6.2 installed from the
RPMs in the Redhat EPEL repository.  TS is running on the firewall for
our office, acting as a transparent proxy.  IPTables is intercepting
all outbound http traffic and redirecting it at trafficserver
listening on port 8080:

[0:0] -A PREROUTING -m state --state NEW,ESTABLISHED,RELATED -m tcp -s
192.168.x.y/255.255.x.y -p tcp --dport 80 -j REDIRECT --to-port 8080

This was to replace an existing squid setup that wasn't performing
quite as well as we'd like, and functionally, it's been working great
for over a week now.

However, when we were using squid, we also had the program "sarg" (1)
doing a daily analysis of our squid logs.  So I thought, no problem,
TS has the capability to write logfiles in squid format, we can just
use sarg against those logs and continue on as normal.  However, that
is not working.  SARG keeps bailing on what looks to be invalid lines
in the log files generated by traffic server.  A sample of one of
those lines as displayed by "less squid.log" is shown below:

1339592276.829 40 192.168.x.y TCP_MISS/200 1032 GET http:///_tp/js/JSONRequest.
js - DIRECT/ application/x-javascript -
INVALID_CODE(45)/1 - text/html

Also of note, the "hex" characters within <> is hilited when looking
at it in less.

Has anyone ever seen output like this from the squid format logs
generated by traffic server?  Any way to solve this problem?

Thanks for any help anyone can give!

Jeremy Utley

View raw message