Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[APM] UnhandledPromiseRejection with Authorization Exception on startup #40876

Open
tylersmalley opened this issue Jul 11, 2019 · 3 comments

Comments

Projects
None yet
4 participants
@tylersmalley
Copy link
Member

commented Jul 11, 2019

Kibana version: master/7.3

Describe the bug:

UnhandledPromiseRejectionWarning with an authorization exception when starting Kibana.

Steps to reproduce:

  1. Start ES/Kibana yarn start and yarn es snapshot
  2. Observe logs

Provide logs and/or server output (if relevant):

server   error  [15:44:53.102] [warning][process] UnhandledPromiseRejectionWarning: Authorization Exception :: {"path":"/.apm-agent-configuration","query":{},"statusCode":403,"response":""}
    at respond (/mnt/c/elastic/kibana/node_modules/elasticsearch/src/lib/transport.js:315:15)
    at checkRespForFailure (/mnt/c/elastic/kibana/node_modules/elasticsearch/src/lib/transport.js:274:7)
    at HttpConnector.<anonymous> (/mnt/c/elastic/kibana/node_modules/elasticsearch/src/lib/connectors/http.js:166:7)
    at IncomingMessage.wrapper (/mnt/c/elastic/kibana/node_modules/elasticsearch/node_modules/lodash/lodash.js:4935:19)
    at IncomingMessage.emit (events.js:194:15)
    at endReadableNT (_stream_readable.js:1103:12)
    at process._tickCallback (internal/process/next_tick.js:63:19)
    at emitWarning (internal/process/promises.js:81:15)
    at emitPromiseRejectionWarnings (internal/process/promises.js:120:9)
    at process._tickCallback (internal/process/next_tick.js:69:34)
@elasticmachine

This comment has been minimized.

Copy link
Collaborator

commented Jul 11, 2019

Pinging @elastic/apm-ui

@graphaelli

This comment has been minimized.

Copy link
Member

commented Jul 11, 2019

Is this an issue only when running from source or also present in snapshots?

@tylersmalley

This comment has been minimized.

Copy link
Member Author

commented Jul 11, 2019

I haven't checked the snapshot, only saw this when running from source.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.