2018-02-22T20:16:09.000000+00:00 app[api]: Build succeeded
2018-02-22T20:16:27.585818+00:00 heroku[web.1]: Starting process with command `npm start`
2018-02-22T20:16:31.358885+00:00 heroku[web.1]: State changed from starting to crashed
2018-02-22T20:16:31.365454+00:00 heroku[web.1]: State changed from crashed to starting
2018-02-22T20:16:31.344307+00:00 heroku[web.1]: Process exited with status 1
2018-02-22T20:16:31.210298+00:00 app[web.1]:
2018-02-22T20:16:31.210316+00:00 app[web.1]: > facerecognizerapi@1.0.0 start /app
2018-02-22T20:16:31.210318+00:00 app[web.1]: > nodemon server.js
2018-02-22T20:16:31.210320+00:00 app[web.1]:
2018-02-22T20:16:31.222086+00:00 app[web.1]: sh: 1: nodemon: not found
2018-02-22T20:16:31.228407+00:00 app[web.1]: npm ERR! file sh
2018-02-22T20:16:31.228893+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2018-02-22T20:16:31.229265+00:00 app[web.1]: npm ERR! errno ENOENT
2018-02-22T20:16:31.229636+00:00 app[web.1]: npm ERR! syscall spawn
2018-02-22T20:16:31.231703+00:00 app[web.1]: npm ERR! facerecognizerapi@1.0.0 start: `nodemon server.js`
2018-02-22T20:16:31.231984+00:00 app[web.1]: npm ERR! spawn ENOENT
2018-02-22T20:16:31.232327+00:00 app[web.1]: npm ERR!
2018-02-22T20:16:31.232606+00:00 app[web.1]: npm ERR! Failed at the facerecognizerapi@1.0.0 start script.
2018-02-22T20:16:31.232836+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2018-02-22T20:16:31.246202+00:00 app[web.1]:
2018-02-22T20:16:31.246576+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2018-02-22T20:16:31.246812+00:00 app[web.1]: npm ERR!     /app/.npm/_logs/2018-02-22T20_16_31_240Z-debug.log
2018-02-22T20:16:35.212970+00:00 heroku[web.1]: Starting process with command `npm start`
2018-02-22T20:16:38.922375+00:00 heroku[web.1]: State changed from starting to crashed
2018-02-22T20:16:38.907740+00:00 heroku[web.1]: Process exited with status 1
2018-02-22T20:16:38.601564+00:00 app[web.1]:
2018-02-22T20:16:38.601708+00:00 app[web.1]: > facerecognizerapi@1.0.0 start /app
2018-02-22T20:16:38.601712+00:00 app[web.1]: > nodemon server.js
2018-02-22T20:16:38.601714+00:00 app[web.1]:
2018-02-22T20:16:38.694717+00:00 app[web.1]: sh: 1: nodemon: not found
2018-02-22T20:16:38.737156+00:00 app[web.1]: npm ERR! file sh
2018-02-22T20:16:38.737586+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2018-02-22T20:16:38.738227+00:00 app[web.1]: npm ERR! errno ENOENT
2018-02-22T20:16:38.739126+00:00 app[web.1]: npm ERR! syscall spawn
2018-02-22T20:16:38.746427+00:00 app[web.1]: npm ERR! facerecognizerapi@1.0.0 start: `nodemon server.js`
2018-02-22T20:16:38.747002+00:00 app[web.1]: npm ERR! spawn ENOENT
2018-02-22T20:16:38.748204+00:00 app[web.1]: npm ERR!
2018-02-22T20:16:38.748992+00:00 app[web.1]: npm ERR! Failed at the facerecognizerapi@1.0.0 start script.
2018-02-22T20:16:38.749792+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2018-02-22T20:16:38.787235+00:00 app[web.1]:
2018-02-22T20:16:38.790512+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2018-02-22T20:16:38.791558+00:00 app[web.1]: npm ERR!     /app/.npm/_logs/2018-02-22T20_16_38_756Z-debug.log
2018-02-22T20:16:40.832830+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=murmuring-basin-76989.herokuapp.com request_id=c91f0080-539c-4319-9ece-4bfa609d9574 fwd="172.98.155.140" dyno= connect= service= status=503 bytes= protocol=https
2018-02-22T20:16:41.550692+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=murmuring-basin-76989.herokuapp.com request_id=1fb91378-f3c7-4005-b9f1-90fbbf297b55 fwd="172.98.155.140" dyno= connect= service= status=503 bytes= protocol=https
2018-02-22T20:16:48.693442+00:00 heroku[web.1]: State changed from crashed to starting