Resolved ERROR: Dr.Web Updater: failed to download files ! return code 105

[trialotto]

@trialotto can you please confirm what are the exact errors you encounter when running the /etc/cron.daily/drweb-update and /opt/drweb/update.pl? I am unable to replicate the behavior on a test environment.

@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.

 

[Sebahat.hadzhi]

Thank you for the update. The initially reported error with 105 error code was reviewed by our engineers and it was determined it is due to connectivity issue with Dr.Web's update servers. Regarding the last reported errors with code 109, the root cause is also usually due to connectivity issues. Could everyone who experiences the 109 errors try applying the following workaround and let us know if the issue still persists afterward?

 

[chris-design]

I tried the mentioned workaround yesterday. I added

81.176.67.172 update.geo.drweb.com

to the hosts file and increased the timeout value to 360. This morning I received this message again:

/etc/cron.daily/drweb-update:
ERROR: Dr.Web Updater: failed to download files !
run-parts: /etc/cron.daily/drweb-update exited with return code 105

When I run

/opt/drweb/update.pl

manually on the system, everything updates fine without any error or warning.

 

[hebeyer]

I received the same error today in the morning.

 

[hexx_network]

I receive the error too since 03.06.2025 on a daily base:

/etc/cron.daily/drweb-update:
ERROR: Dr.Web Updater: failed to download files !
run-parts: /etc/cron.daily/drweb-update exited with return code 105

Manually executing /etc/cron.dailty/drweb-update does work without errors.

 

[chris-design]

@Sebahat.hadzhi any updates from Plesk support team on this topic? I am receiving those mails every day for a lot of servers. It gets kind of annoying now since there is no fix for this.

 

[Sebahat.hadzhi]

@chris-design , it is still believed the errors result from connectivity issue on Dr.Web's update servers. Can you please try replacing the IP address in the hosts file with another one from the same article?

 

[chris-design]

@Sebahat.hadzhi I think the connectivity issue would also be visible in the manual updating process. But this runs through everything very fast. The entire update process just needs a couple of seconds. So I think this is not a connectivity issue.

 

[Sebahat.hadzhi]

Thank you for the update. I consulted with our team again and the other suggestion than connectivity issue is incorrect license. Hence, please execute the following command and let us know what the output is:

systemctl status drwebd

 

[trialotto]

Thank you for the update. I consulted with our team again and the other suggestion than connectivity issue is incorrect license. Hence, please execute the following command and let us know what the output is:

@Sebahat.hadzhi

Output of systemctl status drwebd will not result in abnormalities - at least, it should not be the case.

It is clearly a bug of some kind that is not related to connectivity issues and/or license issues - after all, manual updates should not work if that was the case.

Again, I believe that it simply is something related to the cronjob (or the time at which it is run).

Kind regards....

 

[Sebahat.hadzhi]

Thank you for the update. The status should return if there are any issues detected with the license. According to internal discussion with our team about this case, it could be correlated to an issue with invalid license. It might be a bug, but since it is not possible to replicate it and it is intermittent, there isn't enough evidence to classify it as such.

 

[Bitpalast]

I am experiencing daily (nightly) messages that DrWeb didn't update, too. And they are on several severs. No license issues here.

 

[trialotto]

Thank you for the update. The status should return if there are any issues detected with the license. According to internal discussion with our team about this case, it could be correlated to an issue with invalid license. It might be a bug, but since it is not possible to replicate it and it is intermittent, there isn't enough evidence to classify it as such.

@Sebahat.hadzhi

It is not a license issue, unless Plesk did issue problematic licenses themselves.

The simple proof that it is not a license issue is already present in 2 ways : (a) you cannot replicate it and (b) all manual updates work fine.

Again, it should be wise to focus on the cronjob - it only goes wrong with updates triggered by cronjobs.

Also, to exclude the most strange explanation for these error notifications, please try to verify with DrWeb when they reboot servers - any cronjob triggering an update during intervals in which DrWeb servers are reset / rebooted, that cronjob will also cause issues.

In addition, please do the same verification for the licensing server ..... there is another explanation for the error notifications.

Anyway, a solution should be found for all those DrWeb related error notifications.

Kind regards....