![]() Tue Mar 7 11:18:29 2006 - DEBUG 1 - Call to Read_Plugins with list: Tue Mar 7 11:18:29 2006 - DEBUG 1 - Call to Read_Ref_Data Tue Mar 7 11:18:29 2006 - DEBUG 1 - Call to Read_Ref_Data with files to load: status_http.pm,search_engines.pm,domains.pm,operating_systems.pm,robots.pm,browsers.pm,mime.pm Tue Mar 7 11:18:29 2006 - DEBUG 1 - Call to Read_Language_Data Tue Mar 7 11:18:29 2006 - DEBUG 1 - Call to Check_Config Tue Mar 7 11:18:29 2006 - DEBUG 1 - Config file read was "/*/typo3conf/ext/cc_awstats/awstats/nf" (level 1) This debug information may help to find the reason. There was something wrong with the call of the AWStats script! Setup ('/*/typo3conf/ext/cc_awstats/awstats/nf' file, web server or permissions) may be wrong.Ĭheck config file, permissions and AWStats documentation (in 'docs' directory). This means each line in your web server log file need to have "combined log format" like this:ġ11.22.33.44 - "GET / HTTP/1.1" 200 1234 "" "Mozilla/4.0 (compatible MSIE 5.01 Windows NT 5.0)"Īnd this is an example of records AWStats found in your log file (the record number 50 in your log):Ħ8.142.250.49 - "GET /index.php?idcatside=87 HTTP/1.0" 200 33823 Your log file /*/fileadmin/logfile.txt must have a bad format or LogFormat parameter setup does not match this format. hoffentlich hilft das weiter :)ĪWStats did not find any valid log lines that match your LogFormat parameter, in the 50th first non commented lines read of your log. It may also lead to a situation when requests partially matching the regex pattern are incorrectly routed to this location.Īlways use ^ or $ achor in a regex pattern.Ich habe jetzt die access_log manuell über das logfile von awstats kopiert.īeim aktualisieren kommt nun folgender fehler. This is a configuration style that is prone to errors. Regex location has a regex pattern without ^ or $. "Regex location has no anchors in regex pattern Please refer to the documentation describing location directive to learn more." Performance-wise it is more efficient to configure exact or prefix matching for locations that do not require regex matching. Regex location has a valid modifier, but does not have a regex pattern. My nginx config analysis warns that the prescribed replacement:ĭoes not have an ideal regex pattern. ![]() Regenerate web-server configuration files: Try_files $uri $uri/ /index.php$is_args$args ![]() Index index.php index.cgi index.html index.xhtml index.htm index.shtml Index quote($VAR->domain->physicalHosting->directoryIndex)?> ĬONFIG_TEXT: domain->physicalHosting->directoryIndex & !$VAR->domain->physicalHosting->proxySettings): ?> Open the file /usr/local/psa/admin/conf/templates/custom/domain/nginxDomainVirtualHost.php in any text editor (for example, with vi editor) and replace the section:ĬONFIG_TEXT: domain->physicalHosting->directoryIndex): ?> Note: Any changes made in original configuration templates will be lost after an installation of Plesk micro-updates. # cp /usr/local/psa/admin/conf/templates/default/domain/nginxDomainVirtualHost.php /usr/local/psa/admin/conf/templates/custom/domain/nginxDomainVirtualHost.php # mkdir -p /usr/local/psa/admin/conf/templates/custom/domain Create a directory for custom templates and copy default configuration templates there:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |