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
failed: [matrix.domain.com] (item=matrix-beeper-linkedin.service) => changed=false
ansible_loop_var: item
item: matrix-beeper-linkedin.service
msg: matrix-beeper-linkedin.service was not detected to be running. It's possible that there's a configuration problem or another service on your server interferes with it (uses the same ports, etc.). Try running systemctl status matrix-beeper-linkedin.service and journalctl -fu matrix-beeper-linkedin.service on the server to investigate. If you're on a slow or overloaded server, it may be that services take a longer time to start and that this error is a false-positive. You can consider raising the value of the matrix_common_after_systemd_service_start_wait_for_timeout_seconds variable. See roles/matrix-common-after/defaults/main.yml for more details about that.
The text was updated successfully, but these errors were encountered:
No support for arm64 as of now.
Edit: There is support for self-building now: dcab14d
Solution: Update and re-run the playbook and Beeper Linkedin should start working.
HarHarLinks
pushed a commit
to HarHarLinks/matrix-docker-ansible-deploy
that referenced
this issue
Feb 16, 2022
failed: [matrix.domain.com] (item=matrix-beeper-linkedin.service) => changed=false
ansible_loop_var: item
item: matrix-beeper-linkedin.service
msg: matrix-beeper-linkedin.service was not detected to be running. It's possible that there's a configuration problem or another service on your server interferes with it (uses the same ports, etc.). Try running
systemctl status matrix-beeper-linkedin.service
andjournalctl -fu matrix-beeper-linkedin.service
on the server to investigate. If you're on a slow or overloaded server, it may be that services take a longer time to start and that this error is a false-positive. You can consider raising the value of thematrix_common_after_systemd_service_start_wait_for_timeout_seconds
variable. Seeroles/matrix-common-after/defaults/main.yml
for more details about that.The text was updated successfully, but these errors were encountered: