ERROR: [dn3]: SSL connection has been closed unexpectedly

Question

I have been working on the timescaleDB multinode clustering concept. When I go to add a data node, I run the add_data_node query in the access node at that time I got an error like SSL Connection has been closed unexpectedly

Config in the access node

postgresql.conf

listen_addresses = '*'
enable_partitionwise_aggregate = on
jit = off

Config in Data Node

Postgresql.conf

listen_addresses = '*'
max_prepared_transactions = 150
wal_level = logical

If you know the root cause of the problem let me know

Answer 1

While running the add_data_node query, the connection will be made. if any unexpected error will be thrown from the data_node service. it throws the error with the SSL connection has been closed unexpectedly.

To check the PostgreSQL database error log we need to enable two of the configurations.

log_connections = on
log_disconnections = on

Through the log what I have found is, in the postgresql.conf file, 'shared_preload_libraries' was with the empty string. I want to add the string 'timescaldb' for that variable (shared_preload_libraries).

I will not recommend this enabling log for production.

https://www.digitalocean.com/community/questions/how-can-i-investigate-postgres-managed-server-error-ssl-connection-has-been-closed-unexpectedly