zodern / meteor-up

Production Quality Meteor Deployment to Anywhere
http://meteor-up.com/
MIT License
1.27k stars 280 forks source link

bug: possible ssh2-classic problem #1323

Open jirikrepl opened 2 years ago

jirikrepl commented 2 years ago

Hello, I encountered this problem when I updated to version 1.5.9. I used v1.5.8 without any problems. In the source code I saw you changed shh2 package for ssh2-classic.

This change seems to cause some problems for me. Strange thing is, I can deploy fine with mup deploy. But if I schedule deployment with at command, I get this error.

Mup version (mup --version): 1.5.9

Mup config

{
  "servers": {
    "one": {
      "host": "1.2.3.4",
      "username": "root",
      "pem": "~/.ssh/pem"
    }
  },
  "app": {
    "name": "my-app",
    "path": "../../",
    "servers": {
      "one": {}
    },
    "buildOptions": {
      "serverOnly": true,
      "cleanBuildLocation": true
    },
    "env": {
      "ROOT_URL": "https://subdomain.host.com",
    },
    "deployCheckWaitTime": 300,
    "docker": {
      "image": "zodern/meteor:0.6.1-root",
      "args": [
        "-v /etc/timezone:/etc/timezone",
        "-v /etc/localtime:/etc/localtime"
      ],
      "stopAppDuringPrepareBundle": true,
      "imagePort": 3000
    },
    "enableUploadProgressBar": true,
    "type": "meteor"
  },
  "proxy": {
    "domains": "subdomain.host.com",
    "ssl": {
      "letsEncryptEmail": "email@domain.com",
      "forceSSL": true
    }
  },
}

Output of command

events.js:174
      throw er; // Unhandled 'error' event
      ^

Error: read ETIMEDOUT
    at TCP.onStreamRead (internal/stream_base_commons.js:111:27)
Emitted 'error' event at:
    at Socket.<anonymous> (/Users/jirkakrepl/.nvm/versions/node/v10.24.1/lib/node_modules/mup/node_modules/ssh2-classic/lib/client.js:307:10)
    at Socket.emit (events.js:203:15)
    at emitErrorNT (internal/streams/destroy.js:91:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
    at process._tickCallback (internal/process/next_tick.js:63:19)