----- Original Message -----
From: "Milan Zamazal" <mzamazal@redhat.com> To: "lifuqiong" <lifuqiong@cncloudsec.com> Cc: devel@ovirt.org Sent: Tuesday, July 26, 2016 3:46:42 PM Subject: Re: [ovirt-devel] Debug vdsm 4.0.0 report error: libvirt: XML-RPC error : Failed to connect socket to '/var/run/libvirt/libvirt-sock': Permission denied
"lifuqiong" <lifuqiong@cncloudsec.com> writes:
I know it’s a multithreaded application , and debug vdsm is a very difficult job, but without debug, I don’t know which code I should replace or logging, Is there any remote debug solution like ovirt engine? I found that
I can do remote debug in simple python application , but I didn’t success yet remote debugging vdsm.
As Michal mentioned, making a breakpoint in Vdsm may break things due to the stopped execution of the given thread. Inserting logging messages to proper places of the code, where you need to get some information about the runtime state, is typically much simpler and good enough solution.
Additionally, another option is to use our manhole integration: https://pypi.python.org/pypi/manhole this is available on ovirt-4.0.z check manhole_enable in [devel] section. As the name hints, this should not be enabled in production settings. Bests, -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani