Re: [ovirt-users] ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages General SSLEngine problem

2017-09-03 Thread Piotr Kliczewski
Gary,

Looking at your engine log I see this: Unable to process messages
General SSLEngine problem.
It means that you have an issue with establishing secure connection.
In order to understand more details about your failure please set log
level to debug by doing [1].
Once you enable it please provide more information why engine fails to
talk to vdsm.

Thanks,
Piotr

[1] 
http://www.ovirt.org/develop/developer-guide/engine/engine-development-environment/#enable-debug-log---restart-required

On Fri, Sep 1, 2017 at 10:40 PM, Gary Balliet  wrote:
> Good day all.
>
> Just playing with ovirt. New to it but seems quite good.
>
> Single instance/nfs share/centos7/ovirt 4.1
>
>
>
> Had a power outage and this error message is in my logs whilst trying to
> activate a downed host.  The snippet below is from engine.log.
>
> 2017-09-01 13:32:03,092-07 INFO
> [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor)
> [] Connecting to /192.168.1.147
> 2017-09-01 13:32:03,097-07 ERROR
> [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) []
> Unable to process messages General SSLEngine problem
> 2017-09-01 13:32:04,547-07 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand]
> (DefaultQuartzScheduler5) [77a871f9-4947-46c9-977f-db5f76cac358] Command
> 'GetAllVmStatsVDSCommand(HostName = DellServer,
> VdsIdVDSCommandParametersBase:{runAsync='true',
> hostId='b8ceb86f-c4e1-4bbd-afad-5044ebe9eddd'})' execution failed:
> VDSGenericException: VDSNetworkException: General SSLEngine problem
> 2017-09-01 13:32:04,547-07 INFO
> [org.ovirt.engine.core.vdsbroker.monitoring.PollVmStatsRefresher]
> (DefaultQuartzScheduler5) [77a871f9-4947-46c9-977f-db5f76cac358] Failed to
> fetch vms info for host 'DellServer' - skipping VMs monitoring.
> 2017-09-01 13:32:19,548-07 INFO
> [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor)
> [] Connecting to /192.168.1.147
> 2017-09-01 13:32:19,552-07 ERROR
> [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) []
> Unable to process messages General SSLEngine problem
> 2017-09-01 13:32:23,115-07 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (DefaultQuartzScheduler4) [77a871f9-4947-46c9-977f-db5f76cac358] EVENT_ID:
> VDS_BROKER_COMMAND_FAILURE(10,802), Correlation ID: null, Call Stack: null,
> Custom Event ID: -1, Message: VDSM DellServer command GetCapabilitiesVDS
> failed: General SSLEngine problem
> 2017-09-01 13:32:23,115-07 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
> (DefaultQuartzScheduler4) [77a871f9-4947-46c9-977f-db5f76cac358] Command
> 'org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand' return
> value 'org.ovirt.engine.core.vdsbroker.vdsbroker.VDSInfoReturn@65b16430'
> 2017-09-01 13:32:23,115-07 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
> (DefaultQuartzScheduler4) [77a871f9-4947-46c9-977f-db5f76cac358] HostName =
> DellServer
> 2017-09-01 13:32:23,116-07 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
> (DefaultQuartzScheduler4) [77a871f9-4947-46c9-977f-db5f76cac358] Command
> 'GetCapabilitiesVDSCommand(HostName = DellServer,
> VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
> hostId='b8ceb86f-c4e1-4bbd-afad-5044ebe9eddd',
> vds='Host[DellServer,b8ceb86f-c4e1-4bbd-afad-5044ebe9eddd]'})' execution
> failed: VDSGenericException: VDSNetworkException: General SSLEngine problem
> 2017-09-01 13:32:23,116-07 ERROR
> [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]
> (DefaultQuartzScheduler4) [77a871f9-4947-46c9-977f-db5f76cac358] Failure to
> refresh host 'DellServer' runtime info: VDSGenericException:
> VDSNetworkException: General SSLEngine problem
> 2017-09-01 13:32:26,118-07 INFO
> [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor)
> [] Connecting to /192.168.1.147
> 2017-09-01 13:32:26,122-07 ERROR
> [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) []
> Unable to process messages General SSLEngine problem
> 2017-09-01 13:32:39,550-07 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand]
> (DefaultQuartzScheduler1) [77a871f9-4947-46c9-977f-db5f76cac358] Command
> 'GetAllVmStatsVDSCommand(HostName = DellServer,
> VdsIdVDSCommandParametersBase:{runAsync='true',
> hostId='b8ceb86f-c4e1-4bbd-afad-5044ebe9eddd'})' execution failed:
> VDSGenericException: VDSNetworkException: General SSLEngine problem
> 2017-09-01 13:32:39,551-07 INFO
> [org.ovirt.engine.core.vdsbroker.monitoring.PollVmStatsRefresher]
> (DefaultQuartzScheduler1) [77a871f9-4947-46c9-977f-db5f76cac358] Failed to
> fetch vms info for host 'DellServer' - skipping VMs monitoring.
> 2017-09-01 13:32:46,125-07 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (DefaultQuartzScheduler7) [77a871f9-4947-46c9-977f-db5f76cac358] EVENT_ID:
> 

[ovirt-users] ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages General SSLEngine problem

2017-09-01 Thread Gary Balliet
Good day all.

Just playing with ovirt. New to it but seems quite good.

Single instance/nfs share/centos7/ovirt 4.1



Had a power outage and this error message is in my logs whilst trying to
activate a downed host.  The snippet below is from engine.log.

2017-09-01 13:32:03,092-07 INFO
 [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor)
[] Connecting to /192.168.1.147
2017-09-01 13:32:03,097-07 ERROR
[org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) []
Unable to process messages General SSLEngine problem
2017-09-01 13:32:04,547-07 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand]
(DefaultQuartzScheduler5) [77a871f9-4947-46c9-977f-db5f76cac358] Command
'GetAllVmStatsVDSCommand(HostName = DellServer,
VdsIdVDSCommandParametersBase:{runAsync='true',
hostId='b8ceb86f-c4e1-4bbd-afad-5044ebe9eddd'})' execution failed:
VDSGenericException: VDSNetworkException: General SSLEngine problem
2017-09-01 13:32:04,547-07 INFO
 [org.ovirt.engine.core.vdsbroker.monitoring.PollVmStatsRefresher]
(DefaultQuartzScheduler5) [77a871f9-4947-46c9-977f-db5f76cac358] Failed to
fetch vms info for host 'DellServer' - skipping VMs monitoring.
2017-09-01 13:32:19,548-07 INFO
 [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor)
[] Connecting to /192.168.1.147
2017-09-01 13:32:19,552-07 ERROR
[org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) []
Unable to process messages General SSLEngine problem
2017-09-01 13:32:23,115-07 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(DefaultQuartzScheduler4) [77a871f9-4947-46c9-977f-db5f76cac358] EVENT_ID:
VDS_BROKER_COMMAND_FAILURE(10,802), Correlation ID: null, Call Stack: null,
Custom Event ID: -1, Message: VDSM DellServer command GetCapabilitiesVDS
failed: General SSLEngine problem
2017-09-01 13:32:23,115-07 INFO
 [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
(DefaultQuartzScheduler4) [77a871f9-4947-46c9-977f-db5f76cac358] Command
'org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand'
return value
'org.ovirt.engine.core.vdsbroker.vdsbroker.VDSInfoReturn@65b16430'
2017-09-01 13:32:23,115-07 INFO
 [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
(DefaultQuartzScheduler4) [77a871f9-4947-46c9-977f-db5f76cac358] HostName =
DellServer
2017-09-01 13:32:23,116-07 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
(DefaultQuartzScheduler4) [77a871f9-4947-46c9-977f-db5f76cac358] Command
'GetCapabilitiesVDSCommand(HostName = DellServer,
VdsIdAndVdsVDSCommandParametersBase:{runAsync='true',
hostId='b8ceb86f-c4e1-4bbd-afad-5044ebe9eddd',
vds='Host[DellServer,b8ceb86f-c4e1-4bbd-afad-5044ebe9eddd]'})' execution
failed: VDSGenericException: VDSNetworkException: General SSLEngine problem
2017-09-01 13:32:23,116-07 ERROR
[org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]
(DefaultQuartzScheduler4) [77a871f9-4947-46c9-977f-db5f76cac358] Failure to
refresh host 'DellServer' runtime info: VDSGenericException:
VDSNetworkException: General SSLEngine problem
2017-09-01 13:32:26,118-07 INFO
 [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor)
[] Connecting to /192.168.1.147
2017-09-01 13:32:26,122-07 ERROR
[org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) []
Unable to process messages General SSLEngine problem
2017-09-01 13:32:39,550-07 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand]
(DefaultQuartzScheduler1) [77a871f9-4947-46c9-977f-db5f76cac358] Command
'GetAllVmStatsVDSCommand(HostName = DellServer,
VdsIdVDSCommandParametersBase:{runAsync='true',
hostId='b8ceb86f-c4e1-4bbd-afad-5044ebe9eddd'})' execution failed:
VDSGenericException: VDSNetworkException: General SSLEngine problem
2017-09-01 13:32:39,551-07 INFO
 [org.ovirt.engine.core.vdsbroker.monitoring.PollVmStatsRefresher]
(DefaultQuartzScheduler1) [77a871f9-4947-46c9-977f-db5f76cac358] Failed to
fetch vms info for host 'DellServer' - skipping VMs monitoring.
2017-09-01 13:32:46,125-07 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(DefaultQuartzScheduler7) [77a871f9-4947-46c9-977f-db5f76cac358] EVENT_ID:
VDS_BROKER_COMMAND_FAILURE(10,802), Correlation ID: null, Call Stack: null,
Custom Event ID: -1, Message: VDSM DellServer command GetCapabilitiesVDS
failed: General SSLEngine problem
2017-09-01 13:32:46,125-07 INFO
 [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
(DefaultQuartzScheduler7) [77a871f9-4947-46c9-977f-db5f76cac358] Command
'org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand'
return value
'org.ovirt.engine.core.vdsbroker.vdsbroker.VDSInfoReturn@64999c2a'
2017-09-01 13:32:46,125-07 INFO
 [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
(DefaultQuartzScheduler7) [77a871f9-4947-46c9-977f-db5f76cac358] HostName =
DellServer
2017-09-01 13:32:46,125-07 ERROR

Re: [ovirt-users] ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages

2016-07-26 Thread Martin Perina
On Tue, Jul 26, 2016 at 5:39 PM, Jiri Belka  wrote:

> > Hi,
> >
> > Unfortunately, upgrading to 4.0.1RC didn't solve the problem. Actually,
> > the error changed to 'General SSLEngine problem', but the result was the
> > same, like this:
> >
> > 2016-07-13 09:52:22,010 INFO
> > [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp
> > Reactor) [] Connecting to /10.X.X.X
> > 2016-07-13 09:52:22,018 ERROR
> > [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) []
> > Unable to process messages: General SSLEngine problem
> >
> > It's worth mentioning that we're using our own SSL certificates (not
> > self-signed), and I imported the combined certificate into the
> > /etc/pki/ovirt-engine/.truststore key file. Not sure if related, but
> > just in case.
> >
> > I had to downgrade to 3.6.7. I'm attaching requested logs, if you need
> > anything else don't hesitate to ask.
>
>
> FYI I migrated my 3.6 env (engine + 1 host) to 4.0 and the host is up
> and running fine on datacenter/cluster 4.0 compat level.
>
> FYA there's a BZ about engine certs
> https://bugzilla.redhat.com/show_bug.cgi?id=1336838


​We should mention​
​ that above bug described how to use custom HTTPS certificate signed by
custom CA. But even if this is configured, all communication between engine
and host will still use certificate signed by internal oVirt CA.


>
> j.
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages

2016-07-26 Thread Jiri Belka
> > Unfortunately, upgrading to 4.0.1RC didn't solve the problem. Actually,
> > the error changed to 'General SSLEngine problem', but the result was the
> > same, like this:
> > 
> > 2016-07-13 09:52:22,010 INFO
> > [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp
> > Reactor) [] Connecting to /10.X.X.X
> > 2016-07-13 09:52:22,018 ERROR
> > [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) []
> > Unable to process messages: General SSLEngine problem
> > 
> > It's worth mentioning that we're using our own SSL certificates (not
> > self-signed), and I imported the combined certificate into the
> > /etc/pki/ovirt-engine/.truststore key file. Not sure if related, but
> > just in case.
> > 
> > I had to downgrade to 3.6.7. I'm attaching requested logs, if you need
> > anything else don't hesitate to ask.
> 
> 
> FYI I migrated my 3.6 env (engine + 1 host) to 4.0 and the host is up
> and running fine on datacenter/cluster 4.0 compat level.
> 
> FYA there's a BZ about engine certs
> https://bugzilla.redhat.com/show_bug.cgi?id=1336838

Ah, I forgot to mention that I used my own CA and thus custom certificate
for Apache httpd.

j.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages

2016-07-26 Thread Jiri Belka
> Hi,
> 
> Unfortunately, upgrading to 4.0.1RC didn't solve the problem. Actually,
> the error changed to 'General SSLEngine problem', but the result was the
> same, like this:
> 
> 2016-07-13 09:52:22,010 INFO
> [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp
> Reactor) [] Connecting to /10.X.X.X
> 2016-07-13 09:52:22,018 ERROR
> [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) []
> Unable to process messages: General SSLEngine problem
> 
> It's worth mentioning that we're using our own SSL certificates (not
> self-signed), and I imported the combined certificate into the
> /etc/pki/ovirt-engine/.truststore key file. Not sure if related, but
> just in case.
> 
> I had to downgrade to 3.6.7. I'm attaching requested logs, if you need
> anything else don't hesitate to ask.


FYI I migrated my 3.6 env (engine + 1 host) to 4.0 and the host is up
and running fine on datacenter/cluster 4.0 compat level.

FYA there's a BZ about engine certs 
https://bugzilla.redhat.com/show_bug.cgi?id=1336838

j.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages

2016-07-25 Thread Sandro Bonazzola
On Mon, Jul 25, 2016 at 11:40 AM, Piotr Kliczewski <
piotr.kliczew...@gmail.com> wrote:

> I remember an issue that engine upgrade corrupted certificates and
> "General SSLEngine problem" may be indication that you saw it.
> I asked to open BZ for it but was unable to find it.
>
> @Sandro @Simone was it fixed already?
>

I've vague memories of something related being fixed, but without a bug
number I can't tell for sure.
Adding also Didi, since ssl / pki is his area and he may be aware.




>
> On Thu, Jul 21, 2016 at 3:18 PM, Martin Perina  wrote:
> > Thanks a lot for you effort, I'm glad that you were able to upgrade
> > successfully although we were not able to find the cause for the issue
> :-(
> >
> > On Thu, Jul 21, 2016 at 2:30 PM,  wrote:
> >>
> >> So I gave it another try and this time it worked without any issue (with
> >> 4.0.1.1 version). Strange, maybe the first upgrade failure left system
> in a
> >> weird state? Anyhow almost everything ([1]) is working fine now. Thanks
> for
> >> the help!
> >>
> >>   [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1358737
> >
> >
> > Adding Tomas about this one
> >
> >>
> >>
> >> El 2016-07-20 20:23, Martin Perina escribió:
> >>>
> >>> On Wed, Jul 20, 2016 at 6:18 PM, Nicolás  wrote:
> >>>
>  El 20/07/16 a las 16:45, Martin Perina escribió:
> 
>  On Wed, Jul 20, 2016 at 4:44 PM, Nicolás  wrote:
> 
>  Hi Martin,
> 
>  Actually, up until now we had that cert configured in httpd and in
>  websocket proxy. Seems that now in 4.0.x it's not enough, as opening
>  the https://fqdn [1] complains about the cert not being imported in
>  the key chain.
> 
>  Yes, there's an updated procedure on using external CA in 4.0,
>  for details please take a look at Doc Text in
> 
>  https://bugzilla.redhat.com/show_bug.cgi?id=1336838 [2]
> 
>  So I imported it via keytool, but I don't want to use it in the
>  engine <-> VDSM communication.
> 
>  Hmm, so that would imply that we have some issue with existing
>  internal enigne CA during upgrade ...
> 
>  The strange thing is that we test upgrades a lot but so far we
>  haven't seen any issues which will broke
> 
>  SSL setup between engine and VDSM. You said that you had to
>  downgrade back to 3.6.7 (so unfortunately for us we cannot
>  investigate your nonworking setup more), but how did you do that?
> 
>  Removing all engine packages and configuration, installing back
>  3.6.7 packaging and restoring configuration form backup?
> 
>  I'm asking to know what changed in your setup between not working
>  4.0 and working 3.6.7 ...
> >>>
> >>>
> >>>  Indeed, those are the steps I followed to the point.
> >>>
> >>>  To add more strangeness, previously to upgrading this oVirt
> >>> infrastructure, we upgraded another one that we have (also using own
> >>> cert, a different one but from the same CA) and everything went
> >>> smoothly. And what's more, previously to upgrading the engine that
> >>> failed, I created a copy of that engine machine in a sandbox
> >>> environment to see if upgrade process would or not success, and it
> >>> worked perfectly.
> >>>
> >>>  The only difference between the sandbox and the real machine's
> >>> process was that when upgrading the real one, the first time I run
> >>> "engine-setup" it failed because 'systemd' reported PostgreSQL as it
> >>> was not running (actually it was, thougg), so everything rolled back.
> >>> I had to kill the PostgreSQL process, start it again with systemctl
> >>> and then run "engine-setup", where the process completed successfully
> >>> but the SSL issue appeared. Not sure if this rollback could have
> >>> shattered the whole thing...
> >>>
> >>>  Anyhow, tomorrow I'm going to create another copy of the engine
> >>> machine to a sandbox environment and try again. If it works I'll cross
> >>> my fingers and give another try on the real machine...
> >>>
> >>>  Thanks!
> >>>
> >>> Thanks a lot for you effort. I will try to perform same upgrade
> >>> tomorrow in my test env.
> >>>
> >>>
>  Thanks
> 
>  Martin
> 
>  Thanks!
>  En 20/7/2016 2:48 p. m., Martin Perina 
>  escribió:
> 
>  Hi,
> 
>  sorry for late response, I overlook your reply :-(
> 
>  I looked at your logs and it seems to me that there's SSL
>  error when engine tries to contact VDSM.
> 
>  You have mentioned that your are using your own custom CA. Are
>  you using it only for HTTPS certificate or do you want to use it
>  also for Engine <-> VDSM communication?
> 
> 
>  Martin Perina
> 
> 
> 
>  On Wed, Jul 20, 2016 at 9:18 AM,  wrote:
>  Any hints about this?
> 
>  El 2016-07-13 11:13, nico...@devels.es escribió:
>  Hi,
> 
>  

Re: [ovirt-users] ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages

2016-07-25 Thread Piotr Kliczewski
I remember an issue that engine upgrade corrupted certificates and
"General SSLEngine problem" may be indication that you saw it.
I asked to open BZ for it but was unable to find it.

@Sandro @Simone was it fixed already?

On Thu, Jul 21, 2016 at 3:18 PM, Martin Perina  wrote:
> Thanks a lot for you effort, I'm glad that you were able to upgrade
> successfully although we were not able to find the cause for the issue :-(
>
> On Thu, Jul 21, 2016 at 2:30 PM,  wrote:
>>
>> So I gave it another try and this time it worked without any issue (with
>> 4.0.1.1 version). Strange, maybe the first upgrade failure left system in a
>> weird state? Anyhow almost everything ([1]) is working fine now. Thanks for
>> the help!
>>
>>   [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1358737
>
>
> Adding Tomas about this one
>
>>
>>
>> El 2016-07-20 20:23, Martin Perina escribió:
>>>
>>> On Wed, Jul 20, 2016 at 6:18 PM, Nicolás  wrote:
>>>
 El 20/07/16 a las 16:45, Martin Perina escribió:

 On Wed, Jul 20, 2016 at 4:44 PM, Nicolás  wrote:

 Hi Martin,

 Actually, up until now we had that cert configured in httpd and in
 websocket proxy. Seems that now in 4.0.x it's not enough, as opening
 the https://fqdn [1] complains about the cert not being imported in
 the key chain.

 Yes, there's an updated procedure on using external CA in 4.0,
 for details please take a look at Doc Text in

 https://bugzilla.redhat.com/show_bug.cgi?id=1336838 [2]

 So I imported it via keytool, but I don't want to use it in the
 engine <-> VDSM communication.

 Hmm, so that would imply that we have some issue with existing
 internal enigne CA during upgrade ...

 The strange thing is that we test upgrades a lot but so far we
 haven't seen any issues which will broke

 SSL setup between engine and VDSM. You said that you had to
 downgrade back to 3.6.7 (so unfortunately for us we cannot
 investigate your nonworking setup more), but how did you do that?

 Removing all engine packages and configuration, installing back
 3.6.7 packaging and restoring configuration form backup?

 I'm asking to know what changed in your setup between not working
 4.0 and working 3.6.7 ...
>>>
>>>
>>>  Indeed, those are the steps I followed to the point.
>>>
>>>  To add more strangeness, previously to upgrading this oVirt
>>> infrastructure, we upgraded another one that we have (also using own
>>> cert, a different one but from the same CA) and everything went
>>> smoothly. And what's more, previously to upgrading the engine that
>>> failed, I created a copy of that engine machine in a sandbox
>>> environment to see if upgrade process would or not success, and it
>>> worked perfectly.
>>>
>>>  The only difference between the sandbox and the real machine's
>>> process was that when upgrading the real one, the first time I run
>>> "engine-setup" it failed because 'systemd' reported PostgreSQL as it
>>> was not running (actually it was, thougg), so everything rolled back.
>>> I had to kill the PostgreSQL process, start it again with systemctl
>>> and then run "engine-setup", where the process completed successfully
>>> but the SSL issue appeared. Not sure if this rollback could have
>>> shattered the whole thing...
>>>
>>>  Anyhow, tomorrow I'm going to create another copy of the engine
>>> machine to a sandbox environment and try again. If it works I'll cross
>>> my fingers and give another try on the real machine...
>>>
>>>  Thanks!
>>>
>>> Thanks a lot for you effort. I will try to perform same upgrade
>>> tomorrow in my test env.
>>>
>>>
 Thanks

 Martin

 Thanks!
 En 20/7/2016 2:48 p. m., Martin Perina 
 escribió:

 Hi,

 sorry for late response, I overlook your reply :-(

 I looked at your logs and it seems to me that there's SSL
 error when engine tries to contact VDSM.

 You have mentioned that your are using your own custom CA. Are
 you using it only for HTTPS certificate or do you want to use it
 also for Engine <-> VDSM communication?


 Martin Perina



 On Wed, Jul 20, 2016 at 9:18 AM,  wrote:
 Any hints about this?

 El 2016-07-13 11:13, nico...@devels.es escribió:
 Hi,

 Unfortunately, upgrading to 4.0.1RC didn't solve the problem.
 Actually, the error changed to 'General SSLEngine problem', but the
 result was the same, like this:

 2016-07-13 09:52:22,010 INFO
 [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp
 Reactor) [] Connecting to /10.X.X.X
 2016-07-13 09:52:22,018 ERROR
 [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp
 Reactor)
 [] Unable to process messages: General SSLEngine problem

 It's worth mentioning 

Re: [ovirt-users] ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages

2016-07-21 Thread Martin Perina
Thanks a lot for you effort, I'm glad that you were able to upgrade
successfully although we were not able to find the cause for the issue :-(

On Thu, Jul 21, 2016 at 2:30 PM,  wrote:

> So I gave it another try and this time it worked without any issue (with
> 4.0.1.1 version). Strange, maybe the first upgrade failure left system in a
> weird state? Anyhow almost everything ([1]) is working fine now. Thanks for
> the help!
>
>   [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1358737
>

​Adding Tomas about this one
​


>
> El 2016-07-20 20:23, Martin Perina escribió:
>
>> On Wed, Jul 20, 2016 at 6:18 PM, Nicolás  wrote:
>>
>> El 20/07/16 a las 16:45, Martin Perina escribió:
>>>
>>> On Wed, Jul 20, 2016 at 4:44 PM, Nicolás  wrote:
>>>
>>> Hi Martin,
>>>
>>> Actually, up until now we had that cert configured in httpd and in
>>> websocket proxy. Seems that now in 4.0.x it's not enough, as opening
>>> the https://fqdn [1] complains about the cert not being imported in
>>> the key chain.
>>>
>>> ​Yes, there's an updated procedure on using external CA in 4.0,
>>> for details please take a look at Doc Text in
>>>
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1336838 [2]
>>> ​
>>> So I imported it via keytool, but I don't want to use it in the
>>> engine <-> VDSM communication.
>>>
>>> ​Hmm, so that would imply that we have some issue with existing
>>> internal enigne CA during upgrade ...
>>>
>>> The strange thing is that we test upgrades a lot but so far we
>>> haven't seen any issues which will broke
>>>
>>> SSL setup between engine and VDSM. You said that you had to
>>> downgrade back to 3.6.7 (so unfortunately for us we cannot
>>> investigate your nonworking setup more), but how did you do that?
>>>
>>> Removing all engine packages and configuration​, installing back
>>> 3.6.7 packaging and restoring configuration form backup?
>>>
>>> I'm asking to know what changed in your setup between not working
>>> 4.0 and working 3.6.7 ...
>>>
>>
>>  Indeed, those are the steps I followed to the point.
>>
>>  To add more strangeness, previously to upgrading this oVirt
>> infrastructure, we upgraded another one that we have (also using own
>> cert, a different one but from the same CA) and everything went
>> smoothly. And what's more, previously to upgrading the engine that
>> failed, I created a copy of that engine machine in a sandbox
>> environment to see if upgrade process would or not success, and it
>> worked perfectly.
>>
>>  The only difference between the sandbox and the real machine's
>> process was that when upgrading the real one, the first time I run
>> "engine-setup" it failed because 'systemd' reported PostgreSQL as it
>> was not running (actually it was, thougg), so everything rolled back.
>> I had to kill the PostgreSQL process, start it again with systemctl
>> and then run "engine-setup", where the process completed successfully
>> but the SSL issue appeared. Not sure if this rollback could have
>> shattered the whole thing...
>>
>>  Anyhow, tomorrow I'm going to create another copy of the engine
>> machine to a sandbox environment and try again. If it works I'll cross
>> my fingers and give another try on the real machine...
>>
>>  Thanks!
>>
>> ​Thanks a lot for you effort. I will try to perform same upgrade
>> tomorrow in my test env.
>> ​
>>
>> Thanks
>>>
>>> Martin
>>>
>>> Thanks!
>>> En 20/7/2016 2:48 p. m., Martin Perina 
>>> escribió:
>>>
>>> Hi,
>>>
>>> sorry for late response, I overlook your reply :-(
>>>
>>> ​I looked at your logs and it seems to me that​ there's SSL
>>> error when engine tries to contact VDSM.
>>>
>>> ​You have mentioned that your are using your own custom CA. ​Are
>>> you using it only for HTTPS certificate or do you want to use it
>>> also for Engine <-> VDSM communication?
>>> ​
>>>
>>> Martin Perina
>>>
>>>
>>>
>>> On Wed, Jul 20, 2016 at 9:18 AM,  wrote:
>>> Any hints about this?
>>>
>>> El 2016-07-13 11:13, nico...@devels.es escribió:
>>> Hi,
>>>
>>> Unfortunately, upgrading to 4.0.1RC didn't solve the problem.
>>> Actually, the error changed to 'General SSLEngine problem', but the
>>> result was the same, like this:
>>>
>>> 2016-07-13 09:52:22,010 INFO
>>> [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp
>>> Reactor) [] Connecting to /10.X.X.X
>>> 2016-07-13 09:52:22,018 ERROR
>>> [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp
>>> Reactor)
>>> [] Unable to process messages: General SSLEngine problem
>>>
>>> It's worth mentioning that we're using our own SSL certificates
>>> (not
>>> self-signed), and I imported the combined certificate into the
>>> /etc/pki/ovirt-engine/.truststore key file. Not sure if related,
>>> but
>>> just in case.
>>>
>>
>> I had to downgrade to 3.6.7. I'm attaching requested logs, if you
>>> need
>>> anything else don't hesitate to ask.
>>>
>>> Regards.
>>>
>>> El 2016-07-13 09:45, Martin Perina escribió:
>>> Hi,

Re: [ovirt-users] ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages

2016-07-21 Thread nicolas
So I gave it another try and this time it worked without any issue (with 
4.0.1.1 version). Strange, maybe the first upgrade failure left system 
in a weird state? Anyhow almost everything ([1]) is working fine now. 
Thanks for the help!


  [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1358737

El 2016-07-20 20:23, Martin Perina escribió:

On Wed, Jul 20, 2016 at 6:18 PM, Nicolás  wrote:


El 20/07/16 a las 16:45, Martin Perina escribió:

On Wed, Jul 20, 2016 at 4:44 PM, Nicolás  wrote:

Hi Martin,

Actually, up until now we had that cert configured in httpd and in
websocket proxy. Seems that now in 4.0.x it's not enough, as opening
the https://fqdn [1] complains about the cert not being imported in
the key chain.

​Yes, there's an updated procedure on using external CA in 4.0,
for details please take a look at Doc Text in

https://bugzilla.redhat.com/show_bug.cgi?id=1336838 [2]
​  
So I imported it via keytool, but I don't want to use it in the
engine <-> VDSM communication.

​Hmm, so that would imply that we have some issue with existing
internal enigne CA during upgrade ...

The strange thing is that we test upgrades a lot but so far we
haven't seen any issues which will broke

SSL setup between engine and VDSM. You said that you had to
downgrade back to 3.6.7 (so unfortunately for us we cannot
investigate your nonworking setup more), but how did you do that?

Removing all engine packages and configuration​, installing back
3.6.7 packaging and restoring configuration form backup?

I'm asking to know what changed in your setup between not working
4.0 and working 3.6.7 ...


 Indeed, those are the steps I followed to the point.

 To add more strangeness, previously to upgrading this oVirt
infrastructure, we upgraded another one that we have (also using own
cert, a different one but from the same CA) and everything went
smoothly. And what's more, previously to upgrading the engine that
failed, I created a copy of that engine machine in a sandbox
environment to see if upgrade process would or not success, and it
worked perfectly.

 The only difference between the sandbox and the real machine's
process was that when upgrading the real one, the first time I run
"engine-setup" it failed because 'systemd' reported PostgreSQL as it
was not running (actually it was, thougg), so everything rolled back.
I had to kill the PostgreSQL process, start it again with systemctl
and then run "engine-setup", where the process completed successfully
but the SSL issue appeared. Not sure if this rollback could have
shattered the whole thing...

 Anyhow, tomorrow I'm going to create another copy of the engine
machine to a sandbox environment and try again. If it works I'll cross
my fingers and give another try on the real machine...

 Thanks!

​Thanks a lot for you effort. I will try to perform same upgrade
tomorrow in my test env.
​ 


Thanks

Martin

Thanks!
En 20/7/2016 2:48 p. m., Martin Perina 
escribió:

Hi,

sorry for late response, I overlook your reply :-(

​I looked at your logs and it seems to me that​ there's SSL
error when engine tries to contact VDSM.

​You have mentioned that your are using your own custom CA. ​Are
you using it only for HTTPS certificate or do you want to use it
also for Engine <-> VDSM communication?
​

Martin Perina

 

On Wed, Jul 20, 2016 at 9:18 AM,  wrote:
Any hints about this?

El 2016-07-13 11:13, nico...@devels.es escribió:
Hi,

Unfortunately, upgrading to 4.0.1RC didn't solve the problem.
Actually, the error changed to 'General SSLEngine problem', but the
result was the same, like this:

2016-07-13 09:52:22,010 INFO
[org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp
Reactor) [] Connecting to /10.X.X.X
2016-07-13 09:52:22,018 ERROR
[org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp
Reactor)
[] Unable to process messages: General SSLEngine problem

It's worth mentioning that we're using our own SSL certificates
(not
self-signed), and I imported the combined certificate into the
/etc/pki/ovirt-engine/.truststore key file. Not sure if related,
but
just in case.



I had to downgrade to 3.6.7. I'm attaching requested logs, if you
need
anything else don't hesitate to ask.

Regards.

El 2016-07-13 09:45, Martin Perina escribió:
Hi,

could you please share also vdsm.log from your hosts and also
server.log and setup logs from /var/log/ovirt-engine/setup
directory?

Thanks

Martin Perina

On Wed, Jul 13, 2016 at 10:36 AM,  wrote:

Hi,

We upgraded from 3.6.6 to 4.0.0 and we have a big issue since the
engine cannot connect to hosts. In the logs all we see is this
error:

    ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL
Stomp Reactor) [] Unable to process messages

I'm attaching full logs.

Could someone help please?

Thanks.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users [3] [1]


Re: [ovirt-users] ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages

2016-07-20 Thread Martin Perina
On Wed, Jul 20, 2016 at 6:18 PM, Nicolás  wrote:

>
>
> El 20/07/16 a las 16:45, Martin Perina escribió:
>
>
>
> On Wed, Jul 20, 2016 at 4:44 PM, Nicolás  wrote:
>
>> Hi Martin,
>>
>> Actually, up until now we had that cert configured in httpd and in
>> websocket proxy. Seems that now in 4.0.x it's not enough, as opening the
>> https://fqdn complains about the cert not being imported in the key
>> chain.
>>
>
> ​Yes, there's an updated procedure on using external CA in 4.0, for
> details please take a look at Doc Text in
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1336838
> ​
>
>
>> So I imported it via keytool, but I don't want to use it in the engine
>> <-> VDSM communication.
>>
>
> ​Hmm, so that would imply that we have some issue with existing internal
> enigne CA during upgrade ...
> The strange thing is that we test upgrades a lot but so far we haven't
> seen any issues which will broke
> SSL setup between engine and VDSM. You said that you had to downgrade back
> to 3.6.7 (so unfortunately for us we cannot investigate your nonworking
> setup more), but how did you do that?
> Removing all engine packages and configuration​, installing back 3.6.7
> packaging and restoring configuration form backup?
> I'm asking to know what changed in your setup between not working 4.0 and
> working 3.6.7 ...
>
>
> Indeed, those are the steps I followed to the point.
>
> To add more strangeness, previously to upgrading this oVirt
> infrastructure, we upgraded another one that we have (also using own cert,
> a different one but from the same CA) and everything went smoothly. And
> what's more, previously to upgrading the engine that failed, I created a
> copy of that engine machine in a sandbox environment to see if upgrade
> process would or not success, and it worked perfectly.
>
> The only difference between the sandbox and the real machine's process was
> that when upgrading the real one, the first time I run "engine-setup" it
> failed because 'systemd' reported PostgreSQL as it was not running
> (actually it was, thougg), so everything rolled back. I had to kill the
> PostgreSQL process, start it again with systemctl and then run
> "engine-setup", where the process completed successfully but the SSL issue
> appeared. Not sure if this rollback could have shattered the whole thing...
>
> Anyhow, tomorrow I'm going to create another copy of the engine machine to
> a sandbox environment and try again. If it works I'll cross my fingers and
> give another try on the real machine...
>
> Thanks!
>

​Thanks a lot for you effort. I will try to perform same upgrade tomorrow
in my test env.
​


>
> Thanks
>
> Martin
>
>
>> Thanks!
>> En 20/7/2016 2:48 p. m., Martin Perina  escribió:
>>
>> Hi,
>>
>> sorry for late response, I overlook your reply :-(
>>
>> ​I looked at your logs and it seems to me that​ there's SSL error when
>> engine tries to contact VDSM.
>> ​You have mentioned that your are using your own custom CA. ​Are you
>> using it only for HTTPS certificate or do you want to use it also for
>> Engine <-> VDSM communication?
>> ​
>> Martin Perina
>>
>>
>> On Wed, Jul 20, 2016 at 9:18 AM,  wrote:
>>
>>> Any hints about this?
>>>
>>> El 2016-07-13 11:13, nico...@devels.es escribió:
>>>
 Hi,

 Unfortunately, upgrading to 4.0.1RC didn't solve the problem.
 Actually, the error changed to 'General SSLEngine problem', but the
 result was the same, like this:

 2016-07-13 09:52:22,010 INFO
 [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp
 Reactor) [] Connecting to /10.X.X.X
 2016-07-13 09:52:22,018 ERROR
 [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor)
 [] Unable to process messages: General SSLEngine problem

 It's worth mentioning that we're using our own SSL certificates (not
 self-signed), and I imported the combined certificate into the
 /etc/pki/ovirt-engine/.truststore key file. Not sure if related, but
 just in case.

>>>
 I had to downgrade to 3.6.7. I'm attaching requested logs, if you need
 anything else don't hesitate to ask.

 Regards.

 El 2016-07-13 09:45, Martin Perina escribió:

> Hi,
>
> could you please share also vdsm.log from your hosts and also
> server.log and setup logs from /var/log/ovirt-engine/setup directory?
>
> Thanks
>
> Martin Perina
>
> On Wed, Jul 13, 2016 at 10:36 AM,  wrote:
>
> Hi,
>>
>> We upgraded from 3.6.6 to 4.0.0 and we have a big issue since the
>> engine cannot connect to hosts. In the logs all we see is this
>> error:
>>
>> ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL
>> Stomp Reactor) [] Unable to process messages
>>
>> I'm attaching full logs.
>>
>> Could someone help please?
>>
>> Thanks.
>> 

Re: [ovirt-users] ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages

2016-07-20 Thread Nicolás



El 20/07/16 a las 16:45, Martin Perina escribió:



On Wed, Jul 20, 2016 at 4:44 PM, Nicolás > wrote:


Hi Martin,

Actually, up until now we had that cert configured in httpd and in
websocket proxy. Seems that now in 4.0.x it's not enough, as
opening the https://fqdn complains about the cert not being
imported in the key chain.


​Yes, there's an updated procedure on using external CA in 4.0, for 
details please take a look at Doc Text in


https://bugzilla.redhat.com/show_bug.cgi?id=1336838
​

So I imported it via keytool, but I don't want to use it in the
engine <-> VDSM communication.


​Hmm, so that would imply that we have some issue with existing 
internal enigne CA during upgrade ...
The strange thing is that we test upgrades a lot but so far we haven't 
seen any issues which will broke
SSL setup between engine and VDSM. You said that you had to downgrade 
back to 3.6.7 (so unfortunately for us we cannot investigate your 
nonworking setup more), but how did you do that?
Removing all engine packages and configuration​, installing back 3.6.7 
packaging and restoring configuration form backup?
I'm asking to know what changed in your setup between not working 4.0 
and working 3.6.7 ...




Indeed, those are the steps I followed to the point.

To add more strangeness, previously to upgrading this oVirt 
infrastructure, we upgraded another one that we have (also using own 
cert, a different one but from the same CA) and everything went 
smoothly. And what's more, previously to upgrading the engine that 
failed, I created a copy of that engine machine in a sandbox environment 
to see if upgrade process would or not success, and it worked perfectly.


The only difference between the sandbox and the real machine's process 
was that when upgrading the real one, the first time I run 
"engine-setup" it failed because 'systemd' reported PostgreSQL as it was 
not running (actually it was, thougg), so everything rolled back. I had 
to kill the PostgreSQL process, start it again with systemctl and then 
run "engine-setup", where the process completed successfully but the SSL 
issue appeared. Not sure if this rollback could have shattered the whole 
thing...


Anyhow, tomorrow I'm going to create another copy of the engine machine 
to a sandbox environment and try again. If it works I'll cross my 
fingers and give another try on the real machine...


Thanks!


Thanks

Martin


Thanks!
En 20/7/2016 2:48 p. m., Martin Perina > escribió:

Hi,

sorry for late response, I overlook your reply :-(

​I looked at your logs and it seems to me that​ there's SSL
error when engine tries to contact VDSM.
​You have mentioned that your are using your own custom CA.
​Are you using it only for HTTPS certificate or do you want to
use it also for Engine <-> VDSM communication?
​
Martin Perina


On Wed, Jul 20, 2016 at 9:18 AM, > wrote:

Any hints about this?

El 2016-07-13 11:13, nico...@devels.es
 escribió:

Hi,

Unfortunately, upgrading to 4.0.1RC didn't solve the
problem.
Actually, the error changed to 'General SSLEngine
problem', but the
result was the same, like this:

2016-07-13 09:52:22,010 INFO
[org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient]
(SSL Stomp
Reactor) [] Connecting to /10.X.X.X
2016-07-13 09:52:22,018 ERROR
[org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL
Stomp Reactor)
[] Unable to process messages: General SSLEngine problem

It's worth mentioning that we're using our own SSL
certificates (not
self-signed), and I imported the combined certificate
into the
/etc/pki/ovirt-engine/.truststore key file. Not sure
if related, but
just in case.


I had to downgrade to 3.6.7. I'm attaching requested
logs, if you need
anything else don't hesitate to ask.

Regards.

El 2016-07-13 09:45, Martin Perina escribió:

Hi,

could you please share also vdsm.log from your
hosts and also
server.log and setup logs from
/var/log/ovirt-engine/setup directory?

Thanks

Martin Perina

On Wed, Jul 13, 2016 at 10:36 AM,
> wrote:

Hi,

 

Re: [ovirt-users] ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages

2016-07-20 Thread Martin Perina
On Wed, Jul 20, 2016 at 4:44 PM, Nicolás  wrote:

> Hi Martin,
>
> Actually, up until now we had that cert configured in httpd and in
> websocket proxy. Seems that now in 4.0.x it's not enough, as opening the
> https://fqdn complains about the cert not being imported in the key
> chain.
>

​Yes, there's an updated procedure on using external CA in 4.0, for details
please take a look at Doc Text in

https://bugzilla.redhat.com/show_bug.cgi?id=1336838
​


> So I imported it via keytool, but I don't want to use it in the engine <->
> VDSM communication.
>

​Hmm, so that would imply that we have some issue with existing internal
enigne CA during upgrade ...
The strange thing is that we test upgrades a lot but so far we haven't seen
any issues which will broke
SSL setup between engine and VDSM. You said that you had to downgrade back
to 3.6.7 (so unfortunately for us we cannot investigate your nonworking
setup more), but how did you do that?
Removing all engine packages and configuration​, installing back 3.6.7
packaging and restoring configuration form backup?
I'm asking to know what changed in your setup between not working 4.0 and
working 3.6.7 ...

Thanks

Martin


> Thanks!
> En 20/7/2016 2:48 p. m., Martin Perina  escribió:
>
> Hi,
>
> sorry for late response, I overlook your reply :-(
>
> ​I looked at your logs and it seems to me that​ there's SSL error when
> engine tries to contact VDSM.
> ​You have mentioned that your are using your own custom CA. ​Are you using
> it only for HTTPS certificate or do you want to use it also for Engine <->
> VDSM communication?
> ​
> Martin Perina
>
>
> On Wed, Jul 20, 2016 at 9:18 AM,  wrote:
>
>> Any hints about this?
>>
>> El 2016-07-13 11:13, nico...@devels.es escribió:
>>
>>> Hi,
>>>
>>> Unfortunately, upgrading to 4.0.1RC didn't solve the problem.
>>> Actually, the error changed to 'General SSLEngine problem', but the
>>> result was the same, like this:
>>>
>>> 2016-07-13 09:52:22,010 INFO
>>> [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp
>>> Reactor) [] Connecting to /10.X.X.X
>>> 2016-07-13 09:52:22,018 ERROR
>>> [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor)
>>> [] Unable to process messages: General SSLEngine problem
>>>
>>> It's worth mentioning that we're using our own SSL certificates (not
>>> self-signed), and I imported the combined certificate into the
>>> /etc/pki/ovirt-engine/.truststore key file. Not sure if related, but
>>> just in case.
>>>
>>
>>> I had to downgrade to 3.6.7. I'm attaching requested logs, if you need
>>> anything else don't hesitate to ask.
>>>
>>> Regards.
>>>
>>> El 2016-07-13 09:45, Martin Perina escribió:
>>>
 Hi,

 could you please share also vdsm.log from your hosts and also
 server.log and setup logs from /var/log/ovirt-engine/setup directory?

 Thanks

 Martin Perina

 On Wed, Jul 13, 2016 at 10:36 AM,  wrote:

 Hi,
>
> We upgraded from 3.6.6 to 4.0.0 and we have a big issue since the
> engine cannot connect to hosts. In the logs all we see is this
> error:
>
> ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL
> Stomp Reactor) [] Unable to process messages
>
> I'm attaching full logs.
>
> Could someone help please?
>
> Thanks.
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users [1]
>



 Links:
 --
 [1] http://lists.ovirt.org/mailman/listinfo/users

>>>
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages

2016-07-20 Thread Nicolás
Hi Martin,

Actually, up until now we had that cert configured in httpd and in websocket proxy. Seems that now in 4.0.x it's not enough, as opening the https://fqdn complains about the cert not being imported in the key chain. So I imported it via keytool, but I don't want to use it in the engine <-> VDSM communication.

Thanks!En 20/7/2016 2:48 p. m., Martin Perina  escribió:Hi,sorry for late response, I overlook your reply :-(​I looked at your logs and it seems to me that​ there's SSL error when engine tries to contact VDSM.​You have mentioned that your are using your own custom CA. ​Are you using it only for HTTPS certificate or do you want to use it also for Engine <-> VDSM communication?​Martin Perina On Wed, Jul 20, 2016 at 9:18 AM,   wrote:Any hints about this?

El 2016-07-13 11:13, nico...@devels.es escribió:

Hi,

Unfortunately, upgrading to 4.0.1RC didn't solve the problem.
Actually, the error changed to 'General SSLEngine problem', but the
result was the same, like this:

2016-07-13 09:52:22,010 INFO
[org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp
Reactor) [] Connecting to /10.X.X.X
2016-07-13 09:52:22,018 ERROR
[org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor)
[] Unable to process messages: General SSLEngine problem

It's worth mentioning that we're using our own SSL certificates (not
self-signed), and I imported the combined certificate into the
/etc/pki/ovirt-engine/.truststore key file. Not sure if related, but
just in case.

I had to downgrade to 3.6.7. I'm attaching requested logs, if you need
anything else don't hesitate to ask.

Regards.

El 2016-07-13 09:45, Martin Perina escribió:

Hi,

could you please share also vdsm.log from your hosts and also
server.log and setup logs from /var/log/ovirt-engine/setup directory?

Thanks

Martin Perina

On Wed, Jul 13, 2016 at 10:36 AM,  wrote:


Hi,

We upgraded from 3.6.6 to 4.0.0 and we have a big issue since the
engine cannot connect to hosts. In the logs all we see is this
error:

    ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL
Stomp Reactor) [] Unable to process messages

I'm attaching full logs.

Could someone help please?

Thanks.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users [1]




Links:
--
[1] http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages

2016-07-20 Thread Martin Perina
Hi,

sorry for late response, I overlook your reply :-(

​I looked at your logs and it seems to me that​ there's SSL error when
engine tries to contact VDSM.
​You have mentioned that your are using your own custom CA. ​Are you using
it only for HTTPS certificate or do you want to use it also for Engine <->
VDSM communication?
​
Martin Perina


On Wed, Jul 20, 2016 at 9:18 AM,  wrote:

> Any hints about this?
>
> El 2016-07-13 11:13, nico...@devels.es escribió:
>
>> Hi,
>>
>> Unfortunately, upgrading to 4.0.1RC didn't solve the problem.
>> Actually, the error changed to 'General SSLEngine problem', but the
>> result was the same, like this:
>>
>> 2016-07-13 09:52:22,010 INFO
>> [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp
>> Reactor) [] Connecting to /10.X.X.X
>> 2016-07-13 09:52:22,018 ERROR
>> [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor)
>> [] Unable to process messages: General SSLEngine problem
>>
>> It's worth mentioning that we're using our own SSL certificates (not
>> self-signed), and I imported the combined certificate into the
>> /etc/pki/ovirt-engine/.truststore key file. Not sure if related, but
>> just in case.
>>
>
>> I had to downgrade to 3.6.7. I'm attaching requested logs, if you need
>> anything else don't hesitate to ask.
>>
>> Regards.
>>
>> El 2016-07-13 09:45, Martin Perina escribió:
>>
>>> Hi,
>>>
>>> could you please share also vdsm.log from your hosts and also
>>> server.log and setup logs from /var/log/ovirt-engine/setup directory?
>>>
>>> Thanks
>>>
>>> Martin Perina
>>>
>>> On Wed, Jul 13, 2016 at 10:36 AM,  wrote:
>>>
>>> Hi,

 We upgraded from 3.6.6 to 4.0.0 and we have a big issue since the
 engine cannot connect to hosts. In the logs all we see is this
 error:

 ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL
 Stomp Reactor) [] Unable to process messages

 I'm attaching full logs.

 Could someone help please?

 Thanks.
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users [1]

>>>
>>>
>>>
>>> Links:
>>> --
>>> [1] http://lists.ovirt.org/mailman/listinfo/users
>>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages

2016-07-20 Thread nicolas

Any hints about this?

El 2016-07-13 11:13, nico...@devels.es escribió:

Hi,

Unfortunately, upgrading to 4.0.1RC didn't solve the problem.
Actually, the error changed to 'General SSLEngine problem', but the
result was the same, like this:

2016-07-13 09:52:22,010 INFO
[org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp
Reactor) [] Connecting to /10.X.X.X
2016-07-13 09:52:22,018 ERROR
[org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor)
[] Unable to process messages: General SSLEngine problem

It's worth mentioning that we're using our own SSL certificates (not
self-signed), and I imported the combined certificate into the
/etc/pki/ovirt-engine/.truststore key file. Not sure if related, but
just in case.

I had to downgrade to 3.6.7. I'm attaching requested logs, if you need
anything else don't hesitate to ask.

Regards.

El 2016-07-13 09:45, Martin Perina escribió:

Hi,

could you please share also vdsm.log from your hosts and also
server.log and setup logs from /var/log/ovirt-engine/setup directory?

Thanks

Martin Perina

On Wed, Jul 13, 2016 at 10:36 AM,  wrote:


Hi,

We upgraded from 3.6.6 to 4.0.0 and we have a big issue since the
engine cannot connect to hosts. In the logs all we see is this
error:

    ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL
Stomp Reactor) [] Unable to process messages

I'm attaching full logs.

Could someone help please?

Thanks.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users [1]




Links:
--
[1] http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages

2016-07-13 Thread Martin Perina
Hi,

could you please share also vdsm.log from your hosts and also server.log
and setup logs from /var/log/ovirt-engine/setup directory?

Thanks

Martin Perina


On Wed, Jul 13, 2016 at 10:36 AM,  wrote:

> Hi,
>
> We upgraded from 3.6.6 to 4.0.0 and we have a big issue since the engine
> cannot connect to hosts. In the logs all we see is this error:
>
> ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp
> Reactor) [] Unable to process messages
>
> I'm attaching full logs.
>
> Could someone help please?
>
> Thanks.
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] Unable to process messages

2016-07-13 Thread Michal Skrivanek

> On 13 Jul 2016, at 10:36, nico...@devels.es wrote:
> 
> Hi,
> 
> We upgraded from 3.6.6 to 4.0.0 and we have a big issue since the engine 
> cannot connect to hosts. In the logs all we see is this error:

4.0.1 might be a better bet. There were quite a few json-rpc issues around the 
time of GA, you may be suffering from those. 4.0.1 is about to be GAed, and if 
things are broken right now the last RC can only help.

> 
>ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) 
> [] Unable to process messages
> 
> I'm attaching full logs.
> 
> Could someone help please?
> 
> Thanks.___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users