Conversation
|
heh - ignore that. autopilot, of course i verify my commits |
|
Pinging @elastic/kibana-operations (Team:Operations) |
|
@jbudz, can you add the release note text per the format in https://www.elastic.co/guide/en/kibana/master/contributing.html#_create_the_release_notes_text |
|
I am not seeing the logs - am I missing something? |
|
huh that's interesting - I think we lose all logs if there's a permission error. It might make more sense to redirect stdout to file.. |
|
Is this ready for another look? |
|
@elasticmachine merge upstream |
|
@elasticmachine merge upstream |
|
I am fine with this approach since it's the current behavior for anyone using |
|
@elasticmachine merge upstream |
tylersmalley
left a comment
There was a problem hiding this comment.
Actually, spoke too soon - set_access is still being called for Red Hat in the post_install
| fi | ||
|
|
||
| set_access | ||
| setup |
There was a problem hiding this comment.
Why do we no longer want to call this for Red Hat?
There was a problem hiding this comment.
fixed with a2ba7f4. I haven't been able to get a build through pending the x-pack master failure, so not quite ready for testing yet. Will update.
tylersmalley
left a comment
There was a problem hiding this comment.
We're no longer setting permissions for Red Hat:
$ ls -al /etc/kibana
total 24
drwxr-xr-x. 2 root root 44 Oct 5 22:14 .
drwxr-xr-x. 81 root root 8192 Oct 5 22:15 ..
-rw-r--r--. 1 root root 4818 Oct 5 20:28 kibana.yml
-rw-r--r--. 1 root root 216 Oct 5 20:28 node.options
vs expected on Ubuntu
$ sudo ls -al /etc/kibana
total 24
drwxr-s--- 2 root kibana 4096 Sep 28 23:35 .
drwxr-xr-x 86 root root 4096 Sep 28 22:00 ..
-rw-r--r-- 1 root kibana 130 Sep 28 23:35 kibana.keystore
-rw-rw---- 1 root kibana 5194 Sep 28 18:40 kibana.yml
-rw-r--r-- 1 root kibana 216 Sep 28 18:40 node.options
tylersmalley
left a comment
There was a problem hiding this comment.
LGTM tested both deb/RPM
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: |
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
|
7.x/7.11: 60813d7 |
This adds a CLI arg for sysv and systemd to set logging dest.
In cases where the logger still isn't initialized logs are sent to the kibana.log or the system journal (journalctl -u kibana.server) respectively. I'm undecided what we want here, this is the prior behavior but inconsistent.
We also may want to consider this as a breaking change
Closes #6579
Release note
Fixes the logging destination for systemd installations and and updates the sysv filename to be consistent with other stack products. Previously, systemd logged to the system journal or
/var/log/kibana/kibana.stoud. Now both will log to the `/var/log/kibana/kibana.log'.