bcrawley01
asked on
Apache weblog status %>s issue
Hi,
Our Apache web server has been configured so the web logs capture the last status by using the directive %>s however this is producing the following in the log file ???>???s instead of the last correct status number.
Does anyone know why this occurs and how it can be fixed?
Thanks.
Our Apache web server has been configured so the web logs capture the last status by using the directive %>s however this is producing the following in the log file ???>???s instead of the last correct status number.
Does anyone know why this occurs and how it can be fixed?
Thanks.
Richard Quadling
Can you show your entire LogFormat please?
ASKER
LogFormat "%h %v %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" \"%{Cookie}i\""
Can you try %s to make sure that at least this is working? The original status will be logged rather than the last status.
Can you do a hex dump of the log file to see exactly what is ???>???s is.
Hmmm.
OOI, Can you try looking at the file containing this logformat in hex mode?
Have you used 16bit UTF format?
25 00 3E 00 73 for the %>s but as %\000>\000s in 8bit mode.
Almost certain this is the issue.
If you view the log file in hex mode, you should probably see that the ??? is really 00 - a null.
Can you do a hex dump of the log file to see exactly what is ???>???s is.
Hmmm.
OOI, Can you try looking at the file containing this logformat in hex mode?
Have you used 16bit UTF format?
25 00 3E 00 73 for the %>s but as %\000>\000s in 8bit mode.
Almost certain this is the issue.
If you view the log file in hex mode, you should probably see that the ??? is really 00 - a null.
ASKER
%s does work and is logging the original status.
When opening the log file in hex, ???>???s is 3F 3F 3F 3E 3F 3F 3F 73
When opening the log file in hex, ???>???s is 3F 3F 3F 3E 3F 3F 3F 73
Hmm. That's odd.
Really was expecting that to be the tool that displayed the log showing NULLs as ???
Can you put the > back into the log format and do a hex on that.
Really was expecting that to be the tool that displayed the log showing NULLs as ???
Can you put the > back into the log format and do a hex on that.
ASKER
That before was with the > added.
Yes. But I'm wondering if the editing of the logformat is the issue. Can you show the hex of the file with the logformat in it, not the log file itself.
Whilst it is not likely, but if the logformat is corrupted with nulls (16bit UTF rather than 8bit), then the leading null bytes _COULD_ be shown as ??? and depending upon how the translation is done from logformat to log file, ...
Sort of clutching at straws...
Can you attach the file with the logformat to this question?
Whilst it is not likely, but if the logformat is corrupted with nulls (16bit UTF rather than 8bit), then the leading null bytes _COULD_ be shown as ??? and depending upon how the translation is done from logformat to log file, ...
Sort of clutching at straws...
Can you attach the file with the logformat to this question?
ASKER
Log format file is attached.
server.xml
server.xml
As the file is XML, I wonder if %> is getting in the way somehow.
Is the remainder of the log entry exist?
Is the remainder of the log entry exist?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
So, \" => " was the issue?
Ha! A million ways to escape and URLencoding never occurred to me.
Ha! A million ways to escape and URLencoding never occurred to me.