Opened 10 years ago
Last modified 17 months ago
#118 closed defect
xpra server dies overnight — at Version 1
Reported by: | Doug Doole | Owned by: | Antoine Martin |
---|---|---|---|
Priority: | critical | Milestone: | 0.3 |
Component: | server | Version: | 0.2.0 |
Keywords: | Cc: |
Description (last modified by )
I've been running xpra 0.2.0 on Ubuntu (11.10 for the server, 11.04 for the client) for the last two days. My client disconnects overnight and on both days, when I attempt to connect the next morning, the client does not attach.
doole@andammo:~$ xpra attach ssh:reorx:1 Connection failed: [Errno 2] No such file or directory connection lost: empty marker in read queue Connection lost
I took a look at .xpra/reorx-1.log, but I don't see anything obvious. I have attached both reorx-1.log and reorx-1.log.old.
On the server, I can see the xpra process running:
doole@reorx:~$ ps -ef | grep xpra doole 915 1 52 Apr26 ? 11:05:18 /usr/bin/python /opt/xpra/bin/xpra start :1
but I am unable to stop it:
doole@reorx:~$ xpra stop :1 Connection failed: [Errno 2] No such file or directory doole@reorx:~$ xpra stop Usage: xpra start DISPLAY xpra attach [DISPLAY] xpra detach [DISPLAY] xpra screenshot filename [DISPLAY] xpra version [DISPLAY] xpra stop [DISPLAY] xpra list xpra upgrade DISPLAY xpra: error: cannot find a live server to connect to
So I manually kill the xpra session (kill 915 - process is gone) and restart xpra. When I reconnect from the client, all my windows are still present (so killing xpra didn't wipe out the window manager for some reason) although the windows have all moved to +0+0 on the screen.
In case it matters, my line to start xpra is:
/usr/bin/xpra start :1
I was previously using 0.0.7.34 and did not see this behaviour.
I suspect that you'll need more diagnostics - just let me know what to gather.
Change History (3)
Changed 10 years ago by
Attachment: | reorx-1.log added |
---|
Changed 10 years ago by
Attachment: | reorx-1.log.old added |
---|
comment:1 Changed 10 years ago by
Description: | modified (diff) |
---|---|
Status: | new → accepted |
The
Is a little odd, it means the socket is gone - why is not entirely clear.
Can you check if the xpra process still has it open?
After that, xpra stop will fail, and connect also..
Maybe you could try to strace the process next time this happens to see what it is doing, or just run the server in debug mode (with '
-d all
') so we can get some diagnostics.