> Isn’t the most likely cause by far a simple startup delay? We do open the > listener “soon” and responds with code 99, but it’s still not instant of > course
That is possible of course and we handle those "errors" just fine. But connection refused never happened with xmlrpc. It might have been luck, but it always worked there :) Martin On Wed, Nov 9, 2016 at 9:11 AM, Michal Skrivanek <[email protected]> wrote: > >> On 9 Nov 2016, at 08:55, Francesco Romani <[email protected]> wrote: >> >> ----- Original Message ----- >>> From: "Piotr Kliczewski" <[email protected]> >>> To: "Martin Perina" <[email protected]> >>> Cc: "Francesco Romani" <[email protected]>, "Shira Maximov" >>> <[email protected]>, "devel" <[email protected]> >>> Sent: Tuesday, November 8, 2016 9:31:43 PM >>> Subject: Re: [vdsm] Connection refused when talking to jsonrpc >> >> >>>>> 2016-11-08 18:25:30,030 - mom - ERROR - Failed to initialize MOM threads >>>>> Traceback (most recent call last): >>>>> File "/usr/lib/python2.7/site-packages/mom/__init__.py", line 29, in >>>>> run >>>>> hypervisor_iface = self.get_hypervisor_interface() >>>>> File "/usr/lib/python2.7/site-packages/mom/__init__.py", line 217, >>>>> in get_hypervisor_interface >>>>> return module.instance(self.config) >>>>> File "/usr/lib/python2.7/site-packages/mom/HypervisorInterfaces/v >>>>> dsmjsonrpcbulkInterface.py", >>>>> line 47, in instance >>>>> return JsonRpcVdsmBulkInterface() >>>>> File "/usr/lib/python2.7/site-packages/mom/HypervisorInterfaces/v >>>>> dsmjsonrpcbulkInterface.py", >>>>> line 29, in __init__ >>>>> super(JsonRpcVdsmBulkInterface, self).__init__() >>>>> File "/usr/lib/python2.7/site-packages/mom/HypervisorInterfaces/v >>>>> dsmjsonrpcInterface.py", >>>>> line 43, in __init__ >>>>> .orRaise(RuntimeError, 'No connection to VDSM.') >>>>> File "/usr/lib/python2.7/site-packages/mom/optional.py", line 28, in >>>>> orRaise >>>>> raise exception(*args, **kwargs) >>>>> RuntimeError: No connection to VDSM. >>>>> >>>>> >>>>> The question here is, how much time does VDSM need to allow jsonrpc to >>>>> connect and request a ping and list of VMs? >>>>> >>>>> >>> It depends on recovery logic in vdsm and it can take quite some time. >>> >>> Please share vdsm logs so I could take a look? >> >> +1 >> >> the most likely cause is the recovery still in progress, however I was >> expecting >> a different error, so worth looking at the logs. > > Isn’t the most likely cause by far a simple startup delay? We do open the > listener “soon” and responds with code 99, but it’s still not instant of > course > >> >> Bests, >> >> -- >> Francesco Romani >> Red Hat Engineering Virtualization R & D >> Phone: 8261328 >> IRC: fromani >> _______________________________________________ >> Devel mailing list >> [email protected] >> http://lists.ovirt.org/mailman/listinfo/devel >> >> > _______________________________________________ Devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/devel
