Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Interface says "connecting", error on console #9

Closed
coljac opened this issue Jan 22, 2020 · 2 comments
Closed

Interface says "connecting", error on console #9

coljac opened this issue Jan 22, 2020 · 2 comments

Comments

@coljac
Copy link

coljac commented Jan 22, 2020

I have successfully used sshmon on several machines (it's amazing!). On a new machine, after configuring a host and hitting connect, the GUI reports "connecting" and gets stuck there. The following is written to the console. The temp files are there in /tmp.

[2020-01-22T22:11:55.757Z] DEBUG: sshmon/7298 on hubble: register socket 2f_v_ftfAnSJrydkAAAB (scope=api/socket-notify)
[2020-01-22T22:12:07.620Z] DEBUG: sshmon/7298 on hubble: ssh -N -T -M -o ControlPersist=no -o BatchMode=yes -o StreamLocalBindUnlink=yes -o ServerAliveInterval=5 -o ServerAliveCountMax=3 -S /tmp/sshmon-7298wQE0Ol2Rrm5x/1 predator (scope=host/ssh, childPid=7794)
[2020-01-22T22:12:07.620Z] DEBUG: sshmon/7298 on hubble:  (scope=redux)
    action: {
      "type": "HOST_STATE_CHANGE",
      "id": "predator",
      "status": "connecting",
      "pid": 7794,
      "controlPath": "/tmp/sshmon-7298wQE0Ol2Rrm5x/1",
      "reason": "api"
    }
[2020-01-22T22:12:07.622Z]  INFO: sshmon/7298 on hubble: api call success (scope=api/socket-setup)
    apiCall: {
      "key": "hostConnect",
      "args": {
        "id": "predator"
      }
    }
[2020-01-22T22:12:07.624Z] ERROR: sshmon/7298 on hubble: watcher error (scope=host/thunks/connect-thunks, err.code=ENOSPC)
    Error: watch /tmp/sshmon-7298wQE0Ol2Rrm5x ENOSPC
        at _errnoException (util.js:1031:13)
        at FSWatcher.start (fs.js:1397:19)
        at Object.fs.watch (fs.js:1423:11)
        at createFsWatchInstance (/snapshot/sshmon/server/node_modules/chokidar/lib/nodefs-handler.js:37:15)
        at setFsWatchListener (/snapshot/sshmon/server/node_modules/chokidar/lib/nodefs-handler.js:80:15)
        at FSWatcher.NodeFsHandler._watchWithNodeFs (/snapshot/sshmon/server/node_modules/chokidar/lib/nodefs-handler.js:229:14)
        at FSWatcher.NodeFsHandler._handleDir (/snapshot/sshmon/server/node_modules/chokidar/lib/nodefs-handler.js:408:19)
        at FSWatcher.<anonymous> (/snapshot/sshmon/server/node_modules/chokidar/lib/nodefs-handler.js:456:19)
        at FSWatcher.<anonymous> (/snapshot/sshmon/server/node_modules/chokidar/lib/nodefs-handler.js:461:16)
        at FSReqWrap.oncomplete (fs.js:167:5)
@hpello
Copy link
Owner

hpello commented Jan 23, 2020

ENOSPC means "Device out of space". It probably means that you have reached the maximum number of open file watchers.

Could you try to increase fs.inotify.max_user_watches, like advised in https://stackoverflow.com/questions/22475849/node-js-what-is-enospc-error-and-how-to-solve ?

@coljac
Copy link
Author

coljac commented Jan 26, 2020

Correct! Issue was Dropbox using all the file watchers. Sshmon working again fine.

@coljac coljac closed this as completed Jan 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants