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

_sincedb_write failed: /dev/null.new: Permission denied #2935

Closed
rmoff opened this issue Apr 1, 2015 · 8 comments
Closed

_sincedb_write failed: /dev/null.new: Permission denied #2935

rmoff opened this issue Apr 1, 2015 · 8 comments
Assignees

Comments

@rmoff
Copy link

rmoff commented Apr 1, 2015

$ ./bin/logstash -V
logstash 1.5.0.rc2

On shutdown (Ctrl-C) on Mac, I get this warning:

SIGINT received. Shutting down the pipeline. {:level=>:warn}
_sincedb_write failed: /dev/null.new: Permission denied - /dev/null.new {:level=>:warn}

Is this a benign warning, or have I got something setup wrong?

Thanks.

@suyograo suyograo added the bug label Apr 6, 2015
@suyograo suyograo added this to the v1.5.0 milestone Apr 9, 2015
@ph
Copy link
Contributor

ph commented Apr 9, 2015

@rmoff would you mind posting your configuration?
Is your sincedb_path is set to /dev/null or something else?

@ph
Copy link
Contributor

ph commented Apr 9, 2015

@rmoff nevermind, this look like a regression in the library we are using to tail the files.

@ralphbellofatto
Copy link

Is something being changed to fix this problem, or is this directions for a user workaround? If it is a user level workaround what does the user have to change?

The release candidate appears to be a bit useless when doing file io, as it won't remember the sincedb info.

@suyograo
Copy link
Contributor

suyograo commented Apr 9, 2015

@ralphbellofatto we are working on a fix here: jordansissel/ruby-filewatch#54

We will be releasing a RC3 soon, or you can just update the file input using bin/plugin update (when the fix is in)

@suyograo
Copy link
Contributor

Fixed in 0.6.2 of filewatch

@ph
Copy link
Contributor

ph commented Apr 14, 2015

@ralphbellofatto we just pushed a new version of the plugin, if you do bin/plugin update logstash-input-file you should get the updated plugin.

@rmoff
Copy link
Author

rmoff commented Apr 15, 2015

Can confirm this issue is fixed after updating the plugin. Thanks @ph, @suyograo.

@jsvd
Copy link
Member

jsvd commented Apr 15, 2015

🎆 thanks for testing @rmoff

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

No branches or pull requests

6 participants