Re: can't get rhn_register (and therefore client s) working

On Thu, 25 Apr 2002 17:25:26 +0100
[email protected] wrote:

> On Thu, Apr 25, 2002 at 09:15:54AM -0700, Ryan Speed wrote:
> 
>  
> > For some reason no matter what value I put as the debuglevel in my
> > current config I still get no verbosity at all in the logfile, just the
> > start/stop messages (you will also notice that I tried to start it when
> > it was already running and I got failed to bind to port messages).
> 
> Hmm, just a thought can you test the ssl stuff
> 
> openssl s_client -connect https://lada:8081/

[root@cascia rhn]# openssl s_client -host lada.corp.van.dwave -port 8081 -debug
CONNECTED(00000003)
write to 0814E898 [08152730] (124 bytes => 124 (0x7C))
0000 - 80 7a 01 03 01 00 51 00-00 00 20 00 00 16 00 00   .z....Q... .....
0010 - 13 00 00 0a 07 00 c0 00-00 66 00 00 05 00 00 04   .........f......
0020 - 03 00 80 01 00 80 08 00-80 00 00 65 00 00 64 00   ...........e..d.
0030 - 00 63 00 00 62 00 00 61-00 00 60 00 00 15 00 00   .c..b..a..`.....
0040 - 12 00 00 09 06 00 40 00-00 14 00 00 11 00 00 08   ......@.........
0050 - 00 00 06 00 00 03 04 00-80 02 00 80 9a 31 e3 84   .............1..
0060 - 4f bd 79 a6 25 b4 73 e1-d2 00 95 1c 62 52 fa 46   O.y.%.s.....bR.F
0070 - b9 27 e6 94 3b f1 26 fa-a2 f8 13 66               .'..;.&....f
read from 0814E898 [08157C90] (7 bytes => -1 (0xFFFFFFFF))
write:errno=104

> openssl s_client -connect https://lada:8081/ -cert CERT-FILE

unable to get private key from '/usr/share/rhn/RHNS-CA-CERT'
4639:error:0906D06C:PEM routines:PEM_read_bio:no start line:pem_lib.c:662:Expecting: ANY PRIVATE KEY
4639:error:140B0009:SSL routines:SSL_CTX_use_PrivateKey_file:missing asn1 eos:ssl_rsa.c:707:

I copied the pem file to the client and attempted to connect with it as the CERT_FILE and I get the same output as that with no -cert argument.

> 
> Also try to connect with the client to the non ssl instance.

when I do this I get 

Apr 04 10:25:34 requesthandler.log_error(): code 400, message Bad HTTP/0.9 request type ('\200z\001\003\001\000Q\000\000\000')


> 
> Also check if there are any cert files in /etc/sysconfig/rhn as that
> foo'd up one of my installs.

/etc/sysconfig/rhn
[root@cascia rhn]# ls -l
-rw-r--r--    1 root     root          861 Apr 25 09:49 rhn_register
-rw-r--r--    1 root     root           13 Sep  7  2001 rhnsd
-rw-r--r--    1 root     root         1903 Apr 25 09:49 up2date

> 
> Paul 

Thanks Paul, does any of the above make sense to you?  Does this look like a client or a server side issue?

thanks,
ryan