Generation of logs for kibana has stopped after SIGHUP

I observed that after SIGHUP signal sent to kibana, logs generation have stopped.
Please tell how and why sighup signal is sent to kibana service.

What version of Kibana is this?

What does your logging configuration look like?

How are you starting Kibana?

Why are the SIGHUP signals being sent?

This signal is to make Kibana reload its logging settings. The logging settings may be changing in a way that stops the logs from being sent where you expect them.

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