From: eldy <> Date: Sat, 16 Feb 2002 15:00:15 +0000 (+0000) Subject: no message X-Git-Tag: AWSTATS_4_0_BETA~108 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=0a004017abcff8ea655c0b41ed49e08d1c52cc71;p=thirdparty%2FAWStats.git no message --- diff --git a/docs/awstats_faq.html b/docs/awstats_faq.html index 8e9bc27a..8016d2a4 100644 --- a/docs/awstats_faq.html +++ b/docs/awstats_faq.html @@ -51,11 +51,12 @@ FAQ-SET050 Error "Missing $ on loop variable ..."I see Perl script's source instead of its execution in my browser.
FAQ-SET150 Error "... couldn't spawn child process..." with Apache for windows.
FAQ-SET200 "Internal Error" or "Error 500" in a browser connecting to Apache.
-FAQ-SET250 "Internal Error" after a long time in my browser (See FAQ-COM100 "AWStats speed/timeout problems").
+FAQ-SET210 "Internal Error" after a long time in my browser (See FAQ-COM100 "AWStats speed/timeout problems").
+FAQ-SET250 Log format setup or errors.
+FAQ-SET260 Setup for FTP server log files.
+FAQ-SET280 Error "Not same number of records of...".
FAQ-SET300 Error "Couldn't open file ..."
FAQ-SET350 Empty or null statistics reported.
-FAQ-SET400 Log format setup or errors.
-FAQ-SET420 Setup for FTP server log files.
FAQ-SET450 No pictures/graphics shown.
FAQ-SET500 Frequency to launch AWStats to update statistics (See FAQ-COM150 "Benchmark question").
FAQ-SET550 How can i run AWStats frequently ?
@@ -204,51 +205,8 @@ Then restart Apache. This will tell Apache to use the program associated to .pl to find the perl interpreter.

-
-FAQ-SET300 : ERROR "COULDN'T OPEN FILE ..."
-PROBLEM: I have the following error:
-"Couldn't open file /workingpath/awstatsmmyyyy.tmp.9999: Permission denied."
-SOLUTION: This error means that the web server -didn't succeed in writing the working temporary file (file ended by .tmp.9999 -where 9999 is a number) because of permissions problems.
-First check that the directory /workingpath has write permission for
-user nobody (default used user by apache on linux systems)
-or user IUSR_SERVERNAME (default used user by IIS on NT).
-With Unix, try with a path with no links.
-With NT, you must check NTFS permissions if your directory is on a NTFS partition.
-With IIS, there is also a write permission attribute, defined in directory properties -in your IIS setup, that you must check.
-With IIS, if a default cgi-bin directory was created during IIS install, try to -put AWStats directly this directory.
-If this still doesn't work, you can change the DirData parameter to say AWStats -that you want to use another directory (A directory you are sure that the default -user, used by web server process, can write into).
-
- -
-FAQ-SET350 : EMPTY OR NULL STATISTICS REPORTED
-PROBLEM: Awstats seems to work but i'm not -getting any results. i get a statistics page that looks like i have no hits.
-SOLUTION: That's the most common problem you -can have and reason is simple: Your log file format setup is wrong.
-If you use Apache web server
-The best way of working is to use the "combined" log format (See into the README.TXT file -to know the way to change your apache server log from "common" log format into "combined"). -Don't forget to stop apache, reset your log file and restart Apache to make change into combined -effective. Then you must setup your AWStats config file with value LogFormat=1.
-If you want to use another format, read the next FAQ to have examples of LogFile value according -to log files format.
-If you use IIS server or Windows built-in web server
-The Internet Information Server default W3C Extended Log Format will not work correctly with AWStats. -To make it work correctly, start the IIS Snap-in, select the web site and look at it's Properties. -Choose W3C Extended Log Format, then Properties, then the Tab Extended Properties and uncheck everything -under Extended Properties. Once they are all unchecked, check off the list in the ReadMe file in the -IIS section, "With IIS Server". -You can also read the next FAQ to have examples of LogFormat value according to log files format.
-
-
-FAQ-SET400 : LOG FORMAT SETUP OR ERRORS
+FAQ-SET250 : LOG FORMAT SETUP OR ERRORS
PROBLEM: Which value do I have to put in the LogFormat parameter to make AWStats working with my log file format ?
SOLUTION: @@ -299,7 +257,7 @@ support other various log formats.


-FAQ-SET420 : SETUP FOR FTP SERVER LOG FILES
+FAQ-SET260 : SETUP FOR FTP SERVER LOG FILES
PROBLEM: What do I have to do to use Awstats to analyze some FTP server log files.
SOLUTION: AWStats was built to analyze web,wap or proxy servers log files. However it can be used with some FTP server log files.
@@ -316,6 +274,65 @@ LogFormat="%time1 %host %logname %method %url %code %bytesd"
DNSLookup=0
ShowLinksOnUrl=0
ShowAuthenticatedUsers=1
+Warning: This tip doesn't work for FTPed files that contains spaces in them (they are not reported). You can still convert your +log file to replace 'space' char into '_'...
+
+ +
+FAQ-SET280 : ERROR "NOT SAME NUMBER OF RECORDS OF..."
+PROBLEM: When I run AWStats from command line (or as a cgi from a browser), I get +a message "Not same number of records of ...".
+SOLUTION: +This means your AWStats reference database files (operating systems, browsers, robots...) are not correct. +Check in your disk that you have only ONE of those files (They should be in 'db' directory where awstats.pl is installed):
+browsers.pl
+operating_systems.pl
+robots.pl
+domains.pl
+search_engines.pl
+
+ +
+FAQ-SET300 : ERROR "COULDN'T OPEN FILE ..."
+PROBLEM: I have the following error:
+"Couldn't open file /workingpath/awstatsmmyyyy.tmp.9999: Permission denied."
+SOLUTION: This error means that the web server +didn't succeed in writing the working temporary file (file ended by .tmp.9999 +where 9999 is a number) because of permissions problems.
+First check that the directory /workingpath has write permission for
+user nobody (default used user by apache on linux systems)
+or user IUSR_SERVERNAME (default used user by IIS on NT).
+With Unix, try with a path with no links.
+With NT, you must check NTFS permissions if your directory is on a NTFS partition.
+With IIS, there is also a write permission attribute, defined in directory properties +in your IIS setup, that you must check.
+With IIS, if a default cgi-bin directory was created during IIS install, try to +put AWStats directly this directory.
+If this still doesn't work, you can change the DirData parameter to say AWStats +that you want to use another directory (A directory you are sure that the default +user, used by web server process, can write into).
+
+ +
+FAQ-SET350 : EMPTY OR NULL STATISTICS REPORTED
+PROBLEM: Awstats seems to work but i'm not +getting any results. i get a statistics page that looks like i have no hits.
+SOLUTION: That's the most common problem you +can have and reason is simple: Your log file format setup is wrong.
+If you use Apache web server
+The best way of working is to use the "combined" log format (See into the README.TXT file +to know the way to change your apache server log from "common" log format into "combined"). +Don't forget to stop apache, reset your log file and restart Apache to make change into combined +effective. Then you must setup your AWStats config file with value LogFormat=1.
+If you want to use another format, read the next FAQ to have examples of LogFile value according +to log files format.
+If you use IIS server or Windows built-in web server
+The Internet Information Server default W3C Extended Log Format will not work correctly with AWStats. +To make it work correctly, start the IIS Snap-in, select the web site and look at it's Properties. +Choose W3C Extended Log Format, then Properties, then the Tab Extended Properties and uncheck everything +under Extended Properties. Once they are all unchecked, check off the list in the ReadMe file in the +IIS section, "With IIS Server". +You can also read the next FAQ to have examples of LogFormat value according to log files format.