Having issue when setup app with postgre

[sebastienbourda]

Hey !

I'm facing an issue during kamal setup :

ERROR bin/rails aborted!
ActiveRecord::ConnectionNotEstablished: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory (ActiveRecord::ConnectionNotEstablished)
        Is the server running locally and accepting connections on that socket?


Caused by:
PG::ConnectionBad: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory (PG::ConnectionBad)
        Is the server running locally and accepting connections on that socket?

Tasks: TOP => db:prepare
(See full trace by running task with --trace)
 ERROR {
  "Status": "unhealthy",
  "FailingStreak": 1,
  "Log": [
    {
      "Start": "2024-03-20T10:31:31.886555891Z",
      "End": "2024-03-20T10:31:32.100354475Z",
      "ExitCode": 1,
      "Output": "  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current\n                                 Dload  Upload   Total   Spent    Left  Speed\n\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0\ncurl: (7) Failed to connect to localhost port 3000 after 12 ms: Couldn't connect to server\n"
    }
  ]
}
  INFO [fc7276b3] Running docker container ls --all --filter name=^healthcheck-sebastien-blog-b07371a23ca8b04227f23bb385d8976f89e3fc06_uncommitted_997c8b914435f337$ --quiet | xargs docker stop on 37.27.12.29
  INFO [fc7276b3] Finished in 0.276 seconds with exit status 0 (successful).
  INFO [51e30fc0] Running docker container ls --all --filter name=^healthcheck-sebastien-blog-b07371a23ca8b04227f23bb385d8976f89e3fc06_uncommitted_997c8b914435f337$ --quiet | xargs docker container rm on 37.27.12.29
  INFO [51e30fc0] Finished in 0.271 seconds with exit status 0 (successful).
  Finished all in 74.2 seconds
Releasing the deploy lock...
  Finished all in 93.6 seconds
  ERROR (Kamal::Cli::Healthcheck::Poller::HealthcheckError): Exception while executing on host 37.27.12.29: container not ready (unhealthy)

here my deploy.yml :

  # Name of your application. Used to uniquely configure containers.
service: sebastien-blog

# Name of the container image.
image: se2b/sebastien-blog

# Deploy to these servers.
servers:
  - 37.27.12.29

# Credentials for your image host.
registry:
  # Specify the registry server, if you're not using Docker Hub
  # server: registry.digitalocean.com / ghcr.io / ...
  username: se2b

  # Always use an access token rather than real password when possible.
  password:
    - KAMAL_REGISTRY_PASSWORD

# Inject ENV variables into containers (secrets come from .env).
# Remember to run `kamal env push` after making changes!
env:
  clear:
    DB_HOST: 37.27.12.29
    RAILS_SERVE_STATIC_FILES: true
  secret:
    - RAILS_MASTER_KEY
    - POSTGRES_PASSWORD
volumes:
  - storage:/rails/storage

# Use accessory services (secrets come from .env).
accessories:
  db:
    image: postgres:16
    host: 37.27.12.29
    port: 5432
    env:
      clear:
        POSTGRES_USER: "blog"
        POSTGRES_DB: "blog_production" # The database will be created automatically on first boot.
      secret:
        - POSTGRES_PASSWORD
    directories:
      - data:/var/lib/postgresql/data

[fredrikburmester]

I have the same issue!

[sebastienbourda]

I resolved it by uninstall postgres and install again.
Brew commands not working so i did it manually by removing folder of each postgres version.
On my mac, in /usr/local/var/
then i did brew install postgres and it solved it.

[rikas]

So this error is happening locally? I have the same issue but I thought it was due to an error in the server... I'm very confused.

[sebastienbourda]

I've had the issue both in local and production. I have resolved it by clean install of postgre in local and by removing postmaster.pid file in production.
I wrote an article to remember this issue.
https://sebastienbourda.com/posts/fix-error-port-5432-postgreSQL-rails-app-kamal-deploy

Hope it will help you.

[fredrikburmester]

I solved this by setting the DATABASE_URL to the actual connection string:

postgresql://postgres:[email protected]:5000/production

Note the use of the local IP address of the server and the port defined in the Postgres accessory

[rikas]

Yeah I figured it out, using url instead of a unix socket connection solved the issue in production.

[sebscholl]

How would this get solved for production by making a local change?