• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

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

Goncharenko

New Pleskian
Server operating system version
Ubuntu 24.04.2 LTS
Plesk version and microupdate number
Plesk Obsidian 18.0.69.3
Hello everyone,

I'm experiencing an issue with my daily Dr.Web Updater cron job. Each day, I receive the following error message via email:
/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

Just for your information, the databases were successfully updated manually yesterday.

/opt/drweb/update.pl
Dr.Web update details:
Update server: http://update.geo.drweb.com/plesk/1100/unix
Update has begun at Mon Jun 2 09:01:44 2025
Update has finished at Mon Jun 2 09:01:48 2025


Has anyone encountered this issue before or know how to resolve it? Any advice would be greatly appreciated.

Thank you!
 
Same here ... last week I have got that E-Mail and today the second one. Manual update via putty appears to work fine.
 
Thank you for the update, @Goncharenko . I attempted to reproduce the issue on a test Ubuntu 24.04 environment, but when running the update task manually doesn't produce the said error. Could you please give it a go and let me know:

/etc/cron.daily/drweb-update
 
Thank you for the update, @Goncharenko . I attempted to reproduce the issue on a test Ubuntu 24.04 environment, but when running the update task manually doesn't produce the said error. Could you please give it a go and let me know:
Thanks for the suggestion.
I ran /etc/cron.daily/drweb-update manually on my system, and no error occurred during execution.
Please see the attached screenshot for reference.
 

Attachments

  • Untitled.png
    Untitled.png
    4 KB · Views: 10
Thank you for your update. In this case, it's safe to conclude that it was due to temporary connectivity issue on Dr. Web's servers.
 
I do get this same error emailed on daily basis for the past week or so - I ran the cron job manually and this did not return any error, will let you know tomorrow if same message is emailed again.
 
Same error on daily base since 03.06.2025.

/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
 
Hi there, I am having the same problem. I ran the job manually but the notification was sent 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 109
 
It ain't. We're seeing the download warning messages again on several servers nightly.
@Sebahat.hadzhi @Bitpalast

Error codes are NOT limited to 105 codes.

The random behavior of DrWeb is also resulting in other symptoms, like 109 error codes (incompatible software) and/or failures to download files (without any output of error codes whatsoever).

I have played around a bit with the DrWeb issue and it is likely to be a bug, resulting from an unknown root cause of the problem.


In essence, the following applies or should apply :

1 - it is or should be possible to run /opt/drweb/update.pl without any issue : no error codes should be present,

2 - the /etc/cron.daily/drweb-update cronjob is resulting in an error notification by mail, on a daily basis.


This is really odd behavior, since EITHER the cronjob is buggy OR the update.pl script is behaving oddly (read: no errors similar to that of the cronjob).


Running the cronjob (as root) from Plesk > Tools & Settings > Scheduled Task Manager : new task > run now (for test purposes) does not result in errors.


Replicating this issue on various OSes (all Ubuntu) does not yield the same test results - 4 test servers, 3 failures (odd behavior), one good.


I am at a loss here ......... anybody having a clue?


Kind regards.....
 
Back
Top