This repository has been archived by the owner on Dec 31, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 476
Issue on heroku deployment #349
Comments
You can try these changes: #348 (comment) |
@curiousdannii not worked:
|
Closing in favor of #348 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
After deply app on heroku application wont start, and if you start with command then this issues appear.
Feedback consumer started: watching for feedback messages (bounces, complaints, etc) from SQS
(node:58) DeprecationWarning: Using the automatically created return value from client.query as an event emitter is deprecated and will be removed in pg@7.0. Please see the upgrade guide at https://node-postgres.com/guides/upgrading
Connection has been established successfully.
Unhandled rejection SequelizeBaseError: relation "settings" does not exist
at Query.formatError (/app/node_modules/sequelize/lib/dialects/postgres/query.js:357:14)
at Result. (/app/node_modules/sequelize/lib/dialects/postgres/query.js:88:19)
at emitOne (events.js:96:13)
at Result.emit (events.js:189:7)
at Result.Query.handleError (/app/node_modules/pg/lib/query.js:163:8)
at Client. (/app/node_modules/pg/lib/client.js:188:26)
at emitOne (events.js:96:13)
at Connection.emit (events.js:189:7)
at TLSSocket. (/app/node_modules/pg/lib/connection.js:133:12)
at emitOne (events.js:96:13)
at TLSSocket.emit (events.js:189:7)
at readableAddChunk (_stream_readable.js:176:18)
at TLSSocket.Readable.push (_stream_readable.js:134:10)
at TLSWrap.onread (net.js:551:20)
Clickthrough tracking: Make sure that geoip data has been downloaded:
$ cd node_modules/geoip-lite
$ npm run-script updatedb
/app/node_modules/ws/lib/websocket.js:347
...options
^^^
SyntaxError: Unexpected token ...
at Object.exports.runInThisContext (vm.js:73:16)
at Module._compile (module.js:543:28)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
at Module.require (module.js:498:17)
at require (internal/module.js:20:19)
at Object. (/app/node_modules/ws/index.js:3:19)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
at Module.require (module.js:498:17)
at require (internal/module.js:20:19)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! nonprofit-email-service@1.0.0 start:main:
node server/index.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the nonprofit-email-service@1.0.0 start:main 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! /app/.npm/_logs/2020-02-04T11_11_25_168Z-debug.log
ERROR: "start:main" exited with 1.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! nonprofit-email-service@1.0.0 start:
NODE_ENV=production npm-run-all --parallel start:*
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the nonprofit-email-service@1.0.0 start 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! /app/.npm/_logs/2020-02-04T11_11_25_278Z-debug.log
The text was updated successfully, but these errors were encountered: