1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

DrWeb Selfupdate Error

Discussion in 'Plesk 9.x for Linux Issues, Fixes, How-To' started by Pioneer1976, Dec 22, 2009.

  1. Pioneer1976

    Pioneer1976 Guest

    0
     
    Hi,

    I am getting those two types of mails every half hour. What can I do about it?

     
  2. IgorG

    IgorG Forums Analyst Staff Member

    49
    24%
    Joined:
    Oct 27, 2009
    Messages:
    24,572
    Likes Received:
    1,243
    Location:
    Novosibirsk, Russia
    Is http://update.msk3.drweb.com/unix/500 accessible and not firewalled from your server? Do you have running update.pl process - check it with something like 'ps ax | grep update'. Try to kill this process if it is started. After that try to run /opt/drweb/update.pl manually and investigate /var/drweb/log/updater.log log file.
     
  3. Pioneer1976

    Pioneer1976 Guest

    0
     
    Thank you for the quick answer.

    The server does not have any outgoing firewall rules at all, it has free access to the internet. Only incoming traffic is restricted. The update was working until last night and suddenly stopped to do so.

    I found two running processes and killed both of them:

    I tried to wget the URL it cannot contact and got the following result:

    The manual running of update.pl takes a long time and returns this. It tries to connect to serveral alternate servers and fails on all of them with different error messages (cannot read / timeout getting). I stopped the execution after those two servers since it really takes very long:

    And finally the log file dows not exist. The directory /var/drweb/log is existant, but empty.
     
  4. Chris Magnuson

    Chris Magnuson Guest

    0
     
    # wget http://update.msk3.drweb.com/unix/500
    --2009-12-22 10:07:20-- http://update.msk3.drweb.com/unix/500
    Resolving update.msk3.drweb.com... 81.176.67.170
    Connecting to update.msk3.drweb.com|81.176.67.170|:80... connected.
    HTTP request sent, awaiting response... 301 Moved Permanently
    Location: http://update.msk3.drweb.com/unix/500/ [following]
    --2009-12-22 10:07:20-- http://update.msk3.drweb.com/unix/500/
    Reusing existing connection to update.msk3.drweb.com:80.
    HTTP request sent, awaiting response... 403 Forbidden
    2009-12-22 10:07:20 ERROR 403: Forbidden.
     
  5. Chris Magnuson

    Chris Magnuson Guest

    0
     
    When I tried to run it (new guy) I get:

    # /opt/drweb/update.pl
    ERROR: Dr.Web (R) Updater: timeout getting file drw50000.vdb !
    ERROR: Dr.Web (R) Updater: Quitting on signal INT !
    See Dr.Web (R) Updater log file for details.

    And also:

    # more /var/drweb/log/updater.log
    /var/drweb/log/updater.log: No such file or directory
    [root@teton2 sso]# cd /var/log/


    No log file.

    My earlier Quick Reply showed what happened when I tried to go to that URL manually with wget, looked like it wasn't set up properly to me.
     
  6. Chris Magnuson

    Chris Magnuson Guest

    0
     
    Same Problem

    I am also receiving these failure notices when the Dr.Web updater runs.

    I've checked for a running update.pl process and there is none.

    The firewall does not appear to be an issue. When I enter "wget http://update.msk3.drweb.com/unix/500/" in the cmd line I'm met with a 403:Forbidden error.

    When I run /opt/drweb/update.pl manually, I'm met with the following error.

    Additionally, No log file is generated generated in /var/drweb/log/.

    Any further suggestions would be appreciated. Thanks!
     
  7. IgorG

    IgorG Forums Analyst Staff Member

    49
    24%
    Joined:
    Oct 27, 2009
    Messages:
    24,572
    Likes Received:
    1,243
    Location:
    Novosibirsk, Russia
    I think that it is DrWeb related problems and you may contact their support or look at their forum.
     
Loading...