From f87aae1dbdf9b9062310b77e2b89f22621e7b7d4 Mon Sep 17 00:00:00 2001
From: Dan <14043624+delivrance@users.noreply.github.com>
Date: Tue, 6 Aug 2019 13:16:48 +0200
Subject: [PATCH] Add FAQ about "database is locked" error

---
 docs/source/faq.rst | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/docs/source/faq.rst b/docs/source/faq.rst
index 5d4823c8..203dde8a 100644
--- a/docs/source/faq.rst
+++ b/docs/source/faq.rst
@@ -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
 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!
 -----------------------------------------