<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=windows-1252">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi, I've been trying to get nova-compute (devstack, Newton,
all-in-one) to work with the remote debugger in eclipse/pydev. (I've
also tried pyCharm with the same results.) Following instructions
here:
<a class="moz-txt-link-freetext" href="http://docs.openstack.org/developer/nova/development.environment.html">http://docs.openstack.org/developer/nova/development.environment.html</a>
<br>
<br>
I see the message in the nova code about results being unpredictable
when you do this, so I'd like to know if this is expected or if I'm
doing something wrong.<br>
<br>
I am starting nova-compute in devstack with these switches:
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<font face="Courier 10 Pitch"><font style="font-size: 9pt" size="2"><font
face="Courier 10 Pitch"> </font></font></font><font
style="font-size: 9pt" size="+1">--remote_debug-host
192.168.9.94 --remote_debug-port 5678<br>
</font>
<title></title>
<meta name="generator" content="LibreOffice 4.4.3.2 (Linux)">
<style type="text/css">
@page { margin: 0.79in }
p { margin-bottom: 0.1in; direction: ltr; line-height: 120%; text-align: left; orphans: 2; widows: 2 }
p.western { font-size: 12pt }
p.cjk { font-size: 12pt; so-language: zh-CN }
p.ctl { font-size: 12pt }
a:link { color: #0000ff }
a.ctl:link { font-family: "Times New Roman" }
</style><br>
Nova-compute starts up ok and then as expected hits its embedded
settrace() breakpoint:<br>
<br>
LOG.warning(_LW('WARNING: Using the remote debug option changes how
'<br>
'Nova uses the eventlet library to support async
IO. This '<br>
'could result in failures that do not occur
under normal '<br>
'operation. Use at your own risk.'))<br>
<br>
which so far is all good. I see the breakpoint and I can see all the
variables in the debugger. <br>
<br>
But when I resume execution, several more log messages are
outputted, and then nova-compute hangs. The last line in the log is:<br>
<br>
... Connecting to libvirt: qemu:///system from (pid=556)
_get_new_connection /opt/stack/nova/nova/virt/libvirt/host.py:367<br>
<br>
At this point I can't ^c the process and the only way to get going
again is to kill nova-compute from the command line.<br>
<br>
I am guessing that this hang is due to some debugger/eventlet
conflict as mentioned in that log message. Or am I missing some
configuration step? If this isn't going to work, what do other
people recommend for debugging nova-compute? Thanks,<br>
<br>
Steve<br>
<br>
<br>
<br>
<br>
</body>
</html>