Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

failed to create connection for pool [error: connection reset (error set): No route to host (errno: 113) #48

Open
nsankur opened this issue May 20, 2021 · 3 comments
Labels

Comments

@nsankur
Copy link

nsankur commented May 20, 2021

We are seeing below error.


postgresql_1  | PostgreSQL Database directory appears to contain a database; Skipping initialization
postgresql_1  | 
postgresql_1  | 2021-05-20 17:51:24.211 UTC [1] LOG:  starting PostgreSQL 13.3 (Debian 13.3-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
redis_1       | 1:C 20 May 2021 17:51:24.191 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1       | 1:C 20 May 2021 17:51:24.191 # Redis version=6.2.3, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1       | 1:C 20 May 2021 17:51:24.191 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
xcmetrics_1   | [ NOTICE ] Connecting to xcmetrics-dev in ****** as xcmetrics-dev password length 13
xcmetrics_1   | [ INFO ] Using redis host ******* and port 6379
redis_1       | 1:M 20 May 2021 17:51:24.192 * monotonic clock: POSIX clock_gettime
postgresql_1  | 2021-05-20 17:51:24.214 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
redis_1       | 1:M 20 May 2021 17:51:24.195 # Warning: Could not create server TCP listening socket ::*:6379: unable to bind socket, errno: 97
redis_1       | 1:M 20 May 2021 17:51:24.195 * Running mode=standalone, port=6379.
redis_1       | 1:M 20 May 2021 17:51:24.196 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
redis_1       | 1:M 20 May 2021 17:51:24.196 # Server initialized
redis_1       | 1:M 20 May 2021 17:51:24.196 * Ready to accept connections
postgresql_1  | 2021-05-20 17:51:24.216 UTC [1] LOG:  could not create IPv6 socket for address "::": Address family not supported by protocol
postgresql_1  | 2021-05-20 17:51:24.222 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgresql_1  | 2021-05-20 17:51:24.233 UTC [25] LOG:  database system was shut down at 2021-05-20 17:42:18 UTC
postgresql_1  | 2021-05-20 17:51:24.240 UTC [1] LOG:  database system is ready to accept connections
postgresql_1  | 2021-05-20 17:51:34.222 UTC [38] FATAL:  role "xcmetricsdb" does not exist
postgresql_1  | 2021-05-20 17:51:44.371 UTC [45] FATAL:  role "xcmetricsdb" does not exist
postgresql_1  | 2021-05-20 17:51:54.518 UTC [53] FATAL:  role "xcmetricsdb" does not exist
xcmetrics_1   | [ ERROR ] failed to create connection for pool [error: connection reset (error set): No route to host (errno: 113), rdstk_conpool_id: 49365023-7B19-4F38-B99E-BF9F35C3DC3E]
xcmetrics_1   | [ ERROR ] failed to create connection for pool [error: connection reset (error set): No route to host (errno: 113), rdstk_conpool_id: 49365023-7B19-4F38-B99E-BF9F35C3DC3E]
xcmetrics_1   | [ ERROR ] Job run failed: RedisConnectionPoolError(baseError: RediStack.RedisConnectionPoolError.BaseError.timedOutWaitingForConnection)

@polac24 polac24 added the backend label Oct 7, 2021
@rprisram
Copy link

Hi @nsankur , Did you happen to find a workaround for the above issue?

@ptsiogas
Copy link

ptsiogas commented Dec 8, 2021

Hi, I have the same problem. Do you have any workaround?

@jkmathew
Copy link
Contributor

I am also seeing similar logs, does anyone find a reason/solution for this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants