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
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
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
> >
> > 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) []
> 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) []
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
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
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
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
>>
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
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
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
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
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
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
> 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
17 matches
Mail list logo