Ad Widget

Collapse

3.4 to 4.0 upgrade error

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • brhunt
    Member
    • Feb 2013
    • 50

    #1

    3.4 to 4.0 upgrade error

    Hello,

    Following instructions to upgrade from 3.4 to 4.0 on Centos. Had error. Can anyone tell me why the 404 errors are occurring?

    [root@zabbix ~]# rpm -Uvh https://repo.zabbix.com/zabbix/4.0/r...el7.noarch.rpm
    Retrieving https://repo.zabbix.com/zabbix/4.0/r...el7.noarch.rpm
    Preparing... ################################# [100%]
    Updating / installing...
    1:zabbix-release-4.0-1.el7 ################################# [ 50%]
    Cleaning up / removing...
    2:zabbix-release-3.4-1.el7.centos ################################# [100%]
    [root@zabbix ~]# yum upgrade zabbix-server-mysql zabbix-web-mysql zabbix-agent
    Loaded plugins: fastestmirror
    Loading mirror speeds from cached hostfile
    * base: mirror.cisp.com
    * epel: mirror.grid.uchicago.edu
    * extras: mirror.cisp.com
    * updates: linux.cc.lehigh.edu
    Resolving Dependencies
    --> Running transaction check
    ---> Package zabbix-agent.x86_64 0:3.4.11-1.el7 will be updated
    ---> Package zabbix-agent.x86_64 0:3.4.15-1.el7 will be an update
    ---> Package zabbix-server-mysql.x86_64 0:3.4.11-1.el7 will be updated
    ---> Package zabbix-server-mysql.x86_64 0:3.4.15-1.el7 will be an update
    ---> Package zabbix-web-mysql.noarch 0:3.4.11-1.el7 will be updated
    --> Processing Dependency: zabbix-web-database = 3.4.11-1.el7 for package: zabbix-web-3.4.11-1.el7.noarch
    ---> Package zabbix-web-mysql.noarch 0:3.4.15-1.el7 will be an update
    --> Running transaction check
    ---> Package zabbix-web.noarch 0:3.4.11-1.el7 will be updated
    ---> Package zabbix-web.noarch 0:3.4.15-1.el7 will be an update
    --> Finished Dependency Resolution

    Dependencies Resolved

    ================================================== ==============================
    Package Arch Version Repository Size
    ================================================== ==============================
    Updating:
    zabbix-agent x86_64 3.4.15-1.el7 zabbix 369 k
    zabbix-server-mysql x86_64 3.4.15-1.el7 zabbix 2.0 M
    zabbix-web-mysql noarch 3.4.15-1.el7 zabbix 7.2 k
    Updating for dependencies:
    zabbix-web noarch 3.4.15-1.el7 zabbix 2.6 M

    Transaction Summary
    ================================================== ==============================
    Upgrade 3 Packages (+1 Dependent package)

    Total download size: 5.0 M
    Is this ok [y/d/N]: y
    Downloading packages:
    Delta RPMs disabled because /usr/bin/applydeltarpm not installed.
    zabbix-server-mysql-3.4.15-1.e FAILED
    http://repo.zabbix.com/zabbix/4.0/rh...l7.x86_64.rpm: [Errno 14] HTTP Error 404 - Not Found
    Trying other mirror.
    To address this issue please refer to the below wiki article



    If above article doesn't help to resolve this issue please use https://bugs.centos.org/.

    zabbix-agent-3.4.15-1.el7.x86_ FAILED
    http://repo.zabbix.com/zabbix/4.0/rh...l7.x86_64.rpm: [Errno 14] HTTP Error 404 - Not Found
    Trying other mirror.
    zabbix-web-3.4.15-1.el7.noarch FAILED
    http://repo.zabbix.com/zabbix/4.0/rh...l7.noarch.rpm: [Errno 14] HTTP Error 404 - Not Found
    Trying other mirror.
    zabbix-web-mysql-3.4.15-1.el7. FAILED
    http://repo.zabbix.com/zabbix/4.0/rh...l7.noarch.rpm: [Errno 14] HTTP Error 404 - Not Found
    Trying other mirror.


    Error downloading packages:
    zabbix-web-mysql-3.4.15-1.el7.noarch: [Errno 256] No more mirrors to try.
    zabbix-web-3.4.15-1.el7.noarch: [Errno 256] No more mirrors to try.
    zabbix-server-mysql-3.4.15-1.el7.x86_64: [Errno 256] No more mirrors to try.
    zabbix-agent-3.4.15-1.el7.x86_64: [Errno 256] No more mirrors to try.

    [root@zabbix ~]#
  • brhunt
    Member
    • Feb 2013
    • 50

    #2
    The 3.4 files are certainly not in the 4.0 repository, but why is the yum upgrade calling for them?

    Thanks.

    Bryan Hunt

    Comment

    • LenR
      Senior Member
      • Sep 2009
      • 1005

      #3
      yum clean all && try again

      Comment

      • brhunt
        Member
        • Feb 2013
        • 50

        #4
        Good lord, that was simple... (if you know what you are doing)...

        Thanks LenR for the correct answer!

        Perhaps that step should be in the documentation.....

        Comment

        Working...