Skip to content

Mqtt error #154

@daschmidt1994

Description

@daschmidt1994

gerade im Log das hier gesehen,deswegen lässt sich die mupibox auch nicht per mqtt stoppen und das ist sehr schade.

     Loaded: loaded (/etc/systemd/system/mupi_mqtt.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Sat 2026-05-16 19:12:32 CEST; 44min ago
   Duration: 11h 52min 29.597s
    Process: 641 ExecStart=/usr/bin/python3 -B /usr/local/bin/mupibox/mqtt.py (code=exited, status=1/FAILURE)
   Main PID: 641 (code=exited, status=1/FAILURE)
        CPU: 2.130s

May 16 19:12:32 MuPiBox python3[641]: Traceback (most recent call last):
May 16 19:12:32 MuPiBox python3[641]:   File "/usr/local/bin/mupibox/mqtt.py", line 1001, in 
May 16 19:12:32 MuPiBox python3[641]:     main()
May 16 19:12:32 MuPiBox python3[641]:   File "/usr/local/bin/mupibox/mqtt.py", line 993, in main
May 16 19:12:32 MuPiBox python3[641]:     print(f"Signal {signum} received. Service will be stopped...")
May 16 19:12:32 MuPiBox python3[641]:                     ^^^^^^
May 16 19:12:32 MuPiBox python3[641]: NameError: name 'signum' is not defined. Did you mean: 'signal'?
May 16 19:12:32 MuPiBox systemd[1]: mupi_mqtt.service: Main process exited, code=exited, status=1/FAILURE
May 16 19:12:32 MuPiBox systemd[1]: mupi_mqtt.service: Failed with result 'exit-code'.
May 16 19:12:32 MuPiBox systemd[1]: mupi_mqtt.service: Consumed 2.130s CPU time.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions