Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1199133

Summary: vds.MultiProtocolAcceptor WARNING Unrecognized protocol: ''
Product: Red Hat Enterprise Virtualization Manager Reporter: Douglas Schilling Landgraf <dougsland>
Component: vdsmAssignee: Piotr Kliczewski <pkliczew>
Status: CLOSED WORKSFORME QA Contact: Aharon Canan <acanan>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.5.1CC: bazulay, cshao, danken, dougsland, ecohen, fdeutsch, gklein, hadong, huiwa, iheim, leiwang, lpeer, lsurette, oourfali, rbarry, yaniwang, ybronhei, ycui, yeylon
Target Milestone: ---   
Target Release: 3.5.1   
Hardware: All   
OS: Linux   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-16 07:57:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1199035    
Attachments:
Description Flags
logs
none
login-failed.tar.gz none

Description Douglas Schilling Landgraf 2015-03-05 13:55:13 UTC 
Description of problem:

vdsm is unable to execute handshake protocol. This is affecting communication between ovirt-node-plugin-vdsm and vdsm. For the record, original bug report: bz#1198029

messages
==========
Mar  3 05:46:24 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: ''
Mar  3 05:46:27 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: ''
Mar  3 05:46:30 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: ''
Mar  3 05:46:30 localhost journal: Forwarding to syslog missed 42 messages.
Mar  3 05:46:33 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: ''
Mar  3 05:46:36 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: ''
Mar  3 05:46:39 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: ''
Mar  3 05:46:42 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: ''
Mar  3 05:46:45 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: ''
Mar  3 05:46:48 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: ''
Mar  3 05:46:51 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: ''
Mar  3 05:46:54 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: ''
Mar  3 05:46:57 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: ''
Mar  3 05:47:00 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: ''
Mar  3 05:47:00 localhost journal: Forwarding to syslog missed 10 messages.
Mar  3 05:47:03 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: ''
Mar  3 05:47:06 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: ''
Mar  3 05:47:09 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: ''
Mar  3 05:47:12 localhost journal: vdsm vds.MultiProtocolAcceptor WARNING Unrecognized protocol: ''
Mar  3 05:47:13 localhost python: Error in communication with subscription manager, trying to recover:
Mar  3 05:47:13 localhost python: Unable to recover, retry in 60 seconds.


vdsm.log
=============
storageRefresh::DEBUG::2015-02-27 08:28:03,047::lvm::416::Storage.OperationMutex::(_reloadvgs) Operation 'lvm reload operation' released the operation mutex
storageRefresh::DEBUG::2015-02-27 08:28:03,047::hsm::410::Storage.HSM::(storageRefresh) HSM is ready
Detector thread::DEBUG::2015-02-27 08:28:03,348::protocoldetector::187::vds.MultiProtocolAcceptor::(_add_connection) Adding connection from 10.66.109.77:44889
Detector thread::DEBUG::2015-02-27 08:28:03,378::protocoldetector::207::vds.MultiProtocolAcceptor::(_process_handshake) Error during handshake: sslv3 alert certificate unknown
Detector thread::DEBUG::2015-02-27 08:28:03,378::protocoldetector::201::vds.MultiProtocolAcceptor::(_remove_connection) Connection removed from 10.66.109.77:44889
Detector thread::WARNING::2015-02-27 08:28:03,379::protocoldetector::241::vds.MultiProtocolAcceptor::(_handle_connection_read) Unrecognized protocol: ''
Detector thread::DEBUG::2015-02-27 08:28:06,402::protocoldetector::187::vds.MultiProtocolAcceptor::(_add_connection) Adding connection from 10.66.109.77:58982
Detector thread::DEBUG::2015-02-27 08:28:06,406::protocoldetector::207::vds.MultiProtocolAcceptor::(_process_handshake) Error during handshake: sslv3 alert certificate unknown
Detector thread::DEBUG::2015-02-27 08:28:06,407::protocoldetector::201::vds.MultiProtocolAcceptor::(_remove_connection) Connection removed from 10.66.109.77:58982
Detector thread::WARNING::2015-02-27 08:28:06,407::protocoldetector::241::vds.MultiProtocolAcceptor::(_handle_connection_read) Unrecognized protocol: ''
Detector thread::DEBUG::2015-02-27 08:28:09,428::protocoldetector::187::vds.MultiProtocolAcceptor::(_add_connection) Adding connection from 10.66.109.77:47584
Detector thread::DEBUG::2015-02-27 08:28:09,431::protocoldetector::207::vds.MultiProtocolAcceptor::(_process_handshake) Error during handshake: sslv3 alert certificate unknown
Detector thread::DEBUG::2015-02-27 08:28:09,431::protocoldetector::201::vds.MultiProtocolAcceptor::(_remove_connection) Connection removed from 10.66.109.77:47584
Detector thread::WARNING::2015-02-27 08:28:09,432::protocoldetector::241::vds.MultiProtocolAcceptor::(_handle_connection_read) Unrecognized protocol: ''
Detector thread::DEBUG::2015-02-27 08:28:12,457::protocoldetector::187::vds.MultiProtocolAcceptor::(_add_connection) Adding connection from 10.66.109.77:33782
Detector thread::DEBUG::2015-02-27 08:28:12,460::protocoldetector::207::vds.MultiProtocolAcceptor::(_process_handshake) Error during handshake: sslv3 alert certificate unknown
Comment 1 Piotr Kliczewski 2015-03-05 14:04:47 UTC 
It seems that sslv3 cert is unknown. Can you please change your protocol setting to tls and see whether the issue still occurs?
Comment 2 Douglas Schilling Landgraf 2015-03-05 14:05:18 UTC 
Created attachment 998387 [details]
logs
Comment 3 Douglas Schilling Landgraf 2015-03-05 14:08:30 UTC 
Hello shaochen,

(In reply to Piotr Kliczewski from comment #1)
> It seems that sslv3 cert is unknown. Can you please change your protocol
> setting to tls and see whether the issue still occurs?

As you found this bug and if you still have this machine available could you please provide all data needed to Piotr.

Thanks!
Comment 4 Douglas Schilling Landgraf 2015-03-05 14:11:23 UTC 
Hi Shaochen,

Could you please also provide the VDSM and Engine version that you have in your systems?

Thanks
Comment 5 Piotr Kliczewski 2015-03-05 14:15:39 UTC 
Please update vdsm configuration in config.py and change value of ssl_protocol to 'tlsv1'.

Please set engine configuration of VdsmSSLProtocol config in vdc_options to 'TLSv1'.
Comment 7 cshao 2015-03-06 02:21:49 UTC 
(In reply to Douglas Schilling Landgraf from comment #3)
> Hello shaochen,

> As you found this bug and if you still have this machine available could you
> please provide all data needed to Piotr.
> Thanks!

The env has gone due to new build testing, but all log (/var/log/*.*) still available, no sosreport due to bug1197302, please see attachment.

> Hi Shaochen,
> Could you please also provide the VDSM and Engine version that you have in your > systems?
> Thanks

Test version:
rhev-hypervisor7-7.1-20150226.0.el7ev
ovirt-node-3.2.1-7.el7.noarch 
vdsm-4.16.12-2.el7ev.x86_64
rhevm-3.5.0-0.32.el6ev

How reproducible:
Only met once
Comment 8 cshao 2015-03-06 02:33:44 UTC 
Created attachment 998635 [details]
login-failed.tar.gz
Comment 9 Oved Ourfali 2015-03-16 07:57:20 UTC 
Closing - please reopen it is occurs again. Make sure you set the proper settings as mentioned by Piotr in Comment #5.
Also, removing blocking other bug, as the bug it was blocking is already on_qa.