pm2-meteor seem not working with pm2 version 3.0.0

[adalidda]

Hi,

I just upgrade pm2 to version 3.0.0 on my host and development machine.
When I run pm2-meteor deploy on my development machine, I got the following error message:
Building your app and deploying to host machine
missing pm2

ERROR: Please make sure you have node, npm and pm2 installed on your remote machine!

----- Version running on my development machine:
meteor --version
Meteor 1.7.0.3

pm2 -v
3.0.0

node -v
v8.11.2

npm -v
6.1.0

------ Version running on my Server/Host:
pm2 -v
3.0.0

which node
/root/.nvm/versions/node/v8.11.2/bin/node

which pm2
/root/.nvm/versions/node/v8.11.2/bin/pm2

node -v
v8.11.2

npm -v
6.1.0

Thank You
Adalidda

[frankwo1]

Hi,
I have the same issue - I downgraded pm2 (2.10.3) on my server but still have the same problem
Can u suggest a solution?
Thanks
Frank

[adalidda]

Hi, I didn't found solution so move to use MUP instead. Thank you Kosona

…

On Tue, Aug 7, 2018, 11:46 AM FrankWo1 ***@***.***> wrote: Hi, I have the same issue - I downgraded pm2 (2.10.3) on my server but still have the same problem Can u suggest a solution? Thanks Frank — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#78 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AOoSB8mtJJ346NWQ1fkksK-W2P801CxHks5uOWH6gaJpZM4VPJ8Z> .

[frankwo1]

Thanks - will try that
I have tried to bundle and untar and run "pm2 start pm2-env.json"
Not sure where the problem is - have tried it with both [email protected] and [email protected]

[frankwo1]

Hi Kosona, Would you share your MUP settings? MUP has always been a bit unreliable to me and I can't seem to get it to install correctly - I am unable to access the instance behind the firewall - most likely one of my settings is awry or missing: (see below)
Thanks
Frank

module.exports = {
servers: {
one: {
// TODO: set host address, username, and authentication method
host: "142.142.142.142",
username: "root",
pem:"~/path/to/rsa",
}
},
appName: "myApp",
meteor: {
// TODO: change app name and path
name: 'myApp',
path: '../',

servers: {
  one: {},
},

buildOptions: {
  serverOnly: true,
},

env: {
  // TODO: Change to your app's url
  // If you are using ssl, it needs to start with https://
  ROOT_URL: 'http://142.142.142.142',
  PORT: 80,
  MONGO_URL: "mongodb://myapp.mlab.com:43532/myapp"
},

// ssl: { // (optional)
//   // Enables let's encrypt (optional)
//   autogenerate: {
//     email: '[email protected]',
//     // comma seperated list of domains
//     domains: 'website.com,www.website.com'
//   }
// },

    docker: {
      // change to 'kadirahq/meteord' if your app is not using Meteor 1.4
      image: 'abernix/meteord:node-8.4.0-base',
      // imagePort: 80, // (default: 80, some images EXPOSE different ports)
    },


// This is the maximum time in seconds it will wait
// for your app to start
// Add 30 seconds if the server has 512mb of ram
// And 30 more if you have binary npm dependencies.
deployCheckWaitTime: 120,

// Show progress bar while uploading bundle to server
// You might need to disable it on CI servers
enableUploadProgressBar: true

}
};

[zodern]

@frankwo1 if you run mup meteor status, what do the lines after App running at show?

[frankwo1]

Exposed Ports:
- 3000/tcp
Published Ports:
- 80/tcp => 80
App running at http://142.142.142.142:80
- Available in app's docker container: false
- Available on server: true
- Available on local computer: false

[frankwo1]

any suggestions? Things to try? (I have already switched to Zodern docker image, changed some of the port settings, opened all firewall ports )

[andruschka]

Hey folks - I think this is because of using nvm. We also run into errors when having installed system nodejs and then installing nvm... Our solution was to removing nvm and reinstalling nodejs via apt-get ...

[adalidda]

Hi,

I am using the below option and now everything is running fine with PM2.

If you want to deploy the bundle by yourself
$ pm2-meteor generateBundle
then transfer it to your machine, unzip it and run
$ pm2 start pm2-env.json