raytracy
Basic Pleskian
I have a Centos 7.3+Onyx 17.5 eject the following error to root every hour after upgraded to Update#14:
/etc/cron.hourly/awstats:
/usr/share/awstats/tools/awstats_updateall.pl: line 11: my: command not found
/usr/share/awstats/tools/awstats_updateall.pl: line 12: my: command not found
/usr/share/awstats/tools/awstats_updateall.pl: line 15: my: command not found
/usr/share/awstats/tools/awstats_updateall.pl: line 17: my: command not found
/usr/share/awstats/tools/awstats_updateall.pl: line 19: my: command not found
/usr/share/awstats/tools/awstats_updateall.pl: line 21: my: command not found
/usr/share/awstats/tools/awstats_updateall.pl: line 22: my: command not found
/usr/share/awstats/tools/awstats_updateall.pl: line 23: my: command not found
/usr/share/awstats/tools/awstats_updateall.pl: line 38: sub: command not found
/usr/share/awstats/tools/awstats_updateall.pl: line 39: print: command not found
I have try to uninstall/re-install awstats from panel but not help.
There are 4 hosts upgraded to #14, only one got this message hourly.
By the way, it seems something wrong when I re-install awstats, because there are a word like (missing...) flashing over the progress window, but I have no chance to capture it.
Is there any log file I can inspect the installation? Or any command line let me re-install the awstats so I can get the message from console?
----- Update
if I try to run the command in cron.hourly, it seems reponse normal as following:
Running '"/usr/share/awstats/wwwroot/cgi-bin/awstats.pl" -update -config=localhost.localdomain -configdir="/etc/awstats"' to update config localhost.localdomain
Create/Update database for config "/etc/awstats/awstats.localhost.localdomain.conf" by AWStats version 7.6 (build 20161204)
From data in log file "/var/log/httpd/access_log"...
Phase 1 : First bypass old records, searching new record...
Direct access after last parsed record (after line 5545)
Jumped lines in file: 5545
Found 5545 already parsed records.
Parsed lines in file: 28
Found 12 dropped records,
Found 0 comments,
Found 0 blank records,
Found 0 corrupted records,
Found 0 old records,
Found 16 new qualified records.
I have no idea why same command will produce error in cron schedule?
/etc/cron.hourly/awstats:
/usr/share/awstats/tools/awstats_updateall.pl: line 11: my: command not found
/usr/share/awstats/tools/awstats_updateall.pl: line 12: my: command not found
/usr/share/awstats/tools/awstats_updateall.pl: line 15: my: command not found
/usr/share/awstats/tools/awstats_updateall.pl: line 17: my: command not found
/usr/share/awstats/tools/awstats_updateall.pl: line 19: my: command not found
/usr/share/awstats/tools/awstats_updateall.pl: line 21: my: command not found
/usr/share/awstats/tools/awstats_updateall.pl: line 22: my: command not found
/usr/share/awstats/tools/awstats_updateall.pl: line 23: my: command not found
/usr/share/awstats/tools/awstats_updateall.pl: line 38: sub: command not found
/usr/share/awstats/tools/awstats_updateall.pl: line 39: print: command not found
I have try to uninstall/re-install awstats from panel but not help.
There are 4 hosts upgraded to #14, only one got this message hourly.
By the way, it seems something wrong when I re-install awstats, because there are a word like (missing...) flashing over the progress window, but I have no chance to capture it.
Is there any log file I can inspect the installation? Or any command line let me re-install the awstats so I can get the message from console?
----- Update
if I try to run the command in cron.hourly, it seems reponse normal as following:
Running '"/usr/share/awstats/wwwroot/cgi-bin/awstats.pl" -update -config=localhost.localdomain -configdir="/etc/awstats"' to update config localhost.localdomain
Create/Update database for config "/etc/awstats/awstats.localhost.localdomain.conf" by AWStats version 7.6 (build 20161204)
From data in log file "/var/log/httpd/access_log"...
Phase 1 : First bypass old records, searching new record...
Direct access after last parsed record (after line 5545)
Jumped lines in file: 5545
Found 5545 already parsed records.
Parsed lines in file: 28
Found 12 dropped records,
Found 0 comments,
Found 0 blank records,
Found 0 corrupted records,
Found 0 old records,
Found 16 new qualified records.
I have no idea why same command will produce error in cron schedule?
Last edited: