Linux Application Error on Heroku Open Node App - linux

When I heroku open a basic node app, I get a series of errors. This comes after a successful heroku push.
I looked on GitHub and found the same error for a windows user, but I'm on a mac. It was suggested to run the command
--no-bin-links though I do not know what that will do. Help, please.
$ heroku logs
2015-11-18T22:00:42.465970+00:00 heroku[api]: Enable Logplex by adamcweitzman#gmail.com
2015-11-18T22:00:42.465970+00:00 heroku[api]: Release v2 created by adamcweitzman#gmail.com
2015-11-18T22:01:13.964233+00:00 heroku[api]: Deploy 95ab50f by adamcweitzman#gmail.com
2015-11-18T22:01:13.964233+00:00 heroku[api]: Release v3 created by adamcweitzman#gmail.com
2015-11-18T22:01:13.898217+00:00 heroku[api]: Scale to web=1 by adamcweitzman#gmail.com
2015-11-18T22:01:14.302776+00:00 heroku[slug-compiler]: Slug compilation started
2015-11-18T22:01:14.302785+00:00 heroku[slug-compiler]: Slug compilation finished
2015-11-18T22:01:15.248283+00:00 heroku[web.1]: Starting process with command `npm start`
2015-11-18T22:01:17.147380+00:00 app[web.1]:
2015-11-18T22:01:17.147400+00:00 app[web.1]:
2015-11-18T22:01:17.147399+00:00 app[web.1]: > shufflebod#0.0.0 start /app
2015-11-18T22:01:17.147400+00:00 app[web.1]: > node ./bin/www
2015-11-18T22:01:17.709403+00:00 app[web.1]: npm ERR! Linux 3.13.0-66-generic
2015-11-18T22:01:17.709767+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
2015-11-18T22:01:17.710006+00:00 app[web.1]: npm ERR! node v5.0.0
2015-11-18T22:01:17.710500+00:00 app[web.1]: npm ERR! npm v3.3.6
2015-11-18T22:01:17.710886+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2015-11-18T22:01:17.711057+00:00 app[web.1]: npm ERR! shufflebod#0.0.0 start: `node ./bin/www`
2015-11-18T22:01:17.711204+00:00 app[web.1]: npm ERR! Exit status 1
2015-11-18T22:01:17.711370+00:00 app[web.1]: npm ERR!
2015-11-18T22:01:17.711524+00:00 app[web.1]: npm ERR! Failed at the shufflebod#0.0.0 start script 'node ./bin/www'.
2015-11-18T22:01:17.711690+00:00 app[web.1]: npm ERR! This is most likely a problem with the shufflebod package,
2015-11-18T22:01:17.711879+00:00 app[web.1]: npm ERR! not with npm itself.
2015-11-18T22:01:17.712210+00:00 app[web.1]: npm ERR! node ./bin/www
2015-11-18T22:01:17.712025+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system:
2015-11-18T22:01:17.712359+00:00 app[web.1]: npm ERR! You can get their info via:
2015-11-18T22:01:17.712648+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
2015-11-18T22:01:17.712503+00:00 app[web.1]: npm ERR! npm owner ls shufflebod
2015-11-18T22:01:17.715348+00:00 app[web.1]:
2015-11-18T22:01:17.715563+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2015-11-18T22:01:17.715707+00:00 app[web.1]: npm ERR! /app/npm-debug.log
2015-11-18T22:01:17.697334+00:00 app[web.1]:
2015-11-18T22:01:17.697338+00:00 app[web.1]: /app/node_modules/mongodb/lib/server.js:235
2015-11-18T22:01:17.697339+00:00 app[web.1]: process.nextTick(function() { throw err; })
2015-11-18T22:01:17.697340+00:00 app[web.1]: ^
2015-11-18T22:01:17.697341+00:00 app[web.1]: Error: getaddrinfo ENOTFOUND undefined undefined:27017
2015-11-18T22:01:17.697343+00:00 app[web.1]: at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:77:26)
2015-11-18T22:01:17.697342+00:00 app[web.1]: at errnoException (dns.js:26:10)
2015-11-18T22:01:17.704845+00:00 app[web.1]:
2015-11-18T22:01:18.349594+00:00 heroku[web.1]: Process exited with status 1
2015-11-18T22:01:19.268580+00:00 heroku[web.1]: Starting process with command `npm start`
2015-11-18T22:01:20.934317+00:00 app[web.1]:
2015-11-18T22:01:20.934327+00:00 app[web.1]: > shufflebod#0.0.0 start /app
2015-11-18T22:01:20.934328+00:00 app[web.1]: > node ./bin/www
2015-11-18T22:01:20.934329+00:00 app[web.1]:
2015-11-18T22:01:21.402689+00:00 app[web.1]: npm ERR! Linux 3.13.0-66-generic
2015-11-18T22:01:21.389182+00:00 app[web.1]:
2015-11-18T22:01:21.389186+00:00 app[web.1]: /app/node_modules/mongodb/lib/server.js:235
2015-11-18T22:01:21.403047+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
2015-11-18T22:01:21.403274+00:00 app[web.1]: npm ERR! node v5.0.0
2015-11-18T22:01:21.389187+00:00 app[web.1]: process.nextTick(function() { throw err; })
2015-11-18T22:01:21.389188+00:00 app[web.1]: ^
2015-11-18T22:01:21.389220+00:00 app[web.1]: Error: getaddrinfo ENOTFOUND undefined undefined:27017
2015-11-18T22:01:21.389223+00:00 app[web.1]: at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:77:26)
2015-11-18T22:01:21.403921+00:00 app[web.1]: npm ERR! npm v3.3.6
2015-11-18T22:01:21.389222+00:00 app[web.1]: at errnoException (dns.js:26:10)
2015-11-18T22:01:21.404128+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2015-11-18T22:01:21.398077+00:00 app[web.1]:
2015-11-18T22:01:21.404250+00:00 app[web.1]: npm ERR! shufflebod#0.0.0 start: `node ./bin/www`
2015-11-18T22:01:21.404341+00:00 app[web.1]: npm ERR! Exit status 1
2015-11-18T22:01:21.404490+00:00 app[web.1]: npm ERR!
2015-11-18T22:01:21.404594+00:00 app[web.1]: npm ERR! Failed at the shufflebod#0.0.0 start script 'node ./bin/www'.
2015-11-18T22:01:21.404805+00:00 app[web.1]: npm ERR! not with npm itself.
2015-11-18T22:01:21.404703+00:00 app[web.1]: npm ERR! This is most likely a problem with the shufflebod package,
2015-11-18T22:01:21.404901+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system:
2015-11-18T22:01:21.405100+00:00 app[web.1]: npm ERR! You can get their info via:
2015-11-18T22:01:21.404998+00:00 app[web.1]: npm ERR! node ./bin/www
2015-11-18T22:01:21.405200+00:00 app[web.1]: npm ERR! npm owner ls shufflebod
2015-11-18T22:01:21.405292+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
2015-11-18T22:01:21.407531+00:00 app[web.1]:
2015-11-18T22:01:21.407693+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2015-11-18T22:01:21.407785+00:00 app[web.1]: npm ERR! /app/npm-debug.log
2015-11-18T22:01:21.971588+00:00 heroku[web.1]: State changed from starting to crashed
2015-11-18T22:01:21.992188+00:00 heroku[web.1]: Process exited with status 1
2015-11-18T22:01:18.396645+00:00 heroku[web.1]: State changed from starting to crashed
2015-11-18T22:01:18.397743+00:00 heroku[web.1]: State changed from crashed to starting
2015-11-18T22:01:46.680907+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=arcane-scrubland-5339.herokuapp.com request_id=1b2efaee-c58e-4f2f-9c5d-9cac682c21e8 fwd="208.191.152.154" dyno= connect= service= status=503 bytes=
2015-11-18T22:01:48.353321+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=arcane-scrubland-5339.herokuapp.com request_id=7bbff939-36e5-4566-9556-a00e705dd48f fwd="208.191.152.154" dyno= connect= service= status=503 bytes=
2015-11-18T22:02:06.643850+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=arcane-scrubland-5339.herokuapp.com request_id=eca3d154-2aa1-4c4c-86b7-0a12d7043302 fwd="208.191.152.154" dyno= connect= service= status=503 bytes=
2015-11-18T22:02:06.931913+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=arcane-scrubland-5339.herokuapp.com request_id=fb796d4c-c4ce-4696-a019-8d1e208ad8ef fwd="208.191.152.154" dyno= connect= service= status=503 bytes=
2015-11-18T22:10:19.380625+00:00 heroku[slug-compiler]: Slug compilation started
2015-11-18T22:10:19.380667+00:00 heroku[slug-compiler]: Slug compilation finished
2015-11-18T22:10:19.245516+00:00 heroku[api]: Deploy 52e6c8e by adamcweitzman#gmail.com
2015-11-18T22:10:19.245516+00:00 heroku[api]: Release v4 created by adamcweitzman#gmail.com
2015-11-18T22:10:19.481578+00:00 heroku[web.1]: State changed from crashed to starting
2015-11-18T22:10:20.489282+00:00 heroku[web.1]: Starting process with command `nodemon bin/www`
2015-11-18T22:10:22.069790+00:00 app[web.1]: bash: nodemon: command not found
2015-11-18T22:10:22.731271+00:00 heroku[web.1]: Process exited with status 127
2015-11-18T22:10:22.755823+00:00 heroku[web.1]: State changed from starting to crashed
2015-11-18T22:10:25.421596+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=arcane-scrubland-5339.herokuapp.com request_id=fd282f48-9ccb-4e9a-ba08-2db5d503ab3e fwd="208.191.152.154" dyno= connect= service= status=503 bytes=
2015-11-18T22:10:30.012124+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=arcane-scrubland-5339.herokuapp.com request_id=5704bcfe-ad83-4a8a-ae02-b7cc590f1e7b fwd="208.191.152.154" dyno= connect= service= status=503 bytes=


so i figured a solution, not sure why it works though...
in my package.json I had node: nodemon bin/www when I needed web: node ./bin/www I do not know why this is the case, if someone could explain, that would be amazing.

Related

Deployed app on Heroku crashed at startup [duplicate]

This question already has answers here:
Heroku failing to start my node app because its trying to do it with nodemon
(4 answers)
Closed last year.
if I run the application from terminal, it is working, I mean that it is running in the browser.
The problem is when I try to host it on Heroku. My app has Backend: Nodejs with Express and Database: MySQL.
I see that I have errors, but I don't understand them and I've tried multiple things to make it work, but I can't.
Logs from the error:
2022-01-14T11:42:19.516824+00:00 app[web.1]:
2022-01-14T11:42:19.516835+00:00 app[web.1]: > presidentialelections#0.0.0 start /app
2022-01-14T11:42:19.516835+00:00 app[web.1]: > nodemon ./bin/www
2022-01-14T11:42:19.516835+00:00 app[web.1]:
2022-01-14T11:42:19.520231+00:00 app[web.1]: sh: 1: nodemon: not found
2022-01-14T11:42:19.524055+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2022-01-14T11:42:19.524197+00:00 app[web.1]: npm ERR! syscall spawn
2022-01-14T11:42:19.524258+00:00 app[web.1]: npm ERR! file sh
2022-01-14T11:42:19.524466+00:00 app[web.1]: npm ERR! errno ENOENT
2022-01-14T11:42:19.526613+00:00 app[web.1]: npm ERR! presidentialelections#0.0.0 start: `nodemon ./bin/www`
2022-01-14T11:42:19.526650+00:00 app[web.1]: npm ERR! spawn ENOENT
2022-01-14T11:42:19.526699+00:00 app[web.1]: npm ERR!
2022-01-14T11:42:19.526737+00:00 app[web.1]: npm ERR! Failed at the presidentialelections#0.0.0 start script.2022-01-14T11:42:19.526788+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2022-01-14T11:42:19.532863+00:00 app[web.1]:
2022-01-14T11:42:19.532933+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2022-01-14T11:42:19.532983+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2022-01-14T11_42_19_527Z-debug.log
2022-01-14T11:42:19.647800+00:00 heroku[web.1]: Process exited with status 1
2022-01-14T11:42:19.723822+00:00 heroku[web.1]: State changed from starting to crashed
2022-01-14T11:42:22.997860+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=pacific-ravine-23602.herokuapp.com request_id=867758f1-1252-4674-a7cc-261fbe9f98d1 fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T11:42:23.312967+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=pacific-ravine-23602.herokuapp.com request_id=5cb55772-dad6-486d-bc15-d37731d94661 fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T11:46:57.000000+00:00 app[api]: Build started by user daviddserb#yahoo.com
2022-01-14T11:47:11.000000+00:00 app[api]: Build succeeded
2022-01-14T11:47:11.297457+00:00 app[api]: Deploy 7ee73460 by user daviddserb#yahoo.com
2022-01-14T11:47:11.297457+00:00 app[api]: Release v4 created by user daviddserb#yahoo.com
2022-01-14T11:47:12.210235+00:00 heroku[web.1]: State changed from crashed to starting
2022-01-14T11:47:14.084097+00:00 heroku[web.1]: Starting process with command `npm start`
2022-01-14T11:47:15.244156+00:00 app[web.1]:
2022-01-14T11:47:15.244170+00:00 app[web.1]: > presidentialelections#0.0.0 start /app
2022-01-14T11:47:15.244170+00:00 app[web.1]: > nodemon ./bin/www
2022-01-14T11:47:15.244170+00:00 app[web.1]:
2022-01-14T11:47:15.248738+00:00 app[web.1]: sh: 1: nodemon: not found
2022-01-14T11:47:15.254959+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2022-01-14T11:47:15.255206+00:00 app[web.1]: npm ERR! syscall spawn
2022-01-14T11:47:15.255316+00:00 app[web.1]: npm ERR! file sh
2022-01-14T11:47:15.255405+00:00 app[web.1]: npm ERR! errno ENOENT
2022-01-14T11:47:15.259050+00:00 app[web.1]: npm ERR! presidentialelections#0.0.0 start: `nodemon ./bin/www`
2022-01-14T11:47:15.259107+00:00 app[web.1]: npm ERR! spawn ENOENT
2022-01-14T11:47:15.259167+00:00 app[web.1]: npm ERR!
2022-01-14T11:47:15.259216+00:00 app[web.1]: npm ERR! Failed at the presidentialelections#0.0.0 start script.2022-01-14T11:47:15.259274+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2022-01-14T11:47:15.266461+00:00 app[web.1]:
2022-01-14T11:47:15.266545+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2022-01-14T11:47:15.266590+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2022-01-14T11_47_15_260Z-debug.log
2022-01-14T11:47:15.397039+00:00 heroku[web.1]: Process exited with status 1
2022-01-14T11:47:15.454442+00:00 heroku[web.1]: State changed from starting to crashed
2022-01-14T11:47:18.779406+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=pacific-ravine-23602.herokuapp.com request_id=325e420b-9e58-4f7e-bad0-4872dc699fe0 fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T11:47:19.023207+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=pacific-ravine-23602.herokuapp.com request_id=e081eb63-0cff-4e27-a710-1d60cbc9beb1 fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T11:48:40.000000+00:00 app[api]: Build started by user daviddserb#yahoo.com
2022-01-14T11:48:53.770119+00:00 app[api]: Deploy 7fc9ef13 by user daviddserb#yahoo.com
2022-01-14T11:48:53.770119+00:00 app[api]: Release v5 created by user daviddserb#yahoo.com
2022-01-14T11:48:54.000000+00:00 app[api]: Build succeeded
2022-01-14T11:48:54.117745+00:00 heroku[web.1]: State changed from crashed to starting
2022-01-14T11:48:55.999691+00:00 heroku[web.1]: Starting process with command `npm start`
2022-01-14T11:48:56.952415+00:00 app[web.1]:
2022-01-14T11:48:56.952427+00:00 app[web.1]: > presidentialelections#0.0.0 start /app
2022-01-14T11:48:56.952428+00:00 app[web.1]: > nodemon ./bin/www
2022-01-14T11:48:56.952428+00:00 app[web.1]:
2022-01-14T11:48:56.962683+00:00 app[web.1]: sh: 1: nodemon: not found
2022-01-14T11:48:56.968511+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2022-01-14T11:48:56.968735+00:00 app[web.1]: npm ERR! syscall spawn
2022-01-14T11:48:56.968786+00:00 app[web.1]: npm ERR! file sh
2022-01-14T11:48:56.968886+00:00 app[web.1]: npm ERR! errno ENOENT
2022-01-14T11:48:56.972412+00:00 app[web.1]: npm ERR! presidentialelections#0.0.0 start: `nodemon ./bin/www`
2022-01-14T11:48:56.972521+00:00 app[web.1]: npm ERR! spawn ENOENT
2022-01-14T11:48:56.972620+00:00 app[web.1]: npm ERR!
2022-01-14T11:48:56.972734+00:00 app[web.1]: npm ERR! Failed at the presidentialelections#0.0.0 start script.2022-01-14T11:48:56.972822+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2022-01-14T11:48:56.977729+00:00 app[web.1]:
2022-01-14T11:48:56.977829+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2022-01-14T11:48:56.977880+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2022-01-14T11_48_56_974Z-debug.log
2022-01-14T11:48:57.123929+00:00 heroku[web.1]: Process exited with status 1
2022-01-14T11:48:57.256711+00:00 heroku[web.1]: State changed from starting to crashed
2022-01-14T11:49:03.042405+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=pacific-ravine-23602.herokuapp.com request_id=40e7bba7-b78d-4472-b652-c1b296a4343a fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T11:49:03.312210+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=pacific-ravine-23602.herokuapp.com request_id=4b214bf1-4d44-4895-8bc7-2d8cc34e172d fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T11:51:59.531549+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=pacific-ravine-23602.herokuapp.com request_id=c38f2d45-f1a5-43a9-9f4e-e2f34ef4d1bb fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T11:51:59.801198+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=pacific-ravine-23602.herokuapp.com request_id=a5c7fb1c-5ce3-4ccf-81ac-3cb8fdce759f fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T11:56:02.383069+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=pacific-ravine-23602.herokuapp.com request_id=22db8c3d-1714-42f8-a40f-9e02d0cc737a fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T11:56:02.634499+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=pacific-ravine-23602.herokuapp.com request_id=fc256052-006a-4289-a836-ce8094e64944 fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T12:05:20.233183+00:00 heroku[web.1]: State changed from crashed to starting
2022-01-14T12:05:22.754848+00:00 heroku[web.1]: Starting process with command `npm start`
2022-01-14T12:05:23.970064+00:00 app[web.1]:
2022-01-14T12:05:23.970078+00:00 app[web.1]: > presidentialelections#0.0.0 start /app
2022-01-14T12:05:23.970079+00:00 app[web.1]: > nodemon ./bin/www
2022-01-14T12:05:23.970079+00:00 app[web.1]:
2022-01-14T12:05:23.973595+00:00 app[web.1]: sh: 1: nodemon: not found
2022-01-14T12:05:23.978419+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2022-01-14T12:05:23.978592+00:00 app[web.1]: npm ERR! syscall spawn
2022-01-14T12:05:23.978667+00:00 app[web.1]: npm ERR! file sh
2022-01-14T12:05:23.978764+00:00 app[web.1]: npm ERR! errno ENOENT
2022-01-14T12:05:23.981475+00:00 app[web.1]: npm ERR! presidentialelections#0.0.0 start: `nodemon ./bin/www`
2022-01-14T12:05:23.981519+00:00 app[web.1]: npm ERR! spawn ENOENT
2022-01-14T12:05:23.981564+00:00 app[web.1]: npm ERR!
2022-01-14T12:05:23.982264+00:00 app[web.1]: npm ERR! Failed at the presidentialelections#0.0.0 start script.2022-01-14T12:05:23.982320+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There
is likely additional logging output above.
2022-01-14T12:05:23.984901+00:00 app[web.1]:
2022-01-14T12:05:23.984998+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2022-01-14T12:05:23.985048+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2022-01-14T12_05_23_982Z-debug.log
2022-01-14T12:05:24.128019+00:00 heroku[web.1]: Process exited with status 1
2022-01-14T12:05:24.211507+00:00 heroku[web.1]: State changed from starting to crashed
I don't know what else to give you, so please, if you need some other files or information about my project, let me know and I will upload them.

Seems like you are using "nodemon". Probably if you installed with "npm i -g nodemon"
you can see that error. So nodemon installed on your pc but your project have not nodemon. Just run npm i nodemon in your terminal while located project. Finally deploy again. And i'm sorry about bad english.

"npm ERR! code ELIFECYCLE" error Heroku deployment

I was trying to deploy a Node.js application with [this][1] becaon library into Heroku. The Heroku logs says that the error might be coming from start script but there is no problem with my start script.When I deployed the app to Heroku I got the following error:
When I run node index.js locally I get no errors. But the application does not run on Heroku
Warning: heroku update available from 7.0.49 to 7.18.10
2018-12-01T04:06:34.300391+00:00 heroku[web.1]: Starting process with command `npm start`
2018-12-01T04:06:35.940335+00:00 app[web.1]:
2018-12-01T04:06:35.940352+00:00 app[web.1]: > beacon#1.0.0 start /app
2018-12-01T04:06:35.940354+00:00 app[web.1]: > node index.js
2018-12-01T04:06:35.940355+00:00 app[web.1]:
2018-12-01T04:06:36.182490+00:00 app[web.1]: node: ../deps/uv/src/unix/poll.c:120: uv_poll_start: Assertion `!(((handle)->flags & (UV_CLOSING | UV_CLOSED)) != 0)' failed.
2018-12-01T04:06:36.185072+00:00 app[web.1]: Aborted
2018-12-01T04:06:36.188032+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2018-12-01T04:06:36.188313+00:00 app[web.1]: npm ERR! errno 134
2018-12-01T04:06:36.189384+00:00 app[web.1]: npm ERR! beacon#1.0.0 start: `node index.js`
2018-12-01T04:06:36.189493+00:00 app[web.1]: npm ERR! Exit status 134
2018-12-01T04:06:36.189660+00:00 app[web.1]: npm ERR!
2018-12-01T04:06:36.189769+00:00 app[web.1]: npm ERR! Failed at the beacon#1.0.0 start script.
2018-12-01T04:06:36.189870+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2018-12-01T04:06:36.196620+00:00 app[web.1]:
2018-12-01T04:06:36.197883+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2018-12-01T04:06:36.197884+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2018-12-01T04_06_36_191Z-debug.log
2018-12-01T04:06:36.252135+00:00 heroku[web.1]: Process exited with status 134
2018-12-01T04:06:36.269181+00:00 heroku[web.1]: State changed from starting to crashed
2018-12-01T04:06:36.271462+00:00 heroku[web.1]: State changed from crashed to starting
2018-12-01T04:06:38.878330+00:00 heroku[web.1]: Starting process with command `npm start`
2018-12-01T04:06:41.389907+00:00 app[web.1]: node: ../deps/uv/src/unix/poll.c:120: uv_poll_start: Assertion `!(((handle)->flags & (UV_CLOSING | UV_CLOSED)) != 0)' failed.
2018-12-01T04:06:41.399890+00:00 app[web.1]: Aborted
2018-12-01T04:06:41.414233+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2018-12-01T04:06:41.415046+00:00 app[web.1]: npm ERR! errno 134
2018-12-01T04:06:41.415963+00:00 app[web.1]: npm ERR! beacon#1.0.0 start: `node index.js`
2018-12-01T04:06:41.416136+00:00 app[web.1]: npm ERR! Exit status 134
2018-12-01T04:06:41.416369+00:00 app[web.1]: npm ERR!
2018-12-01T04:06:41.416552+00:00 app[web.1]: npm ERR! Failed at the beacon#1.0.0 start script.
2018-12-01T04:06:41.416721+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2018-12-01T04:06:41.424049+00:00 app[web.1]:
2018-12-01T04:06:41.428265+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2018-12-01T04:06:41.428268+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2018-12-01T04_06_41_418Z-debug.log
2018-12-01T04:06:41.108083+00:00 app[web.1]:
2018-12-01T04:06:41.108108+00:00 app[web.1]: > beacon#1.0.0 start /app
2018-12-01T04:06:41.108110+00:00 app[web.1]: > node index.js
2018-12-01T04:06:41.108111+00:00 app[web.1]:
2018-12-01T04:06:41.596884+00:00 heroku[web.1]: State changed from starting to crashed
2018-12-01T04:06:41.485308+00:00 heroku[web.1]: Process exited with status 134
2018-12-01T04:07:26.397433+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=shrouded-earth-56576.herokuapp.com request_id=d07bc3c2-d97c-42e1-9dd6-9898eb760ac4 fwd="71.82.55.26" dyno= connect= service= status=503 bytes= protocol=https
2018-12-01T04:07:26.994317+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=shrouded-earth-56576.herokuapp.com request_id=dd732048-d3f9-44e9-98d2-46eb8cc85cda fwd="71.82.55.26" dyno= connect= service= status=503 bytes= protocol=https
2018-12-01T04:13:25.564521+00:00 heroku[web.1]: State changed from crashed to starting
2018-12-01T04:13:27.647004+00:00 heroku[web.1]: Starting process with command `npm start`
2018-12-01T04:13:29.564971+00:00 heroku[web.1]: Process exited with status 134
2018-12-01T04:13:29.294660+00:00 app[web.1]:
2018-12-01T04:13:29.294685+00:00 app[web.1]: > beacon#1.0.0 start /app
2018-12-01T04:13:29.294687+00:00 app[web.1]: > node index.js
2018-12-01T04:13:29.294688+00:00 app[web.1]:
2018-12-01T04:13:29.510248+00:00 app[web.1]: node: ../deps/uv/src/unix/poll.c:120: uv_poll_start: Assertion `!(((handle)->flags & (UV_CLOSING | UV_CLOSED)) != 0)' failed.
2018-12-01T04:13:29.513133+00:00 app[web.1]: Aborted
2018-12-01T04:13:29.516318+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2018-12-01T04:13:29.516650+00:00 app[web.1]: npm ERR! errno 134
2018-12-01T04:13:29.517766+00:00 app[web.1]: npm ERR! beacon#1.0.0 start: `node index.js`
2018-12-01T04:13:29.517871+00:00 app[web.1]: npm ERR! Exit status 134
2018-12-01T04:13:29.518068+00:00 app[web.1]: npm ERR!
2018-12-01T04:13:29.518177+00:00 app[web.1]: npm ERR! Failed at the beacon#1.0.0 start script.
2018-12-01T04:13:29.518300+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2018-12-01T04:13:29.523910+00:00 app[web.1]:
2018-12-01T04:13:29.524106+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2018-12-01T04:13:29.524250+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2018-12-01T04_13_29_519Z-debug.log
2018-12-01T04:13:29.599675+00:00 heroku[web.1]: State changed from starting to crashed
2018-12-01T04:13:31.494135+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=shrouded-earth-56576.herokuapp.com request_id=67443cd5-7197-4ef7-a0b0-2a5491d9e4d6 fwd="71.82.55.26" dyno= connect= service= status=503 bytes= protocol=https
2018-12-01T04:13:33.189065+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=shrouded-earth-56576.herokuapp.com request_id=0146892f-fab3-4636-ad2d-b1f8d03800e5 fwd="71.82.55.26" dyno= connect= service= status=503 bytes= protocol=https
2018-12-01T04:21:18.599016+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=shrouded-earth-56576.herokuapp.com request_id=72ad062c-7a36-4b87-9aae-b4c661284deb fwd="71.82.55.26" dyno= connect= service= status=503 bytes= protocol=https
2018-12-01T04:21:20.379722+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=shrouded-earth-56576.herokuapp.com request_id=bf46325b-6def-4060-b091-a14d5764f01c fwd="71.82.55.26" dyno= connect= service= status=503 bytes= protocol=https
2018-12-01T04:24:03.236771+00:00 heroku[web.1]: State changed from crashed to starting
2018-12-01T04:24:07.724222+00:00 app[web.1]: Aborted
2018-12-01T04:24:07.727689+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2018-12-01T04:24:07.728039+00:00 app[web.1]: npm ERR! errno 134
2018-12-01T04:24:07.729239+00:00 app[web.1]: npm ERR! beacon#1.0.0 start: `node index.js`
2018-12-01T04:24:07.729410+00:00 app[web.1]: npm ERR! Exit status 134
2018-12-01T04:24:07.729636+00:00 app[web.1]: npm ERR!
2018-12-01T04:24:07.729806+00:00 app[web.1]: npm ERR! Failed at the beacon#1.0.0 start script.
2018-12-01T04:24:07.729961+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2018-12-01T04:24:07.733417+00:00 app[web.1]:
2018-12-01T04:24:07.733683+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2018-12-01T04:24:07.733804+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2018-12-01T04_24_07_731Z-debug.log
2018-12-01T04:24:07.471562+00:00 app[web.1]:
2018-12-01T04:24:07.471584+00:00 app[web.1]: > beacon#1.0.0 start /app
2018-12-01T04:24:07.471586+00:00 app[web.1]: > node index.js
2018-12-01T04:24:07.471587+00:00 app[web.1]:
2018-12-01T04:24:07.721101+00:00 app[web.1]: node: ../deps/uv/src/unix/poll.c:120: uv_poll_start: Assertion `!(((handle)->flags & (UV_CLOSING | UV_CLOSED)) != 0)' failed.
2018-12-01T04:24:07.796807+00:00 heroku[web.1]: Process exited with status 134
This is my packgae.json
{
"name": "beacon",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {
"start": "node index.js",
"test": "echo \"Error: no test specified\" && exit 1"
},
"dependencies": {
"bluetooth-hci-socket": "^0.5.1",
"body-parser": "^1.18.3",
"ejs": "^2.6.1",
"express": "^4.16.4",
"noble": "^1.9.1",
"node-beacon-scanner": "^0.1.0",
"node-gyp": "^3.8.0",
"rebuild": "^0.1.2"
},
"engines": {
"node": "8.11.1"
},
"author": "sas",
"license": "ISC"
}
Edit 1
Complete Logs:
Warning: heroku update available from 7.0.49 to 7.18.10
2018-12-01T04:06:35.940354+00:00 app[web.1]: > node index.js
2018-12-01T04:06:35.940355+00:00 app[web.1]:
2018-12-01T04:06:36.182490+00:00 app[web.1]: node: ../deps/uv/src/unix/poll.c:120: uv_poll_start: Assertion `!(((handle)->flags & (UV_CLOSING | UV_CLOSED)) != 0)' failed.
2018-12-01T04:06:36.185072+00:00 app[web.1]: Aborted
2018-12-01T04:06:36.188032+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2018-12-01T04:06:36.188313+00:00 app[web.1]: npm ERR! errno 134
2018-12-01T04:06:36.189384+00:00 app[web.1]: npm ERR! beacon#1.0.0 start: `node index.js`
2018-12-01T04:06:36.189493+00:00 app[web.1]: npm ERR! Exit status 134
2018-12-01T04:06:36.189660+00:00 app[web.1]: npm ERR!
2018-12-01T04:06:36.189769+00:00 app[web.1]: npm ERR! Failed at the beacon#1.0.0 start script.
2018-12-01T04:06:36.189870+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2018-12-01T04:06:36.196620+00:00 app[web.1]:
2018-12-01T04:06:36.197883+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2018-12-01T04:06:36.197884+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2018-12-01T04_06_36_191Z-debug.log
2018-12-01T04:06:36.252135+00:00 heroku[web.1]: Process exited with status 134
2018-12-01T04:06:36.269181+00:00 heroku[web.1]: State changed from starting to crashed
2018-12-01T04:06:36.271462+00:00 heroku[web.1]: State changed from crashed to starting
2018-12-01T04:06:38.878330+00:00 heroku[web.1]: Starting process with command `npm start`
2018-12-01T04:06:41.389907+00:00 app[web.1]: node: ../deps/uv/src/unix/poll.c:120: uv_poll_start: Assertion `!(((handle)->flags & (UV_CLOSING | UV_CLOSED)) != 0)' failed.
2018-12-01T04:06:41.399890+00:00 app[web.1]: Aborted
2018-12-01T04:06:41.414233+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2018-12-01T04:06:41.415046+00:00 app[web.1]: npm ERR! errno 134
2018-12-01T04:06:41.415963+00:00 app[web.1]: npm ERR! beacon#1.0.0 start: `node index.js`
2018-12-01T04:06:41.416136+00:00 app[web.1]: npm ERR! Exit status 134
2018-12-01T04:06:41.416369+00:00 app[web.1]: npm ERR!
2018-12-01T04:06:41.416552+00:00 app[web.1]: npm ERR! Failed at the beacon#1.0.0 start script.
2018-12-01T04:06:41.416721+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2018-12-01T04:06:41.424049+00:00 app[web.1]:
2018-12-01T04:06:41.428265+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2018-12-01T04:06:41.428268+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2018-12-01T04_06_41_418Z-debug.log
2018-12-01T04:06:41.108083+00:00 app[web.1]:
2018-12-01T04:06:41.108108+00:00 app[web.1]: > beacon#1.0.0 start /app
2018-12-01T04:06:41.108110+00:00 app[web.1]: > node index.js
2018-12-01T04:06:41.108111+00:00 app[web.1]:
2018-12-01T04:06:41.596884+00:00 heroku[web.1]: State changed from starting to crashed
2018-12-01T04:06:41.485308+00:00 heroku[web.1]: Process exited with status 134
2018-12-01T04:07:26.397433+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=shrouded-earth-56576.herokuapp.com request_id=d07bc3c2-d97c-42e1-9dd6-9898eb760ac4 fwd="71.82.55.26" dyno= connect= service= status=503 bytes= protocol=https
2018-12-01T04:07:26.994317+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=shrouded-earth-56576.herokuapp.com request_id=dd732048-d3f9-44e9-98d2-46eb8cc85cda fwd="71.82.55.26" dyno= connect= service= status=503 bytes= protocol=https
2018-12-01T04:13:25.564521+00:00 heroku[web.1]: State changed from crashed to starting
2018-12-01T04:13:27.647004+00:00 heroku[web.1]: Starting process with command `npm start`
2018-12-01T04:13:29.564971+00:00 heroku[web.1]: Process exited with status 134
2018-12-01T04:13:29.294660+00:00 app[web.1]:
2018-12-01T04:13:29.294685+00:00 app[web.1]: > beacon#1.0.0 start /app
2018-12-01T04:13:29.294687+00:00 app[web.1]: > node index.js
2018-12-01T04:13:29.294688+00:00 app[web.1]:
2018-12-01T04:13:29.510248+00:00 app[web.1]: node: ../deps/uv/src/unix/poll.c:120: uv_poll_start: Assertion `!(((handle)->flags & (UV_CLOSING | UV_CLOSED)) != 0)' failed.
2018-12-01T04:13:29.513133+00:00 app[web.1]: Aborted
2018-12-01T04:13:29.516318+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2018-12-01T04:13:29.516650+00:00 app[web.1]: npm ERR! errno 134
2018-12-01T04:13:29.517766+00:00 app[web.1]: npm ERR! beacon#1.0.0 start: `node index.js`
2018-12-01T04:13:29.517871+00:00 app[web.1]: npm ERR! Exit status 134
2018-12-01T04:13:29.518068+00:00 app[web.1]: npm ERR!
2018-12-01T04:13:29.518177+00:00 app[web.1]: npm ERR! Failed at the beacon#1.0.0 start script.
2018-12-01T04:13:29.518300+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2018-12-01T04:13:29.523910+00:00 app[web.1]:
2018-12-01T04:13:29.524106+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2018-12-01T04:13:29.524250+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2018-12-01T04_13_29_519Z-debug.log
2018-12-01T04:13:29.599675+00:00 heroku[web.1]: State changed from starting to crashed
2018-12-01T04:13:31.494135+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=shrouded-earth-56576.herokuapp.com request_id=67443cd5-7197-4ef7-a0b0-2a5491d9e4d6 fwd="71.82.55.26" dyno= connect= service= status=503 bytes= protocol=https
2018-12-01T04:13:33.189065+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=shrouded-earth-56576.herokuapp.com request_id=0146892f-fab3-4636-ad2d-b1f8d03800e5 fwd="71.82.55.26" dyno= connect= service= status=503 bytes= protocol=https
2018-12-01T04:21:18.599016+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=shrouded-earth-56576.herokuapp.com request_id=72ad062c-7a36-4b87-9aae-b4c661284deb fwd="71.82.55.26" dyno= connect= service= status=503 bytes= protocol=https
2018-12-01T04:21:20.379722+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=shrouded-earth-56576.herokuapp.com request_id=bf46325b-6def-4060-b091-a14d5764f01c fwd="71.82.55.26" dyno= connect= service= status=503 bytes= protocol=https
2018-12-01T04:24:03.236771+00:00 heroku[web.1]: State changed from crashed to starting
2018-12-01T04:24:07.724222+00:00 app[web.1]: Aborted
2018-12-01T04:24:07.727689+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2018-12-01T04:24:07.728039+00:00 app[web.1]: npm ERR! errno 134
2018-12-01T04:24:07.729239+00:00 app[web.1]: npm ERR! beacon#1.0.0 start: `node index.js`
2018-12-01T04:24:07.729410+00:00 app[web.1]: npm ERR! Exit status 134
2018-12-01T04:24:07.729636+00:00 app[web.1]: npm ERR!
2018-12-01T04:24:07.729806+00:00 app[web.1]: npm ERR! Failed at the beacon#1.0.0 start script.
2018-12-01T04:24:07.729961+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2018-12-01T04:24:07.733417+00:00 app[web.1]:
2018-12-01T04:24:07.733683+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2018-12-01T04:24:07.733804+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2018-12-01T04_24_07_731Z-debug.log
2018-12-01T04:24:07.471562+00:00 app[web.1]:
2018-12-01T04:24:07.471584+00:00 app[web.1]: > beacon#1.0.0 start /app
2018-12-01T04:24:07.471586+00:00 app[web.1]: > node index.js
2018-12-01T04:24:07.471587+00:00 app[web.1]:
2018-12-01T04:24:07.721101+00:00 app[web.1]: node: ../deps/uv/src/unix/poll.c:120: uv_poll_start: Assertion `!(((handle)->flags & (UV_CLOSING | UV_CLOSED)) != 0)' failed.
2018-12-01T04:24:07.796807+00:00 heroku[web.1]: Process exited with status 134
2018-12-01T04:45:54.163823+00:00 heroku[web.1]: State changed from crashed to starting
2018-12-01T04:45:57.333106+00:00 heroku[web.1]: Starting process with command `npm start`
2018-12-01T04:46:00.197869+00:00 app[web.1]:
2018-12-01T04:46:00.197897+00:00 app[web.1]: > beacon#1.0.0 start /app
2018-12-01T04:46:00.197899+00:00 app[web.1]: > node index.js
2018-12-01T04:46:00.197900+00:00 app[web.1]:
2018-12-01T04:46:00.626118+00:00 app[web.1]: node: ../deps/uv/src/unix/poll.c:120: uv_poll_start: Assertion `!(((handle)->flags & (UV_CLOSING | UV_CLOSED)) != 0)' failed.
2018-12-01T04:46:00.630209+00:00 app[web.1]: Aborted
2018-12-01T04:46:00.642201+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2018-12-01T04:46:00.642204+00:00 app[web.1]: npm ERR! errno 134
2018-12-01T04:46:00.642215+00:00 app[web.1]: npm ERR! beacon#1.0.0 start: `node index.js`
2018-12-01T04:46:00.642217+00:00 app[web.1]: npm ERR! Exit status 134
2018-12-01T04:46:00.642220+00:00 app[web.1]: npm ERR!
2018-12-01T04:46:00.642224+00:00 app[web.1]: npm ERR! Failed at the beacon#1.0.0 start script.
2018-12-01T04:46:00.649736+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2018-12-01T04:46:00.671528+00:00 app[web.1]:
2018-12-01T04:46:00.671785+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2018-12-01T04:46:00.671953+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2018-12-0s

heroku node cannot find module 'app/console'

I was adding AWS S3 on my nodejs, this is the first time i use this.
when i run my app, it had an error
2018-10-03T11:56:13.843291+00:00 app[web.1]: sh: 1: nodemon: not found
2018-10-03T11:56:13.827644+00:00 app[web.1]: > nodemon server.js
2018-10-03T11:56:13.854413+00:00 app[web.1]: npm ERR! file sh
2018-10-03T11:56:13.854859+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2018-10-03T11:56:13.855269+00:00 app[web.1]: npm ERR! errno ENOENT
2018-10-03T11:56:13.855634+00:00 app[web.1]: npm ERR! syscall spawn
2018-10-03T11:56:13.858988+00:00 app[web.1]: npm ERR! novel-ist-api#1.0.0 start: `nodemon server.js`
2018-10-03T11:56:13.859985+00:00 app[web.1]: npm ERR!
2018-10-03T11:56:13.860414+00:00 app[web.1]: npm ERR! Failed at the novel-ist-api#1.0.0 start script.
2018-10-03T11:56:13.859363+00:00 app[web.1]: npm ERR! spawn ENOENT
2018-10-03T11:56:13.901352+00:00 app[web.1]:
2018-10-03T11:56:13.860881+00:00 app[web.1]: npm ERR! This is probably not a problem
with npm. There is likely additional logging output above.
2018-10-03T11:56:13.902089+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2018-10-03T11_56_13_866Z-debug.log
2018-10-03T11:56:13.901742+00:00 app[web.1]: npm ERR! A complete log of this run can
be found in:
2018-10-03T11:56:30.126455+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=morning-hamlet-21755.herokuapp.com request_id=2db274ec-3b56-4a75-ad11-0fecf2e93821 fwd="180.243.188.17" dyno= connect= service= status=503 bytes= protocol=https
2018-10-03T11:56:31.865897+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=morning-hamlet-21755.herokuapp.com request_id=d54be99d-3257-49c7-ae9a-d3a8ced50d74 fwd="180.243.188.17" dyno= connect= service= status=503 bytes= protocol=https
then i tried to run heroku run node console, it gives me this:
module.js:550
throw err;
^
Error: Cannot find module '/app/console'
at Function.Module._resolveFilename (module.js:548:15)
at Function.Module._load (module.js:475:25)
at Function.Module.runMain (module.js:694:10)
at startup (bootstrap_node.js:204:16)
at bootstrap_node.js:625:3
i dont know how to fix this

Cannot install debug.log file in node.js

I have a problem with npm
2018-07-03T06:26:50.490789+00:00 app[web.1]: npm ERR! npm bugs slacky-
slack
2018-07-03T06:26:50.491029+00:00 app[web.1]: npm ERR! Or if that isn't
available, you can get their info via:
2018-07-03T06:26:50.491259+00:00 app[web.1]: npm ERR! npm owner ls
slacky-slack
2018-07-03T06:26:50.491483+00:00 app[web.1]: npm ERR! There is likely
additional logging output above.
2018-07-03T06:26:50.504304+00:00 app[web.1]:
2018-07-03T06:26:50.504649+00:00 app[web.1]: npm ERR! Please include the
following file with any support request:
2018-07-03T06:26:50.504652+00:00 app[web.1]: npm ERR! /app/npm-debug.log
2018-07-03T06:26:50.562975+00:00 heroku[web.1]: Process exited with status 1
2018-07-03T06:26:50.591872+00:00 heroku[web.1]: State changed from up to
crashed
2018-07-03T06:27:22.933639+00:00 heroku[router]: at=error code=H10 desc="App
crashed" method=POST path="/v1/account/register"
host=chattychatj.herokuapp.com request_id=e647073e-4b59-4ca4-a2a0-
c6b17a3b610e fwd="49.34.114.184" dyno= connect= service= status=503 bytes=
protocol=httpsstrong text
How to solve this problem?

After i pushed to heroku with "git push heroku" i get this error

An error occurred in the application and your page could not be served. If you are the application owner, check your logs for details.
and these logs messages
2017-06-20T13:46:11.664248+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "
start"
2017-06-20T13:46:11.664249+00:00 app[web.1]: npm ERR! node v6.11.0
2017-06-20T13:46:11.665569+00:00 app[web.1]: npm ERR! npm v3.10.10
2017-06-20T13:46:11.665571+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2017-06-20T13:46:11.665572+00:00 app[web.1]: npm ERR! node-web-server#1.0.0 start: `node server.js`
2017-06-20T13:46:11.665573+00:00 app[web.1]: npm ERR! Exit status 1
2017-06-20T13:46:11.665574+00:00 app[web.1]: npm ERR!
2017-06-20T13:46:11.665574+00:00 app[web.1]: npm ERR! Failed at the node-web-server#1.0.0 start script 'node server.j
s'.
2017-06-20T13:46:11.665575+00:00 app[web.1]: npm ERR! Make sure you have the latest version of node.js and npm instal
led.
2017-06-20T13:46:11.668262+00:00 app[web.1]: npm ERR! If you do, this is most likely a problem with the node-web-serv
er package,
2017-06-20T13:46:11.668264+00:00 app[web.1]: npm ERR! not with npm itself.
2017-06-20T13:46:11.668264+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system:
2017-06-20T13:46:11.668265+00:00 app[web.1]: npm ERR! node server.js
2017-06-20T13:46:11.668266+00:00 app[web.1]: npm ERR! You can get information on how to open an issue for this projec
t with:
2017-06-20T13:46:11.668267+00:00 app[web.1]: npm ERR! npm bugs node-web-server
2017-06-20T13:46:11.668267+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via:
2017-06-20T13:46:11.668268+00:00 app[web.1]: npm ERR! npm owner ls node-web-server
2017-06-20T13:46:11.668268+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
2017-06-20T13:46:11.672268+00:00 app[web.1]:
2017-06-20T13:46:11.673433+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2017-06-20T13:46:11.673435+00:00 app[web.1]: npm ERR! /app/npm-debug.log
2017-06-20T13:46:11.809096+00:00 heroku[web.1]: Process exited with status 1
2017-06-20T13:46:11.822443+00:00 heroku[web.1]: State changed from starting to crashed
2017-06-20T17:15:40.868366+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=secret
-ridge-97436.herokuapp.com request_id=c9623bbb-fb23-4052-b118-006d91a1644d fwd="41.13.66.39" dyno= connect= service=
status=503 bytes= protocol=https
2017-06-20T17:15:42.397116+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico"
host=secret-ridge-97436.herokuapp.com request_id=8471e291-6c09-4bd6-88f7-9bf4e5d05357 fwd="41.13.66.39" dyno= connect
= service= status=503 bytes= protocol=https
2017-06-20T17:15:42.749308+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico"
host=secret-ridge-97436.herokuapp.com request_id=7a132992-ca56-42e0-afcf-d16a14ea7861 fwd="41.13.66.39" dyno= connect
= service= status=503 bytes= protocol=https
muzij#muzij-Inspiron-3543:~/Documents/Projects/node/Express/node-web-server$

Resources