redis ConnectionError: Error 99 connecting to redis.railway.internal:6379. Cannot assign requested address.
shxkm
HOBBYOP

21 days ago

I see many errors such as:

ConnectionError: Error 99 connecting to redis.railway.internal:6379. Cannot assign requested address.

I've some stack trace info:

canonname:

''

err:

OSError(99, 'Cannot assign requested address')

family:

<AddressFamily.AF_INET6: 10>

proto:

6

res:

["<AddressFamily.AF_INET6: 10>","<SocketKind.SOCK_STREAM: 1>","6","''",["'fd12:8a4c:4b1c:0:a000:42:a9a5:df47'","6379","0","0"]]

self:

Connection<host=redis.railway.internal,port=6379,db=0>

sock:

<socket.socket [closed] fd=-1, family=10, type=1, proto=6>

socket_address:

["'fd12:8a4c:4b1c:0:a000:42:a9a5:df47'","6379","0","0"]

socktype:

<SocketKind.SOCK_STREAM: 1>

What could be the cause of this?

$20 Bounty

4 Replies

Railway
BOT

21 days ago

This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.

Status changed to Open Railway 21 days ago


Can you share the code that connects to redis?


darseen

Can you share the code that connects to redis?

shxkm
HOBBYOP

21 days ago

It happens in a 3rd-party library called kombu which is utilized by celery


shxkm
HOBBYOP

21 days ago

My Redis URL is correctly set in env vars to: redis://default:[redacted]@redis.railway.internal:6379


shxkm
HOBBYOP

21 days ago

Investigating whether this is caused by CELERY_BROKER_POOL_LIMIT=0, which has been this way since 2018. But I keep having to change things in my app to accomodate Railway's "way of things". We'll see.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...