On Wed, 2012-06-13 at 13:26 +0200, Togan Muftuoglu wrote:

On 06/13/2012 01:03 PM, Roger Oberholtzer wrote:

...

I am trying to update a 12.1 system, and zypper gives me "Digest verification failed." for all repos I try to access. If I understand it, this indicates that the server has some issue. If I tell zypper to continue, it just asks again (and again...), but with a new set of vales.

Suggestions are to select a different mirror.

I am using http://download.opensuse.org/ for all repos. One example that fails is http://download.opensuse.org/update/12.1.

So I guess it is choosing a mirror near me. How can I see which mirror is being used?

You can manually select a mirror

<http://download.opensuse.org/update/12.1/openSUSE:12.1:Update.repo.mirrorlist>

I had the same issue yesterday evening ending with a broken system, so I have decided to wait a bit but YMMV

I have another 12.1 system that works fine. I have now tried adding new repos from the mirrors, and I get the same error. What happens is that it complains about an incorrect checksum when getting the digest for the new repo. As I noted elsewhere in this thread, there is some odd network thing going on in this system: * I cannot scp files in or out. I get messages like: Corrupted MAC on input. Disconnecting: Packet corrupt lost connection * If I mount a remote file system with NFS, the checksum I get for a file on the 12.1 client is wrong. If it is zip file, and I try to access it, it complains it is corrupt. It is OK on the server and on other clients. This is case with all files. Oddly, directories look correct. * If I use rdesktop against this system, I get messy screen updating (big black squares) when the display is updating frequently. So perhaps the problem with the repos is really a fundamental network issue. This system has a 4-port intel e1000 network card that we use in all our systems. All other activity on the ports seems ok. We have many network transducers that are working fine. But none of that is on this specific port on the multiport card. Could it be a problem with only this interface on the board? Seems unusual that what appears to be data corruption errors find their way to TCP clients. What is the best way to get statistics about packet activity on an ethernet port? Age is making me forget what I once knew. That and the fact that things are generally so stable one forgets how to troubleshoot... Yours sincerely, Roger Oberholtzer OPQ Systems / Ramböll RST Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org