You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The matrix-synapse-reverse-proxy-companion role fails its uninstallation task if you have previously installed Synapse on your server, and decide to change to Conduit or Dendrite
A workaround i'm currently using is to delete matrix-synapse-reverse-proxy-companion.service manually in /etc/systemd/system/ before I run just setup-all for setting up Conduit/Dendrite, but my understanding is that the matrix-synapse-reverse-proxy-companion uninstallation task should take care of removing itself from the service directory.
To Reproduce
Starting from the default vars.yml example file with updates to default entries + adding ansible_ssh_private_key_file. Ensure that matrix_homeserver_implementation is Synapse and that workers are enabled so that the matrix-synapse-reverse-proxy-companion service is created.
If not ran yet: just roles
just setup-all
just start-all
just stop-all
Change in vars.yml the field matrix_homeserver_implementation to conduit or dendrite
just setup-all
The error output after running the last command:
TASK [custom/matrix-synapse-reverse-proxy-companion : Ensure matrix-synapse-reverse-proxy-companion.service is stopped] *****
task path: /matrix_test2/roles/custom/matrix-synapse-reverse-proxy-companion/tasks/setup_uninstall.yml:10
...
fatal: [<SERVER>]: FAILED! => changed=false
invocation:
module_args:
daemon_reexec: false
daemon_reload: true
enabled: false
force: null
masked: null
name: matrix_synapse_reverse_proxy_companion_service_stat
no_block: false
scope: system
state: stopped
msg: 'Could not find the requested service matrix_synapse_reverse_proxy_companion_service_stat: host'
Error Cause
If the service matrix-synapse-reverse-proxy-companion.service still exists in /etc/systemd/system/, then this error will happen. As mentioned earlier, if you remove this file manually before running just setup-all, then this task will pass.
Matrix Server:
OS: Rocky Linux RockyLinux 8.6 x64
Architecture: amd64
Ansible:
where you run Ansible: On the Matrix server, standard installation
Describe the bug
The
matrix-synapse-reverse-proxy-companion
role fails its uninstallation task if you have previously installed Synapse on your server, and decide to change to Conduit or DendriteA workaround i'm currently using is to delete
matrix-synapse-reverse-proxy-companion.service
manually in/etc/systemd/system/
before I runjust setup-all
for setting up Conduit/Dendrite, but my understanding is that thematrix-synapse-reverse-proxy-companion
uninstallation task should take care of removing itself from the service directory.To Reproduce
Starting from the default
vars.yml
example file with updates to default entries + addingansible_ssh_private_key_file
. Ensure thatmatrix_homeserver_implementation
is Synapse and that workers are enabled so that thematrix-synapse-reverse-proxy-companion
service is created.just roles
just setup-all
just start-all
just stop-all
vars.yml
the fieldmatrix_homeserver_implementation
toconduit
ordendrite
just setup-all
The error output after running the last command:
Error Cause
If the service
matrix-synapse-reverse-proxy-companion.service
still exists in/etc/systemd/system/
, then this error will happen. As mentioned earlier, if you remove this file manually before runningjust setup-all
, then this task will pass.Matrix Server:
Ansible:
The text was updated successfully, but these errors were encountered: