Sponsored Content
Full Discussion: Help with RollBack options
Operating Systems Linux SuSE Help with RollBack options Post 302963734 by phanidhar6039 on Tuesday 5th of January 2016 10:46:16 AM
Old 01-05-2016
Help with RollBack options

Hi,

Recently we have patched our server to the highest level after which our application running on that server is having an issue with ssl handshake as below between 2 hosts. same error is also generated when checked from other host.

Code:
 Invalid/unknown SSL header was received from peer remote hostname  - < remote ip address> during SSL handshake

So the application team has asked us to roll back the changes.

we are running SUSE LINUX 11.3

so could any one let me know how can we resolve the ssl error or perform rollback to same state before applying patches.

Thanks,
P
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

options

I am just beginning to learn unix and I was wondering if there was a list of all the options somewhere on the net or hidden in the man pages? Also do options always have - and then a letter, or can it be - and a number as well? Thanks! (1 Reply)
Discussion started by: terms5
1 Replies

2. AIX

no options

Hi All, I have a situation here that's very fun... I have a system with AIX and iPlanet (sunOne) installed, when occurs an unknown event on the network the WebServer shows a thousand of CLOSE_WAIT connections and this number grows and grows until the webserver crashs. I read some documents... (2 Replies)
Discussion started by: nascimento.rp
2 Replies

3. Post Here to Contact Site Administrators and Moderators

Have we just had a rollback of a few hours?

Have we just had a rollback of a few hours? (1 Reply)
Discussion started by: porter
1 Replies

4. UNIX for Dummies Questions & Answers

RPM Package - Rollback

Is it possible to rollback a package in Redhat ?I don't want to delete any packages. I have upgraded a package using rpm -Uvh & now i decided to use the old package, is it possible to revert it back to the original package ? (3 Replies)
Discussion started by: sydney2008
3 Replies

5. Emergency UNIX and Linux Support

/var/log/wtmp SuSE log permission rollback

Hello All, On my SuSE system, I have wtmp log this log file permission is 644 but every reboot the file permission rollback to 664. In the logrotate.conf and logrotate.d/wtmp files the wtmp logrotate set to 644. I would like to know, which "file" or "script" modify the wtmp log to rollback to... (7 Replies)
Discussion started by: kalaso
7 Replies

6. Solaris

zfs rollback

i created a snapshot as follow as bash-3.00# zfs snapshot dinu/dinu1@dinusnap1 then i deleted the contents in the directory dinu1 now i want to rollback that contents from snapshot and i used bash-3.00# zfs rollback dinu/dinu1/@dinusnap1 but i received error as follow as cannot... (3 Replies)
Discussion started by: dinu
3 Replies

7. Ubuntu

Kernel boot options removed by fault, no boot options

Hello Everyone, First of all, I highly appreciate all Linux forum members and whole Linux community. http://forums.linuxmint.com/images/smilies/icon_wink.gif. I wish you the best for all of you ! I will try to be short and concise: I am using Linux Mint 10 for 2 months on 2 ws, and all went... (3 Replies)
Discussion started by: cdt
3 Replies
SSL_connect(3)							      OpenSSL							    SSL_connect(3)

NAME
SSL_connect - initiate the TLS/SSL handshake with an TLS/SSL server SYNOPSIS
#include <openssl/ssl.h> int SSL_connect(SSL *ssl); DESCRIPTION
SSL_connect() initiates the TLS/SSL handshake with a server. The communication channel must already have been set and assigned to the ssl by setting an underlying BIO. NOTES
The behaviour of SSL_connect() depends on the underlying BIO. If the underlying BIO is blocking, SSL_connect() will only return once the handshake has been finished or an error occurred. If the underlying BIO is non-blocking, SSL_connect() will also return when the underlying BIO could not satisfy the needs of SSL_connect() to continue the handshake. In this case a call to SSL_get_error() with the return value of SSL_connect() will yield SSL_ERROR_WANT_READ or SSL_ERROR_WANT_WRITE. The calling process then must repeat the call after taking appropriate action to satisfy the needs of SSL_connect(). The action depends on the underlying BIO. When using a non-blocking socket, nothing is to be done, but select() can be used to check for the required condition. When using a buffering BIO, like a BIO pair, data must be written into or retrieved out of the BIO before being able to continue. RETURN VALUES
The following return values can occur: 1 The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been established. 0 The TLS/SSL handshake was not successful but was shut down controlled and by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the return value ret to find out the reason. <0 The TLS/SSL handshake was not successful, because a fatal error occurred either at the protocol level or a connection failure occurred. The shutdown was not clean. It can also occur of action is need to continue the operation for non-blocking BIOs. Call SSL_get_error() with the return value ret to find out the reason. SEE ALSO
SSL_get_error(3), SSL_accept(3), SSL_shutdown(3), ssl(3), bio(3), SSL_set_connect_state(3), SSL_do_handshake(3), SSL_CTX_new(3) 0.9.7a 2002-07-19 SSL_connect(3)
All times are GMT -4. The time now is 01:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy