Problem with September 2014 OES 11 SP2 SMU

I've tried to patch my non production OES11SP2 servers with the latest patches this morning. But I got this error.

Anyone else getting this checksum error?
Is there anything wrong in Novell repositories? :(

Retrieving package novell-nrm-2.0.3-0.121.1.i586 (3/31), 2.3 MiB (5.7 MiB unpacked)
Retrieving: novell-nrm-2.0.3-0.121.1.i586.rpm [done]
Digest verification failed for novell-nrm-2.0.3-0.121.1.i586.rpm. Expected ebee72bf0ad41d4917e7c6a8884e8ad9f1bb428c, found ee9ff94085431cd9340a8ec8b755a56f564d152b. Continue? [yes/no] (no): n
Failed to provide Package novell-nrm-2.0.3-0.121.1. Do you want to retry retrieval?

[nu_novell_com:OES11-SP2-Updates|https://nu.novell.com/repo/$RCE/OES11-SP2-Updates/sle-11-x86_64?credentials=NCCcredentials] Can't provide file './rpm/i586/novell-nrm-2.0.3-0.121.1.i586.rpm' from repository 'nu_novell_com:OES11-SP2-Updates'
History:
- novell-nrm-2.0.3-0.121.1.i586.rpm has wrong checksum

Abort, retry, ignore? [a/r/i] (a): a
  • BoNeLeSS;2334364 wrote:
    I've tried to patch my non production OES11SP2 servers with the latest patches this morning. But I got this error.

    Anyone else getting this checksum error?
    Is there anything wrong in Novell repositories? :(



    Same error here. :-( - Seems to be a Novell problem....
  • On 24/09/2014 10:46, BoNeLeSS wrote:

    > I've tried to patch my non production OES11SP2 servers with the latest
    > patches this morning. But I got this error.
    >
    > Anyone else getting this checksum error?
    > Is there anything wrong in Novell repositories? :(
    >
    >
    > Code:
    > --------------------
    > Retrieving package novell-nrm-2.0.3-0.121.1.i586 (3/31), 2.3 MiB (5.7 MiB unpacked)
    > Retrieving: novell-nrm-2.0.3-0.121.1.i586.rpm [done]
    > Digest verification failed for novell-nrm-2.0.3-0.121.1.i586.rpm. Expected ebee72bf0ad41d4917e7c6a8884e8ad9f1bb428c, found ee9ff94085431cd9340a8ec8b755a56f564d152b. Continue? [yes/no] (no): n
    > Failed to provide Package novell-nrm-2.0.3-0.121.1. Do you want to retry retrieval?
    >
    > [nu_novell_com:OES11-SP2-Updates|https://nu.novell.com/repo/$RCE/OES11-SP2-Updates/sle-11-x86_64?credentials=NCCcredentials] Can't provide file './rpm/i586/novell-nrm-2.0.3-0.121.1.i586.rpm' from repository 'nu_novell_com:OES11-SP2-Updates'
    > History:
    > - novell-nrm-2.0.3-0.121.1.i586.rpm has wrong checksum
    >
    > Abort, retry, ignore? [a/r/i] (a): a
    > --------------------


    I've also seen this for novell-NDSserv-32bit-8.8.8.3-0.6.6.2.x86_64.rpm
    and have reported this to my Novell contacts.

    HTH.
    --
    Simon
    Novell Knowledge Partner

    ------------------------------------------------------------------------
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below. Thanks.
    ------------------------------------------------------------------------
  • On 24/09/2014 13:36, rob collins wrote:

    > I got the same with the firefox.rpm


    From the SLEx11-SPx-Updates repo? If so, that would suggest it's not
    necessarily a problem specific to these updates but something up with
    one (or more) of Novell/SUSE's update servers.

    HTH.
    --
    Simon
    Novell Knowledge Partner

    ------------------------------------------------------------------------
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below. Thanks.
    ------------------------------------------------------------------------
  • It looks as though it's hit and miss depending on which server you update from.
    The updates will be up there soon. It's a patience thing...
    Tom
  • On 24/09/2014 14:46, tomanstey wrote:

    > It looks as though it's hit and miss depending on which server you
    > update from.
    > The updates will be up there soon. It's a patience thing...


    Yes, there's a problem with one (or more) of EdgeCast's Content Delivery
    Network servers that mirror the updates. Novell are working hard with
    them to fix it.

    HTH.
    --
    Simon
    Novell Knowledge Partner

    ------------------------------------------------------------------------
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below. Thanks.
    ------------------------------------------------------------------------
  • Thanks for the feedback, guys. Let's hope it gets fixed soon
  • Seems to be fixed now. Update went through here... :-)