Login | Register
My pages Projects Community openCollabNet
Project highlights: Stable Version: 1.6.1, Development Version: 1.7.6

current
Reply to message

2020-03-13: This site is going to be decommissioned and shut down very soon. Please copy and archive any data you wish to keep ASAP

* = Required fields
* Subject
* Body
Attachments
Send reply to
Topic
Author (directly in email)
Please type the letters in the image above.

Original message

Author Alexandros Papadopoulos <apapadop@cmu.edu>
Full name Alexandros Papadopoulos <apapadop@cmu.edu>
Date 2003-07-20 17:26:44 PDT
Message On Thursday 17 July 2003 17:16, Hunter Matthews wrote:
> On Thu, 2003-07-17 at 16:52, Alexandros Papadopoulos wrote:
> > Hi guys.
> >
> > I've been using current for this past week and it's been flawless. Today
> > I was upgrading two identical clients (both RH7.2, completely
> > unpatched...), when I ran into this problem with the one of them:
> >
> > There was a fatal error communicating with the server. The message was:
> > 400: "Bad Request" while attempting to get
> > $RHN/{'X-RHN-Auth-Channels': [['redhat-7.2-i386', '20030715123620']],
> > 'X-RHN-Server-Id': '10.31.0.15', 'X-RHN-Auth-Expiration': '1058473638',
> > 'X-RHN-Auth': '303d055dcec932210cd​06a625256a3e1272d491​f',
> > 'X-RHN-Auth-User-Id': 'x'}/set_headers
>
> This is due to a very old up2date client, and the client and the server
> having their clocks fairly far off from each other.
>
> Either fix the clocks and up2date will update itself, or upgrade up2date
> by hand. (Newer versions of up2date don't have this bug)

Confirmed.

Thanks for the help!

-A
--
http://andrew.cmu.ed​u/~apapadop/pub_key.​asc
3DAD 8435 DB52 F17B 640F D78C 8260 0CC1 0B75 8265