Frequently Asked Questions

The NearlyFreeSpeech.NET FAQ (*)

Log Files (*)

What is the easiest way to make sense of my log files?

Do my site's log files count as space usage for billing purposes?

I've enabled log files, now where are they?

What are log files and how are they used?

My log file is huge and I can't remove it. What do I do?

How does log rotation work?

How do I enable my log files?

Why aren't log files enabled by default?

The return code 304 shows up in my log files all the time. What is it?

How come the bytes in my site's access log file do not match the site's actual traffic?

How many old log files will be kept during log rotation?

What are each of the fields in the access log?

I rotated my log files, but the access_log.old file was not compressed. Why not?

The .old log files are never automatically compressed. If you rotate again, it will be renamed based on its last-modified date and only then will it be automatically compressed.

This is for two reasons. First, log entries come from many different parts of our network so there needs to be a "cooling off" period after rotating to make sure all parts of the network have switched to the new log. Otherwise, stuff might still be logged while compression is happening, and it would get lost.

Also, many people like to run analysis against a static log file. That way, if you change an analyzer setting and run it again, or if you want to do more than one thing to the log, you're working with a consistent set of logs. After log files are compressed, they're a lot harder to analyze, so keeping the .old file around often makes log analyzing much easier.

You're free to remove the .old log file yourself if you like, although we recommend waiting until you see log entries appearing in the new log file. If you rename or compress it yourself, it will not be auto-rotated in the future.

What is the format of the error log?

What happens if I change log file compression techniques?