ccapitalK
commented
2 years ago I've encountered this issue as well, I had to bump the service startup timeout in the ansible playbooks up to 60 seconds to get it working.
Open roughnecks opened 2 years ago
ccapitalK
commented
2 years ago I've encountered this issue as well, I had to bump the service startup timeout in the ansible playbooks up to 60 seconds to get it working.
roughnecks
commented
2 years ago I've encountered this issue as well, I had to bump the service startup timeout in the ansible playbooks up to 60 seconds to get it working.
I have a similar issue with heisenbridge, fixed by using a timeout of 30 seconds; also heisenbridge's devel said it's an easy fix, but I'm not sure is the same exact issue.
moan0s
commented
2 years ago So IIUC the problem is that when using matrix-docker-ansible-deploy and use ansible-playbook -i inventory/hosts setup.yml --tags=start the bot throws the error you've shown above?
roughnecks
commented
2 years ago yep!
moan0s
commented
1 year ago So I guess what happens is:
Jonny1797
commented
9 months ago Kind of an old issue, but I'd like to add: your guess @moan0s seems to be right. I'm also using the bot with matrix-docker-ansible-deploy. At first, it threw a few times the same error as happened to @roughnecks, but after a while (probably depending on the speed of the server) - meaning several restarts / retries - it's up, running and functioning.
spantaleev
commented
8 months ago For matrix-docker-ansible-deploy, the problem is likely that the installation instructions for the service were a bit inaccurate, telling people to run the setup-all,start tags for the playbook.
However, this is not enough. Without the ensure-matrix-users-created tag, the bot's user account won't get created.
I've updated the installation instructions here. Running install-all or setup-all via just, actually invokes all the necessary tags (install-all,ensure-matrix-users-created,start or setup-all,ensure-matrix-users-created,start, respectively).
I believe with this, the bot's account will be prepared before the playbook tries to start the service.. and it would be able to then start successfully.
It works after the error, so this is happening only when restarting the Ansible playbook.