I apply this to three node cluster
all of them are master/data/kibana
two of them starts up kibana without any problem
one does not. it do not even puts any log on log file or on screen
systemctl status kibana
● kibana.service - Kibana
Loaded: loaded (/etc/systemd/system/kibana.service; enabled; vendor preset: disabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2020-06-19 09:24:45 CDT; 1s ago
Process: 31345 ExecStart=/usr/share/kibana/bin/kibana (code=exited, status=1/FAILURE)
Main PID: 31345 (code=exited, status=1/FAILURE)
Jun 19 09:24:45 elkdev01 systemd: Unit kibana.service entered failed state.
Jun 19 09:24:45 elkdev01 systemd: kibana.service failed.
Are kibana folders with the right user ? With space left on filesystem ?
Is kibana port free ?
all folder with proper permission as other system as I double check.
netstat show port is not being used 5601
I even rebooted system. but same thing
is it something to do with user
kibana_system as I read in release note that user kibana is no longer used
I am using user kibana in my config file. but how come two system are still working? this is most definitly something to do with 7.8 version
anyone having issue after upgrade?
I have install kibana as root and running as root
journalctl -fu kibana.service
-- Logs begin at Fri 2020-06-19 10:14:56 CDT. --
Jun 20 08:11:40 elkdev01 kibana: at Module._compile (/usr/share/kibana/node_modules/pirates/lib/index.js:99:24)
Jun 20 08:11:40 elkdev01 kibana: at Module._extensions..js (internal/modules/cjs/loader.js:789:10)
Jun 20 08:11:40 elkdev01 systemd: kibana.service: main process exited, code=exited, status=1/FAILURE
Jun 20 08:11:40 elkdev01 systemd: Unit kibana.service entered failed state.
Jun 20 08:11:40 elkdev01 systemd: kibana.service failed.
Jun 20 08:11:43 elkdev01 systemd: kibana.service holdoff time over, scheduling restart.
Jun 20 08:11:43 elkdev01 systemd: start request repeated too quickly for kibana.service
Jun 20 08:11:43 elkdev01 systemd: Failed to start Kibana.
Jun 20 08:11:43 elkdev01 systemd: Unit kibana.service entered failed state.
Jun 20 08:11:43 elkdev01 systemd: kibana.service failed.
I have even reinstall kibana.
first remove kibana package, remove all dir's and reinstall.
still won't start and no error message on log at all.
something went wrong with uid/gid I guess.
remove rpm first
than created manual uid/gid same as my other two node on cluster.
install rpm again
copy back same config that I had it before
restarted and it is working.
do not know what went wrong on installation but something did which cause this problem.
This has the fixed.
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.