Mantis - Resin
Viewing Issue Advanced Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1449 minor always 11-08-06 11:45 11-29-06 11:53
Reporter: sam Platform:  
Assigned To: ferg OS:  
Priority: normal OS Version:  
Status: closed Product Version: 3.0.21  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 3.1.0  
Summary: 0001449: incorrect newline in access log
Description: (rep by C Head)

Most of our access log lines end with \r\n, but occasionally there is a line ending with just \n, and our log analysis tool is not coping well.
Steps To Reproduce:
Additional Information:
Relationships
Attached Files:

Notes
(0001579)
ChrisH   
11-08-06 12:50   
Sam,

The files that I sent you were straight from the Resin software and were not combined or converted in any ways so they are exactly as resin produced them. The servers are running Resin 3.0.21 and yes they are windows servers. I am not sure about how the code is producing the log files but they are being created that way as I have viewed the files using a GUI editor as well as using vi on a linux box and getting the exact same results. If there is any other information that I can provide please let me know as this is a large issue for us and our customers as they are unable to effectively track their SEO budgets without this information.

Thanks for all your assistance.
(0001583)
ChrisH   
11-10-06 08:16   
Sam,

Any update on this issue as I am getting pressed several times a day on it. If there is any other support avenue that we need to take with this please let me know as I need something to present to the customers and the owner.

Thanks
Chris Head
(0001584)
ChrisH   
11-10-06 11:45   
Sam,

Any update on this issue as I am getting pressed several times a day on it. If there is any other support avenue that we need to take with this please let me know as I need something to present to the customers and the owner.

Thanks
Chris Head
(0001586)
sam   
11-14-06 06:34   
Confirmed, occurs one time in an log file with 291,544 lines.
(0001591)
ChrisH   
11-20-06 07:08   
Sam, any update on this issue?
(0001594)
sam   
11-20-06 10:37   
As a workaround until this bug can be confirmend and fixed, one can strip all
of the \r characters from the access log files before there are given to
analysis tools.

In unix:

$ cat access.log | tr -d '\r' > access_fixed.log
(0001595)
ChrisH   
11-20-06 10:55   
Sam, How will this cause the referring url to show in the correct line as opposed to a seperate line as it is most of the time and thusly not showing up in the tracking software as was stated in the original issue. Thanks for your assistance
(0001616)
ferg   
11-29-06 11:53   
The getNewline() needs to check for windows if the getProperty("line.separator") fails.