1.4 doesn't detect that Meteor has started

With 1.4, I get the following error

	      ------------------------------------STDERR------------------------------------
	      Too much time spent restarting.
	=> Starting meteor app on port:80
	Note: you are using a pure-JavaScript implementation of bcrypt.
	While this implementation will work correctly, it is known to be
	approximately three times slower than the native implementation.
	In order to use the native implementation instead, run

	  meteor npm install --save bcrypt

	in the root directory of your application.
	Meteor login token  9f8sd0f98sdfj3j4jFFFF1

	=> Redeploying previous version of the app

Which is strange, since it seems like it has started (btw, tried expanding the wait time, with no result). Downgrading with exactly the same settings worked. I think the problem might be the additional line that I console.log - do you do some kind of regexp on the output to determine when the container is ready?

[AfaaqSuhail]

Hey @zodern I am using 1.5.1 mup version, has changed the image name according to http://meteor-up.com/docs#meteor-support but still my container goes down continuously, I am pasting my mup deploy --verbose output, Please guide me through this

  ------------------------------------STDERR------------------------------------
      ify/examples/custom-cache-example/node_modules/reify/lib/parsers: implausibly old time stamp 1970-01-01 00:00:00
tar: bundle/programs/server/npm/node_modules/meteor/modules/node_modules/reify/examples/top-level-example/node_modules/acorn/src/bin: implausibly old time stamp 1970-01-01 00:00:00
tar: bundle/programs/server/npm/node_modules/meteor/modules/node_modules/reify/examples/top-level-example/node_modules/acorn/src/loose: implausibly old time stamp 1970-01-01 00:00:00
tar: bundle/programs/server/npm/node_modules/meteor/modules/node_modules/reify/examples/top-level-example/node_modules/acorn/src/walk: implausibly old time stamp 1970-01-01 00:00:00
tar: bundle/programs/server/npm/node_modules/meteor/modules/node_modules/reify/examples/top-level-example/node_modules/magic-string/src/utils: implausibly old time stamp 1970-01-01 00:00:00
tar: bundle/programs/server/npm/node_modules/meteor/modules/node_modules/reify/examples/top-level-example/node_modules/reify/lib/parsers: implausibly old time stamp 1970-01-01 00:00:00
tar: bundle/programs/server/npm/node_modules/meteor/babel-compiler/node_modules/reify/examples/babel-parser-example/node_modules/reify/lib/parsers/acorn-extensions: implausibly old time stamp 1970-01-01 00:00:00
tar: bundle/programs/server/npm/node_modules/meteor/cfs_data-man/node_modules/request/node_modules/bl/node_modules/readable-stream/node_modules/core-util-is/lib: implausibly old time stamp 1970-01-01 00:00:00
tar: bundle/programs/server/npm/node_modules/meteor/cfs_data-man/node_modules/request/node_modules/bl/node_modules/readable-stream/node_modules/isarray/build: implausibly old time stamp 1970-01-01 00:00:00
tar: bundle/programs/server/npm/node_modules/meteor/modules/node_modules/reify/examples/babel-parser-example/node_modules/reify/lib/parsers/acorn-extensions: implausibly old time stamp 1970-01-01 00:00:00
tar: bundle: implausibly old time stamp 1970-01-01 00:00:00
npm WARN deprecated This version of npm lacks support for important features,
npm WARN deprecated such as scoped packages, offered by the primary npm
npm WARN deprecated registry. Consider upgrading to at least npm@2, if not the
npm WARN deprecated latest stable version. To upgrade to npm@2, run:
npm WARN deprecated 
npm WARN deprecated   npm -g install npm@latest-2
npm WARN deprecated 
npm WARN deprecated To upgrade to the latest stable version, run:
npm WARN deprecated 
npm WARN deprecated   npm -g install npm@latest
npm WARN deprecated 
npm WARN deprecated (Depending on how Node.js was installed on your system, you
npm WARN deprecated may need to prefix the preceding commands with `sudo`, or if
npm WARN deprecated on Windows, run them from an Administrator prompt.)
npm WARN deprecated 
npm WARN deprecated If you're running the version of npm bundled with
npm WARN deprecated Node.js 0.10 LTS, be aware that the next version of 0.10 LTS
npm WARN deprecated will be bundled with a version of npm@2, which has some small
npm WARN deprecated backwards-incompatible changes made to `npm run-script` and
npm WARN deprecated semver behavior.
npm ERR! Error: This version of npm doesn't support scoped packages (caused by reference to @babel/parser@https://registry.npmjs.org/@babel/parser/-/parser-7.7.5.tgz). Update to npm@2+.
npm ERR!     at add (/opt/nodejs/lib/node_modules/npm/lib/cache.js:248:15)
npm ERR!     at Function.cache.add (/opt/nodejs/lib/node_modules/npm/lib/cache.js:208:10)
npm ERR!     at resolver (/opt/nodejs/lib/node_modules/npm/lib/install.js:712:11)
npm ERR!     at null._onTimeout (/opt/nodejs/lib/node_modules/npm/lib/install.js:666:7)
npm ERR!     at Timer.listOnTimeout [as ontimeout] (timers.js:121:15)
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!     <http://github.com/npm/npm/issues>

npm ERR! System Linux 5.3.0-1023-aws
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "i"
npm ERR! cwd /bundle/bundle/programs/server
npm ERR! node -v v0.10.43
npm ERR! npm -v 1.4.29
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /bundle/bundle/programs/server/npm-debug.log
npm ERR! not ok code 0
 
=> Redeploying previous version of the app
 

      ------------------------------------STDOUT------------------------------------
IP: 172.17.0.3
IP: 172.17.0.3
IP: 172.17.0.3
CONTAINER IP EMPTRY
IP: 172.17.0.3
IP: 172.17.0.3
IP: 172.17.0.3
IP: 172.17.0.3
IP: 172.17.0.3
CONTAINER IP EMPTRY
IP: 172.17.0.3
IP: 172.17.0.3
IP: 172.17.0.3
IP: 172.17.0.3
IP: 172.17.0.3
CONTAINER IP EMPTRY
IP: 172.17.0.3
IP: 172.17.0.3
IP: 172.17.0.3
IP: 172.17.0.3
IP: 172.17.0.3
CONTAINER IP EMPTRY
IP: 
Container has no IP Address, likely from the app crashing.
IP: 172.17.0.3
IP: 172.17.0.3
IP: 172.17.0.3
IP: 172.17.0.3
IP: 172.17.0.3
CONTAINER IP EMPTRY
IP: 
Container has no IP Address, likely from the app crashing.
CONTAINER IP EMPTRY
IP: 
Container has no IP Address, likely from the app crashing.
CONTAINER IP EMPTRY
IP: 
Container has no IP Address, likely from the app crashing.
CONTAINER IP EMPTRY
IP: 
Container has no IP Address, likely from the app crashing.
IP: 172.17.0.3
IP: 172.17.0.3
IP: 172.17.0.3
IP: 172.17.0.3
IP: 172.17.0.3
CONTAINER IP EMPTRY
IP: 
Container has no IP Address, likely from the app crashing.
CONTAINER IP EMPTRY
IP: 
Container has no IP Address, likely from the app crashing.
CONTAINER IP EMPTRY
IP: 
Container has no IP Address, likely from the app crashing.
CONTAINER IP EMPTRY
IP: 
Container has no IP Address, likely from the app crashing.
CONTAINER IP EMPTRY
IP: 
Container has no IP Address, likely from the app crashing.
=> Container status:
restarted: 8 times {"Bridge":"","SandboxID":"877fd27054b923e7efd5798fd37e34ec551d8656e5d9fea298977f623cb46bc7","HairpinMode":false,"LinkLocalIPv6Address":"","LinkLocalIPv6PrefixLen":0,"Ports":{},"SandboxKey":"/var/run/docker/netns/877fd27054b9","SecondaryIPAddresses":null,"SecondaryIPv6Addresses":null,"EndpointID":"","Gateway":"","GlobalIPv6Address":"","GlobalIPv6PrefixLen":0,"IPAddress":"","IPPrefixLen":0,"IPv6Gateway":"","MacAddress":"","Networks":{"bridge":{"IPAMConfig":null,"Links":null,"Aliases":null,"NetworkID":"1886e0c022ce5e9e5366a9a8547169a3d3caba94aaebf01c8e11fea23ba27dc5","EndpointID":"","Gateway":"","IPAddress":"","IPPrefixLen":0,"IPv6Gateway":"","GlobalIPv6Address":"","GlobalIPv6PrefixLen":0,"MacAddress":"","DriverOpts":null}}} {"Status":"restarting","Running":true,"Paused":false,"Restarting":true,"OOMKilled":false,"Dead":false,"Pid":0,"ExitCode":1,"Error":"","StartedAt":"2020-07-02T11:48:09.242382921Z","FinishedAt":"2020-07-02T11:48:14.017456654Z"}

To see more logs type 'mup logs --tail=200'


      ------------------------------------------------------------------------------

[asgaraliyev]

@AfaaqSuhail same error .How did you fix it?