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

Errors and warnings in docker logs #58

Open
slifty opened this issue Jan 10, 2023 · 0 comments
Open

Errors and warnings in docker logs #58

slifty opened this issue Jan 10, 2023 · 0 comments

Comments

@slifty
Copy link
Contributor

slifty commented Jan 10, 2023

After running docker-compose up I'm seeing errors in the logs related to the health check:

database_1        | 2023-01-10 16:26:27.329 UTC [2052] FATAL:  role "root" does not exist

stela_1           | 1/10/2023, 4:26:51?PM error: Error connecting to database: connect ECONNREFUSED 127.0.0.1:5432 {"name":"TinyPgError","queryContext":{"id":"34b52cb1-6673-4978-9bda-6cf0eb7b8b29","sql":"SELECT VERSION();\n","start":1673368011170,"name":"health_queries_ping","wait_duration":1,"active_duration":0,"end":1673368011171,"duration":1,"error":{"errno":-111,"code":"ECONNREFUSED","syscall":"connect","address":"127.0.0.1","port":5432},"data":null}}

stela_1           | [health_queries_ping]

stela_1           | 

stela_1           | SELECT VERSION();

stela_1           | 

stela_1           | 

stela_1           | Error: connect ECONNREFUSED 127.0.0.1:5432

stela_1           |     at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1487:16)

stela_1           | 1/10/2023, 4:26:51?PM http: HTTP GET /api/v2/health {"meta":{"req":{"url":"/api/v2/health","headers":{"host":"localhost:8080","user-agent":"curl/7.87.0","accept":"*/*"},"method":"GET","httpVersion":"1.1","originalUrl":"/api/v2/health","query":{}},"res":{"statusCode":200},"responseTime":2}}

database_1        | 2023-01-10 16:26:57.423 UTC [2061] FATAL:  role "root" does not exist

These don't appear to result in any broken functionality but it would be good to resolve (at the very least they reflect a red herring when attempting to debug other issues)

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

No branches or pull requests

1 participant