There had been bugs with respect to the time zone in older versions. Anything better than 4.1.24 should work fine. I hadn't heard of bugs with respect to a bug in the timezone offset with respect to the common format. What is your timezone? (Wondering if that has anything to do with it.)

If all else fails, do this before passing the file to Analog. Since the + is also required. (IIRC)

perl -pi -e 's/00\[/+0000]/' logfile.txt

-Tim

Paul Wallace wrote:
Thanks for that,
That is an option. Although theoretically I should not need to
do this. My local development installation (4.0.4) with server.xml using
a 'common' pattern, is outputting the date/time/zone log file entries in
a format that Analog WILL process ([01/Jul/2003:17:00:03 10000]). But my
production instance (4.0.4), is outputting the zone in a format that
will not - [01/Jul/2003:17:00:03 00]. Both AccessLogvalve patterns are
'common'. Perhaps it is a locale zone setting?


Thanks



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to