Forum Discussion
Nimbostratusopenssl command in v11 is not working
I am trying to connect backend server using openssl to know Renegotiation details. My pool members are configured under route domains. It is giving me error message as below: [l044091@AC2004-TILTM2-EPS:/S1-green-P:Active] ~ openssl s_client -connect 10.16.185.150%102:https connect: Connection timed out connect:errno=29 [l044091@AC2004-TILTM2-EPS:/S1-green-P:Active] ~ [l044091@AC2004-TILTM2-EPS:/S1-green-P:Active] ~ ping 10.16.185.150%102 PING 10.16.185.150%102 (10.16.185.150%102) 56(84) bytes of data. 64 bytes from 10.16.185.150%102: icmp_seq=1 ttl=127 time=1.50 ms 64 bytes from 10.16.185.150%102: icmp_seq=2 ttl=127 time=0.985 ms
This server is part of pool and that pool is in use for years now. Can anyone help to know how to run openssl in v11.3?
5 Replies
uni_87886Cirrostratus
Try this instead:
rdexec 102 openssl s_client -connect 10.16.185.150:https- uni_87886rdexec puts your command in the context of the route domain number which folllows it. You can also use rdsh followed by the rd number. This puts you in a shell within the route domain, so all subsequent IP addresses will be for that route domain (which is the same as "rdexec 102 bash")
uniAltocumulus
Try this instead:
rdexec 102 openssl s_client -connect 10.16.185.150:https- unirdexec puts your command in the context of the route domain number which folllows it. You can also use rdsh followed by the rd number. This puts you in a shell within the route domain, so all subsequent IP addresses will be for that route domain (which is the same as "rdexec 102 bash")
- Stefan_Klotz
Cumulonimbus
Thank you very much!!! I had a similar issue and the "openssl s_client" command doesn't seem to work as expected in v11. But with rdexec or rdsh the command works fine again. This will be helpful for several other commands and troubleshooting as well.
Ciao Stefan :)
