Hi , i installed a elk years ago , and everything is fine , but i start to getting this in kibana :
any idea?
hey
Can you be more specific about the versions you are using ?
Thanks
Rashmi
i have a similar behavior when trying to start my newly installed kibana. Kibana is auto-restarting in loops till is completly stop with this exact error message with no explicit error message to guide me in my investigations to fix the issue.
Kibana dosen't seem to write logs with this issue so i have not otherr information beside what is in the above picture.
here's my relevant kibana.yml config:
server.port: 5601
server.host: "xx.xx.xx.xxx" #(same ip as the local machine which is where ES is running too)
server.name: "DEV Kibana"
elasticsearch.url: "http://xx.xx.xx.xx:9200" #(i am able to access this via browser or curl)
logging.dest: /opt/kibana/logs/kibana.log #(did a mkdir for the log folder with a chown for kibana user)
I'd like to know how to get more precise information about startup crashes of Kibana since i'm not able to find any log. Could someone give some insight on this?
Thanks!
EDIT: i'm using kibana 4.5.4 with ES 5.6x i believe
hi Rashmi , i don't remember the version ...maybe i could check that via cli.
{
"name" : "Maria Hill",
"cluster_name" : "elasticsearch",
"cluster_uuid" : "dYmDNxz6TWKwO7d3oyWSDw",
"version" : {
"number" : "2.4.5",
"build_hash" : "c849dd13904f53e63e88efc33b2ceeda0b6a1276",
"build_timestamp" : "2017-04-24T16:18:17Z",
"build_snapshot" : false,
"lucene_version" : "5.5.4"
},
"tagline" : "You Know, for Search"
}
If you're using the systemd service logs are saved in the system journal. Can you try journalctl -fu kibana.service?
1 Like
i get te same report that earlier.
Can you scroll up? the arrow keys should be usable.
there is no more ....
logging.quiet will suppress all logs of that option is set. logging.dest will pipe all logs from stdout to that path - it looks fine, if the logs and kibana.log folder are owned by kibana:kibana. Do you know if you're using the official 4.6 packages?
Okay, lets try running kibana not as a service to see if we can get the error to stdout.
Can you run bin/kibana from the /opt/kibana folder, and comment out the logging.dest line for now?
Starting kibana after running your command in another terminal gave me this:
Nov 01 14:13:58 VSALINUXDEV01 systemd[1]: Started no description given.
Nov 01 14:13:59 VSALINUXDEV01 kibana[5163]: FATAL { [ValidationError: child "server" fails because ["name" is not allowed]]
Nov 01 14:13:59 VSALINUXDEV01 kibana[5163]: name: 'ValidationError',
Nov 01 14:13:59 VSALINUXDEV01 kibana[5163]: details:
Nov 01 14:13:59 VSALINUXDEV01 kibana[5163]: [ { message: '"name" is not allowed',
Nov 01 14:13:59 VSALINUXDEV01 kibana[5163]: path: 'server.name',
Nov 01 14:13:59 VSALINUXDEV01 kibana[5163]: type: 'object.allowUnknown',
Nov 01 14:13:59 VSALINUXDEV01 kibana[5163]: context: [Object] } ],
Nov 01 14:13:59 VSALINUXDEV01 kibana[5163]: _object:
Nov 01 14:13:59 VSALINUXDEV01 kibana[5163]: { pkg:
Nov 01 14:13:59 VSALINUXDEV01 kibana[5163]: { version: '4.5.4',
Nov 01 14:13:59 VSALINUXDEV01 kibana[5163]: buildNum: 10000,
Nov 01 14:13:59 VSALINUXDEV01 kibana[5163]: buildSha: '00d0f493b91e3215703b8c8a64ec09966216ed95' },
Nov 01 14:13:59 VSALINUXDEV01 kibana[5163]: pid: { exclusive: false },
Nov 01 14:13:59 VSALINUXDEV01 kibana[5163]: server: { port: 5601, host: '10.33.41.237', name: 'DEV Kibana' } },
Nov 01 14:13:59 VSALINUXDEV01 kibana[5163]: annotate: [Function] }
Nov 01 14:13:59 VSALINUXDEV01 systemd[1]: kibana.service: Main process exited, code=exited, status=1/FAILURE
Nov 01 14:13:59 VSALINUXDEV01 systemd[1]: kibana.service: Unit entered failed state.
Nov 01 14:13:59 VSALINUXDEV01 systemd[1]: kibana.service: Failed with result 'exit-code'.
Nov 01 14:13:59 VSALINUXDEV01 systemd[1]: kibana.service: Service hold-off time over, scheduling restart.
Nov 01 14:13:59 VSALINUXDEV01 systemd[1]: Stopped no description given.
I'll read about the constraint on the server.name config in kibana a try to fix it. I'll keep you updated
i removed 'proxy_pass http://localhost:5601' from kibana.yml and the service starts fine.
i don't know what happened.
server.name is a newer config and didn't exist in 4.5 - see https://www.elastic.co/guide/en/kibana/4.5/kibana-server-properties.html for configs on that version.
1 Like
Thanks a lot!
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.