hcare@appsrv:~$ ^C
hcare@appsrv:~$ sudo docker logs 05ceb963f56b
1:C 04 Sep 2025 06:10:51.417 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1:C 04 Sep 2025 06:10:51.417 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 04 Sep 2025 06:10:51.417 * Redis version=7.4.2, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 04 Sep 2025 06:10:51.417 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
1:M 04 Sep 2025 06:10:51.418 * monotonic clock: POSIX clock_gettime
1:M 04 Sep 2025 06:10:51.421 * Running mode=standalone, port=6379.
1:M 04 Sep 2025 06:10:51.421 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:M 04 Sep 2025 06:10:51.421 # Warning: Could not create server TCP listening socket *:6379: bind: Address already in use
1:M 04 Sep 2025 06:10:51.421 # Failed listening on port 6379 (tcp), aborting.
1:C 04 Sep 2025 06:10:51.925 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1:C 04 Sep 2025 06:10:51.925 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 04 Sep 2025 06:10:51.925 * Redis version=7.4.2, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 04 Sep 2025 06:10:51.925 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
1:M 04 Sep 2025 06:10:51.926 * monotonic clock: POSIX clock_gettime
1:M 04 Sep 2025 06:10:51.929 * Running mode=standalone, port=6379.
1:M 04 Sep 2025 06:10:51.929 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:M 04 Sep 2025 06:10:51.929 # Warning: Could not create server TCP listening socket *:6379: bind: Address already in use
1:M 04 Sep 2025 06:10:51.929 # Failed listening on port 6379 (tcp), aborting.
1:C 04 Sep 2025 06:10:52.520 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1:C 04 Sep 2025 06:10:52.521 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 04 Sep 2025 06:10:52.521 * Redis version=7.4.2, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 04 Sep 2025 06:10:52.521 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
1:M 04 Sep 2025 06:10:52.521 * monotonic clock: POSIX clock_gettime
1:M 04 Sep 2025 06:10:52.524 * Running mode=standalone, port=6379.
1:M 04 Sep 2025 06:10:52.524 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:M 04 Sep 2025 06:10:52.524 # Warning: Could not create server TCP listening socket *:6379: bind: Address already in use
1:M 04 Sep 2025 06:10:52.524 # Failed listening on port 6379 (tcp), aborting.
1:C 04 Sep 2025 06:10:53.344 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1:C 04 Sep 2025 06:10:53.344 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 04 Sep 2025 06:10:53.344 * Redis version=7.4.2, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 04 Sep 2025 06:10:53.344 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
1:M 04 Sep 2025 06:10:53.345 * monotonic clock: POSIX clock_gettime
1:M 04 Sep 2025 06:10:53.348 * Running mode=standalone, port=6379.
1:M 04 Sep 2025 06:10:53.348 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:M 04 Sep 2025 06:10:53.348 # Warning: Could not create server TCP listening socket *:6379: bind: Address already in use
1:M 04 Sep 2025 06:10:53.348 # Failed listening on port 6379 (tcp), aborting.
1:C 04 Sep 2025 06:10:54.511 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1:C 04 Sep 2025 06:10:54.511 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 04 Sep 2025 06:10:54.511 * Redis version=7.4.2, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 04 Sep 2025 06:10:54.511 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
1:M 04 Sep 2025 06:10:54.512 * monotonic clock: POSIX clock_gettime
1:M 04 Sep 2025 06:10:54.515 * Running mode=standalone, port=6379.
1:M 04 Sep 2025 06:10:54.515 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:M 04 Sep 2025 06:10:54.515 # Warning: Could not create server TCP listening socket *:6379: bind: Address already in use
1:M 04 Sep 2025 06:10:54.515 # Failed listening on port 6379 (tcp), aborting.
1:C 04 Sep 2025 06:10:56.554 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1:C 04 Sep 2025 06:10:56.555 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 04 Sep 2025 06:10:56.555 * Redis version=7.4.2, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 04 Sep 2025 06:10:56.555 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
1:M 04 Sep 2025 06:10:56.555 * monotonic clock: POSIX clock_gettime
1:M 04 Sep 2025 06:10:56.559 * Running mode=standalone, port=6379.
1:M 04 Sep 2025 06:10:56.559 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:M 04 Sep 2025 06:10:56.559 # Warning: Could not create server TCP listening socket *:6379: bind: Address already in use
1:M 04 Sep 2025 06:10:56.559 # Failed listening on port 6379 (tcp), aborting.
1:C 04 Sep 2025 06:11:00.159 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1:C 04 Sep 2025 06:11:00.160 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 04 Sep 2025 06:11:00.160 * Redis version=7.4.2, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 04 Sep 2025 06:11:00.160 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
1:M 04 Sep 2025 06:11:00.160 * monotonic clock: POSIX clock_gettime
1:M 04 Sep 2025 06:11:00.163 * Running mode=standalone, port=6379.
1:M 04 Sep 2025 06:11:00.163 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:M 04 Sep 2025 06:11:00.163 # Warning: Could not create server TCP listening socket *:6379: bind: Address already in use
1:M 04 Sep 2025 06:11:00.163 # Failed listening on port 6379 (tcp), aborting.
1:C 04 Sep 2025 06:11:06.954 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1:C 04 Sep 2025 06:11:06.954 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 04 Sep 2025 06:11:06.954 * Redis version=7.4.2, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 04 Sep 2025 06:11:06.954 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
1:M 04 Sep 2025 06:11:06.955 * monotonic clock: POSIX clock_gettime
1:M 04 Sep 2025 06:11:06.958 * Running mode=standalone, port=6379.
1:M 04 Sep 2025 06:11:06.958 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:M 04 Sep 2025 06:11:06.958 # Warning: Could not create server TCP listening socket *:6379: bind: Address already in use
1:M 04 Sep 2025 06:11:06.958 # Failed listening on port 6379 (tcp), aborting.
1:C 04 Sep 2025 06:11:20.140 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1:C 04 Sep 2025 06:11:20.140 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 04 Sep 2025 06:11:20.140 * Redis version=7.4.2, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 04 Sep 2025 06:11:20.140 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
1:M 04 Sep 2025 06:11:20.141 * monotonic clock: POSIX clock_gettime
1:M 04 Sep 2025 06:11:20.143 * Running mode=standalone, port=6379.
1:M 04 Sep 2025 06:11:20.143 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:M 04 Sep 2025 06:11:20.143 # Warning: Could not create server TCP listening socket *:6379: bind: Address already in use
1:M 04 Sep 2025 06:11:20.143 # Failed listening on port 6379 (tcp), aborting.
1:C 04 Sep 2025 06:11:46.163 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1:C 04 Sep 2025 06:11:46.163 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 04 Sep 2025 06:11:46.163 * Redis version=7.4.2, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 04 Sep 2025 06:11:46.163 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
1:M 04 Sep 2025 06:11:46.164 * monotonic clock: POSIX clock_gettime
1:M 04 Sep 2025 06:11:46.167 * Running mode=standalone, port=6379.
1:M 04 Sep 2025 06:11:46.167 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:M 04 Sep 2025 06:11:46.167 # Warning: Could not create server TCP listening socket *:6379: bind: Address already in use
1:M 04 Sep 2025 06:11:46.167 # Failed listening on port 6379 (tcp), aborting.
1:C 04 Sep 2025 06:12:37.826 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1:C 04 Sep 2025 06:12:37.826 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 04 Sep 2025 06:12:37.826 * Redis version=7.4.2, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 04 Sep 2025 06:12:37.826 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
1:M 04 Sep 2025 06:12:37.827 * monotonic clock: POSIX clock_gettime
1:M 04 Sep 2025 06:12:37.831 * Running mode=standalone, port=6379.
1:M 04 Sep 2025 06:12:37.831 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:M 04 Sep 2025 06:12:37.831 # Warning: Could not create server TCP listening socket *:6379: bind: Address already in use
1:M 04 Sep 2025 06:12:37.831 # Failed listening on port 6379 (tcp), aborting.
1:C 04 Sep 2025 06:13:38.274 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1:C 04 Sep 2025 06:13:38.274 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 04 Sep 2025 06:13:38.274 * Redis version=7.4.2, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 04 Sep 2025 06:13:38.274 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
1:M 04 Sep 2025 06:13:38.275 * monotonic clock: POSIX clock_gettime
1:M 04 Sep 2025 06:13:38.277 * Running mode=standalone, port=6379.
1:M 04 Sep 2025 06:13:38.277 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:M 04 Sep 2025 06:13:38.278 # Warning: Could not create server TCP listening socket *:6379: bind: Address already in use
1:M 04 Sep 2025 06:13:38.278 # Failed listening on port 6379 (tcp), aborting.
日志中的问题如何解决
最新发布
本文解决了Redis启动时出现的两个警告：overcommit_memory设置为0可能导致背景保存失败，通过修改配置文件或直接写入sysctl参数解决；TCP backlog设置无法强制执行，通过修改somaxconn值解决。
扫一扫
6680
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
