I'm experiancing different results when the cron is being run from directadmin and when the cron is manually ran.
For instance the below cron was ran last night from DirectAdmin as admin:
Running '"/usr/local/directadmin/plugins/awstats/hooks/cgi-bin/awstats.pl" -update -config=abc.com -configdir="/etc/awstats"' to update config abc.com
Update for config "/etc/awstats/awstats.abc.com.conf"
With data in log file "/var/log/httpd/domains/abc.com.log"...
Phase 1 : First bypass old records, searching new record...
Direct access to last remembered record is out of file.
So searching it from beginning of log file...
Phase 2 : Now process new records (Flush history on disk after 20000 hosts)...
Jumped lines in file: 0
Parsed lines in file: 15
Found 0 dropped records,
Found 0 corrupted records,
Found 0 old records,
Found 15 new qualified records.
Now when running from admin manually through either ssh or the direct "update" through awstats the follwing results occur:
Running '"/usr/local/directadmin/plugins/awstats/hooks/cgi-bin/awstats.pl" -update -config=abc.com -configdir="/etc/awstats"' to update config abc.com
Update for config "/etc/awstats/awstats.abc.com.conf"
With data in log file "/var/log/httpd/domains/abc.com.log"...
Phase 1 : First bypass old records, searching new record...
Direct access after last parsed record (after line 15)
Jumped lines in file: 15
Found 15 already parsed records.
Parsed lines in file: 629
Found 0 dropped records,
Found 0 corrupted records,
Found 0 old records,
Found 629 new qualified records.
You can see a huge difference in the "Found new qualified records" field. The biggest differences are highlighted in red.
For instance the below cron was ran last night from DirectAdmin as admin:
Running '"/usr/local/directadmin/plugins/awstats/hooks/cgi-bin/awstats.pl" -update -config=abc.com -configdir="/etc/awstats"' to update config abc.com
Update for config "/etc/awstats/awstats.abc.com.conf"
With data in log file "/var/log/httpd/domains/abc.com.log"...
Phase 1 : First bypass old records, searching new record...
Direct access to last remembered record is out of file.
So searching it from beginning of log file...
Phase 2 : Now process new records (Flush history on disk after 20000 hosts)...
Jumped lines in file: 0
Parsed lines in file: 15
Found 0 dropped records,
Found 0 corrupted records,
Found 0 old records,
Found 15 new qualified records.
Now when running from admin manually through either ssh or the direct "update" through awstats the follwing results occur:
Running '"/usr/local/directadmin/plugins/awstats/hooks/cgi-bin/awstats.pl" -update -config=abc.com -configdir="/etc/awstats"' to update config abc.com
Update for config "/etc/awstats/awstats.abc.com.conf"
With data in log file "/var/log/httpd/domains/abc.com.log"...
Phase 1 : First bypass old records, searching new record...
Direct access after last parsed record (after line 15)
Jumped lines in file: 15
Found 15 already parsed records.
Parsed lines in file: 629
Found 0 dropped records,
Found 0 corrupted records,
Found 0 old records,
Found 629 new qualified records.
You can see a huge difference in the "Found new qualified records" field. The biggest differences are highlighted in red.
Last edited: