Elastic-agent not respecting the config file parameters

Elastic Stack Beats
,
1

Elastic agent doesn't seem to respect the parameters specified in the config file. As per below config, gRPC should bind to 6790. Rather it binds on 6789 (default).

agent.grpc:
  address: localhost
  port: 6790

Here's the open ports for ES agent after running it.

[elastic-agent.exe]
  TCP    127.0.0.1:6789         127.0.0.1:53942        ESTABLISHED     27460
 [elastic-agent.exe]
  TCP    127.0.0.1:6789         127.0.0.1:53945        ESTABLISHED     27460
 [elastic-agent.exe]
  TCP    127.0.0.1:6789         127.0.0.1:53954        ESTABLISHED     27460
 [elastic-agent.exe]
  TCP    127.0.0.1:6789         127.0.0.1:63411        ESTABLISHED     27460

Is this a bug?

2

This is a bug. Do you mind opening an issue on GH? Sign in to GitHub · GitHub

As a workaround, you can add the same configuration to fleet.yml, and it will work.

3

Should I report an issue with beats repo? Already raised an issue with elastic-agent-client.

4

Getting below error while trying to run a second elastic agent process.

Error: could not start the HTTP server for the API: failed to listen on the named pipe \\.\pipe\elastic-agent: open \\.\pipe\elastic-agent: Access is denied.

P.S.: I'm not performing install, trying to run two processes using enroll and then run.

5

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.