Les discovered that junk (or unknown hosts for that matter) in the terminal server list causes a traceback: 2008-08-05 19:20:33 INFO vsmserver.license: Updating license data from disk to memory 2008-08-05 19:20:33 INFO vsmserver.license: License summary: 200 concurrent users. Hard limit of 220 concurrent users. 2008-08-05 19:20:33 ERROR vsmserver.loadinfo: Unhandled exception fetching load from 10,8.0.204,:904: <class 'socket.gaierror'> (-2, 'Name or service not known') Traceback (most recent call last): File "/opt/thinlinc/modules/thinlinc/vsm/xmlrpc.py", line 319, in xmlrpc_call self . connect ( ( o00oO0oo0OO , int ( O0O0OOOOoo ) ) ) File "/usr/lib/python2.5/asyncore.py", line 307, in connect err = self.socket.connect_ex(address) File "<string>", line 1, in connect_ex gaierror: (-2, 'Name or service not known') . Marking agent as down. 2008-08-05 19:20:33 INFO vsmserver.session: Loaded 0 sessions for 0 users from file 2008-08-05 19:34:05 ERROR vsmserver.loadinfo: Unhandled exception fetching load from 10.8.0.204,:904: <class 'socket.gaierror'> (-2, 'Name or service not known') Traceback (most recent call last): File "/opt/thinlinc/modules/thinlinc/vsm/xmlrpc.py", line 319, in xmlrpc_call self . connect ( ( o00oO0oo0OO , int ( O0O0OOOOoo ) ) ) File "/usr/lib/python2.5/asyncore.py", line 307, in connect err = self.socket.connect_ex(address) File "<string>", line 1, in connect_ex gaierror: (-2, 'Name or service not known') . Marking agent as down.
This bug also occurs if unknown/bad hosts are listed in /vsmserver/explicit_agentselection
Reported again in issue 14610. Reassigning for discussion.
We have similar problems when we get temporary name resolution errors, reported in issue 17976.
All done. Need to test: - Invalid names for terminalservers (both syntax and names that cannot be looked up) - Other socket errors in XML-RPC connection (e.g. ECONNREFUSED) - Bad listen_hostname for vsmagent and vsmserver.
(In reply to comment #9) > All done. Need to test: > > - Invalid names for terminalservers (both syntax and names that cannot be > looked up) Handles everything I've thrown at it with grace. > - Other socket errors in XML-RPC connection (e.g. ECONNREFUSED) > 2016-01-04 15:38:21 WARNING vsmserver.loadinfo: [Errno 111] Connection refused talking to VSM Agent 127.0.0.1:904 in request for loadinfo. Marking as down. > 2016-01-04 15:36:23 WARNING vsmserver.loadinfo: [Errno -9] Address family for hostname not supported talking to VSM Agent ::1:904 in request for loadinfo. Marking as down. > 2016-01-04 15:36:23 WARNING vsmserver.loadinfo: [Errno -2] Name or service not known talking to VSM Agent [2a00:801:107:4700:20c:29ff:fe00:9a5a]:904 in request for loadinfo. Marking as down. Ayup. > - Bad listen_hostname for vsmagent and vsmserver. Works fine, with similar log entries for both vsmserver and vsmagent: > 2016-01-04 15:35:03 ERROR vsmserver: Unhandled socket error [Errno -2] Name or service not known > 2016-01-04 15:35:03 ERROR vsmserver: Exiting
