Hi Simone, I did have the issue you link to below when doing a `hosted-engine --deploy` on this server when I was setting it up to run 3.6. I've commented on the bug with my experiences. I did get the host working in 3.6 and there were no errors, but this one has cropped up since upgrading to 4.0.1.
I did not have the same issue on all of my hosts, but the error I am experiencing now: JsonRpc (StompReactor)::ERROR::2016-07-22 09:59:56,062::betterAsyncore::113::vds.dispatcher::(recv) SSL error during reading data: unexpected eof JsonRpc (StompReactor)::ERROR::2016-07-22 10:00:11,240::betterAsyncore::113::vds.dispatcher::(recv) SSL error during reading data: unexpected eof JsonRpc (StompReactor)::ERROR::2016-07-22 10:00:21,158::betterAsyncore::113::vds.dispatcher::(recv) SSL error during reading data: unexpected eof JsonRpc (StompReactor)::ERROR::2016-07-22 10:00:21,441::betterAsyncore::113::vds.dispatcher::(recv) SSL error during reading data: unexpected eof JsonRpc (StompReactor)::ERROR::2016-07-22 10:00:26,717::betterAsyncore::113::vds.dispatcher::(recv) SSL error during reading data: unexpected eof JsonRpc (StompReactor)::ERROR::2016-07-22 10:00:31,856::betterAsyncore::113::vds.dispatcher::(recv) SSL error during reading data: unexpected eof JsonRpc (StompReactor)::ERROR::2016-07-22 10:00:36,982::betterAsyncore::113::vds.dispatcher::(recv) SSL error during reading data: unexpected eof JsonRpc (StompReactor)::ERROR::2016-07-22 10:00:52,180::betterAsyncore::113::vds.dispatcher::(recv) SSL error during reading data: unexpected eof is happening on all of them. :-( Cheers, Gervais > On Jul 22, 2016, at 5:35 AM, Simone Tiraboschi <[email protected]> wrote: > > On Thu, Jul 21, 2016 at 8:08 PM, Gervais de Montbrun > <[email protected]> wrote: >> Hi Martin >> >> Logs are attached. >> >> Thank you for any help you can offer. >> :-) >> >> Cheers, >> Gervais > > see also this one: https://bugzilla.redhat.com/show_bug.cgi?id=1358530 > > the results are pretty similar. > >> On Jul 21, 2016, at 10:20 AM, Martin Perina <[email protected]> wrote: >> >> So could you please share logs? >> >> Thanks >> >> Martin >> >> On Thu, Jul 21, 2016 at 3:17 PM, Gervais de Montbrun >> <[email protected]> wrote: >>> >>> Hi Oved, >>> >>> Thanks for the suggestion. >>> >>> I tried setting "management_ip = 0.0.0.0" but same result. >>> BTW, management_ip='0.0.0.0' (as suggested in the post) doesn't work for >>> me. vdsmd wouldn't start. >>> >>> Cheers, >>> Gervais >>> >>> >>> >>> On Jul 20, 2016, at 10:50 AM, Oved Ourfali <[email protected]> wrote: >>> >>> Also, this thread seems similar. >>> Also talking about IPV4/IPV6 issue. >>> Does it help? >>> >>> [1] http://lists.ovirt.org/pipermail/users/2016-June/040602.html >>> >>> On Wed, Jul 20, 2016 at 4:43 PM, Martin Perina <[email protected]> wrote: >>>> >>>> Hi, >>>> >>>> could you please create a bug and attach engine host logs (all from >>>> /var/log/ovirt-engine) and VDSM logs (from /var/log/vdsm)? >>>> >>>> Thanks >>>> >>>> Martin Perina >>>> >>>> >>>> On Wed, Jul 20, 2016 at 1:50 PM, Gervais de Montbrun >>>> <[email protected] >>>>> wrote: >>>> >>>>> Hi Qiong, >>>>> >>>>> I am experiencing the exact same issue. All four of my hosts are >>>>> throwing >>>>> the same error to the vdsm.log If you find a solution, please let me >>>>> know >>> >>> >>> >> >> >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.ovirt.org/mailman/listinfo/users >>
_______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
