[Bug 297201] deskutils/py-paperless-ngx: service paperless-worker doesn't start

[email protected] Fri, 31 Jul 2026 12:59:35 +0000
Newsgroups gmane.os.freebsd.devel.ports.bugs
Message-ID <[email protected]/bugzilla/>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=297201

            Bug ID: 297201
           Summary: deskutils/py-paperless-ngx: service paperless-worker
                    doesn't start
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: [email protected]
          Reporter: [email protected]
             Flags: maintainer-feedback?([email protected])
          Assignee: [email protected]

Created attachment 273351
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=273351&action=edit
Fix paperless-worker service start

Starting paperless-worker results in following syslog message:

[CRITICAL] [celery.worker] Unrecoverable error: AttributeError("'NoneType'
object has no attribute 'isatty'") Traceback (most recent call last):   File
"/usr/local/lib/python3.12/site-packages/celery/worker/worker.py", line 202, in
start     self.blueprint.start(self)   File
"/usr/local/lib/python3.12/site-packages/celery/bootsteps.py", line 112, in
start     self.on_start()   File
"/usr/local/lib/python3.12/site-packages/celery/apps/worker.py", line 135, in
on_start     self.emit_banner()   File
"/usr/local/lib/python3.12/site-packages/celery/apps/worker.py", line 164, in
emit_banner     use_image = term.supports_images()                
^^^^^^^^^^^^^^^^^^^^^^   File
"/usr/local/lib/python3.12/site-packages/celery/utils/term.py", line 165, in
supports_images     return sys.stdin.isatty() and ITERM_PROFILE           
^^^^^^^^^^^^^^^^ AttributeError: 'NoneType' object has no attribute 'isatty'

It seems that the worker barfs because /dev/stdout is not existent.

Workaround is to add parameter "-f" to daemon in rc.d, see attachment.

I'm not sure whether it's related to FreeBSD 15.1p2, because on initial setup
using FreeBSD 15.1p1, this problem didn't occur.

-- 
You are receiving this mail because:
You are the assignee for the bug.