Facebook
Twitter@Sebahat.hadzhi
It is probably difficult or even impossible to replicate a specific symptom.
In essence, there are multiple "symptoms" which are very likely to be caused by ONE root cause of the problem.
In addition, the "symptoms" are not consistent over time - in a test environment, I can get different errors per day.
In summary, in order to create STR (steps-to-reproduce), it is best to
1 - assume that there is an issue with DrWeb updates, with the issue TRIGGERED by the (daily) cronjob (read: taking into account that manual updates work),
2 - change the following lines in /etc/cron.daily/drweb-update
"${update_scr}" >$outfile 2>&1
rc=$?
to
"${update_scr}" >$outfile 2>&1
cp $outfile /[testdir]/drweb/
rc=$?
and leave it for a couple of days.
3 - compare the contents of the (copy) of the outfile (which is in format "drweb-update.XXXXXX") with the actual error notification send by mail.
Please note that all of the above will ONLY be a first step to create STR - it is an analysis of the random results from running the (daily) cronjob.
In case that one finds output in the (copy of the) outfile, then one STILL has to run /opt/drweb/update.pl manually and compare results.
In most cases, a non-empty outfile will provide totally different results from a manual run of /opt/drweb/update.pl ..... and therein lies the issue : any (daily) cronjob that executes update.pl should have exactly the same (and consistent) results.
I hope the above helps a bit ..... I cannot provide more feedback yet.
Kind regards.....
PS Plesk still has to investigate why the update.pl script, if run from a new task created in Scheduled Task Manager, does NOT yield issues, whilst the same script, if run from /etc/cron.daily, is actually creating issues that are rather random and odd.
