Service 503
Olá, meu servidor caiu hoje, umas 19 horas e não voltou mais.
Fiz um build manual, e percebi que o problema era com uma resolução do bower.
Resolvi a resolução, porém meu servidor não volta.
Em eventos esta mostrando esse erro:
| 22/08/2017, 21:00:59 | BackOff | Pod | web-221-7yffw | Back-off restarting failed docker container (x41) |
|
Também o build do container do mongo não esta funcionando |
-
Comentário oficial
Boa tarde.
Sua aplicação contém erros nos arquivos back/managers/poll.js:7 e back/managers/notificacoes.js:15
Por isso não inicializa. Corrigindo isso na mão, o próximo erro é de autorização no SQS:
npm info it worked if it ends with ok
npm info using npm@4.1.2
npm info using node@v6.2.0
npm info lifecycle amodelivery@0.1.0~prestart: amodelivery@0.1.0
npm info lifecycle amodelivery@0.1.0~start: amodelivery@0.1.0
> amodelivery@0.1.0 start /opt/app-root/src
> gulp --gulpfile gulpfile.js && node server.js
[15:31:19] Using gulpfile ~/gulpfile.js
[15:31:19] Starting 'sass'...
[15:31:19] Starting 'pug'...
[15:31:19] Starting 'amo_sass'...
[15:31:19] Starting 'amo_pug'...
[15:31:19] Starting 'cliente_sass'...
[15:31:19] Starting 'cliente_pug'...
[15:31:19] Starting 'cliente_concatjs'...
[15:31:20] Finished 'cliente_concatjs' after 968 ms
[15:31:20] Finished 'amo_pug' after 973 ms
[15:31:20] Finished 'cliente_pug' after 970 ms
[15:31:20] Finished 'sass' after 992 ms
[15:31:20] Finished 'amo_sass' after 1.01 s
[15:31:20] Finished 'cliente_sass' after 1.01 s
[15:31:21] Finished 'pug' after 2.52 s
[15:31:21] Starting 'templatecache'...
[15:31:22] Finished 'templatecache' after 109 ms
[15:31:22] Starting 'concatjs'...
[15:31:22] Finished 'concatjs' after 152 ms
[15:31:22] Starting 'default'...
[15:31:22] Finished 'default' after 6.5 μs
[MONGO] Conectando...
(node:311) DeprecationWarning: `open()` is deprecated in mongoose >= 4.11.0, use `openUri()` instead, or set the `useMongoClient` option if using `connect()` or `createConnection()`. See http://mongoosejs.com/docs/connections.html#use-mongo-client
Express server listening on port 8080
Db.prototype.authenticate method will no longer be available in the next major release 3.x as MongoDB 3.6 will only allow auth against users in the admin db and will no longer allow multiple credentials on a socket. Please authenticate using MongoClient.connect with auth credentials.
[MONGO] Conectado!
[MONGO] Conexão aberta
{ ResponseMetadata: { RequestId: '6f6e5c6c-b6f7-54d6-ad1a-0e7b14fbc54a' },
QueueUrl: 'https://sqs.sa-east-1.amazonaws.com/XXX/poll' }
{ ResponseMetadata: { RequestId: '026f8275-d5f6-5c4b-88b8-d06277faad37' },
Attributes: { QueueArn: 'arn:aws:sqs:sa-east-1:563940129114:poll' } }
{ AuthorizationError: User: arn:aws:iam::563940129114:user/amodelivery is not authorized to perform: SNS:Subscribe on resource: arn:aws:sns:sa-east-1:XXX:XXX
at Request.extractError (/opt/app-root/src/node_modules/aws-sdk/lib/protocol/query.js:47:29)
at Request.callListeners (/opt/app-root/src/node_modules/aws-sdk/lib/sequential_executor.js:105:20)
at Request.emit (/opt/app-root/src/node_modules/aws-sdk/lib/sequential_executor.js:77:10)
at Request.emit (/opt/app-root/src/node_modules/aws-sdk/lib/request.js:683:14)
at Request.transition (/opt/app-root/src/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/opt/app-root/src/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /opt/app-root/src/node_modules/aws-sdk/lib/state_machine.js:26:10
at Request.<anonymous> (/opt/app-root/src/node_modules/aws-sdk/lib/request.js:38:9)
at Request.<anonymous> (/opt/app-root/src/node_modules/aws-sdk/lib/request.js:685:12)
at Request.callListeners (/opt/app-root/src/node_modules/aws-sdk/lib/sequential_executor.js:115:18)
at Request.emit (/opt/app-root/src/node_modules/aws-sdk/lib/sequential_executor.js:77:10)
at Request.emit (/opt/app-root/src/node_modules/aws-sdk/lib/request.js:683:14)
at Request.transition (/opt/app-root/src/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/opt/app-root/src/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /opt/app-root/src/node_modules/aws-sdk/lib/state_machine.js:26:10
at Request.<anonymous> (/opt/app-root/src/node_modules/aws-sdk/lib/request.js:38:9)
at Request.<anonymous> (/opt/app-root/src/node_modules/aws-sdk/lib/request.js:685:12)
at Request.callListeners (/opt/app-root/src/node_modules/aws-sdk/lib/sequential_executor.js:115:18)
at callNextListener (/opt/app-root/src/node_modules/aws-sdk/lib/sequential_executor.js:95:12)
at IncomingMessage.onEnd (/opt/app-root/src/node_modules/aws-sdk/lib/event_listeners.js:269:13)
at emitNone (events.js:91:20)
at IncomingMessage.emit (events.js:185:7)
message: 'User: arn:aws:iam::563940129114:user/XXX is not authorized to perform: SNS:Subscribe on resource: arn:aws:sns:sa-east-1:XXX:XXX',
code: 'AuthorizationError',
time: 2017-08-23T15:31:24.928Z,
requestId: 'ca4e9402-9c53-56b1-a899-c6153e5f9daa',
statusCode: 403,
retryable: false,
retryDelay: 73.9067347459036 }
NÃO FOI POSSÍVEL INICIAR POLLING
npm info lifecycle amodelivery@0.1.0~start: Failed to exec start script
npm ERR! Linux 3.10.0-514.2.2.el7.x86_64
npm ERR! argv "/usr/local/bin/node" "/opt/app-root/src/.npm-global/bin/npm" "run" "-d" "start"
npm ERR! node v6.2.0
npm ERR! npm v4.1.2
npm ERR! code ELIFECYCLE
npm ERR! amodelivery@0.1.0 start: `gulp --gulpfile gulpfile.js && node server.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the amodelivery@0.1.0 start script 'gulp --gulpfile gulpfile.js && node server.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the amodelivery package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! gulp --gulpfile gulpfile.js && node server.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs amodelivery
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls amodelivery
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /opt/app-root/src/npm-debug.logAções de comentário -
Sua aplicação teve algum outra alteração? Parece que está iniciando e terminando em seguida como pode ser visto nos logs:
$ oc logs web-223-2taos
npm info it worked if it ends with ok
npm info using npm@4.1.2
npm info using node@v7.4.0
npm info lifecycle amodelivery@0.1.0~prestart: amodelivery@0.1.0
npm info lifecycle amodelivery@0.1.0~start: amodelivery@0.1.0> amodelivery@0.1.0 start /opt/app-root/src
> gulp --gulpfile gulpfile.js[00:42:51] Using gulpfile ~/gulpfile.js
[00:42:51] Starting 'sass'...
[00:42:51] Starting 'pug'...
[00:42:51] Starting 'amo_sass'...
[00:42:51] Starting 'amo_pug'...
[00:42:51] Starting 'cliente_sass'...
[00:42:51] Starting 'cliente_pug'...
[00:42:51] Starting 'cliente_concatjs'...
[00:42:52] Finished 'amo_pug' after 987 ms
[00:42:52] Finished 'cliente_pug' after 985 ms
[00:42:52] Finished 'sass' after 1.01 s
[00:42:52] Finished 'amo_sass' after 990 ms
[00:42:52] Finished 'cliente_concatjs' after 1.02 s
[00:42:52] Finished 'cliente_sass' after 1.03 s
[00:42:54] Finished 'pug' after 2.61 s
[00:42:54] Starting 'templatecache'...
[00:42:54] Finished 'templatecache' after 204 ms
[00:42:54] Starting 'concatjs'...
[00:42:54] Finished 'concatjs' after 231 ms
[00:42:54] Starting 'production'...
RUN!
[00:42:54] Finished 'production' after 6.17 ms
[00:42:54] Starting 'default'...
[00:42:54] Finished 'default' after 52 μs
-----------START LOG-------------
[MONGO] Conectando...------------END LOG--------------
npm info lifecycle amodelivery@0.1.0~poststart: amodelivery@0.1.0
npm info ok
$ -
Não é nada disso.
Eu inicio minha aplicação usando gulp.
Sempre foi assim, nada foi alterado.
Até chequei no repositório.
O que observei é que a aws estava dando erro 403 para o polling do SQS, e isso que causou um novo deploy.
Porém, pelo que observei ele ficou com o deploy 223 em loop.
e não esta avançando para o latest.
Confere?
Veja a imagem acima, parece que ele não esta conseguindo cancelar o deploy 224 para iniciar um novo.
Por favor, entrar para comentar.
Comentários
8 comentários