Getting stuck at "INFO - Login via password" #1
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: bobmaster/matrix-stt-bot#1
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi! Thanks for providing this repo. Very cool idea that I would like to experiment with for deaf people.
I am using the Yunohost package synapse_ynh. I followed the instructions and edited the config.json according to my server dates. Unfortunately when starting the the docker image with
sudo docker compose up
this is the output (won't change in 1 hour):I restarted the system and double checked the login credentials. Using Cinny I can login just fine.
This is my current config.json
Any idea? How can I get more verbose logging on why the login doesn't work?
Hi, I just tested it without problem, It seems you stuck at model downloading step? Can you provide your working directory screenshot for me?
If you have downloaded model before, you can start to use the bot when getting
INFO - Login via password
.Besides, you can try without importing e2ee keys, here is my test configuration.
config.json
compose.yaml
Some errors can be ignored if you are not using E2EE room.
Hi! Thanks for the quick reply.
Model download worked just fine i think. I used "medium" and the model could be found in the dir. I tested again now with
"model_size": "base"
and without E2EE. So my config and compose are identical to yours (except of URL and credentials of course). This is the log:Here it gets stuck again. When going to the channel there is no response and it is saying that the bot is offline...
This is my working dir:
I also added some more logs to the code and can now be sure that it gets stuck in line 484 (
resp = await self.client.login(password=self.password)
). It never enters the followingif not isinstance(resp, LoginResponse):
Any idea? Could it be a whitelisting problem or so? Bot and Matrix are on the same machine, should not be a problem I think..
room_id correct? Try remove it.
already tried without room_id yes :( like so:
I just update dependencies, can you pull the latest image and try again?
unfortunately I am still stuck at "INFO - Login via password"
I wonder how I could debug the login process further. I already double checked the credentials... If an connection from my local computer is possible it should be also possible from the same machine( the server) ...
Try using a new device id, such as
FMIAZSVFF
. Besides, you can debug the code easily if you have python environment.f20b1d5d40/bot.py (L454-L468)
or mount
bot.py
in container.Ok cool, got it working at least with the bot.py script (without docker):
I ran into issues with the dependencies first and then had to
sudo chown -R admin:1007 *
in the repo folder because the/model/
dir had root:root rights only and so I couldn't run bot.py withoutsudo
.After doing so I could run
python bot.py
and I could sucessfully transcribe messages.sudo docker compose up
however still doesn't work. Changing device_id had no effect.logger.info("Login Success")
never gets called (as said before) it blocks atresp = await self.client.login(password=self.password)
I am not so experienced in docker. Maybe I need to do some network settings or so?
That's so weird. Can you provide your compose file and docker version?
you mean the compose.yaml? Just like yours:
And the docker version:
Docker version 24.0.4, build 3713ee1
This is my folder now, after the
chown
thing:thanks for your patience!
I can't find what wrong with that. Try
sudo docker compose down
andrm -r models
thensudo docker compose up
.If still no luck, you can run the bot in a screen session(~~~).
no sucess with compose down and up again.
You mean just use the .py as e.g. systemd service?
You can write a systemd service or use screen or tmux to run bot in background.
Hi, we can debug it by adding a timeout for login step.
bot.py
During local debugging, I accidentally triggered the same issue, and magically, the program resumed responsiveness when I pressed the Enter key.