RE: New release posted

On Thu, 2001-12-13 at 12:00, Robert Hagopian wrote:
> I'm having a some difficulty getting 0.9 to connect to current (using
> stunnel):
> 
> loglevel = 10
> Starting up Backend
> /usr/share/current/channel.py:read({'db_dir': '/disk1/6.2/current'})
> /usr/share/current/channel.py:read({'db_dir': '/disk1/7.0/current'})
> /usr/share/current/channel.py:read({'db_dir': '/disk1/7.1/current'})
> /usr/share/current/channel.py:read({'db_dir': '/disk1/7.2/current'})
> Starting Up Server
> requesthandler.log_error(): code 400, message Bad request syntax ('')
> requesthandler.log_error(): code 400, message Bad request syntax ('')
> requesthandler.log_error(): code 400, message Bad request syntax ('')
> requesthandler.log_error(): code 400, message Bad request syntax ('')
> requesthandler.log_error(): code 400, message Bad request syntax ('')
> 
> Printed to stderr:
> ----------------------------------------
> Exception happened during processing of request from ('127.0.0.1', 39346)
> Traceback (innermost last):
>   File "/usr/lib/python1.5/site-packages/SocketServer.py", line 213, in
> handle_request
>     self.process_request(request, client_address)
>   File "/usr/lib/python1.5/site-packages/SocketServer.py", line 239, in
> process_request
>     self.finish_request(request, client_address)
>   File "/usr/lib/python1.5/site-packages/SocketServer.py", line 243, in
> finish_request
>     self.RequestHandlerClass(request, client_address, self)
>   File "/usr/lib/python1.5/site-packages/SocketServer.py", line 366, in
> __init__
>     self.handle()
>   File "/usr/lib/python1.5/site-packages/BaseHTTPServer.py", line 249, in
> handle
>     self.send_error(400, "Bad request syntax (%s)" % `requestline`)
>   File "/usr/lib/python1.5/site-packages/BaseHTTPServer.py", line 283, in
> send_error
>     self.wfile.write(self.error_message_format %
> IOError: [Errno 32] Broken pipe
> ----------------------------------------
> 
> And up2date/rhn_register just say "SSL_connect error"
> 
> Any thoughts offhand?

It looks like a mismatch with stunnel. Either stunnel isn't running at
all, its forwarding to a different port than the one current is
listening on, OR finally, your RHN-CA-CERTS file on the _client_ doesn't
match the .pem file you gave stunnel. 

Is it any wonder I want stunnel to go away?
-- 
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.