Xpra: Ticket #1506: Version. 2.1. Session start and Socket availability

Seems that there are issues with sessions' start. And from Terminal commands and from PY scripts.

Sun, 23 Apr 2017 11:15:58 GMT - Denis01: component, summary changed

Sun, 23 Apr 2017 11:52:53 GMT - Antoine Martin: owner, component changed

As always, please follow wiki/ReportingBugs. In particular:


Sun, 23 Apr 2017 12:54:00 GMT - Denis01:

Centos 7.x The easiest way is to put a call for a new session for user on target hosts in xx_auth.py/get_sessions() on Proxy server. Basically 1 connection can be established normally but then there are more than 1 session on 1 target_host - behavior of proxy/sessions/ports is unpredictable (mentioned above).

Version 2.0.2 reliably starts many sessions with ports open less then 3 sec for users. Proxy connects html client easily. With the same ssh paramico call from the same xxx_auth.get_session() function. Tested today and 2.1 and 2.0 .2 on the same server and 2 auth modules(multi and sql). Seems that it could be somehow linked with new in 2.1 "flag of stealing session" or other modif.

P.s. almost happy :-) as it got me absolutly mad :-) so getting back to normalize balancing script

Sun, 23 Apr 2017 13:00:27 GMT - Antoine Martin:

Please provide reproducible steps for this issue with any supported xpra version, without making changes to the code. Otherwise I will have to close this ticket as "invalid". I am also having a very hard time understanding your comments.

Sun, 23 Apr 2017 15:06:51 GMT - Denis01:

Having tried with different scenarios I was unable to reproduce that with Terminal use only. So the all descriptions are relevant only to the calls from the modified code.

Sun, 23 Apr 2017 15:08:21 GMT - Antoine Martin: status changed; resolution set

Sat, 23 Jan 2021 05:26:09 GMT - migration script:

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1506