PID of the kibana process could be written to pid file earlier #4680
Labels
Comments
This was referenced Jan 25, 2016
bevacqua
added a commit
to bevacqua/kibana
that referenced
this issue
Mar 15, 2016
7 tasks
e40pud
added a commit
to e40pud/kibana
that referenced
this issue
Sep 7, 2022
9 tasks
e40pud
added a commit
that referenced
this issue
Sep 13, 2022
…fields and exceptions (#4680) (#140221) * [Detections] Rule Preview should process override fields and exceptions (#4680) * CI fixes - Types - Unused translations - Unit tests * Fix cypress tests * Fix broken alerts table in fullscreen mode * Update rule configuration state on about step overrides chnges * [CI] Auto-commit changed files from 'node scripts/precommit_hook.js --ref HEAD~1..HEAD --fix' * Review comments Co-authored-by: Kibana Machine <[email protected]>
e40pud
added a commit
to e40pud/kibana
that referenced
this issue
Sep 14, 2022
…k on override fields changes (elastic#4680)
e40pud
added a commit
that referenced
this issue
Sep 14, 2022
…k on override fields changes (#140736) * [Security Solution][Detections] Rule Preview: Refreshing does not work on override fields changes (#4680) * [CI] Auto-commit changed files from 'node scripts/precommit_hook.js --ref HEAD~1..HEAD --fix' Co-authored-by: kibanamachine <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When Kibana starts and elasticsearch is not available, PID of Kibana's process is not written into file. It appears there only after connection if available. This complicates creation of Kibana init.d script (mainly stop function) that must detect PID itself instead of going to pid file. One cannot simply call
killproc -p $pidfileThe text was updated successfully, but these errors were encountered: