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

Task "Execute Postgres managed database initialization SQL file for synapse" crashes my matrix server #3769

Open
ralfi opened this issue Nov 14, 2024 · 8 comments
Labels
needs-info This issue is blocked awaiting information from the reporter question This issue is a question related to installation

Comments

@ralfi
Copy link

ralfi commented Nov 14, 2024

Hi all,

after just update for all and try to setup the play the task above runs in a timeout - i think so...

Anmerkung 2024-11-14 074350

...because matrix-postgres is up and port is open.

If i try just run-tags run-postgres-vacuum it crashes with

Anmerkung 2024-11-14 075554

Any hints?

@ralfi ralfi added the bug label Nov 14, 2024
@ralfi
Copy link
Author

ralfi commented Nov 14, 2024

After this i connect to matrix-postgres container and try to exec

psql -v ON_ERROR_STOP=1 -c ''VACUUM FULL VERBOSE ANALYZE''

image

it fails. What is th syntax to execute on the psql console?

@spantaleev
Copy link
Owner

Your first ANALYZE; is executed successfully.

Your second ANALYZE is not terminated with ;, so.. psql is waiting for more input.

You're appending VACUUM VERBOSE; to it, so it becomes ANALYZE VACUUM VERBOSE; which is incorrect.


Something odd is going on.. It seems like Postgres is up now, so maybe it was slow the first time around?

If you try install-all once again (now that Postgres is known to be up), does it work?


Checking the status of the Postgres service (systemctl status matrix-postgres.service) and its logs (journalctl -fu matrix-postgres.service) may be helpful.

@spantaleev spantaleev added question This issue is a question related to installation needs-info This issue is blocked awaiting information from the reporter and removed bug labels Nov 14, 2024
@ralfi
Copy link
Author

ralfi commented Nov 14, 2024

Thanks a lot but it seem a big problem with networking connectivity after debians d-u yesterday. Many curious network problem, f.i. cannot connect to containers in the same network and so on. Really frustraded...

Same of two independent docker server with kernel 6.10.12 an docker.io 26.1.5. But it seemsn to be more debian network related and not docker...

@spantaleev
Copy link
Owner

You may have done it already, but.. rebooting the server may help reset the iptables/Docker rules and fix networking between services.

@ralfi
Copy link
Author

ralfi commented Nov 14, 2024

Yes, Slavi but reboot do not help in this case...

@ralfi
Copy link
Author

ralfi commented Nov 14, 2024

image

Seems to me a great tool but recognize only the fact - i know - that i cannot communicate between container in the same network

@ralfi
Copy link
Author

ralfi commented Nov 14, 2024

it seems to to iptables related...

@ralfi
Copy link
Author

ralfi commented Nov 15, 2024

@spantaleev And yes, iptables/unstable breaks docker networking. From testing it works as expected. No rants please for using unstable... ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-info This issue is blocked awaiting information from the reporter question This issue is a question related to installation
Projects
None yet
Development

No branches or pull requests

2 participants