• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue This error email comes every day at 7:30am

JtRGaMeR

New Pleskian

Cron Daemon .plesk.page>​


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

How can i fix it?
 
Really daily? Or only sometimes or recently for very few days in a row? Sometimes the update servers are overloaded or temporarily unavailable for other reasons. The error disappears on future attempts.

You can also check if updates.drweb.com can be reached from your server (from the console).

Have you tried a manual update?
# cd /opt/drweb
# ./update.pl
 
# ping updates.drweb.com
# wget updates.drweb.com
with # ping updates.drweb.com
i have these result:


~# ping updates.drweb.com
PING secure.drweb.com (213.79.64.7) 56(84) bytes of data.
64 bytes from 213.79.64.7 (213.79.64.7): icmp_seq=1 ttl=54 time=42.3 ms
64 bytes from 213.79.64.7 (213.79.64.7): icmp_seq=2 ttl=54 time=42.3 ms
64 bytes from 213.79.64.7 (213.79.64.7): icmp_seq=3 ttl=54 time=42.3 ms
64 bytes from 213.79.64.7 (213.79.64.7): icmp_seq=4 ttl=54 time=42.2 ms
64 bytes from 213.79.64.7 (213.79.64.7): icmp_seq=5 ttl=54 time=42.4 ms
64 bytes from 213.79.64.7 (213.79.64.7): icmp_seq=6 ttl=54 time=42.3 ms
64 bytes from 213.79.64.7 (213.79.64.7): icmp_seq=7 ttl=54 time=42.3 ms
64 bytes from 213.79.64.7 (213.79.64.7): icmp_seq=8 ttl=54 time=42.2 ms
64 bytes from 213.79.64.7 (213.79.64.7): icmp_seq=9 ttl=54 time=42.3 ms
64 bytes from 213.79.64.7 (213.79.64.7): icmp_seq=10 ttl=54 time=42.3 ms
64 bytes from 213.79.64.7 (213.79.64.7): icmp_seq=11 ttl=54 time=42.4 ms
64 bytes from 213.79.64.7 (213.79.64.7): icmp_seq=12 ttl=54 time=42.3 ms
64 bytes from 213.79.64.7 (213.79.64.7): icmp_seq=13 ttl=54 time=42.4 ms
64 bytes from 213.79.64.7 (213.79.64.7): icmp_seq=14 ttl=54 time=42.3 ms
64 bytes from 213.79.64.7 (213.79.64.7): icmp_seq=15 ttl=54 time=42.3 ms
64 bytes from 213.79.64.7 (213.79.64.7): icmp_seq=16 ttl=54 time=42.3 ms
64 bytes from 213.79.64.7 (213.79.64.7): icmp_seq=17 ttl=54 time=42.3 ms
64 bytes from 213.79.64.7 (213.79.64.7): icmp_seq=18 ttl=54 time=42.4 ms
64 bytes from 213.79.64.7 (213.79.64.7): icmp_seq=19 ttl=54 time=42.3 ms
64 bytes from 213.79.64.7 (213.79.64.7): icmp_seq=20 ttl=54 time=42.2 ms
^C
--- secure.drweb.com ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 73ms
rtt min/avg/max/mdev = 42.223/42.303/42.429/0.082 ms

and with # wget updates.drweb.com
i have these result:

wget updates.drweb.com
--2020-12-18 13:11:59-- Dr.Web Antivirus Virus Bases Update Lookup
Resolving updates.drweb.com (updates.drweb.com)... 213.79.64.12, 213.79.64.7
Connecting to updates.drweb.com (updates.drweb.com)|213.79.64.12|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: Dr.Web Antivirus Virus Bases Update Lookup [following]
--2020-12-18 13:12:00-- Dr.Web Antivirus Virus Bases Update Lookup
Connecting to updates.drweb.com (updates.drweb.com)|213.79.64.12|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘index.html.1’

index.html.1 [ <=> ] 271.95K 746KB/s in 0.4s

2020-12-18 13:12:02 (746 KB/s) - ‘index.html.1’ saved [278478]
 
So everything seems to work fine. Have you tried to manually update DrWeb?

# cd /opt/drweb
# ./update.pl
 
I get this:

root@************:~# cd /opt/drweb
root@************:/opt/drweb# ./update.pl
ERROR: Dr.Web Updater: failed to download files !
 
Strange issue.

When you run a few checks on the library files for the version of DrWeb what's the output?

# rpm -qf /var/drweb/bases/update.drl
Expected output:
drweb-bases-6.0.2.4-1302271534pleskel5.noarch

# rpm -qi drweb-bases | grep Vendor
Expected output:
Vendor : Doctor Web, Ltd.

# rpm -qi drweb-bases | grep Packager
Expected output:
Packager : Boris Savelev <b.savelev@drweb.com>, Dmitry Samoylov <d.samoylov@drweb.com>
 
Strange issue.

When you run a few checks on the library files for the version of DrWeb what's the output?

# rpm -qf /var/drweb/bases/update.drl
Expected output:
drweb-bases-6.0.2.4-1302271534pleskel5.noarch

# rpm -qi drweb-bases | grep Vendor
Expected output:
Vendor : Doctor Web, Ltd.

# rpm -qi drweb-bases | grep Packager
Expected output:
Packager : Boris Savelev <b.savelev@drweb.com>, Dmitry Samoylov <d.samoylov@drweb.com>
i get

-bash: rpm: command not found

for all 3 of them
 
You are probably on Debian or Ubuntu. I don't have a suitable test system here for that, so I cannot give you the exact matching commands to check the packages there.

I've seen that similar DrWeb issues were discussed before, but there was no real solution but to contact DrWeb support. If the sources are accessible as shown in the tests above, the updated should not have any issues with them either unless it is outdated. Some users have reported that deinstalling and reinstalling Plesk antivirus solved the issue for them.
 
Please check out this article:
ok i did what the article says and now these commands :

"
# cd /opt/drweb
# ./update.pl
"
works , i got no error

but on these commands

"
# rpm -qf /var/drweb/bases/update.drl
Expected output:
drweb-bases-6.0.2.4-1302271534pleskel5.noarch

# rpm -qi drweb-bases | grep Vendor
Expected output:
Vendor : Doctor Web, Ltd.

# rpm -qi drweb-bases | grep Packager
Expected output:
Packager : Boris Savelev <b.savelev@drweb.com>, Dmitry Samoylov <d.samoylov@drweb.com>
"
i still have "-bash: rpm: command not found" error
 
Great, your issue is solved.

The rpm commands fail, because they are for reference Linux like RHEL, CentOS. Debian uses a different, proprietary installer and not the rpm package manager. No need to continue testing here, because DrWeb will be updated correctly now.
 
Back
Top