yum update [Errno -3] Error performing checksum

-
Recently I had this issue of checksum error while doing yum update in my RHEL5 servers.


# yum update
Loaded plugins: security
rhel5-local/primary_db                                                                                                                          |    0 B     00:00
ftp://10.8.227.50/pub/LocalYumRepoRHEL5.1/repodata/c7408a1fce29f12df452017556509b3a3ebde95d7d01e8ea0adb052f97c43e86-primary.sqlite.bz2: [Errno -3] Error performing checksum
Trying other mirror.
Error: failure: repodata/c7408a1fce29f12df452017556509b3a3ebde95d7d01e8ea0adb052f97c43e86-primary.sqlite.bz2 from rhel5-local: [Errno 256] No more mirrors to try.


The usaual following way didn't work for me:

# yum clean all
# yum clean metadata
# yum update


Further I have disabled fastmirror for my yum config and it didn't work as well:

# grep enabled /etc/yum/pluginconf.d/fastestmirror.conf
enabled=0


I've even disabled http cache in yum.conf but same error:

# cat /etc/yum.conf |grep http_caching
http_caching=none


Rebuilding rpm database also was not not helpful:

# rm -rf /var/lib/rpm/__db*
# rpm --rebuilddb
# yum update


But here was my situation, I've created local yum repository for RHEL 5 on my RHEL 6 server!

When reading the createrepo manual, we can see:

# man createrepo
...
 -s --checksum
              Choose the checksum type used in repomd.xml and for packages in the metadata.  The default is now "sha256" (if python has hashlib).  The
              older  default  was  "sha", which is actually "sha1", however explicitly using "sha1" doesn’t work on older (3.0.x) versions of yum, you
              need to specify "sha".
...


Which was exactly my problem. while creating repositoy for RHEL 5 servers in RHEL 6 server, createrepo command used new hash of SHA256, and it's not comaptible with yum of RHEL 5 and before:

Solution:
To use createrepo with "-s sha" option in the repo server:

# createrepo -d -s sha /var/ftp/pub/LocalYumRepoRHEL5.1/


and in the client side:

# yum clean all
# yum clean metadata
# yum update

and there issue settled.





Comments

Post a Comment

Popular posts from this blog

Linux and AIX user non expiry and force password change at first login

-
In Linux, if you want to set the password for an account to never expire, here is the command: # chage -I -1 -m 0 -M 99999 -E -1 username  And to force a user to change his password upon first login: # chage -d0 username Current status of the account can be checked via chage command : # chage -l username  Last password change                                    : Jun 18, 2013 Password expires                                        : never Password inactive                                       : never Account expires                                         : never Minimum number of days between password change          : 0 Maximum number of days between password change          : 99999 Number of days of warning before password expires       : 7 For AIX, to set the password to non expiry and force the user to change his password upon first login: # chuser expires=0 maxage=0 username  To check the username status in AIX: # lsuser -f username
Read more

Rebuild your new Yum repository after changing the packages

-
If you have done any  changes  to your local  repository  packages, adding new ones or deleting some, you can just simply update your yum sqlite metadata database for your changes to take effect, rather than creating the whole repository again which takes time if you have  thousands  of packages in your repository.  Here is how we rebuild our yum repository. 1. After you are done with adding/removing packages to your local repo, then: # createrepo --update /path/to/repo_dir 2. On the  client  side, you need to clean up the cached yum meta data in order to see the changes after repo rebuild: # yum clean all 3. Now update the  client  yum cache  # yum update
Read more

Running Docker Wildfly/JBoss Application Server in Debug mode via Eclipse

-
I have recently built the whole Development Environment of Java Enterprise Edition (J2EE) project on multiple Docker containers. It has saved the hassle of setting up a dev env for new developers. All it takes to setup the environment is to clone our github repositories and run the Docker images. I will explain the setup in a future post. Build Wildfly Docker Image with Debugging Enabled So basically in order to run the Wildfly in debug mode, we need to add --debug  flag to the Wildfly standalone.sh  startup script. Also we need to expose port 8787  in our image as it's the default port for Wildfly JVM debug mode. 1. Create or change your Wildfly Dockerfile as follows: $ cat Dockerfile FROM jboss/wildfly: 10.0 . 0 .Final EXPOSE 8787 CMD [ "/opt/jboss/wildfly/bin/standalone.sh" , "-b" , "0.0.0.0" , "-bmanagement" , "0.0.0.0" , "--debug" ] 2. Build and tag the image: $ docker build -t wildfly-debug . 3.
Read more