Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- 1:signal-handler (1726683793) Received SIGTERM scheduling shutdown...
- 1:M 18 Sep 2024 18:23:13.337 # User requested shutdown...
- 1:M 18 Sep 2024 18:23:13.337 * Saving the final RDB snapshot before exiting.
- 1:M 18 Sep 2024 18:23:13.355 * DB saved on disk
- 1:M 18 Sep 2024 18:23:13.355 # Redis is now ready to exit, bye bye...
- 1:C 18 Sep 2024 18:23:13.893 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
- 1:C 18 Sep 2024 18:23:13.893 # Redis version=6.2.14, bits=64, commit=00000000, modified=0, pid=1, just started
- 1:C 18 Sep 2024 18:23:13.893 # 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 18 Sep 2024 18:23:13.893 * monotonic clock: POSIX clock_gettime
- 1:M 18 Sep 2024 18:23:13.894 * Running mode=standalone, port=6379.
- 1:M 18 Sep 2024 18:23:13.894 # 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 18 Sep 2024 18:23:13.894 # Server initialized
- 1:M 18 Sep 2024 18:23:13.894 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can 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:M 18 Sep 2024 18:23:13.894 * Loading RDB produced by version 6.2.14
- 1:M 18 Sep 2024 18:23:13.894 * RDB age 0 seconds
- 1:M 18 Sep 2024 18:23:13.894 * RDB memory usage when created 4.35 Mb
- 1:M 18 Sep 2024 18:23:13.903 # Done loading RDB, keys loaded: 34, keys expired: 0.
- 1:M 18 Sep 2024 18:23:13.903 * DB loaded from disk: 0.009 seconds
- 1:M 18 Sep 2024 18:23:13.903 * Ready to accept connections
Advertisement
Add Comment
Please, Sign In to add comment