Closed bhavyarm closed 4 months ago
Pinging @elastic/kibana-operations (Team:Operations)
I don't think this is an issue for the Ops team, maybe @elastic/kibana-core team.
In any case I just tried this my self and it seems like there is not a problem, you probably have just not waited for the successful stop of Kibana and every plugin and closed out the window which left the process open.
[2024-01-16T21:41:12.978+00:00][INFO ][plugins.securitySolution.endpoint:metadata-check-transforms-task:0.0.1] no endpoint installation found
^C[2024-01-16T21:41:24.870+00:00][INFO ][root] SIGINT received - initiating shutdown
[2024-01-16T21:41:24.871+00:00][INFO ][root] Kibana is shutting down
[2024-01-16T21:41:54.877+00:00][INFO ][plugins-system.standard] Stopping all plugins.
[2024-01-16T21:41:54.879+00:00][INFO ][plugins.monitoring.monitoring.kibana-monitoring] Monitoring stats collection is stopped
[2024-01-16T21:41:54.899+00:00][INFO ][plugins-system.standard] All plugins stopped.
However taking 30 seconds to shutdown seems slower than before and probably something that is worth to looking into have changed here. I think its possible the problematic plugin is monitoring as it is the last one logging stop before shutting down the process (Monitoring stats collection is stopped
) but maybe the core team will know more about this.
Closing as cannot reproduce
Kibana version: 8.12.0 BC6
Elasticsearch version: 8.12.0 BC6
Server OS version: darwin_aarch
Original install method (e.g. download page, yum, from source, etc.): from staging
Describe the bug: I cannot terminate Kibana process in my terminal. CTRL-C doesn't work and when I click on x on the window - I get the message about having to be sure about terminating node process and I confirm. But restarting Kibana just tells port 5601 is already in use.
Posting logs and ps -ef output:
ps -ef | grep kibana 501 6853 5559 0 3:53pm ttys001 0:00.01 grep kibana
ps -ef | grep node (no node connected to Kibana)