Closed renanlecaro closed 2 years ago
My change did let the app restart, but trying to deploy anything with "mup deploy" quickly throws this
failed to process "\"\\\"v12.14.0\"\"": unexpected end of statement while looking for matching double-quote
I'll check back tomorrow, the app is running now so i'll stop touching it. My latest changes i originally wanted to deploy are still not out
Just realized EXACT_NODE_VERSION is a boolean flag. Still trying to get my apps to deploy
I tried forcing the version by adding this in the env part of the mup.js file
EXACT_NODE_VERSION: true,
NODE_VERSION: "v12.14.0",
but then mup deploy
crashed with this error
]=> Setting node version
[188.166.160.106]NODE_VERSION=v12.14.0
[188.166.160.106]v12.14.0 is already installed.
[188.166.160.106]Now using node v12.14.0 (npm v6.13.4)
[188.166.160.106]default -> v12.14.0 *
[188.166.160.106]=> Starting meteor app on port 3000
[188.166.160.106]## There is an issue with `node-fibers` ##
[188.166.160.106]`/built_app/programs/server/node_modules/fibers/bin/linux-x64-72-glibc/fibers.node` is missing.
[188.166.160.106]
[188.166.160.106]Try running this to fix the issue: /home/app/.nvm/versions/node/v12.14.0/bin/node /built_app/programs/server/node_modules/fibers/build
[188.166.160.106]Error: Cannot find module '/built_app/programs/server/node_modules/fibers/bin/linux-x64-72-glibc/fibers'
[188.166.160.106]Require stack:
[188.166.160.106]- /built_app/programs/server/node_modules/fibers/fibers.js
[188.166.160.106]- /built_app/programs/server/boot.js
[188.166.160.106]- /built_app/main.js
[188.166.160.106] at Function.Module._resolveFilename (internal/modules/cjs/loader.js:797:15)
[188.166.160.106] at Function.Module._load (internal/modules/cjs/loader.js:690:27)
[188.166.160.106] at Module.require (internal/modules/cjs/loader.js:852:19)
[188.166.160.106] at require (internal/modules/cjs/helpers.js:74:18)
[188.166.160.106] at Object.<anonymous> (/built_app/programs/server/node_modules/fibers/fibers.js:14:39)
[188.166.160.106] at Module._compile (internal/modules/cjs/loader.js:959:30)
[188.166.160.106] at Module.Mp._compile (/built_app/programs/server/runtime.js:99:23)
[188.166.160.106] at Object.Module._extensions..js (internal/modules/cjs/loader.js:995:10)
[188.166.160.106] at Module.load (internal/modules/cjs/loader.js:815:32)
[188.166.160.106] at Module.Mp.load (/built_app/programs/server/runtime.js:46:33)
[188.166.160.106]/built_app/programs/server/node_modules/fibers/fibers.js:23
[188.166.160.106] throw new Error('Missing binary. See message above.');
[188.166.160.106] ^
[188.166.160.106]
[188.166.160.106]Error: Missing binary. See message above.
[188.166.160.106] at Object.<anonymous> (/built_app/programs/server/node_modules/fibers/fibers.js:23:9)
[188.166.160.106] at Module._compile (internal/modules/cjs/loader.js:959:30)
[188.166.160.106] at Module.Mp._compile (/built_app/programs/server/runtime.js:99:23)
[188.166.160.106] at Object.Module._extensions..js (internal/modules/cjs/loader.js:995:10)
[188.166.160.106] at Module.load (internal/modules/cjs/loader.js:815:32)
[188.166.160.106] at Module.Mp.load (/built_app/programs/server/runtime.js:46:33)
[188.166.160.106] at Function.Module._load (internal/modules/cjs/loader.js:727:14)
[188.166.160.106] at Module.require (internal/modules/cjs/loader.js:852:19)
[188.166.160.106] at require (internal/modules/cjs/helpers.js:74:18)
[188.166.160.106] at Object.<anonymous> (/built_app/programs/server/boot.js:2:15)
Looks like the build is made with the specified version, but the npm install is maybe done with another one, and then the compiled dependencies are not for the right version ? Not sure.
I though that maybe it was simply a problem of upgrading my meteor version, so i upgraded my app to 2.6, then deployed without forcing a version. I got the same problem of the mongo node lib not managing to connect to the local mongo server. But now my app requires node 14, i got the following error when trying to build it on node 12 :
=> Starting meteor app on port 3000
Meteor requires Node v14.0.0 or later.
=> Setting node version
NODE_VERSION=v12.14.0
v12.14.0 is already installed.
Now using node v12.14.0 (npm v6.13.4)
default -> v12.14.0 *
=> Starting meteor app on port 3000
Meteor requires Node v14.0.0 or later.
Upgrading mup and meteor to the latest version, runningmup setup
(what i was missing) then mup deploy
worked.
great, you can surely close this issue .
Hi
I've been deploying with mup without problem for about 2 years. Today the deploy failed, the node app couldn't connect to the local mongo server. It seems to be related to the node version (14.x.x) that got auto chosen by the node-version script (/home/app/scripts/node-version.js ) in the docker image "zodern/meteor".
I'm posting this to help other people with the same problem.
The fix was to force an older version with this bit of env config
then restart the app with
mup reconfig
I'm not sure how specific that problem is to my config and deploy setup (digital ocean) but it really took me by surprise, so I'm posting it here. I affected all my deploys at once, in production and on my separate staging server.
Mup version (
mup --version
): 1.5.7Mup config
Final output of
mup deploy
command after checking for a very long time :