Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ADR GUI sometimes fails to start: "No module named qt4reactor" #409

Open
mgiustina opened this issue Feb 3, 2017 · 3 comments
Open

ADR GUI sometimes fails to start: "No module named qt4reactor" #409

mgiustina opened this issue Feb 3, 2017 · 3 comments

Comments

@mgiustina
Copy link
Contributor

Starting the ADR GUI (in /servers/GUIs/ADR/ADRcontrol2.py) sometimes evokes the error:
Traceback (most recent call last):
File "ADRcontrol2.py", line 574, in <module>
import qt4reactor
ImportError: No module named qt4reactor

I haven't figured out how to reliably reproduce the error. Perhaps the error is more likely when the ADR GUI is already running on another machine? But that sometimes also works successfully.

Current fix is to restart all the ADR servers, in the worst case to restart the labradhost machine.

@pklimov
Copy link
Member

pklimov commented Feb 3, 2017

looks like you need to install the qt4reactor module. you should be able to do so by running the following from the terminal :
pip install qt4reactor

@maffoo
Copy link
Contributor

maffoo commented Feb 8, 2017

I'm worried about the "sometimes" here. Modules being on the pythonpath should not be something that changes on its own, though I guess this could actually be a problem with runtime initialization of the qt4reactor module, not just finding the code. Are you always starting the GUI program in the same way? Are you using a virtualenv? I don't think restarting servers should have any effect on this, but I guess we need to figure out what the actual problem is.

@mgiustina
Copy link
Contributor Author

In that particular case, it was my fault: I wasn't in my virtual env. But it reminded me that both Brooks and I have seen such a problem before and hadn't filed an issue. I'll try to update with as much "more info" as I have when it comes up again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants