Open ralfi opened 1 week ago
After this i connect to matrix-postgres container and try to exec
psql -v ON_ERROR_STOP=1 -c ''VACUUM FULL VERBOSE ANALYZE''
it fails. What is th syntax to execute on the psql console?
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.
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...
You may have done it already, but.. rebooting the server may help reset the iptables/Docker rules and fix networking between services.
Yes, Slavi but reboot do not help in this case...
Seems to me a great tool but recognize only the fact - i know - that i cannot communicate between container in the same network
it seems to to iptables related...
@spantaleev And yes, iptables/unstable breaks docker networking. From testing it works as expected. No rants please for using unstable... ;-)
Closing
Hi all,
after just update for all and try to setup the play the task above runs in a timeout - i think so...
...because matrix-postgres is up and port is open.
If i try
just run-tags run-postgres-vacuum
it crashes withAny hints?