Login | Register
My pages Projects Community openCollabNet

Discussions > users > Re: 400: "Bad Request"

Project highlights: Stable Version: 1.6.1, Development Version: 1.7.6

Discussion topic

2020-04-07: This site is going to be decommissioned and shut down on 2020-07-01. Please copy and archive any data you wish to keep before that date.

Back to topic list

Re: 400: "Bad Request"


Author Hunter Matthews <thm at duke dot edu>
Full name Hunter Matthews <thm at duke dot edu>
Date 2003-07-17 14:16:01 PDT
Message 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': '', '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)

> On checking the current logs (on the server), there are a couple of
> worrying entries:
> current.log
> ===========
> Jul 17 13:40:34 Current v1.4.4 starting up
> Jul 17 13:59:58 ERROR: New module called: queue with function get
> Jul 17 13:59:58 params were: ['<?xml version="1.0"?>\​012<params>\0​12<p
> <snip large block of tags>
This is the rhn_check/rhnsd running on the client. If I ship a 1.4.5 the
messages will be ignored.

In any case, this error is completely harmless.

> error.log
> =========
> [Thu Jul 17 16:06:11 2003] [notice] setting normal headers
> [Thu Jul 17 16:11:45 2003] [notice] child pid 8498 exit signal
> Segmentation fault (11)

I have no idea whats causing this.

> [Thu Jul 17 16:24:32 2003] [notice] Inside the PythonHandler
> [Thu Jul 17 16:24:32 2003] [notice] Result = <Fault 1000 """Module queue
> not recognized""">
Same as above in the current.log - its just a dup

Hunter Matthews Unix / Network Administrator
Office: BioScience 145/244 Duke Univ. Biology Department
Key: F0F88438 / FFB5 34C0 B350 99A4 BB02 9779 A5DB 8B09 F0F8 8438
Never take candy from strangers. Especially on the internet.

To unsubscribe, e-mail: users-unsubscribe@cu​rrent.tigris.org
For additional commands, e-mail: users-help at current dot tigris dot org

« Previous message in topic | 2 of 3 | Next message in topic »


Show all messages in topic

400: "Bad Request" Alexandros Papadopoulos <apapadop at andrew dot cmu dot edu> Alexandros Papadopoulos <apapadop at andrew dot cmu dot edu> 2003-07-17 13:52:56 PDT
     Re: 400: "Bad Request" Hunter Matthews <thm at duke dot edu> Hunter Matthews <thm at duke dot edu> 2003-07-17 14:16:01 PDT
         [SOLVED] Re: 400: "Bad Request" Alexandros Papadopoulos <apapadop at cmu dot edu> Alexandros Papadopoulos <apapadop at cmu dot edu> 2003-07-20 17:26:44 PDT
Messages per page: