The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

cPanel 11.50.1.3 auto update failed - RPM conflict - cpanel-clamav

Discussion in 'General Discussion' started by mtxmomoaudio, Sep 23, 2015.

  1. mtxmomoaudio

    mtxmomoaudio Registered

    Joined:
    Sep 23, 2015
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    PA
    cPanel Access Level:
    Root Administrator
    I received a notification from my server that the update failed - here are the relevant bits:

    Code:
    
    [2015-09-23 05:40:54 -0400] Downloading http://httpupdate.cpanel.net/RPM/11.50/centos/6/x86_64/cpanel-clamav-0.98.7-1.cp1150.x86_64.rpm
    
    
    [2015-09-23 06:11:44 -0400] ***** FATAL: Digest for cpanel-clamav-0.98.7-1.cp1150.x86_64.rpm is different from expected
    [2015-09-23 06:11:44 -0400] The Administrator will be notified to review this output when this script completes
    
    
    [2015-09-23 06:11:44 -0400] ***** FATAL: Failed to stage “new RPMS” because of an error: Digest for cpanel-clamav-0.98.7-1.cp1150.x86_64.rpm is different from expected at /usr/local/cpanel/scripts/updatenow.static-cpanelsync line 34759.
    
    [2015-09-23 06:11:44 -0400] : see http://go.cpanel.net/rpmcheckfailed for more information
    
    
    I checked out the rpmcheckfailed link, which suggest to run the command

    rpm qa|grep -i ^mysql


    but I get a usage error - it's saying I'm using the rpm command wrong.

    How does it know "what to expect"?
     
    #1 mtxmomoaudio, Sep 23, 2015
    Last edited by a moderator: Sep 23, 2015
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,854
    Likes Received:
    675
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Hello :)

    To update, a support ticket was opened and it appears this was the result of a bad download mirror. It looks like this issue was addressed after attempting the update on a different mirror.

    Thank you.
     
Loading...

Share This Page