Kibana not starting up properly. pid":6349,"message":"not sending [kibana_settings] monitoring document because [undefined] is null or invalid."}

{"type":"log","@timestamp":"2019-08-21T11:37:04Z","tags":["debug","stats-collection"],"pid":6349,"message":"not sending [kibana_settings] monitoring document because [undefined] is null or invalid."}
{"type":"log","@timestamp":"2019-08-21T11:37:04Z","tags":["debug","monitoring","kibana-monitoring"],"pid":6349,"message":"Uploading bulk stats payload to the local cluster"}
{"type":"log","@timestamp":"2019-08-21T11:37:04Z","tags":["debug","monitoring","kibana-monitoring"],"pid":6349,"message":"Uploaded bulk stats payload to the local cluster"}

Using latest ELK releases for all modules.




so I have looked for this error specifically on the web and no one really mentions how exactly they fixed it ... not an ELK specialist by any means but I have set it up and used it in the past ...

netstat -nltup
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0* LISTEN 3205/sshd
tcp 0 0* LISTEN 3647/master
tcp 0 0* LISTEN 6349/node
tcp6 0 0 :::9100 :::* LISTEN 3196/node_exporter
tcp6 0 0 :::* LISTEN 7726/java
tcp6 0 0 ::1:9200 :::* LISTEN 7726/java
tcp6 0 0 :::6000 :::* LISTEN 3200/calert
tcp6 0 0 :::* LISTEN 7726/java
tcp6 0 0 ::1:9300 :::* LISTEN 7726/java
tcp6 0 0 :::22 :::* LISTEN 3205/sshd
tcp6 0 0 :::3000 :::* LISTEN 3192/grafana-server
tcp6 0 0 ::1:25 :::* LISTEN 3647/master
tcp6 0 0 :::9090 :::* LISTEN 3193/prometheus

can see the services are listening but unable to access the frontend and the error is quite obscure. Currently there have been no customization to the configs.

This is a debug-level log message, and not an error that you should have to worry about. It's primarily a way to troubleshoot in case anything goes wrong with something specific: Kibana's Monitoring stats getting sent to the Monitoring endpoints. It is normal for it to not work immediately after startup, because not enough time has gone by to collect anything, and the code prevents empty payloads getting sent.

I'll confirm this looks like Kibana started normally. Not being able to access the frontend can be a number of things. It helps to know or try other things:

  • what kind of error does the browser show when you try to access Kibana
  • are you able to ping Kibana from other hosts in the network

Finally, this might help. I took a look at the kibana.yml you linked to:

1. # Specifies the address to which the Kibana server will bind. IP addresses and host names are both valid values.
2. # The default is 'localhost', which usually means remote machines will not be able to connect.
3. # To allow connections from remote users, set this parameter to a non-loopback address.
4. localhost

The server should have a non-loopback address to use as the value, which should enable remote hosts to talk to the Kibana service.

LoL sorry that was blind... Thanks for the response and saving me some time if only I read the comments in the config file :frowning:

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