Add FAQ about "database is locked" error
This commit is contained in:
parent
82e0087def
commit
f87aae1dbd
@ -269,6 +269,23 @@ Telegram cloud. This error usually happens in case the provided URL is not publi
|
|||||||
media exceeds 20 MB in size. In such cases, your only option is to download the media yourself and upload from your
|
media exceeds 20 MB in size. In such cases, your only option is to download the media yourself and upload from your
|
||||||
local machine.
|
local machine.
|
||||||
|
|
||||||
|
sqlite3.OperationalError: database is locked
|
||||||
|
--------------------------------------------
|
||||||
|
|
||||||
|
This error occurs when more than one process is using the same session file, that is, when you run two or more clients
|
||||||
|
at the same time using the same session name.
|
||||||
|
|
||||||
|
It could also occur when a background script is still running and you forgot about it. In this case, you either restart
|
||||||
|
your system or find and kill the process that is locking the database. On Unix based systems, you can do the following:
|
||||||
|
|
||||||
|
#. ``cd`` into your session file directory.
|
||||||
|
#. ``fuser my_account.session`` to find the process id.
|
||||||
|
#. ``kill 1234`` to gracefully stop the process.
|
||||||
|
#. If the last command doesn't help, use ``kill -9 1234`` instead.
|
||||||
|
|
||||||
|
If you want to run multiple clients on the same account, you must authorize your account (either user or bot)
|
||||||
|
from the beginning every time, and use different session names for each parallel client you are going to use.
|
||||||
|
|
||||||
My verification code expires immediately!
|
My verification code expires immediately!
|
||||||
-----------------------------------------
|
-----------------------------------------
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user