PDA

View Full Version : SMT: Checksum mismatch



Bernd
12-Aug-2014, 08:08
Hi,

this 7 Files shows a Checksum mismatch since a few days:

E '/srv/www/htdocs/repo/$RCE/SLES11-SP3-Updates/sle-11-x86_64/rpm/src/MozillaFirefox-24.7.0esr-0.8.2.src.rpm': Checksum mismatch'
E '/srv/www/htdocs/repo/$RCE/SLES11-SP3-Updates/sle-11-x86_64/rpm/src/clamav-0.98.3-0.11.1.src.rpm': Checksum mismatch'
E '/srv/www/htdocs/repo/$RCE/SLES11-SP3-Updates/sle-11-x86_64/rpm/src/dbus-1-x11-1.2.10-3.29.1.src.rpm': Checksum mismatch'
E '/srv/www/htdocs/repo/$RCE/SLES11-SP3-Updates/sle-11-x86_64/rpm/src/libvirt-1.0.5.9-0.9.1.src.rpm': Checksum mismatch'
E '/srv/www/htdocs/repo/$RCE/SLES11-SP3-Updates/sle-11-x86_64/rpm/src/sles-manuals_en-11.3-0.25.2.src.rpm': Checksum mismatch'
E '/srv/www/htdocs/repo/$RCE/SLES11-SP3-Updates/sle-11-x86_64/rpm/src/util-linux-2.19.1-6.54.1.src.rpm': Checksum mismatch'
E
'/srv/www/htdocs/repo/$RCE/SLES11-SP3-Updates/sle-11-x86_64/rpm/src/xorg-x11-libs-7.4-8.26.42.1.src.rpm':
Checksum mismatch'

How can I check if this is a local problem or if the files at the
source are damaged?

Bernd

Bernd
12-Aug-2014, 11:26
on Tue, Aug 12th 2014 07:08:54 GMT
wrote Bernd <bnacht@web.de>:

> Hi,
>
> this 7 Files shows a Checksum mismatch since a few days:
>
> E
> '/srv/www/htdocs/repo/$RCE/SLES11-SP3-Updates/sle-11-x86_64/rpm/src/MozillaFirefox-24.7.0esr-0.8.2.src.rpm':
> Checksum mismatch' E
> '/srv/www/htdocs/repo/$RCE/SLES11-SP3-Updates/sle-11-x86_64/rpm/src/clamav-0.98.3-0.11.1.src.rpm':
> Checksum mismatch' E
> '/srv/www/htdocs/repo/$RCE/SLES11-SP3-Updates/sle-11-x86_64/rpm/src/dbus-1-x11-1.2.10-3.29.1.src.rpm':
> Checksum mismatch' E
> '/srv/www/htdocs/repo/$RCE/SLES11-SP3-Updates/sle-11-x86_64/rpm/src/libvirt-1.0.5.9-0.9.1.src.rpm':
> Checksum mismatch' E
> '/srv/www/htdocs/repo/$RCE/SLES11-SP3-Updates/sle-11-x86_64/rpm/src/sles-manuals_en-11.3-0.25.2.src.rpm':
> Checksum mismatch' E
> '/srv/www/htdocs/repo/$RCE/SLES11-SP3-Updates/sle-11-x86_64/rpm/src/util-linux-2.19.1-6.54.1.src.rpm':
> Checksum mismatch' E
> '/srv/www/htdocs/repo/$RCE/SLES11-SP3-Updates/sle-11-x86_64/rpm/src/xorg-x11-libs-7.4-8.26.42.1.src.rpm':
> Checksum mismatch'
>
> How can I check if this is a local problem or if the files at the
> source are damaged?
>
> Bernd
>

Now, I have checked this form two different SMT Servers (different
Accounts in NCC, completely different Environments).

The files noted above and a few from i586 have the wrong checksum.

What is to do?

Bernd

jmozdzen
12-Aug-2014, 11:59
Hi Bernd,

> Now, I have checked this form two different SMT Servers (different
> Accounts in NCC, completely different Environments).

"different environments" in the sense of "no common file proxy between these SMT servers and the SUSE master"?

> What is to do?

"open a service request" would have been one way to handle this - but coming here is ok, too :) I've asked my SUSE contacts to verify and eventually fix the issue.

Regards,
Jens

Bernd
12-Aug-2014, 12:39
on Tue, Aug 12th 2014 11:04:02 GMT
jmozdzen <jmozdzen@no-mx.forums.suse.com> wrote:

(...)
> > Now, I have checked this form two different SMT Servers (different
> > Accounts in NCC, completely different Environments).
>
> "different environments" in the sense of "no common file proxy between
> these SMT servers and the SUSE master"?

Yes, in this sense ...
No proxy, different Providers, different NCC credentials, different
areas, ...

> I've asked my SUSE contacts to verify and eventually fix the issue.

Thx.

Bernd

jmozdzen
12-Aug-2014, 15:15
Hi Bernd,

I got back the information that you need to make sure you're at least running the following SMT 11 SP3 versions :

- smt-support-1.2.5-0.7.1
- smt-1.2.5-0.7.1
- res-signingkeys-1.2.5-0.7.1.x86_64.rpm

The according patch is described at http://download.novell.com/Download?buildid=_-6EwXT1ffs~ - it seems these symptoms point in the direction addressed by that patch.

As no other reports of this problem have come to my attention (and from what I can tell, my own SMT server does not report this problem), I would like you to verify that at least one of your affected servers has this or superseding patches installed.

Regards,
Jens