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

Permission issues on node-id file lead to not very helpful error messages and exit #4410

Closed
lennartkoopmann opened this Issue Dec 10, 2017 · 4 comments

Comments

Projects
None yet
4 participants
@lennartkoopmann
Member

lennartkoopmann commented Dec 10, 2017

The server repeatedly prints an error that no node-id file exists and that it created a new fil before exit if the node-id file cannot be written, but no error about a file permission issue is printed. This happened to me on initial setup.

I moved this into the 2.4.0 milestone for now but am OK with moving it into 3.0.0 if it's hard to fix and if it is not a recent regression.

Your Environment

  • Graylog Version: v2.4.0-beta.4-SNAPSHOT
  • Operating System: Ubuntu 17.10

@lennartkoopmann lennartkoopmann added the bug label Dec 10, 2017

@lennartkoopmann lennartkoopmann added this to the 2.4.0 milestone Dec 10, 2017

@joschi

This comment has been minimized.

Contributor

joschi commented Dec 10, 2017

@lennartkoopmann Please provide some information how to reproduce the issue.

@kroepke

This comment has been minimized.

Member

kroepke commented Dec 13, 2017

If the node id file belongs to root and isn't even readable the server correct exits with:

ERROR: Unable to access file /home/kroepke/local/graylog/server1/node-id

@kroepke

This comment has been minimized.

Member

kroepke commented Dec 13, 2017

The problem is that a readable, but not writable node-id file does not throw the expected AccessDeniedException (any more?) but instead a generic IOException.

@lennartkoopmann

This comment has been minimized.

Member

lennartkoopmann commented Dec 13, 2017

Correct, it happens when the file can't be written.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment