paradizelost/paperless-ngx
1
0
Fork 0
mirror of https://github.com/paperless-ngx/paperless-ngx.git synced 2025-04-02 13:45:10 -05:00
Code Issues Packages Projects Releases Wiki Activity

troubleshooting for #216

Browse Source
This commit is contained in:
Jonas Winkler 2021-02-01 20:14:29 +01:00
parent 48cfb64416
commit 48b042bfb0
1 changed files with 37 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

39
docs/troubleshooting.rst
View File

@ -60,7 +60,8 @@ required so that the user running paperless inside docker has write permissions
to these folders. This happens when pointing these directories to NFS shares, to these folders. This happens when pointing these directories to NFS shares,
for example. for example.
Ensure that `chown` is possible on these directories. Ensure that ``chown`` is possible on these directories.
Classifier error: No training data available Classifier error: No training data available
############################################ ############################################
@ -73,6 +74,7 @@ This may have two reasons:
with Inbox tags. Verify that there are documents in your archive without inbox tags. with Inbox tags. Verify that there are documents in your archive without inbox tags.
The algorithm will only learn from documents not in your inbox. The algorithm will only learn from documents not in your inbox.
UserWarning in sklearn on every single document UserWarning in sklearn on every single document
############################################### ###############################################
@ -91,6 +93,7 @@ in most cases. This warning will disappear automatically when paperless updates
If you want to get rid of the warning or actually experience issues with automatic matching, delete If you want to get rid of the warning or actually experience issues with automatic matching, delete
the file ``classification_model.pickle`` in the data directory and let paperless recreate it. the file ``classification_model.pickle`` in the data directory and let paperless recreate it.
Permission denied errors in the consumption directory Permission denied errors in the consumption directory
##################################################### #####################################################
@ -106,6 +109,38 @@ different from ``1000``. See :ref:`setup-docker_hub`.
Also ensure that you are able to read and write to the consumption directory on the host. Also ensure that you are able to read and write to the consumption directory on the host.
OSError: [Errno 19] No such device when consuming files
#######################################################
If you experience errors such as:
.. code:: shell-session
File "/usr/local/lib/python3.7/site-packages/whoosh/codec/base.py", line 570, in open_compound_file
return CompoundStorage(dbfile, use_mmap=storage.supports_mmap)
File "/usr/local/lib/python3.7/site-packages/whoosh/filedb/compound.py", line 75, in __init__
self._source = mmap.mmap(fileno, 0, access=mmap.ACCESS_READ)
OSError: [Errno 19] No such device
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/django_q/cluster.py", line 436, in worker
res = f(*task["args"], **task["kwargs"])
File "/usr/src/paperless/src/documents/tasks.py", line 73, in consume_file
override_tag_ids=override_tag_ids)
File "/usr/src/paperless/src/documents/consumer.py", line 271, in try_consume_file
raise ConsumerError(e)
Paperless uses a search index to provide better and faster full text searching. This search index is stored inside
the ``data`` folder. The search index uses memory-mapped files (mmap). The above error indicates that paperless
was unable to create and open these files.
This happens when you're trying to store the data directory on certain file systems (mostly network shares)
that don't support memory-mapped files.
Web-UI stuck at "Loading..." Web-UI stuck at "Loading..."
############################ ############################
@ -148,4 +183,4 @@ This might have multiple reasons.
SENDFILE=0 SENDFILE=0
to your `docker-compose.env` file. to your `docker-compose.env` file.