Home

Results 1 to 5 of 5

Thread: rug update connection resets fails

Hybrid View

  1. #1
    Scott5 NNTP User

    rug update connection resets fails

    After completing an OES installation, I'm runing:

    rug up

    to get the latest updates from the OES channel. It does eventually
    work, but I have to babysit it.

    rug It constantly resets my connection, and the only way to recover is
    to restart rcd with either a /etc/init.d/rcd restart or rcrcd restart to
    start over.

    The errors vary; Connection reset by peer, IO errors, download errors, etc.

    What gives with the update server? Is it just getting pounded, or is
    this my problem because I'm behind a proxy?

  2. #2
    Aaron Gresko NNTP User

    Re: rug update connection resets fails

    On Fri, 03 Jun 2005 13:55:28 +0000, Scott5 wrote:

    > After completing an OES installation, I'm runing:
    >
    > rug up
    >
    > to get the latest updates from the OES channel. It does eventually work,
    > but I have to babysit it.


    The documentation specifically says not to use rug up to get patches. In
    rug, you have packages, updates, and patches.

    An update is a single rpm. A patch is a traditional SuSE patch, which
    consists of a patch info file and one or more rpms. Unfortunately, all of
    the patch rpms on the oes channel also show up as updates on rug.

    You should be using rug pl, rug pi, and rug pin to work with patches on
    OES.

    Aaron

  3. #3
    Scott5 NNTP User

    Re: rug update connection resets fails

    Aaron Gresko wrote:
    > On Fri, 03 Jun 2005 13:55:28 +0000, Scott5 wrote:
    >
    >
    >>After completing an OES installation, I'm runing:
    >>
    >>rug up
    >>
    >>to get the latest updates from the OES channel. It does eventually work,
    >>but I have to babysit it.

    >
    >
    > The documentation specifically says not to use rug up to get patches. In
    > rug, you have packages, updates, and patches.
    >
    > An update is a single rpm. A patch is a traditional SuSE patch, which
    > consists of a patch info file and one or more rpms. Unfortunately, all of
    > the patch rpms on the oes channel also show up as updates on rug.
    >
    > You should be using rug pl, rug pi, and rug pin to work with patches on
    > OES.
    >
    > Aaron


    Thanks for the clue, but can you tell me where this is documented? I
    haven't been able to find anything in the OES docs, but that could just
    be my poor search technique.

    Also, am I to assume that if I "patch" an instance of OES using 'rug
    pin' that I will somehow break something later if I use 'rug up' to just
    perform a general update? Should I not be updating packages as a rule?

  4. #4
    Aaron Gresko NNTP User

    Re: rug update connection resets fails

    >
    > Thanks for the clue, but can you tell me where this is documented? I
    > haven't been able to find anything in the OES docs, but that could just be
    > my poor search technique.
    >


    http://www.novell.com/documentation/...a/bu6x2k7.html

    <snip>
    IMPORTANT: Only install patches from the Patches tab. If you update from any
    other area, you can corrupt your server.
    <pins>

    Also, the rug instructions only show patch commands:

    http://www.novell.com/documentation/...a/buqxkfl.html

    A very helpful TID on this is at:

    http://support.novell.com/cgi-bin/se...?/10097537.htm

    If it is missing anything let me know---I wrote it.

    > Also, am I to assume that if I "patch" an instance of OES using 'rug
    > pin' that I will somehow break something later if I use 'rug up' to just
    > perform a general update? Should I not be updating packages as a rule?


    You should not use the update functionality at all on OES. You won't
    usually break anything. In fact, you won't usually break anything by
    updating packages with rug up instead of rug pin. A patch does have the
    capability to run pre and post scripts independent of the rpms in the
    patch---so you may not get part of the update using rug up instead of rug
    pin.

    I know the OES update/patch process is confusing to customers. I'm trying
    to evangelize it so the word gets out.

    Aaron


  5. #5
    Scott5 NNTP User

    Re: rug update connection resets fails

    Aaron Gresko wrote:
    >>Thanks for the clue, but can you tell me where this is documented? I
    >>haven't been able to find anything in the OES docs, but that could just be
    >>my poor search technique.
    >>

    >
    >
    > http://www.novell.com/documentation/...a/bu6x2k7.html
    >
    > <snip>
    > IMPORTANT: Only install patches from the Patches tab. If you update from any
    > other area, you can corrupt your server.
    > <pins>
    >
    > Also, the rug instructions only show patch commands:
    >
    > http://www.novell.com/documentation/...a/buqxkfl.html
    >
    > A very helpful TID on this is at:
    >
    > http://support.novell.com/cgi-bin/se...?/10097537.htm
    >
    > If it is missing anything let me know---I wrote it.
    >
    >
    >>Also, am I to assume that if I "patch" an instance of OES using 'rug
    >>pin' that I will somehow break something later if I use 'rug up' to just
    >>perform a general update? Should I not be updating packages as a rule?

    >
    >
    > You should not use the update functionality at all on OES. You won't
    > usually break anything. In fact, you won't usually break anything by
    > updating packages with rug up instead of rug pin. A patch does have the
    > capability to run pre and post scripts independent of the rpms in the
    > patch---so you may not get part of the update using rug up instead of rug
    > pin.
    >
    > I know the OES update/patch process is confusing to customers. I'm trying
    > to evangelize it so the word gets out.
    >
    > Aaron
    >

    That's funny. I did read that portion of the documentation, but I saw
    the "We recommend you use the command line to update OES for Linux until
    the issues with the Red Carpet interface have been resolved." disclaimer
    and said, "oh, okay, I'll just use rug"

    And then I found your TID, which was helpful in getting the channel
    installed and activated. As soon as it was subscribed, I read the man
    page for rug.

    Gotta read that stuff all the way through, I guess.

    Thanks, Aaron

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •