similar to: yum checksum for updates fails

I''m reasonably confident that the problem I''m having here is upstream. RHEL5: # yum repolist | grep puppet puppetlabs-deps Puppet Labs Dependencies El 5 - x86_64 45 puppetlabs-products Puppet Labs Products El 5 - x86_64 161 # yum clean all Loaded plugins: security Cleaning up Everything # yum repolist 2>&1 | grep puppet

hey guys.. I'm continually seeing the following error although I've got the latest/greatest yum RPM from various CentOS 5.2 repos (mirrors.kernel.org most recently). is there possibly something wrong with the RPM's checksum somewhere upstream? note: I've already regenerated our own mrepo server various times and refreshed the metadata on my yum clients as well. ******* ~# yum

google for "centos error performing checksum" refers to createrepo but of course "yum install createrepo" also fails and the instructions appear to be overkill. Is there a "simple" soultion? here's the result of yum update: # yum -v update Loading "fastestmirror" plugin Config time: 0.118 Yum Version: 3.2.22 Setting up Package Sacks Loading mirror

I keep a local copy of the yum repository using rsync every night. Commands like "yum update" still work, but lately I've been getting the following error: # yum grouplist Setting up Group Process Setting up repositories Error: Caching enabled and local cache: //var/cache/yum/base/ yumgroups.xml does not match checksum My nightly rsync cron job doesn't update

Almost each time I want to use rpmforge with yum I get a "Metadata file does not meet checksum" error. Yum usually has to try at least five mirrors before it succeeds, sometimes it doesn't find a mirror with a useable file. This is with CentOS 5. Is this a known issue with rpmforge lately? Kai -- Kai Sch?tzl, Berlin, Germany Get your web at Conactive Internet Services:

Again with the yum metadata checksum failures: http://yum.puppetlabs.com/el/6/products/x86_64/repodata/primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum I''m thinking it''s time for me to add the Puppetlabs repos to my mrepo box. -- \*..+.- --Greg Chavez +//..;}; -- You received this message because you are subscribed to the Google Groups "Puppet

2007/10/19, Josh Coalson <xflac@yahoo.com>: > > --- Harry Sack <tranzedude@gmail.com> wrote: > > hi > > > > here some questions about the md5 checksum: > > > > - what happens when the md5 checksum of the decoded audio is > > different > > of the internally stored checksum due to file corruption ? Will > > playing/decoding still be

hi here some questions about the md5 checksum: - what happens when the md5 checksum of the decoded audio is different of the internally stored checksum due to file corruption ? Will playing/decoding still be possible (with some error frames) or will playing /decoding be not possible at all (so all audio data is lost)? - what happens when the metadata blocks get corrupt? will the audio part

Hello, Suppose that every day cron runs this: rsync -a --times --delete $HOME /my/backups/dir/latest In general, rsync will only update a file if it has been modified. Now, imagine that one of the files becomes corrupted in the backup directory, but the timestamp hasn't changed. Will rsync detect this? I am using rsync in a backup solution which could be summarized to: cd

I am running 4.1. I have all proxies out of the way. One machine does the following: [root at enoch ~]# yum update Setting up Update Process Setting up Repos dag 100% |=========================| 1.1 kB 00:00 update 100% |=========================| 951 B 00:00 base 100% |=========================| 1.1 kB 00:00 addons

I get this when i try to yum update: http://mirror.centos.org/centos/4/updates/i386/repodata/primary.xml.gz: [Errno -1] Metadata file does not match checksum Trying other mirror. Error: failure: repodata/primary.xml.gz from update: [Errno 256] No more mirrors to try. I have done yum clean all with no joy. I have two servers with CentOS-4.1 and both are exhibiting htis issue. I have not made

Hey Roger, I am seeing this weird behavior when using #linux-next + stable/for-jens-3.8 tree. Basically I can do ''pvscan'' on xvd* disk and quite often I get checksum errors: # pvscan /dev/xvdf PV /dev/xvdf2 VG VolGroup00 lvm2 [18.88 GiB / 0 free] PV /dev/dm-14 VG vg_x86_64-pvhvm lvm2 [4.00 GiB / 68.00 MiB free] PV /dev/dm-12 VG vg_i386-pvhvm lvm2

Until Syslinux 3.86, isolinux.bin contained a checksum that was calculated by 'core/checksumiso.pl'. The checksum is related to the patching of the boot info table. During May 2009, a commit by Peter deleted the checksumiso.pl file. The commit is: core: LZO compress the PM part of the core repo.or.cz/syslinux.git/commit/0d82b71304d596d80f3c4520f9dcf90048ca50b7 And so, since

Hi I have a problem with rsync and the -c option. I think understand what it does, but I'm not sure, it does it correctly. But then I guess, perhaps I don't understand what it does... :-) I use "rsync version 2.6.8 protocol version 29" I use the following command: /opt/rsync/bin/rsync -av --link-dest=/home/user/backup/old /home/user/source

https://bugzilla.samba.org/show_bug.cgi?id=12570 Bug ID: 12570 Summary: Problems with --checksum --existing Product: rsync Version: 3.1.1 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org Reporter: atom at

Hi, I've created an test enviroment for btrfs 0.11. The aim of the test is to compare speed of btrfs to ext3, reiserfs, jfs, xfs, etc. I've created an 70 GB partition for btrfs, created btrfs filesystem on it, which is currently mounted under /data. I put the kernel source tree of Linux 2.6.24 to the btrfs, make allyesconfig, and i've created the following script: while true; do

Hi all. A quick question about the checksum error detection routines in ZFS. Surely ZFS can decide about checksum errors in a redundant environment but what about an non-redundant one? We connected a single RAID5 array to a v440 as a NFS server and while doing backups and the like we see the "zpool status -v" checksum error counters increment once in a while. Nevertheless the

hello centos.. my yum is b0rked... [root at VIRTCENT03:~] #yum repolist Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Traceback (most recent call last): File "/usr/bin/yum", line 29, in ? yummain.user_main(sys.argv[1:], exit_code=True) File "/usr/share/yum-cli/yummain.py", line 309, in user_main errcode = main(args) File

Cant seem to fix this problem, need help --- Tue Mar 30 11:21:17 +0000 2010 //yumconf/File[/etc/hosts] (debug): Creating checksum {md5}0eea71665fb6890c06421fd13aa3f849 Tue Mar 30 11:21:17 +0000 2010 //yumconf/File[/etc/yum.repos.d/CentOS-Base.repo]/checksum (debug): Initializing checksum hash Tue Mar 30 11:21:17 +0000 2010 //yumconf/File[/etc/yum.repos.d/CentOS-Base.repo] (debug): Creating

This is the third time I''ve sent a message about this. Does anybody know what''s going on? I''m going to file a bug if this isn''t fixed soon. RHEL6: http://yum.puppetlabs.com/el/6/products/x86_64/repodata/primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. Error: failure: repodata/primary.sqlite.bz2 from