Postgresql is dead after migration

Hardware: VPS bought online ( Contabo )
YunoHost version: 11.0.9.14 (stable)
I have access to my server : Through SSH and browser
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no

one of the errors that’s coming up non-stop after the migration is service postgresql being dead.

i try to follow the troubleshooting directions given by the diagnosis, but the issue is still there.

$ sudo yunohost service restart postgresql
/bin/systemd-tty-ask-password-agent: error while loading shared libraries: /lib/systemd/libsystemd-shared-247.so: invalid ELF header
Success! Service 'postgresql' restarted
$ sudo yunohost service log postgresql
/var/log/postgresql/postgresql-13-main.log: 
  - 2022-09-19 23:15:47.343 CEST [1748] matrix_synapse@matrix_synapse FATAL:  terminating connection due to administrator command
  - 2022-09-19 23:15:47.345 CEST [1741] matrix_synapse@matrix_synapse FATAL:  terminating connection due to administrator command
  - 2022-09-19 23:15:47.348 CEST [1744] matrix_synapse@matrix_synapse FATAL:  terminating connection due to administrator command
  - 2022-09-19 23:15:47.349 CEST [1749] matrix_synapse@matrix_synapse FATAL:  terminating connection due to administrator command
  - 2022-09-19 23:15:47.355 CEST [1017] LOG:  shutting down
  - 2022-09-19 23:15:47.476 CEST [911] LOG:  database system is shut down
  - 2022-09-19 23:15:47.786 CEST [9740] LOG:  starting PostgreSQL 13.8 (Debian 13.8-0+deb11u1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
  - 2022-09-19 23:15:47.787 CEST [9740] LOG:  listening on IPv6 address "::1", port 5432
  - 2022-09-19 23:15:47.787 CEST [9740] LOG:  listening on IPv4 address "127.0.0.1", port 5432
  - 2022-09-19 23:15:47.788 CEST [9740] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
  - 2022-09-19 23:15:47.827 CEST [9741] LOG:  database system was shut down at 2022-09-19 23:15:47 CEST
  - 2022-09-19 23:15:47.914 CEST [9740] LOG:  database system is ready to accept connections
  - 2022-09-21 01:12:32.921 CEST [9740] LOG:  received fast shutdown request
  - 2022-09-21 01:12:32.992 CEST [9740] LOG:  aborting any active transactions
  - 2022-09-21 01:12:32.997 CEST [9740] LOG:  background worker "logical replication launcher" (PID 9747) exited with exit code 1
  - 2022-09-21 01:12:33.015 CEST [28102] matrix_synapse@matrix_synapse FATAL:  terminating connection due to administrator command
  - 2022-09-21 01:12:33.017 CEST [9767] matrix_synapse@matrix_synapse FATAL:  terminating connection due to administrator command
  - 2022-09-21 01:12:33.019 CEST [9764] matrix_synapse@matrix_synapse FATAL:  terminating connection due to administrator command
  - 2022-09-21 01:12:33.020 CEST [9759] matrix_synapse@matrix_synapse FATAL:  terminating connection due to administrator command
  - 2022-09-21 01:12:33.021 CEST [9765] matrix_synapse@matrix_synapse FATAL:  terminating connection due to administrator command
  - 2022-09-21 01:12:33.025 CEST [10221] gotosocial@gotosocial FATAL:  terminating connection due to administrator command
  - 2022-09-21 01:12:33.025 CEST [9766] matrix_synapse@matrix_synapse FATAL:  terminating connection due to administrator command
  - 2022-09-21 01:12:33.028 CEST [9786] gotosocial@gotosocial FATAL:  terminating connection due to administrator command
  - 2022-09-21 01:12:33.029 CEST [10220] gotosocial@gotosocial FATAL:  terminating connection due to administrator command
  - 2022-09-21 01:12:33.052 CEST [9742] LOG:  shutting down
  - 2022-09-21 01:12:33.200 CEST [9740] LOG:  database system is shut down
  - 2022-09-21 01:12:33.602 CEST [33866] LOG:  starting PostgreSQL 13.8 (Debian 13.8-0+deb11u1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
  - 2022-09-21 01:12:33.603 CEST [33866] LOG:  listening on IPv6 address "::1", port 5432
  - 2022-09-21 01:12:33.603 CEST [33866] LOG:  listening on IPv4 address "127.0.0.1", port 5432
  - 2022-09-21 01:12:33.626 CEST [33866] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
  - 2022-09-21 01:12:33.689 CEST [33867] LOG:  database system was shut down at 2022-09-21 01:12:33 CEST
  - 2022-09-21 01:12:33.760 CEST [33866] LOG:  database system is ready to accept connections
  - 2022-09-21 01:16:11.640 CEST [33866] LOG:  received fast shutdown request
  - 2022-09-21 01:16:11.654 CEST [33866] LOG:  aborting any active transactions
  - 2022-09-21 01:16:11.654 CEST [33925] gotosocial@gotosocial FATAL:  terminating connection due to administrator command
  - 2022-09-21 01:16:11.654 CEST [33891] matrix_synapse@matrix_synapse FATAL:  terminating connection due to administrator command
  - 2022-09-21 01:16:11.655 CEST [33892] matrix_synapse@matrix_synapse FATAL:  terminating connection due to administrator command
  - 2022-09-21 01:16:11.657 CEST [33889] matrix_synapse@matrix_synapse FATAL:  terminating connection due to administrator command
  - 2022-09-21 01:16:11.659 CEST [33888] matrix_synapse@matrix_synapse FATAL:  terminating connection due to administrator command
  - 2022-09-21 01:16:11.659 CEST [33886] matrix_synapse@matrix_synapse FATAL:  terminating connection due to administrator command
  - 2022-09-21 01:16:11.660 CEST [33866] LOG:  background worker "logical replication launcher" (PID 33873) exited with exit code 1
  - 2022-09-21 01:16:11.661 CEST [33890] matrix_synapse@matrix_synapse FATAL:  terminating connection due to administrator command
  - 2022-09-21 01:16:11.667 CEST [33868] LOG:  shutting down
  - 2022-09-21 01:16:12.153 CEST [33866] LOG:  database system is shut down
  - 2022-09-21 01:16:12.428 CEST [33952] LOG:  starting PostgreSQL 13.8 (Debian 13.8-0+deb11u1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
  - 2022-09-21 01:16:12.429 CEST [33952] LOG:  listening on IPv6 address "::1", port 5432
  - 2022-09-21 01:16:12.429 CEST [33952] LOG:  listening on IPv4 address "127.0.0.1", port 5432
  - 2022-09-21 01:16:12.430 CEST [33952] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
  - 2022-09-21 01:16:12.524 CEST [33953] LOG:  database system was shut down at 2022-09-21 01:16:12 CEST
  - 2022-09-21 01:16:12.558 CEST [33952] LOG:  database system is ready to accept connections
journalctl: 
  - error while get services logs from journalctl:
  - Traceback (most recent call last):
  -   File "/usr/lib/python3/dist-packages/yunohost/service.py", line 849, in _get_journalctl_logs
  -     return check_output(
  -   File "/usr/lib/python3/dist-packages/moulinette/utils/process.py", line 29, in check_output
  -     subprocess.check_output(args, stderr=stderr, shell=shell, **kwargs)
  -   File "/usr/lib/python3.9/subprocess.py", line 424, in check_output
  -     return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  -   File "/usr/lib/python3.9/subprocess.py", line 528, in run
  -     raise CalledProcessError(retcode, process.args,
  - subprocess.CalledProcessError: Command 'journalctl --no-hostname --no-pager -u postgresql@11-main -n50' returned non-zero exit status 127.

anyone can help?

well, there is also another problem that popped up after the migration:

Configuration file /usr/share/yunohost/yunohost-config/ssl/yunoCA/openssl.cnf appears to have been manually modified.

tbf, i dont think ive personally modified this file, not even sure what it is.

but then this came up when i checked

sudo yunohost tools regen-conf ssl --dry-run --with-diff
Success! The configuration would have been updated for category 'ssl'
ssl: 
  applied: 
    /usr/share/yunohost/yunohost-config/ssl/yunoCA/openssl.cnf: 
      diff: 
      status: forget-about-it
  pending:

so, lol? is that a message from the developers?
or is something actually going on?

i still have the original issue of the post unresolved btw. :sweat_smile:

Ah yeah that’s definitely confusing :stuck_out_tongue:

I think you can manually

sudo rm /usr/share/yunohost/yunohost-config/ssl/yunoCA/openssl.cnf

or maybe the file got deleted already ? Do you still get the same message when re-running the command ?

oh, i solved that, should’ve updated the thread i guess. :sweat_smile:

im still having problem with postgresql though. :face_holding_back_tears: