Mup deploy node version problem

i created simple app and tried to deploy it using mup.
This is what i see.

Started TaskList: Configuring App
[159.65.127.118] - Pushing the Startup Script
[159.65.127.118] - Pushing the Startup Script: SUCCESS
[159.65.127.118] - Sending Environment Variables
[159.65.127.118] - Sending Environment Variables: SUCCESS

Started TaskList: Start Meteor
[159.65.127.118] - Start Meteor
[159.65.127.118] - Start Meteor: SUCCESS
[159.65.127.118] - Verifying Deployment
[159.65.127.118] x Verifying Deployment: FAILED

	      ------------------------------------STDERR------------------------------------
	        % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
	                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
	curl: (7) Failed to connect to 172.17.0.5 port 3000: Connection refused
	  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
	                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
	curl: (7) Failed to connect to 172.17.0.5 port 3000: Connection refused
	  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
	                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
	curl: (7) Failed to connect to 172.17.0.5 port 3000: Connection refused
	  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
	                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
	curl: (7) Failed to connect to 172.17.0.5 port 3000: Connection refused
	Container spent too much time restarting.
	=> Logs:
	=> Starting meteor app on port:3000
	Meteor requires Node v12.0.0 or later.
	=> Starting meteor app on port:3000
	Meteor requires Node v12.0.0 or later.
	=> Starting meteor app on port:3000

How i can specify node version then? Was sure that mup setup takes care on this. Im using DigitalOcean droplet. Thx i advance.

In your mup.js config file there is this line under app.docker:

image: 'abernix/meteord:base'

You can change this, for example, to such:

image: 'abernix/meteord:node-12.16.1-base'

This would select a specific node version. You can view these here: https://hub.docker.com/r/abernix/meteord

You can view which node version is used in which Meteor version here: https://docs.meteor.com/changelog.html

2 Likes

Thx @vooteles i alredy changed it to node-12-base and i have new error :slight_smile:

Started TaskList: Pushing Meteor App
[206.189.63.106] - Pushing Meteor App Bundle to the Server
[206.189.63.106] - Pushing Meteor App Bundle to the Server: SUCCESS
[206.189.63.106] - Prepare Bundle
[206.189.63.106] x Prepare Bundle: FAILED

	      ------------------------------------STDERR------------------------------------
	      free(): invalid pointer
	SIGABRT: abort
	PC=0x7f9f9778ef47 m=0 sigcode=18446744073709551610
	signal arrived during cgo execution

	goroutine 1 [syscall, locked to thread]:
	runtime.cgocall(0x4afd50, 0xc42004dcc0, 0xc42004dce8)
		/usr/lib/go-1.8/src/runtime/cgocall.go:131 +0xe2 fp=0xc42004dc90 sp=0xc42004dc50
	github.com/docker/docker-credential-helpers/secretservice._Cfunc_free(0x1e53da0)
		github.com/docker/docker-credential-helpers/secretservice/_obj/_cgo_gotypes.go:111 +0x41 fp=0xc42004dcc0 sp=0xc42004dc90
	github.com/docker/docker-credential-helpers/secretservice.Secretservice.List.func5(0x1e53da0)
		/build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/secretservice/secretservice_linux.go:96 +0x60 fp=0xc42004dcf8 sp=0xc42004dcc0
	github.com/docker/docker-credential-helpers/secretservice.Secretservice.List(0x0, 0x756060, 0xc420012390)
		/build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/secretservice/secretservice_linux.go:97 +0x217 fp=0xc42004dda0 sp=0xc42004dcf8
	github.com/docker/docker-credential-helpers/secretservice.(*Secretservice).List(0x77e548, 0xc42004de88, 0x410022, 0xc4200122f0)
		<autogenerated>:4 +0x46 fp=0xc42004dde0 sp=0xc42004dda0
	github.com/docker/docker-credential-helpers/credentials.List(0x756ba0, 0x77e548, 0x7560e0, 0xc42000e018, 0x0, 0x10)
		/build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/credentials/credentials.go:145 +0x3e fp=0xc42004de68 sp=0xc42004dde0
	github.com/docker/docker-credential-helpers/credentials.HandleCommand(0x756ba0, 0x77e548, 0x7ffe23c0de82, 0x4, 0x7560a0, 0xc42000e010, 0x7560e0, 0xc42000e018, 0x40e398, 0x4d35c0)
		/build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/credentials/credentials.go:60 +0x16d fp=0xc42004ded8 sp=0xc42004de68
	github.com/docker/docker-credential-helpers/credentials.Serve(0x756ba0, 0x77e548)
		/build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/obj-x86_64-linux-gnu/src/github.com/docker/docker-credential-helpers/credentials/credentials.go:41 +0x1cb fp=0xc42004df58 sp=0xc42004ded8
	main.main()
		/build/golang-github-docker-docker-credential-helpers-cMhSy1/golang-github-docker-docker-credential-helpers-0.5.0/secretservice/cmd/main_linux.go:9 +0x4f fp=0xc42004df88 sp=0xc42004df58
	runtime.main()
		/usr/lib/go-1.8/src/runtime/proc.go:185 +0x20a fp=0xc42004dfe0 sp=0xc42004df88
	runtime.goexit()
		/usr/lib/go-1.8/src/runtime/asm_amd64.s:2197 +0x1 fp=0xc42004dfe8 sp=0xc42004dfe0

	goroutine 17 [syscall, locked to thread]:
	runtime.goexit()
		/usr/lib/go-1.8/src/runtime/asm_amd64.s:2197 +0x1

	rax    0x0
	rbx    0x7ffe23c0cfc0
	rcx    0x7f9f9778ef47
	rdx    0x0
	rdi    0x2
	rsi    0x7ffe23c0cd50
	rbp    0x7ffe23c0d0c0
	rsp    0x7ffe23c0cd50
	r8     0x0
	r9     0x7ffe23c0cd50
	r10    0x8
	r11    0x246
	r12    0x7ffe23c0cfc0
	r13    0x1000
	r14    0x0
	r15    0x30
	rip    0x7f9f9778ef47
	rflags 0x246
	cs     0x33
	fs     0x0
	gs     0x0
	The command '/bin/sh -c cd /built_app/programs/server &&     npm install --unsafe-perm' returned a non-zero code: 1

	real	1m52.135s
	user	0m3.151s
	sys	0m3.968s

	      ------------------------------------STDOUT------------------------------------
	      ules/grpc/src/node/extension_binary/node-v72-linux-x64-glibc/grpc_node.node" "--module_name=grpc_node" "--module_path=/built_app/programs/server/npm/node_modules/grpc/src/node/extension_binary/node-v72-linux-x64-glibc" "--napi_version=5" "--node_abi_napi=napi"
	gyp ERR! cwd /built_app/programs/server/npm/node_modules/grpc
	gyp ERR! node -v v12.16.1
	gyp ERR! node-gyp -v v5.0.7
	gyp ERR! not ok
	node-pre-gyp ERR! build error
	node-pre-gyp ERR! stack Error: Failed to execute '/opt/nodejs/bin/node /opt/nodejs/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --library=static_library --module=/built_app/programs/server/npm/node_modules/grpc/src/node/extension_binary/node-v72-linux-x64-glibc/grpc_node.node --module_name=grpc_node --module_path=/built_app/programs/server/npm/node_modules/grpc/src/node/extension_binary/node-v72-linux-x64-glibc --napi_version=5 --node_abi_napi=napi' (1)
	node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/built_app/programs/server/npm/node_modules/grpc/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
	node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:311:20)
	node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:1021:16)
	node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
	node-pre-gyp ERR! System Linux 4.15.0-122-generic
	node-pre-gyp ERR! command "/opt/nodejs/bin/node" "/built_app/programs/server/npm/node_modules/grpc/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build" "--library=static_library"
	node-pre-gyp ERR! cwd /built_app/programs/server/npm/node_modules/grpc
	node-pre-gypFailed to execute '/opt/nodejs/bin/node /opt/nodejs/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --library=static_library --module=/built_app/programs/server/npm/node_modules/grpc/src/node/extension_binary/node-v72-linux-x64-glibc/grpc_node.node --module_name=grpc_node --module_path=/built_app/programs/server/npm/node_modules/grpc/src/node/extension_binary/node-v72-linux-x64-glibc --napi_version=5 --node_abi_napi=napi' (1)
	 ERR! node -v v12.16.1
	node-pre-gyp ERR! node-pre-gyp -v v0.10.3
	node-pre-gyp ERR! not ok
	npm ERR! code ELIFECYCLE
	npm ERR! errno 1
	npm ERR! grpc@1.16.0 install: `node-pre-gyp install --fallback-to-build --library=static_library`
	npm ERR! Exit status 1
	npm ERR!
	npm ERR! Failed at the grpc@1.16.0 install script.
	npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

	npm ERR! A complete log of this run can be found in:
	npm ERR!     /root/.npm/_logs/2020-10-30T21_03_20_614Z-debug.log
	npm ERR! code ELIFECYCLE
	npm ERR! errno 1
	npm ERR! meteor-dev-bundle@ install: `node npm-rebuild.js`
	npm ERR! Exit status 1
	npm ERR!
	npm ERR! Failed at the meteor-dev-bundle@ install script.
	npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

	npm ERR! A complete log of this run can be found in:
	npm ERR!     /root/.npm/_logs/2020-10-30T21_03_20_712Z-debug.log

	      ------------------------------------------------------------------------------ ```

Upgrading the docker base image isn’t just a matter of changing the setting. You basically need to get MUP to set it up again from scratch. So something like a mup stop to stop the running instance, and then a mup setup to set up a new docker instance, followed by a mup deploy. There is a little down time in this approach.

@mikkelking of course. I did i even created new droplet for double check. Nothing helps.