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
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)
"service graylog-server restart" fails after upgrade
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
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
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)
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)
Your Environment
Multnode GL
The text was updated successfully, but these errors were encountered: