Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Paperless-ngx
  3. Quick fix for sudden stops in document classification

Quick fix for sudden stops in document classification

Scheduled Pinned Locked Moved Paperless-ngx
1 Posts 1 Posters 120 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • luckowL Offline
    luckowL Offline
    luckow
    translator
    wrote on last edited by luckow
    #1

    In January, I noticed that automatic classification for documents had stopped on two of my Paperless instances. I didn't have time to fix it, so I resorted to manual interaction.
    Now, I looked into the logs and found the following message: System status detected a possible problem while loading the classifier: Classifier file does not exist (yet). Re-training may be pending.
    This specific error made it easy to search the internet for a solution.

    In the official docs, I found information about Managing the Automatic matching algorithm.
    Additionally, the Cloudron documentation provided the syntax for using the console: Cloudron Paperless-NGX Docs.

    Fixing the issue is actually quite simple:

    • Open the console of your paperless app and run
    cd /app/code/src
    python3 manage.py document_create_classifier
    
    • Wait a few seconds/minutes
    • For new documents, automatic classification should work as expected.
    • For older documents, there is an action item reprocess which does not work as expected.

    The reason why document classification stopped in the first place remains unknown.

    Pronouns: he/him | Primary language: German

    1 Reply Last reply
    2
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • Bookmarks
    • Search