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
Empty cluster-config-file crashes redis-server #1349
Comments
It sounds like you manually emptied the file... so this is a normal behavior, but probably it could be handled in a more friendly way. |
Yes, I created an empty file and gave it to the redis user. Indeed, deleting it and giving the whole directory to redis solved it. |
mattsta
added a commit
to mattsta/redis
that referenced
this issue
Mar 12, 2014
If someone has a blank (`touch nodes.conf`) config file, Redis would fail with an assert error, which isn't very user friendly. This commit treats empty files as if the server created the file itself and operations continue as expected. Logic: if no lines successfully processed, treat as new configuration file. Fixes redis#1349
mattsta
added a commit
to mattsta/redis
that referenced
this issue
Mar 14, 2014
If someone has a blank (`touch nodes.conf`) config file, Redis would fail with an assert error, which isn't very user friendly. This commit treats empty files as if the server created the file itself and operations continue as expected. Logic: if no lines successfully processed, treat as new configuration file. Fixes redis#1349
mattsta
added a commit
to mattsta/redis
that referenced
this issue
Mar 27, 2014
If someone has a blank (`touch nodes.conf`) config file, Redis would fail with an assert error, which isn't very user friendly. This commit treats empty files as if the server created the file itself and operations continue as expected. Logic: if no lines successfully processed, treat as new configuration file. Fixes redis#1349
Tracking in #1597 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello!
After deleting cluster-config-file and configuring it to a path where the redis user can write, it started up without a problem.
The text was updated successfully, but these errors were encountered: