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

[Goncharenko]

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!

 

[hebeyer]

Same here ... last week I have got that E-Mail and today the second one. Manual update via putty appears to work fine.

 

[Sebahat.hadzhi]

This could be related to a temporary networking issue on Dr Web's end. Please monitor the situation and do let us know if the same reoccurs tomorrow.

 

[Goncharenko]

This could be related to a temporary networking issue on Dr Web's end. Please monitor the situation and do let us know if the same reoccurs tomorrow.

Hello, it's the same today...

 

[Sebahat.hadzhi]

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

 

[Goncharenko]

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.

 

[Sebahat.hadzhi]

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.