Closed totaam closed 8 years ago
xstata-14-xpra-fail.zip
(387.7 KiB)Xpra stata logs
Are you sure that xpra crashed? You server log shows:
2016-07-05 14:51:54,236 child '/usr/bin/pexpect_run.py xstata-out.txt /nfs/tools/apps/stata/14/xstata-mp' with pid 14531 has terminated ... 2016-07-05 14:51:54,236 all children have exited and --exit-with-children was specified, exiting
That's shortly after evince shows up:
2016-07-05 14:51:53,827 Discovered new ordinary window: WindowModel(0xa00003) (geometry=(259, 54, 600, 600)) ... 2016-07-05 14:51:53,828 make_metadata(4, WindowModel(0xa00003), class-instance)={'class-instance': ['evince', 'Evince']}
This doesn't look like an xpra bug, and I am unable to run this proprietary software on my system. Please try running xstata in an xterm window to see if it exits or not. Maybe pexpect isn't helping. If it does crash... maybe you can try to attach gdb to see where the problem is.
Antoine,
You are right. This does entirely seem to be because of 'pexpect.' Sorry for the hastily created ticket.
I use pexpect because XStata-MP detaches itself on start, so, XPRA thinks Xstata-MP has exited. If I do not use --exit-with-children, I can use Xstata-mp, but, if I quit XStata-MP, XPRA doesn't quit on the server side, which I would like to happen.
Have any tips on how I can accomplish this?
See the process listing
esarmien 17027 31954 36 09:28 pts/1 00:01:12 /usr/bin/python2 /usr/bin/xpra --daemon=no start --start-child=/nfs/tools/apps/stata/14/xstata-mp esarmien 17068 1 0 09:28 pts/1 00:00:00 /nfs/tools/apps/stata/14/xstata-mp esarmien 17117 2435 50 09:28 pts/5 00:01:28 /usr/bin/python2 /usr/bin/xpra --daemon=no -d all attach :0
xstata-mp is not a child of the xpra process.
Thanks Evan
There is no easy way to monitor a process that daemonizes itself (parent pid=1) from userspace. Usually, daemons provide their pid somewhere or have the ability to run non-daemonized. Maybe xstrata has such a feature? If not, your best bet would be to write a script that matches the process from the process list, then polls it until it terminates. You can make that more robust if you can provide unique command line arguments to xstrata-mp that you can then match in the process list. Again, no idea if xstrata will let you do this.
Closing as this is not an xpra bug.
Milestone renamed
Issue migrated from trac ticket # 1246
component: client | priority: major | resolution: invalid
2016-07-05 19:53:08: esarmien created the issue