Dr.Web issues - unable to update virus db

[Gino_Pino]

It's few days we receive this message:
"Dear Administrator,your virus bases are not up to date. Please run updating script manually or use cron for this purpose."

No Parallels update had been run, so Dr.Web's key license can't be the reasing why.
Running the update.pl script manually won't solve the issue.

root@vps18802:/opt/drweb# cat /etc/cron.d/drweb-update
*/30 * * * * drweb /opt/drweb/update.pl >>/var/log/drwebupdate.log

Log says:
root@vps18802:/opt/drweb# tail /var/log/drwebupdate.log
ERROR: Dr.Web (R) Updater: Unable to connect to update.msk5.drweb.com: Connectio n timed out !
ERROR: Dr.Web (R) Updater: Unable to connect to update.msk.drweb.com: Connection timed out !
ERROR: Dr.Web (R) Updater: Unable to connect to update.drweb.com: Connection tim ed out !
ERROR: Dr.Web (R) Updater: cannot download dwrtoday.vdb !
ERROR: Dr.Web (R) Updater: failed to download new/updated files from http://upda te.drweb.com/unix/500 !
ERROR: Dr.Web (R) Updater: Unable to connect to update.msk5.drweb.com: Connectio n timed out !
ERROR: Dr.Web (R) Updater: Unable to connect to update.msk5.drweb.com: Connectio n timed out !
ERROR: Dr.Web (R) Updater: Unable to connect to update.drweb.com: Connection tim ed out !
ERROR: Dr.Web (R) Updater: cannot download dwrtoday.vdb !
ERROR: Dr.Web (R) Updater: failed to download new/updated files from http://upda te.drweb.com/unix/500 !

Is it smth happening on Dr.Web' servers ?

 

[UFHH01]

Sometimes, if updates are a bit bigger than normal, the update servers ( especially with common used schedules ) are in heavy use and you get time out notices for some days. You can always try to update DrWeb all by yourself with the command: /opt/drweb/update.pl as you already did and you now might want to try to update and re-install the latest patches from Plesk with the command:

/usr/local/psa/admin/bin/autoinstaller --select-product-id plesk --select-release-current --reinstall-patch --install-component base​

... and if this didn't work, you might want to use the common bootstrapper, which repairs quite a lot of common issues:

/usr/local/psa/bootstrapper/pp12.0.18-bootstrapper/bootstrapper.sh repair
​

Please reply again with new error messages and log entries, if you still experience issues/problems.

 

[Raph1]

Hello, same exact problem here.
Solution above did nothing.
Manually running /opt/drweb/update.pl as root produces no output.

For my information, what does drweb stand for in the cron entry : */30 * * * * drweb /opt/drweb/update.pl ?

Thank you very much.

 

[UFHH01]

@Raph1 : "drweb" is the systemuser, who should run this cronjob.

Another information about this issue/problem:
As you can see above, the cronjob for DrWeb - updates runs every 30 minutes. If an update fails, this doesn't mean, that DrWeb itself doesn't work anymore... just the latest update - definitions couldn't be downloaded from the DrWeb's update - servers. Most Plesk - Users switch off the notifications after using Plesk and DrWeb for a while, because they can get pretty annoying every 30 minutes, especially, if the DrWeb - update - servers are in heavy use, or have a temporary failure, which may occure from time to time... but do you really want a notification about a temporary failure? And do you want such notifications every 30 minutes?

It's up to you to decide that, but I would recommend to modify the cronjob to : /opt/drweb/update.pl >/dev/null 2>&1
This will send all this update - notifications to the nirwana and you can do something more interesting, than deleting DrWeb - update - notifications.

 

[Raph1]

Ok, alerts are gone for 3 days.
Thank you.