Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • V VISPA web
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 84
    • Issues 84
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • 3pia3pia
  • VISPAVISPA
  • VISPA web
  • Issues
  • #614
Closed
Open
Issue created Apr 22, 2015 by Benjamin Fischer@benjamin.fischerOwner

workspace connection

can not connect to any workspace:

2015-04-22 09:07:10 - DEBUG - vispa.workspace - connect new workspace
2015-04-22 09:07:10 - INFO - vispa.workspace - spawn remote process: ‘localhost’ using command ‘None’
2015-04-22 09:07:10 - DEBUG - vispa.socketbus - send to window_id ‘None’, user_id ‘1’, broadcast False
2015-04-22 09:07:10 - DEBUG - vispa.socketbus - ->sending to subscriber: window_id ‘AkkgkNwp0PJw9zxE’, user_id ‘1’
2015-04-22 09:07:10 - DEBUG - vispa.socketbus - ->sending to subscriber: window_id ‘X6mpV4PiaJBXOgCG’, user_id ‘1’
2015-04-22 09:07:10 - DEBUG - vispa.workspace - connect via ssh to workspace: localhost
2015-04-22 09:07:10 - DEBUG - vispa.socketbus - send to window_id ‘None’, user_id ‘1’, broadcast False
2015-04-22 09:07:10 - DEBUG - vispa.socketbus - ->sending to subscriber: window_id ‘AkkgkNwp0PJw9zxE’, user_id ‘1’
2015-04-22 09:07:10 - DEBUG - vispa.socketbus - ->sending to subscriber: window_id ‘X6mpV4PiaJBXOgCG’, user_id ‘1’
2015-04-22 09:07:10 - ERROR - vispa.workspace - SSH implementation
Traceback (most recent call last):
File “/home/asseldonk/software/vispa_web/vispa/workspace.py”, line 590, in open
username=self.__username)
File “/home/asseldonk/software/vispa_web/vispa/workspace.py”, line 374, in init
self.__client.connect(**connect_args)
File “/usr/local/lib/python2.7/dist-packages/paramiko/client.py”, line 236, in connect
retry_on_signal(lambda: sock.connect(addr))
File “/usr/local/lib/python2.7/dist-packages/paramiko/util.py”, line 278, in retry_on_signal
return function()
File “/usr/local/lib/python2.7/dist-packages/paramiko/client.py”, line 236, in
retry_on_signal(lambda: sock.connect(addr))
File “/usr/lib/python2.7/socket.py”, line 224, in meth
return getattr(self._sock,name)(*args)
error: [Errno 111] Connection refused

(from redmine: issue id 2202, created on 2015-04-22 by Daniel.Van.Asseldonk, closed on 2015-04-22)

  • Changesets:
    • Revision 2125 by Daniel van Asseldonk on 2015-04-22T09:50:54Z:
fixed bug in workspace connection, fix #2202
  • Revision 2125 by Daniel van Asseldonk on 2015-04-22T09:50:54Z:
fixed bug in workspace connection, fix #2202
Assignee
Assign to
Time tracking