Bug 5664 - traceback in vsmserver if session dies whilst connecting
Summary: traceback in vsmserver if session dies whilst connecting
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: VSM Server (show other bugs)
Target Milestone: LowPrio
Assignee: Henrik Andersson
Depends on:
Reported: 2015-10-01 16:34 CEST by Pierre Ossman
Modified: 2023-11-20 16:53 CET (History)
1 user (show)

See Also:
Acceptance Criteria:


Description Pierre Ossman cendio 2015-10-01 16:34:24 CEST
Found whilst doing bug 765. Same conditions as when bug 5556 was found, but I used the same user this time. IOW it stress tested reconnects rather than new sessions.

Got this:

2015-10-01 15:42:11 ERROR vsmserver.session: Unhandled exception trying to unbind ports for display 1 on VSM Agent <type 'exceptions.TypeError'> 'NoneType' object has no attribute '__getitem__' Tr
aceback (most recent call last):
  File "/opt/thinlinc/modules/thinlinc/vsm/async.py", line 112, in iii11
    obj . handle_read_event ( )
  File "/usr/lib64/python2.7/asyncore.py", line 449, in handle_read_event
  File "/usr/lib64/python2.7/asynchat.py", line 147, in handle_read
  File "/opt/thinlinc/modules/thinlinc/vsm/xmlrpc.py", line 405, in found_terminator
    self . handle_response ( )
  File "/opt/thinlinc/modules/thinlinc/vsm/xmlrpc.py", line 437, in handle_response
    self . handle_returnvalue ( )
  File "/opt/thinlinc/modules/thinlinc/vsm/call_unbindports.py", line 41, in handle_returnvalue
    self . callback ( )
  File "/opt/thinlinc/modules/thinlinc/vsm/loginhandler_common.py", line 71, in run_sessionscripts
    self . send_response ( )
  File "/opt/thinlinc/modules/thinlinc/vsm/loginhandler_common.py", line 88, in send_response
    oOOoo ) [ 'sessionkey' ]
TypeError: 'NoneType' object has no attribute '__getitem__'
. Marking agent as down.
Comment 1 Pierre Ossman cendio 2015-10-14 15:22:36 CEST
I was going to test how 4.4.0 behaves, but it turns out that I'm having problems reliably triggering this on 4.5.0. So whatever the race it, it is very rare.
Comment 2 Pierre Ossman cendio 2023-11-20 16:53:13 CET
The race looks to be that the session dies whilst we are trying to establish a connection to it. It's not apparent from the trace if this is a new session, or an existing one. I guess in theory it could happen to either?

Note You need to log in before you can comment on or make changes to this bug.