Application plausible exited: Plausible.Application.start(:normal, []) returned an error: shutdown: failed to start child: Plausible.Session.Salts

[jonaski]

What does this mean? Is it the postgresql connection, or kickhouse?

11:56:16.643 [notice] Application plausible exited: Plausible.Application.start(:normal, []) returned an error: shutdown: failed to start child: Plausible.Session.Salts
    ** (EXIT) exited in: DBConnection.Holder.checkout(#PID<0.4256.0>, [log: #Function<13.22387797/1 in Ecto.Adapters.SQL.with_log/3>, source: "salts", cast_params: [], repo: Plausible.Repo, pool_size: 10, timeout: 300000, pool: DBConnection.ConnectionPool])
        ** (EXIT) killed
{exit,terminating,[{application_controller,call,2,[{file,"application_controller.erl"},{line,511}]},{application,enqueue_or_start,6,[{file,"application.erl"},{line,380}]},{application,ensure_all_started,3,[{file,"application.erl"},{line,359}]},{elixir,start_cli,0,[{file,"src/elixir.erl"},{line,195}]},{init,start_it,1,[]},{init,start_em,1,[]},{init,do_boot,3,[]}]}
Runtime terminating during boot (terminating)
2024-12-16T11:56:16.674818796Z

Before that, I also see this error:

11:56:16.617 [error] Failure while translating Erlang's logger event
** (MatchError) no match of right hand side value: %{label: {:gen_statem, :terminate}, name: #PID<0.4311.0>, reason: {:error, %RuntimeError{message: "connect raised CaseClauseError exception. The exception details are hidden, as they may contain sensitive data such as database credentials. You may set :show_sensitive_data_on_connection_error to true when starting your connection if you wish to see all of the details"}, [{Postgrex.Protocol, :connect, 1, [file: ~c"lib/postgrex/protocol.ex", line: 90]}, {DBConnection.Connection, :handle_event, 4, [file: ~c"lib/db_connection/connection.ex", line: 74]}, {:gen_statem, :loop_state_callback, 11, [file: ~c"gen_statem.erl", line: 3115]}, {:proc_lib, :init_p_do_apply, 3, [file: ~c"proc_lib.erl", line: 329]}]}, log: [], state: Postgrex.Protocol, queue: [internal: {:connect, :init}], modules: [DBConnection.Connection], process_label: :undefined, client_info: :undefined, callback_mode: &DBConnection.Connection.handle_event/4, postponed: [], timeouts: {0, []}, state_enter: false}
    (logger 1.17.1) lib/logger/translator.ex:306: Logger.Translator.report_gen_statem_terminate/2
    (logger 1.17.1) lib/logger/utils.ex:47: Logger.Utils.translate/5
    (logger 1.17.1) lib/logger/utils.ex:25: Logger.Utils.translator/2
    (kernel 10.0) logger_backend.erl:102: :logger_backend.do_apply_filters/4
    (kernel 10.0) logger_backend.erl:87: :logger_backend.apply_filters/4
    (kernel 10.0) logger_backend.erl:33: :logger_backend.log_allowed/3
    (stdlib 6.0) gen_statem.erl:4309: :gen_statem.terminate/7

[ruslandoga]

👋

The error means connections to PostgreSQL fail.

[jonaski]

So it's connection problem, not permission? Any idea why this setting does not work?

DATABASE_URL=postgres://vn_plausible:<retracted>@staging-<retracted>.postgres.database.azure.com:5432/staging_plausible?sslmode=require

It works when connecting manually wtih pqsql from the same pod in kubernetes:

plausible-66cb7dddc7-b22xk:/ # psql -h staging-<retracted>.postgres.database.azure.com -p 5432 -U vn_plausible staging_plausible
Password for user vn_plausible: 
psql (17.2, server 16.4)
SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384, compression: off, ALPN: none)
Type "help" for help.

staging_plausible=> 

[ruslandoga]

AFAIK psql doesn't enforce full peer verification by default so that's probably why it works.

Try using sslmode=verify-full without sslrootcert.

[jonaski]

I see no mention of DATABASE_CACERTS on https://github.com/plausible/community-edition/wiki/Configuration or anywhere in the source code

[ruslandoga]

I'm on my phone right now so not sure how to share a pinned URL but here's where it's used in the current master: https://github.com/plausible/analytics/blob/master/config/runtime.exs#L440

[jonaski]

Seems like setting both sslmode=verify-full and DATABASE_CACERTFILE worked.

[ruslandoga]

Note that sslmode=verify-full is no-op, but it works since it happens to be the default :)

In general, in the current version of CE all sslmode query string params are ignored. The only two supported params are timeout and ssl.

[jonaski]

Ok, thanks, I assume it was DATABASE_CACERTFILE that did it then.