tdlight-team/tdlight-telegram-bot-api

PosixError : Permission denied : 13 : File "user_db.binlog" can't be opened/created for reading and writing

HitaloM opened this issue · 13 comments

HitaloM commented

I'm using the Docker container and after updating it I had this error at container startup.

LOG:00000000:  [ 2][t 0][1624885451.285162925][telegram-bot-api.cpp:468]Bot API 5.3 server started            
LOG:00000070:  [ 2][t 0][1624885451.286713123][ClientManager.cpp:416][!ClientManager]Loaded 0 TQueue events   
LOG:000000e0:  [ 0][t 0][1624885451.286823987][ClientManager.cpp:442][!ClientManager][&status.is_error()]Can't open user_db.binlog [PosixError : Permission denied : 13 : File "user_db.binlog" can't be opened/created for reading and writing]              
[pid 1] [time 1624885451] ------------------------
smaznet commented

@HitaloSama chown -R -u 101 ./tworkdata

HitaloM commented

@HitaloSama chown -R -u 101 ./tworkdata

How can I run the command if the container is not running?

giuseppeM99 commented

docker exec -it container_name /bin/sh

noplanman commented

I have the same problem. Even reverting to the previous version doesn't help, it's failing now too!

I've set the permissions, even tried to chmod 777 to make sure it's not a permission problem, but still fails.

Any other ideas?

cavallium commented

If you are not running anything critical you can do chmod -R 777 but only as a temporary solution

  • 👀1
noplanman commented

I've done that, same error 🤔

giuseppeM99 commented

sorry for that, should be fixed in the next build

noplanman commented

Still curious why reverting to a previous version doesn't work.

My user_db.binlog file is an empty file, is that normal?

giuseppeM99 commented

Still curious why reverting to a previous version doesn't work.

My user_db.binlog file is an empty file, is that normal?

Yes if you don't use the user mode

giuseppeM99 commented

hello, it is now released, you can docker pull or docker-compose pull and restart the container, if you haven't used the user mode and it still gives you permission issues you can delete the user_db.binlog file, it will be recreated with the appropriate permissions

  • ❤️1
noplanman commented

Perfect, it's working again, thanks for the speedy response 🙏

cavallium commented

v5.3.1 includes this fix

smaznet commented

@HitaloSama chown -R -u 101 ./tworkdata

How can I run the command if the container is not running?

should be run on host machine