redis snapshot location not as specified in configHow to link redis rdb file with capistrano deployHow do I delete everything in Redis?Memcached vs. Redis?Configuring Redis to play nice with AppHarborSetting up redis with dockerMISCONF Redis is configured to save RDB snapshotsMISCONF Redis is configured to save RDB snapshots, but is currently not able to persist on diskRedis randomly stats complaining about not being able to save RDB snapshotsRedis is configured to save RDB snapshots after restarting redis serverRedis - Default snapshotting configuration
What happens to the Time Stone
CRT Oscilloscope - part of the plot is missing
What actually is the vector of angular momentum?
In a Latex Table, how can I automatically resize cell heights to account for superscripts?
How could a planet have most of its water in the atmosphere?
Reconstruct a matrix from its traces
I may be a fraud
Was Unix ever a single-user OS?
Should one double the thirds or the fifth in chords?
What was the state of the German rail system in 1944?
Point of the the Dothraki's attack in GoT S8E3?
Junior developer struggles: how to communicate with management?
How to improve/restore vintage Peugeot bike, or is it even worth it?
My ID is expired, can I fly to the Bahamas with my passport?
Would "lab meat" be able to feed a much larger global population
Accidentally deleted the "/usr/share" folder
How to give very negative feedback gracefully?
What happens to matryoshka Mordenkainen's Magnificent Mansions?
What are the differences between credential stuffing and password spraying?
Is it cheaper to drop cargo than to land it?
Type-check an expression
What does a yield inside a yield do?
Is Cola "probably the best-known" Latin word in the world? If not, which might it be?
Number of seconds in 6 weeks
redis snapshot location not as specified in config
How to link redis rdb file with capistrano deployHow do I delete everything in Redis?Memcached vs. Redis?Configuring Redis to play nice with AppHarborSetting up redis with dockerMISCONF Redis is configured to save RDB snapshotsMISCONF Redis is configured to save RDB snapshots, but is currently not able to persist on diskRedis randomly stats complaining about not being able to save RDB snapshotsRedis is configured to save RDB snapshots after restarting redis serverRedis - Default snapshotting configuration
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
After running fine for a while, I am getting write error on my redis instance:
(error) MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
In the log I see:
9948:C 22 Mar 20:49:32.241 # Failed opening the RDB file root (in server root dir /var/spool/cron) for saving: Read-only file system
However, my redis config file is /etc/redis/redis.conf as confirmed by:
redis-cli -p 6379 info | grep 'config_file'
config_file:/etc/redis/redis.conf
And there I have:
dir /mnt/data/redis
And indeed, there is a snapshot there.
But despite the above, redis now thinks my data directory is
redis-cli -p 6379 CONFIG GET dir
1) "dir"
2) "/var/spool/cron"
Corresponding to the error I was getting as quoted above.
Can anyone tell me why/how my data directory is changing after redis starts, such that it is no longer what is specified in the config file?
redis
asked Mar 22 at 20:55
EricEric
1,037718
add a comment |
After running fine for a while, I am getting write error on my redis instance:
(error) MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
In the log I see:
9948:C 22 Mar 20:49:32.241 # Failed opening the RDB file root (in server root dir /var/spool/cron) for saving: Read-only file system
However, my redis config file is /etc/redis/redis.conf as confirmed by:
redis-cli -p 6379 info | grep 'config_file'
config_file:/etc/redis/redis.conf
And there I have:
dir /mnt/data/redis
And indeed, there is a snapshot there.
But despite the above, redis now thinks my data directory is
redis-cli -p 6379 CONFIG GET dir
1) "dir"
2) "/var/spool/cron"
Corresponding to the error I was getting as quoted above.
Can anyone tell me why/how my data directory is changing after redis starts, such that it is no longer what is specified in the config file?
redis
asked Mar 22 at 20:55
EricEric
1,037718
1
Someone might have modified yourdirconfig withCONFIG SET dir /var/spool/croncommand.
– for_stack
Mar 23 at 2:50
@for_stack no one else has access to that machine--at least no one is upposed to. Although I did start noticing this once I opened the port to the world to be able to access it from other servers. Is this a common attack? Perhaps I need to add some middleware to prevent evilness.
– Eric
Mar 23 at 15:26
Looks like opening redis to the universe is just a terrible idea. I will restrict to my security group and/or implement a middleware. techrepublic.com/article/…
– Eric
Mar 23 at 15:29
1
Yes, it's always a bad idea to open Redis to the public. Also check this. It seems someone tried to hack you server.
– for_stack
Mar 24 at 4:13
@for_stack and succeeded. At least so far as changing config and erase data. Although the attempt to write to /var/spool/cron failed as that is read only from the point of view of redis. Security By Obscurity for the Fail!
– Eric
Mar 24 at 13:35
add a comment |
After running fine for a while, I am getting write error on my redis instance:
(error) MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
In the log I see:
9948:C 22 Mar 20:49:32.241 # Failed opening the RDB file root (in server root dir /var/spool/cron) for saving: Read-only file system
However, my redis config file is /etc/redis/redis.conf as confirmed by:
redis-cli -p 6379 info | grep 'config_file'
config_file:/etc/redis/redis.conf
And there I have:
dir /mnt/data/redis
And indeed, there is a snapshot there.
But despite the above, redis now thinks my data directory is
redis-cli -p 6379 CONFIG GET dir
1) "dir"
2) "/var/spool/cron"
Corresponding to the error I was getting as quoted above.
Can anyone tell me why/how my data directory is changing after redis starts, such that it is no longer what is specified in the config file?
redis
asked Mar 22 at 20:55
EricEric
1,037718
After running fine for a while, I am getting write error on my redis instance:
(error) MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
In the log I see:
9948:C 22 Mar 20:49:32.241 # Failed opening the RDB file root (in server root dir /var/spool/cron) for saving: Read-only file system
However, my redis config file is /etc/redis/redis.conf as confirmed by:
redis-cli -p 6379 info | grep 'config_file'
config_file:/etc/redis/redis.conf
And there I have:
dir /mnt/data/redis
And indeed, there is a snapshot there.
But despite the above, redis now thinks my data directory is
redis-cli -p 6379 CONFIG GET dir
1) "dir"
2) "/var/spool/cron"
Corresponding to the error I was getting as quoted above.
Can anyone tell me why/how my data directory is changing after redis starts, such that it is no longer what is specified in the config file?
redis
redis
asked Mar 22 at 20:55
EricEric
1,037718
asked Mar 22 at 20:55
EricEric
1,037718
asked Mar 22 at 20:55
EricEric
1,037718
asked Mar 22 at 20:55
EricEric
1,037718
asked Mar 22 at 20:55
EricEric
1,037718
1,037718
1
Someone might have modified yourdirconfig withCONFIG SET dir /var/spool/croncommand.
– for_stack
Mar 23 at 2:50
@for_stack no one else has access to that machine--at least no one is upposed to. Although I did start noticing this once I opened the port to the world to be able to access it from other servers. Is this a common attack? Perhaps I need to add some middleware to prevent evilness.
– Eric
Mar 23 at 15:26
Looks like opening redis to the universe is just a terrible idea. I will restrict to my security group and/or implement a middleware. techrepublic.com/article/…
– Eric
Mar 23 at 15:29
1
Yes, it's always a bad idea to open Redis to the public. Also check this. It seems someone tried to hack you server.
– for_stack
Mar 24 at 4:13
@for_stack and succeeded. At least so far as changing config and erase data. Although the attempt to write to /var/spool/cron failed as that is read only from the point of view of redis. Security By Obscurity for the Fail!
– Eric
Mar 24 at 13:35
add a comment |
1
Someone might have modified yourdirconfig withCONFIG SET dir /var/spool/croncommand.
– for_stack
Mar 23 at 2:50
@for_stack no one else has access to that machine--at least no one is upposed to. Although I did start noticing this once I opened the port to the world to be able to access it from other servers. Is this a common attack? Perhaps I need to add some middleware to prevent evilness.
– Eric
Mar 23 at 15:26
Looks like opening redis to the universe is just a terrible idea. I will restrict to my security group and/or implement a middleware. techrepublic.com/article/…
– Eric
Mar 23 at 15:29
1
Yes, it's always a bad idea to open Redis to the public. Also check this. It seems someone tried to hack you server.
– for_stack
Mar 24 at 4:13
@for_stack and succeeded. At least so far as changing config and erase data. Although the attempt to write to /var/spool/cron failed as that is read only from the point of view of redis. Security By Obscurity for the Fail!
– Eric
Mar 24 at 13:35
1
1
Someone might have modified your
dir config with CONFIG SET dir /var/spool/cron command.– for_stack
Mar 23 at 2:50
Someone might have modified your
dir config with CONFIG SET dir /var/spool/cron command.– for_stack
Mar 23 at 2:50
@for_stack no one else has access to that machine--at least no one is upposed to. Although I did start noticing this once I opened the port to the world to be able to access it from other servers. Is this a common attack? Perhaps I need to add some middleware to prevent evilness.
– Eric
Mar 23 at 15:26
@for_stack no one else has access to that machine--at least no one is upposed to. Although I did start noticing this once I opened the port to the world to be able to access it from other servers. Is this a common attack? Perhaps I need to add some middleware to prevent evilness.
– Eric
Mar 23 at 15:26
Looks like opening redis to the universe is just a terrible idea. I will restrict to my security group and/or implement a middleware. techrepublic.com/article/…
– Eric
Mar 23 at 15:29
Looks like opening redis to the universe is just a terrible idea. I will restrict to my security group and/or implement a middleware. techrepublic.com/article/…
– Eric
Mar 23 at 15:29
1
1
Yes, it's always a bad idea to open Redis to the public. Also check this. It seems someone tried to hack you server.
– for_stack
Mar 24 at 4:13
Yes, it's always a bad idea to open Redis to the public. Also check this. It seems someone tried to hack you server.
– for_stack
Mar 24 at 4:13
@for_stack and succeeded. At least so far as changing config and erase data. Although the attempt to write to /var/spool/cron failed as that is read only from the point of view of redis. Security By Obscurity for the Fail!
– Eric
Mar 24 at 13:35
@for_stack and succeeded. At least so far as changing config and erase data. Although the attempt to write to /var/spool/cron failed as that is read only from the point of view of redis. Security By Obscurity for the Fail!
– Eric
Mar 24 at 13:35
add a comment |
1 Answer
1
active
oldest
votes
So the answer is that the redis server was hacked and the configuration changed, which is very easy to do as it turns out. (I should point out that I had no reason to think it wasn't easy to do. I just assumed security by obscurity was sufficient in this case--wrong. No matter, this was just a playground not any sort of production server).
So don't open your redis port to the world. Use security groups if on AWS to limit access to machines that need it, or use AUTH (which is still not awesome because then all clients need to know the single password which also apparently gets sent in the clear), or have some middleware controlling access.
Hacking redis is easy to do, can compromise your data, and even enable unauthorized SSH access to your server. And that's why you shouldn't highline.
answered Mar 24 at 13:31
EricEric
1,037718
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55307646%2fredis-snapshot-location-not-as-specified-in-config%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
So the answer is that the redis server was hacked and the configuration changed, which is very easy to do as it turns out. (I should point out that I had no reason to think it wasn't easy to do. I just assumed security by obscurity was sufficient in this case--wrong. No matter, this was just a playground not any sort of production server).
So don't open your redis port to the world. Use security groups if on AWS to limit access to machines that need it, or use AUTH (which is still not awesome because then all clients need to know the single password which also apparently gets sent in the clear), or have some middleware controlling access.
Hacking redis is easy to do, can compromise your data, and even enable unauthorized SSH access to your server. And that's why you shouldn't highline.
answered Mar 24 at 13:31
EricEric
1,037718
add a comment |
So the answer is that the redis server was hacked and the configuration changed, which is very easy to do as it turns out. (I should point out that I had no reason to think it wasn't easy to do. I just assumed security by obscurity was sufficient in this case--wrong. No matter, this was just a playground not any sort of production server).
So don't open your redis port to the world. Use security groups if on AWS to limit access to machines that need it, or use AUTH (which is still not awesome because then all clients need to know the single password which also apparently gets sent in the clear), or have some middleware controlling access.
Hacking redis is easy to do, can compromise your data, and even enable unauthorized SSH access to your server. And that's why you shouldn't highline.
answered Mar 24 at 13:31
EricEric
1,037718
add a comment |
So the answer is that the redis server was hacked and the configuration changed, which is very easy to do as it turns out. (I should point out that I had no reason to think it wasn't easy to do. I just assumed security by obscurity was sufficient in this case--wrong. No matter, this was just a playground not any sort of production server).
So don't open your redis port to the world. Use security groups if on AWS to limit access to machines that need it, or use AUTH (which is still not awesome because then all clients need to know the single password which also apparently gets sent in the clear), or have some middleware controlling access.
Hacking redis is easy to do, can compromise your data, and even enable unauthorized SSH access to your server. And that's why you shouldn't highline.
answered Mar 24 at 13:31
EricEric
1,037718
So the answer is that the redis server was hacked and the configuration changed, which is very easy to do as it turns out. (I should point out that I had no reason to think it wasn't easy to do. I just assumed security by obscurity was sufficient in this case--wrong. No matter, this was just a playground not any sort of production server).
So don't open your redis port to the world. Use security groups if on AWS to limit access to machines that need it, or use AUTH (which is still not awesome because then all clients need to know the single password which also apparently gets sent in the clear), or have some middleware controlling access.
Hacking redis is easy to do, can compromise your data, and even enable unauthorized SSH access to your server. And that's why you shouldn't highline.
answered Mar 24 at 13:31
EricEric
1,037718
answered Mar 24 at 13:31
EricEric
1,037718
answered Mar 24 at 13:31
EricEric
1,037718
answered Mar 24 at 13:31
EricEric
1,037718
1,037718
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55307646%2fredis-snapshot-location-not-as-specified-in-config%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Someone might have modified your
dirconfig withCONFIG SET dir /var/spool/croncommand.– for_stack
Mar 23 at 2:50
@for_stack no one else has access to that machine--at least no one is upposed to. Although I did start noticing this once I opened the port to the world to be able to access it from other servers. Is this a common attack? Perhaps I need to add some middleware to prevent evilness.
– Eric
Mar 23 at 15:26
Looks like opening redis to the universe is just a terrible idea. I will restrict to my security group and/or implement a middleware. techrepublic.com/article/…
– Eric
Mar 23 at 15:29
1
Yes, it's always a bad idea to open Redis to the public. Also check this. It seems someone tried to hack you server.
– for_stack
Mar 24 at 4:13
@for_stack and succeeded. At least so far as changing config and erase data. Although the attempt to write to /var/spool/cron failed as that is read only from the point of view of redis. Security By Obscurity for the Fail!
– Eric
Mar 24 at 13:35