Error :Authentication of [elastic] was terminated by realm [reserved] - failed to authenticate user [elastic]

Hi,

I am getting the following error while running elastic search using "yarn es source"

│ info [o.e.x.s.a.AuthenticationService] [vaseem-virtual-machine] Authentication of [elastic] was terminated by realm [reserved] - failed to authenticate user [elastic]
│ warn assuming [elastic] user not available yet, waiting 1.5 seconds and trying again
│ info [o.e.l.LicenseService] [vaseem-virtual-machine] license [b3f49081-4763-4a50-b50b-4bd0ccf17c7f] mode [basic] - valid
│ info [o.e.x.s.a.AuthenticationService] [vaseem-virtual-machine] Authentication of [elastic] was terminated by realm [reserved] - failed to authenticate user [elastic]
│ERROR ResponseError: security_exception
│ at IncomingMessage.response.on (/home/vaseem/vaseem/kibana/node_modules/@elastic/elasticsearch/lib/Transport.js:290:25)
│ at IncomingMessage.emit (events.js:194:15)
│ at endReadableNT (_stream_readable.js:1103:12)
│ at process._tickCallback (internal/process/next_tick.js:63:19)
│ info [o.e.x.m.p.NativeController] [vaseem-virtual-machine] Native controller process has stopped - no new native processes can be started
│ info [o.e.n.Node] [vaseem-virtual-machine] stopping ...
│ info [o.e.x.w.WatcherService] [vaseem-virtual-machine] stopping watch service, reason [shutdown initiated]
│ info [o.e.n.Node] [vaseem-virtual-machine] stopped
│ info [o.e.n.Node] [vaseem-virtual-machine] closing ...
│ info [o.e.n.Node] [vaseem-virtual-machine] closed

Step:

  1. git clone https://github.com/elastic/kibana kibana
    git checkout v7.2.0
  2. cd kibana
  3. Bootstrap Kibana and install all the dependencies by executing below command(node.js and yarn already installled)

yarn kbn bootstrap

step 3 completed successfully.
4) git clone https://github.com/elastic/elasticsearch.git elasticsearch
git checkout v7.2.0

  1. Execute below command in kibana home
    yarn es source

Note : version of kibana and elasticsearch was v7.2.0

Please guide me how to resolve this error.

I moved this to the Kibana topic because the error is occurring in the Kibana build.

Thanks tim