You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I traced this down to the -m flag to su in the init script. This causes the elasticsearch process to try to read ~root/.bash_profile, but it does not have read access to ~root. The simplest solution I can think of is to remove the -m flag, but I do not know if that would have any bad consequences.
The text was updated successfully, but these errors were encountered:
Hi, there's been a similar discussion at karmi/cookbook-elasticsearch#31 in the past. I've been never able to consistently reproduce this issue. The -m flag is used so the environment is preserved (namely ES_INCLUDE, PIDFILE, etc).
It's really a warning only, as far as I understand? Anyway, running the command as root is pretty rare, actually, apart from some bootstrapping sequence and such?
Note, there's been a regression in the init script, where the PIDFILE was set incorrectly, it's now fixed as part of karmi/cookbook-elasticsearch@52c2632
I get an error message when I run the start script manually:
I traced this down to the -m flag to su in the init script. This causes the elasticsearch process to try to read ~root/.bash_profile, but it does not have read access to ~root. The simplest solution I can think of is to remove the -m flag, but I do not know if that would have any bad consequences.
The text was updated successfully, but these errors were encountered: