To add new top-level domains to http-analyze, just install an up-to-date TLD file. Since release of http-analyze 2.4, some country domains have been changed and the new generic top-level-domains .asia, .tel and .travel have been added. See our List of Top-Level-Domains for more information.


The developement of http-analyze started in 1996 as a statistics tool for the former website, which was built by RENT-A-GURU™. Since other partners and customers also requested a server statistics tool, the first public version of http-analyze numbered 1.9 appeared in early 1997 and has been replaced since then by 2.5 today. http-analyze reached a high quality standard and reliable long-term operation on servers with just one website as well as on huge website farms.

Page: « 1 2 3 4 »

Error messages FAQ

  1. I could install the analyzer on my Linux system, but if I try to execute it, the shell responds with not found. However, a ls shows that the file exists and has execution permissions set. What's going wrong?
    You are probably using an older version of http-analyze, which has been linked against an out-of-date C library. Please download the latest version of the software.
  2. Why does http-analyze print the warning message "Frames creation disabled due to missing buttons"?
    Did you install http-analyze in the default locations or otherwise did you use the environment variable HA_LIBDIR to tell http-analyze about customized location of the required support files? http-analyze needs certain button and image files which are usually located under /usr/local/lib/http-analyze/btn. They are installed in the statistics (output) directory of a web server by http-analyze automatically when the logfile for this server is being analyzed the first time.
  3. I am getting the error message "Invalid timestamp detected in line ...". What does this mean?
    This is caused by timestamps found in some Netscape Enterprise servers which feature the coolest invention since computers exist: They invented the 25th hour! Therefore, those servers can serve documents one hour longer per day than any other web server without generating additional costs! This is an excerpt from the logfile of such a server:
    xx - - [01/Sep/2007:24:17:04 +0200] "GET /foo HTTP/1.1" 200 8943
    xx - - [01/Sep/2007:24:17:27 +0200] "GET /bar HTTP/1.1" 200 2094
    xx - - [01/Sep/2007:00:17:26 +0200] "GET /foo HTTP/1.1" 200 8943
    xx - - [01/Sep/2007:24:17:38 +0200] "GET /bum HTTP/1.1" 200 1207
  4. The analyzer reports "No hits at all?!?", but if I look at the logfile, there are indeed a lot of entries.
    Did you restrict the analysis in some way using the IgnURL, IgnSite or DocRoot directive in the configuration file? If the latter, did you define an absolute pathname for the DocRoot parameter? It should be an URL just as it appears in the request (as for example, in GET /customer/) if (and only if) you want to restrict analysis to this part of your server. DocRoot should be left undefined to generate statistics for the whole server.
  5. When I execute http-analyze I receive the error message "Not enough memory -- need 50 more bytes" and the analyzer terminates. What can I do to avoid this?
    If your system does not support swapping/paging, you may need a fair amount of physical memory when processing huge logfiles. Either try to suppress some detailed lists from the report or run the analyzer on another system with enough (virtual) memory. In case of HP/UX, increase the stack and data regions for processes in the kernel's system tuning parameter table.

Page: « 1 2 3 4 »
Next: Statistics report FAQ

Copyright © 1996-2018 by RENT-A-GURU™