Sickde
Sickde
PostsComments
RRailway
Created by Sickde on 6/3/2023 in #✋｜help
Setting up Redis
What am I doing wrong? 
My Redis server  
1:C 03 Jun 2023 17:14:32.011 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 03 Jun 2023 17:14:32.011 # Redis version=6.2.12, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 03 Jun 2023 17:14:32.011 # Configuration loaded
1:M 03 Jun 2023 17:14:32.012 * monotonic clock: POSIX clock_gettime
1:M 03 Jun 2023 17:14:32.013 * Running mode=standalone, port=6379.
1:M 03 Jun 2023 17:14:32.013 # 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 03 Jun 2023 17:14:32.013 # Server initialized
1:M 03 Jun 2023 17:14:32.013 # 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 03 Jun 2023 17:14:32.014 * DB loaded from append only file: 0.000 seconds
1:M 03 Jun 2023 17:14:32.014 * Ready to accept connections
My Redis server  
1:C 03 Jun 2023 17:14:32.011 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 03 Jun 2023 17:14:32.011 # Redis version=6.2.12, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 03 Jun 2023 17:14:32.011 # Configuration loaded
1:M 03 Jun 2023 17:14:32.012 * monotonic clock: POSIX clock_gettime
1:M 03 Jun 2023 17:14:32.013 * Running mode=standalone, port=6379.
1:M 03 Jun 2023 17:14:32.013 # 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 03 Jun 2023 17:14:32.013 # Server initialized
1:M 03 Jun 2023 17:14:32.013 # 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 03 Jun 2023 17:14:32.014 * DB loaded from append only file: 0.000 seconds
1:M 03 Jun 2023 17:14:32.014 * Ready to accept connections
And on my Backend server 
[ioredis] Unhandled error event: Error: connect ECONNREFUSED 127.0.0.1:6379
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
[ioredis] Unhandled error event: Error: connect ECONNREFUSED 127.0.0.1:6379
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
41 replies