-
Notifications
You must be signed in to change notification settings - Fork 783
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
Interrupted system call #166
Comments
Patch for Issue novnc#166
A reasonable reaction to an "Interrupted system call" is to try again. My patch just catches and continues (a little trickery to catch just "Interrupted system call") |
Yes. For select.select(), you may need to recompute the timeout. But in do_proxy() calls select() in a "while True" loop, so I'm not sure that the timeout matters. By the way, why select() is called with a timeout? It looks like active polling, whereas it should work without polling. See also the PEP 475 which restarts interrupted syscalls in Python 3.5: |
Re: Python 3.x - it's the reason my patch wasn't merged. I'm not too familiar with Python 3 and especially not with code that's cross-compatible. Will have to look into this (fingers crossed for today). Thank you for looking at this. |
@bkanuka after i've applied this patch, WebVirtMgr isnt connecting to spice at all anymore, without it connects but disconnects after few seconds like the initial issue, something seems not quite right here i guess |
Whoa super good to know. Thanks! I'll look into it. Sorry this has totally
|
This is a bit of a cross-post because I'm not entirely sure where this bug lives. WebVirtMgr uses websockify somewhat unsuccessfully. See this bug.
The actual exception however, is happening in websocketproxy.py line 134.
ins, outs, excepts = select(rlist, wlist, [], 1)
is throwing aselect.error error: (4, 'Interrupted system call')
If the
select
timeout is set to 0, things work but obviously at high CPU.The bug linked above may actually be the fault of WebVirtMgr, but ideally websockify should be robust to whatever WebVirtMgr is doing.
The text was updated successfully, but these errors were encountered: