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

Dr. Web Update problem

Stefan Becker

Basic Pleskian
Hi,

since three day i get this error message for the update process:

Dr.Web (R) update details:
Update server: http://update.msk.drweb.com/unix/500
Update has begun at Sun Dec 19 14:30:01 2010 Update has finished at Sun Dec 19 14:30:29 2010

Following files has been updated:
/var/drweb/bases/drwtoday.vdb
/var/drweb/bases/dwrtoday.vdb
/var/drweb/updates/timestamp

ERROR: Dr.Web (R) Updater: cannot send HUP signal to daemon (pid=2427, error=No such process) !
Dr.Web (R) update details:
Update server: http://update.msk.drweb.com/unix/500
Update has begun at Sun Dec 19 14:30:01 2010 Update has finished at Sun Dec 19 14:30:29 2010

Following files has been updated:
/var/drweb/bases/drwtoday.vdb
/var/drweb/bases/dwrtoday.vdb
/var/drweb/updates/timestamp

See Dr.Web (R) Updater log file for details.

Which problem is at Dr.Web?

Best regards

Stefan
 
Seems it was discussed on DrWeb forum. Basically the issue is caused by the fact that cron is not able to give a HUP or restart signal to DrWeb service. That leads to a situation where cron thinks that the schedule didn't happen correctly and thus cron tries to inform the drweb user for this incident.

If you want to disable Dr.Web notifications, please follow this KB article - http://kb.odin.com/en/7023
 
Back
Top