Hello,
it's seams not a bug, at least from the KeyHelp perspective.
The reason you receive the message is, that the
goaccess script seams to writes its output ("Parsing... [258] [0/s]....") not into the normal "stdout" (Standard Output Stream) instead to the "stderr" (Standard Error Stream).
If the cron daemon, responsible for executing cron jobs, detects a non empty "stderr" it considered it as an unsuccessful execution of the script, even if the return code of the script was 0 (which means success).
For fixing this behavior, you can redirect the stderr stream of the goaccess script to the stdout stream by appending " 2>&1" to the command within KeyHelp (without the quotation marks of course).
===
For verifying, my above assumption is correct, please have a look into the crontab config file via "crontab -u <NAME_OF_THE_KEYHELP_USER> -l".
Right now, the command should look like:
Code: Select all
[...] /usr/local/bin/goaccess -p /usr/local/etc/goaccess/goaccess.conf -a - /home/users/USERNAME/logs/access.log -o /home/users/USERNAME/www/mysite.com/access.html > /dev/null
After you have done the fix mentioned above, it should look like:
Code: Select all
[...] /usr/local/bin/goaccess -p /usr/local/etc/goaccess/goaccess.conf -a - /home/users/USERNAME/logs/access.log -o /home/users/USERNAME/www/mysite.com/access.html 2>&1 > /dev/null
Mit freundlichen Grüßen / Best regards
Alexander Mahr
**************************************************************
Keyweb AG - Die Hosting Marke
Neuwerkstr. 45/46, 99084 Erfurt / Germany
http://www.keyweb.de -
http://www.keyhelp.de
**************************************************************