Unhandled error event: Error: read ECONNRESET at TCP.onStreamRead

[sysopsnw18]

Hi,
I am getting below error sometimes. Redis connection gets disconnected sometime. Out of 10 I am facing this issue 2 time. It takes time to reconnect the server and api response time increases from 50-80 msec to 1-2 mins.

Error : Unhandled error event: Error: read ECONNRESET at TCP.onStreamRead

Ioredis client configuration as below:
var redisMasterClient = new IORedis({
host: host ,
connectTimeout: 1000,
password: "password,
keepAlive : 1000,
retryStrategy: function(times) {
var delay = Math.min(times * 10, 2000);
return delay;
},
maxRetriesPerRequest: 1
});

Please help. This is urgent issue on production.

[mrosendin]

I am also having this issue

[wshino]

Me too. I'll watch this issue.

[slaveofcode]

Got the same problem

[ctrlaltdylan]

same issue, tried reseting the worker, deleting and recreating the redis instance but no luck

[ctrlaltdylan]

Turns out Heroku's Redis v6 instances are self-signing certificates. Passing ignoreUnauthorized to the tls options fixed the issue for me. Filing a bug report with Heroku too.

[kapalkat]

Hey, I have the same. Seems like following PR might resolve that: #1236.
The question is: when we can expect a merge?

[luin]

Sorry for the late response. This issue should be fixed in the latest version published in the last week. Closing this. Feel free to reopen if there are any issues.

[burnthoney]

Im still getting the problem and im on the latest version.

[burnthoney]

[yovanoc]

Getting the problem too

[astrolemonade]

I am getting this too

[andredezzy]

Any news for this issue, I am having the same problem.

[flyingcrp]

im getting this too
has any progress for this issue?

[luin]

Network issues can be the cause of ECONNRESET errors. It's in all probability not related to ioredis and the Redis server itself. I'd check the network first by using telnet or something similar in the same network condition of the client to see whether it works.

[flyingcrp]

i guess,ioredis's connection was broken
because i add a setInterval task that send the ping to the redis server at every 15s,now its work fine.

Network issues can be the cause of ECONNRESET errors. It's in all probability not related to ioredis and the Redis server itself. I'd check the network first by using telnet or something similar in the same network condition of the client to see whether it works.

[HowellRen]

i am getting this too,
at 6am and 6:15am every day.

[doptster]

I am getting the same error, any workaround for this?

[doptster]

I resolved my issue by using the following option

const client = new Redis(process.env.REDIS_URL, {
  tls: {
    rejectUnauthorized: false
  }
});

Can try if it helps at your side

[ntedgi]

hi @dopt do you use AWS elasticCache or self hosted redis instance?
did the problem eventually solved

[flyingcrp]

I resolved my issue by using the following option

const client = new Redis(process.env.REDIS_URL, {
  tls: {
    rejectUnauthorized: false
  }
});

Can try if it helps at your side

i dont understand whats the relationship with this attribute.
maybe use setInterval send ping to redisserver is temp solution.

finding the root cause and fixing it is the best solution

[jayantasamaddar]

The right way to do this is to handle the error gracefully. The problem seems to be the IORedis client's behaviour of timed disconnect when inactive but it has an auto reconnect mechanism that will keep trying to reconnect.

Use Node.js Event Emitter to handle it. View all events with client.eventNames() or see the references below. One can simply log out the error, reconnecting and connect events like this to understand the behaviour described above that IORedis is doing in the background. Consequently, this also handles the irritating error message. Hope this helps!

import Redis from 'ioredis';
import dotenv from 'dotenv';
import path from 'path';
dotenv.config({ path: path.resolve(__dirname, '../.env') });

const client = new Redis({
  port: Number(process.env.SESSION_STORE_PORT) || 6379,
  host: process.env.SESSION_STORE_HOSTNAME,
});

// Listen to 'error' events to the Redis connection
client.on('error', error => {
  if (error.code === 'ECONNRESET') {
    console.log('Connection to Redis Session Store timed out.');
  } else if (error.code === 'ECONNREFUSED') {
    console.log('Connection to Redis Session Store refused!');
  } else console.log(error);
});

// Listen to 'reconnecting' event to Redis
client.on('reconnecting', err => {
  if (client.status === 'reconnecting')
    console.log('Reconnecting to Redis Session Store...');
  else console.log('Error reconnecting to Redis Session Store.');
});

// Listen to the 'connect' event to Redis
client.on('connect', err => {
  if (!err) console.log('Connected to Redis Session Store!');
});

export default client;

References:

• IORedis - Connection Events
• IORedis - Options available for new Redis([port], [host], options)

[Felipeex]

Hello, you don't instance radis, when your application starts. you'll instance when you use the radis.

Exemple here:

try {
 await redis.set("test", "test")
} catch (err) {
 console.log("error", err)
} finally {
 redis.quit() // stop connection here, and init other when you need
}

[jayantasamaddar]

Hello, you don't instance radis, when your application starts. you'll instance when you use the radis.

Exemple here:

try {
 await redis.set("test", "test")
} catch (err) {
 console.log("error", err)
} finally {
 redis.quit() // stop connection here, and init other when you need
}

This is okay only when your application is having low throughput into redis. For a medium to higher throughput application, why would you want to open and close connection for every R/W operation and increase your latency per operation? In most cases, you want to keep it open and gracefully handle the error then, unless there's a security reason why you should not or if it's infrequent use.

[ShivaBhattacharjee]

Getting the same error

[PuffMeow]

There is still this error in 2024...

[thepranaygupta]

same issue, tried reseting the worker, deleting and recreating the redis instance but no luck

[babeingineer]

Tried all above solutions but not working....

[jayantasamaddar]

The right way to do this is to handle the error gracefully. The problem seems to be the IORedis client's behaviour of timed disconnect when inactive but it has an auto reconnect mechanism that will keep trying to reconnect.

Use Node.js Event Emitter to handle it. View all events with client.eventNames() or see the references below. One can simply log out the error, reconnecting and connect events like this to understand the behaviour described above that IORedis is doing in the background. Consequently, this also handles the irritating error message. Hope this helps!

import Redis from 'ioredis';
import dotenv from 'dotenv';
import path from 'path';
dotenv.config({ path: path.resolve(__dirname, '../.env') });

const client = new Redis({
  port: Number(process.env.SESSION_STORE_PORT) || 6379,
  host: process.env.SESSION_STORE_HOSTNAME,
});

// Listen to 'error' events to the Redis connection
client.on('error', error => {
  if (error.code === 'ECONNRESET') {
    console.log('Connection to Redis Session Store timed out.');
  } else if (error.code === 'ECONNREFUSED') {
    console.log('Connection to Redis Session Store refused!');
  } else console.log(error);
});

// Listen to 'reconnecting' event to Redis
client.on('reconnecting', err => {
  if (client.status === 'reconnecting')
    console.log('Reconnecting to Redis Session Store...');
  else console.log('Error reconnecting to Redis Session Store.');
});

// Listen to the 'connect' event to Redis
client.on('connect', err => {
  if (!err) console.log('Connected to Redis Session Store!');
});

export default client;

References:

• IORedis - Connection Events
• IORedis - Options available for new Redis([port], [host], options)

@babeingineer try this

[OmGarg8700]

In my case : it is not working : in development mode (http)

so using this helped,
const client = new Redis(process.env.REDIS_URL, {
tls: {
rejectUnauthorized: false
}
});

but in production : remove this

[abdulsamadayoade]

None of the solutions is working for me

[KingPuiWong]

None of the solutions is working for me

me too.