Z
Z
Zohei2016-01-24 12:33:24
FreeBSD
Zohei, 2016-01-24 12:33:24

Why does Redis change its dir and dbfilename options and crash with MISCONF Redis is configured to save RDB snapshots?

[80927] Jan 24 07:04:41.643 * 1 changes in 900 seconds. Saving...
[80927] 24 Jan 07:04:41.648 * Background saving started by pid 52245
[52245] 24 Jan 07:04:41.649 # Error moving temp DB file on the final destination: Is a directory
[80927] 24 Jan 07:04:41.748 # Background saving error

I fill in the paths to the dump with pens:
CONFIG SET dir /usr/bin/redis
CONFIG SET dbfilename temp.rdb

but after a while, the paths go astray again:
redis 127.0.0.1:6379> CONFIG GET dbfilename
1) "dbfilename"
2) "authorized_keys"


df -h
Filesystem Size Used Avail Capacity Mounted on
/dev/vdisk 6.0G 5G 1.1G 82% /
devfs 1.0k 1.0k 0B 100% /dev

when I try to change the memory allocation policy in sysctl under root, I get:
sysctl vm.overcommit=1
vm.overcommit: 0
sysctl: vm.overcommit=1: Operation not permitted
Support response:
Hello.
On this virtualization system, this setting cannot be changed.

Of course, I will transfer projects to another server... if nothing can be done about the crashes... although this scenario is very undesirable..
INFO:
127.0.0.1:6379 redis> the INFO
# Server
redis_version: 2.6.12
redis_git_sha1: 00000000
redis_git_dirty: 0
redis_mode: the standalone
os: the FreeBSD 8.3-STABLE amd64
arch_bits: 64
multiplexing_api: kqueue
gcc_version: 4.2.1
process_id:
80927 run_id: 9f7e6b9b08f49c85f335abe0e21e8d8c4f094d71
TCP_PORT: 6379
uptime_in_seconds:79856
uptime_in_days:0
hz:10
lru_clock:658666
# Clients
connected_clients:1
client_longest_output_list:0
client_biggest_input_buf:0
blocked_clients:0
# Memory
used_memory:1164464
used_memory_human:1.11M
used_memory_rss: 1164464
used_memory_peak: 1244280
used_memory_peak_human: 1.19M
used_memory_lua: 31744
mem_fragmentation_ratio: 1.00
mem_allocator: the libc
# Persistence
loading: 0
rdb_changes_since_last_save: 0
rdb_bgsave_in_progress: 0
rdb_last_save_time: 1453621516
rdb_last_bgsave_status: ok
The rdb_last_bgsave_time_sec: 0
rdb_current_bgsave_time_sec: -1
aof_enabled: 0
aof_rewrite_in_progress: 0
aof_rewrite_scheduled :0
aof_last_rewrite_time_sec:-1
aof_current_rewrite_time_sec:-1
aof_last_bgrewrite_status:ok
# Stats
total_connections_received:290
total_commands_processed: 1077
instantaneous_ops_per_sec: 0
rejected_connections: 0
expired_keys: 2
evicted_keys: 0
keyspace_hits: 722
keyspace_misses: 36
pubsub_channels: 0
pubsub_patterns: 0
latest_fork_usec: 346
# the Replication
role: the master
connected_slaves: 0
# the CPU
used_cpu_sys: 106.24
used_cpu_user: 5.95
used_cpu_sys_children: 136.74
used_cpu_user_children :14.78
# Keyspace
db0:keys=1,expires=0
db1:keys=4,expires=3

Answer the question

In order to leave comments, you need to log in

1 answer(s)
Z
Zohei, 2017-09-30
@Zohei

As always, I am answering my own question.
in runtime, every time I start the application, I resave the config variables

CONFIG SET dir /usr/bin/redis
CONFIG SET dbfilename temp.rdb

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question