ConnectionTimeoutError: Connection timeout

[younes-io]

I get this error and I don't understand why:

How do I get more details about this:

/mnt/c/dev/client-adapter/node_modules/redis/dist/lib/socket.js:157
            socket.setTimeout(__classPrivateFieldGet(this, _RedisSocket_options, "f").connectTimeout, () => socket.destroy(new errors_1.ConnectionTimeoutError()));
                                                                                                                           ^
ConnectionTimeoutError: Connection timeout
    at Socket.<anonymous> (/mnt/c/dev/client-adapter/node_modules/redis/dist/lib/socket.js:157:124)
    at Object.onceWrapper (node:events:513:28)
    at Socket.emit (node:events:394:28)
    at Socket.emit (node:domain:475:12)
    at Socket._onTimeout (node:net:486:8)
    at listOnTimeout (node:internal/timers:557:17)
    at processTimers (node:internal/timers:500:7)
[nodemon] app crashed - waiting for file changes before starting...

---

Environment

─❯ node -v 
v16.6.2

─❯ redis-server -v 
Redis server v=5.0.7 sha=00000000:0 malloc=jemalloc-5.2.1 bits=64 build=636cde3b5c7a3923

─❯ lsb_release -a   
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.3 LTS
Release:        20.04
Codename:       focal

[leibale]

Can you please share the configuration you send to createClient (without the server, username, and password)?

[leibale]

@younes-io?

[younes-io]

Sorry @leibale for the late response.

Actually, I did just as mentioned in the docs:

createClient({
  url: 'redis://alice:foobared@awesome.redis.server:6380',
});

I realized that the error is thrown in these cases:

• Using redis without TLS (my Redis connection uses TLS)
• Using the user default or when omitting the user:

createClient({
  url: 'rediss://:foobared@awesome.redis.server:6380',
});

[eladitzhakian]

I'm having the same problem.

Using node-redis 4.0.0
Redis server image v4-alpine
Connects just fine with redis-cli but getting ConnectionTimeout using node-redis
This is how I connect:

createClient({ url: 'redis://localhost:6379' })

[leibale]

@eladitzhakian

docker run -it -p 6379:6379 redis:4-alpine

import { createClient } from 'redis';

const client = createClient({ url: 'redis://localhost:6379' });

await client.connect();
await client.ping();
await client.disconnect();

works for me (the classic answer :P)... wanna debug it together?

[romulovalez]

I reproduced this issue in two different projects, but I find it difficult to reproduce it on a basic server, If you want we can debug it together 👍

[Chocobozzz]

Hello,

We had this issue on our project. The root cause is that we try to .connect(), and then require many node modules blocking the node loop with sync calls. The socket is blocked and the timeout is thrown. I suggest you to profile your applications to find if it's the same kind of error.

[a1003584293]

Hello,

We had this issue on our project. The root cause is that we try to .connect(), and then require many node modules blocking the node loop with sync calls. The socket is blocked and the timeout is thrown. I suggest you to profile your applications to find if it's the same kind of error.

you are right, Should not be used .connect when using createcluster api

[Raraku]

Hi so, what's the fix?

[aarhusgregersen]

I am facing the same issue as a result of upgrading from v3 to v4. Everything is working just fine, so I am little confused as to why I'm seeing the error.

@Chocobozzz how did you find out about this? And I am also a bit perplexed by the node loop being blocked with sync calls. I mean, how do you know which requires are sync, and which aren't?
This does not necessarily seem to correlate directly to sync/async code, in the classical async/await sense.

[Chocobozzz]

@aarhusgregersen All requires are sync. You can profile your application using chrome about:inspect and nodejs --inspect-brk option