Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade to graylog-server-2.4.0-6.beta.4.noarch generates "Invalid configuration" due to file perm. #4427

Closed
jekelundh opened this issue Dec 18, 2017 · 1 comment · Fixed by #4428
Assignees
Labels
blocker If not finished by release date, the release will be postponed. bug
Milestone

Comments

@jekelundh
Copy link

Upgrade to graylog-server-2.4.0-6.beta.4.noarch (from beta.3) generates "Invalid configuration" due to file permissions.

Log:
com.github.joschi.jadconfig.ValidationException: Node ID file at path /etc/graylog/server/node-id isn't writable. Please specify the correct path or change the permissions
at org.graylog2.Configuration$NodeIdFileValidator.validate(Configuration.java:372) ~[graylog.jar:?]
at org.graylog2.Configuration$NodeIdFileValidator.validate(Configuration.java:345) ~[graylog.jar:?]
at com.github.joschi.jadconfig.JadConfig.validateParameter(JadConfig.java:215) ~[graylog.jar:?]
at com.github.joschi.jadconfig.JadConfig.processClassFields(JadConfig.java:148) ~[graylog.jar:?]
at com.github.joschi.jadconfig.JadConfig.process(JadConfig.java:99) ~[graylog.jar:?]
at org.graylog2.bootstrap.CmdLineTool.processConfiguration(CmdLineTool.java:351) [graylog.jar:?]
at org.graylog2.bootstrap.CmdLineTool.readConfiguration(CmdLineTool.java:344) [graylog.jar:?]
at org.graylog2.bootstrap.CmdLineTool.run(CmdLineTool.java:177) [graylog.jar:?]
at org.graylog2.bootstrap.Main.main(Main.java:44) [graylog.jar:?]

Possible Solution

Fix:
#chown graylog /etc/graylog/server/node-id

Steps to Reproduce (for bugs)

  1. "service graylog-server restart" fails after upgrade

Your Environment

Multnode GL

  • Graylog Version: graylog-server-2.4.0-6.beta.4.noarch
  • Elasticsearch Version: elasticsearch-5.6.4-1.noarch
  • MongoDB Version: mongodb-org-3.2.17-1.el7.x86_64
  • Operating System: CentOS Linux release 7.4.1708 (Core)
  • Browser version: any
@bernd bernd added blocker If not finished by release date, the release will be postponed. bug labels Dec 18, 2017
@bernd bernd added this to the 2.4.0 milestone Dec 18, 2017
@bernd
Copy link
Member

bernd commented Dec 18, 2017

@jekelundh Thank you for the report. This regression has been introduced in #4417 and will be fixed in the next beta/rc release.

@kroepke kroepke self-assigned this Dec 18, 2017
kroepke added a commit that referenced this issue Dec 18, 2017
server start would fail if the node id was non-empty, but not writable.
this is a valid scenario where the node id is frozen by making the file read-only

added tests for various scenarios

fixes #4427
@ghost ghost added the in progress label Dec 18, 2017
bernd pushed a commit that referenced this issue Dec 18, 2017
server start would fail if the node id was non-empty, but not writable.
this is a valid scenario where the node id is frozen by making the file read-only

added tests for various scenarios

fixes #4427
@ghost ghost removed the in progress label Dec 18, 2017
bernd pushed a commit that referenced this issue Dec 18, 2017
server start would fail if the node id was non-empty, but not writable.
this is a valid scenario where the node id is frozen by making the file read-only

added tests for various scenarios

fixes #4427

(cherry picked from commit 3de61c0)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocker If not finished by release date, the release will be postponed. bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants