[Meteor 2.13] node v14.21.4 not found

[pmogollons]

Deployment fails because node v14.21.4 is not found. The script is trying to install from nvm, but I dont think this version is available from nvm.

Meteor version: 2.13

You need to run "nvm install N/A" to install it before using it.
npm notice 
npm notice New major version of npm available! 8.19.4 -> 9.8.1
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.8.1>
npm notice Run `npm install -g [email protected]` to update!
npm notice 
N/A: version "N/A -> N/A" is not yet installed.

You need to run "nvm install N/A" to install it before using it.
Version '14.21.4' not found - try `nvm ls-remote` to browse available versions.
N/A: version "14.21.4 -> N/A" is not yet installed.

You need to run "nvm install 14.21.4" to install it before using it.
! WARNING: Version '14.21.4' does not exist.
tput: terminal attributes: No such device or address

key 'app_staging_dir' does not exist
npm WARN deprecated [email protected]: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future
npm WARN deprecated @npmcli/[email protected]: This functionality has been moved to @npmcli/fs
(node:20039) [DEP0150] DeprecationWarning: Setting process.config is deprecated. In the future the property will be read-only.
(Use `node --trace-deprecation ...` to show where the warning was created)

2023/08/04 15:51:36.327690 [INFO] Running command .platform/hooks/prebuild/47env.sh
2023/08/04 15:51:36.360305 [INFO] env_version=
Long Env is not enabled.

2023/08/04 15:51:36.360323 [INFO] key 'MUP_ENV_FILE_VERSION' does not exist

[pmogollons]

This will happen with versions of meteor > 2.13 because of the custom node version.

To fix this installing with curl will be the solution instead of nvm. Something like this.

Or just making it fallback to the latest nvm node version 14.21.3 (Not ideal, but easier)

[Roshdy]

meteor 2.15 now, is there any workaround for this?
If the workarounds are what mentioned above, please provide step how to do it in mup.js
or should i downgrade to 2.13.0?

[Roshdy]

i ended up downgrading to 2.12

[JLartigaud]

I've been struggling for weeks on trying to upgrade to 2.15, but as always, Meteor is such a pain.
Tried eveything with CodePipeline et .ebsettings to "emulate" the custom 2.14 node version, but nothing works.
Downgrading too ;(

[paulincai]

Ok now @JLartigaud you made me curious... How come I don't have these problems... I deploy 2.15 and my EBS runs it with Node 14.21.3 (which exists in the Node14 AMI machines in EBS). My local Node version within dev. Meteor is 14.21.4 for sure.

I had this EBS setup started a long time ago and I think I first created the environment and then deployed to the same name. Do you already have an environment or/and deploy to an older environment of an older Meteor version. Or asked differently, do you already have an EC2 machine running in EBS with a Node 14 platform (such as 5.9.0)?

[JLartigaud]

To be more specific, I'm stuck on meteor 1.9 with an old EB platform :
We've been running this app since 2018, and never had any deployment issue (using jenkins at first, and now fully with CodeBuild).
The 1.9 platform:

However, I've been trying my 2.15 new version (upgraded successfuly on local) on the same Node 14 platform as yours, but had a lot of weird behaviours. First unable to execute the app because of the node 14.21.4 version, then for unknown reason (the app is not even launching anymore on logs). Sometimes, because nvm was not available on the machine (and start.sh not wanting to launch). I'm pretty sure I'm doing something wrong (that was ok with old platform, but not this one).

Can I push a bit your sympathy and ask what you have in your buildspec.yml / .ebextensions ? I've been trying a loooot of stuff during those last weeks but, except finding lost people like me, never figured out :3

I've even been trying to integrate "wget https://static.meteor.com/dev-bundle-node-os/v14.21.4/node-v14.21.4-linux-x64.tar.gz -O node.tar.xz" or those kind of stuff in my buildspec...

(we're facing issues with mongo 5.0 since Atlas migrated, meteor 1.9 has oplog issues with mongo 5.0 and it was way time to upgrade, anyway).

By advance, thank you, you may save a life today :p

[paulincai]

@JLartigaud from what I read on my logs as shared above, translated to my English: sorry ... could not find a version, will use what we have. I know this is laborious but could you try to deploy a naked meteor project with your mup.js settings and see if you at least get the server logs. It happened to me a couple of times while trying Meteor 3 with EBS, to deploy versions with errors in them. I would struggle for hours trying to understand why my initial Meteor 3 deployment on a new EBS environment is not working when in fact I had a wrong string for my DB connection. At those times I would also not be able to get the logs

Unlike other situations I see in the Forum and in Git where people had problems with this patched Node versions, 14.21.4, with Docker or playn Linux machines, on EBS we do deploy on a machine (AMI) that already has Node 14.21.3 on it.

My handle in the forum is @paulishca. Write to me in private if you want to exchange some contacts and connect more synchronous.