Receiving error while trying to start mock APIs

[sawright02]

I'm new to mockoon and probably doing (or not doing) something obvious. I am simply attempting to run my mock APIs via the cli, but am receiving the following error. Also, the error file referenced below is empty. What am I doing wrong?

? Please select an environment Demo API
› Error: Cannot start mockoon-demo-api due to errors (see errors in /Users/{username}{/.mockoon-cli/logs/mockoon-demo-api-error.log)

// Reference Info:
node version: 14.17.1
/Users/{username}/.nvm/versions/node/v14.17.1/lib
├── @mockoon/cli@1.0.1
├── npm@6.14.13
└── pm2@5.1.0

[255kb]

Hi, could you please check the logs and copy paste the error here? This suggests that something went wrong at runtime, that the CLI couldn't foresee.

[sawright02]

I will try uninstalling/reinstalling the CLI and also check my pm2 logs. Thanks!

[sawright02]

Uninstalling/Reinstalling did not help. Here is an excerpt from pm2.log:

2021-06-25T11:53:23: PM2 log: App [mockoon-demo-api:0] starting in -fork mode-
2021-06-25T11:53:23: PM2 log: App [mockoon-demo-api:0] exited with code [0] via signal [SIGKILL]
2021-06-25T11:53:23: PM2 log: Script /usr/local/lib/node_modules/@mockoon/cli/dist/libs/server.js had too many unstable restarts (1). Stopped. "errored"
2021-06-25T11:53:26: PM2 log: App [mockoon-demo-api:0] online
2021-06-25T11:53:26: PM2 error: Cancelling versioning data parsing
2021-06-25T11:53:26: PM2 log: Stopping app:mockoon-demo-api id:0
2021-06-25T11:53:26: PM2 error: app=mockoon-demo-api id=0 does not have a pid

[255kb]

I tried to reproduce this bug but without success.
Could you please try to run the server.js script directly with Node.js to see if the problem comes from PM2.
To do so:
node /usr/local/lib/node_modules/@mockoon/cli/dist/libs/server.js --data ~/.mockoon-cli/data/mockoon-demo-api.json.
~/.mockoon-cli/data/mockoon-demo-api.json is the path to the environment file that has been "prepared" for the CLI. It should work but th name could vary.

Please let me know if this worked.

[sawright02]

Yes, running server.js directly worked just fine.

[255kb]

So it seems to be related to PM2. After investigating, I couldn't find any recent issue with this lib. All the similar errors to what you are seeing are quite old and suggest that something is wrong with the PM2 package installation. I would tend to believe that it's an install issue as I just noticed that your versioning shows PM2@5.1.0. But it should be using v4.5.6 as I only updated PM2 to v5.1.0 1 hour ago and only on the release/next branch.
As a last try to solve the problem I would suggest that you clean NPM's cash and try to reinstall the CLI.