No internet connection
  1. Home
  2. Technical Support

Tinypilot Fails to Start

By @tcp95
    2025-02-13 13:45:04.973Z

    Logs: https://logs.tinypilotkvm.com/8gfHpwcV

    ● tinypilot.service - TinyPilot - RPi-based virtual KVM
    Loaded: loaded (/lib/systemd/system/tinypilot.service; enabled; vendor preset: enabled)
    Active: active (running) since Thu 2025-02-13 13:34:47 GMT; 135ms ago
    Main PID: 1377 (python)
    Tasks: 1 (limit: 1388)
    CPU: 83ms
    CGroup: /system.slice/tinypilot.service

    Feb 13 13:34:47 tinypilot python[1377]: import flask
    Feb 13 13:34:47 tinypilot python[1377]: File "/opt/tinypilot/venv/lib/python3.9/site-packages/flask/init.py", line 1, in>
    Feb 13 13:34:47 tinypilot python[1377]: from . import json as json
    Feb 13 13:34:47 tinypilot python[1377]: File "/opt/tinypilot/venv/lib/python3.9/site-packages/flask/json/init.py", line >
    Feb 13 13:34:47 tinypilot python[1377]: from ..globals import current_app
    Feb 13 13:34:47 tinypilot python[1377]: File "/opt/tinypilot/venv/lib/python3.9/site-packages/flask/globals.py", line 6, in >
    Feb 13 13:34:47 tinypilot python[1377]: from werkzeug.local import LocalProxy
    Feb 13 13:34:47 tinypilot python[1377]: ModuleNotFoundError: No module named 'werkzeug.local'
    Feb 13 13:34:47 tinypilot systemd[1]: tinypilot.service: Main process exited, code=exited, status=1/FAILURE
    Feb 13 13:34:47 tinypilot systemd[1]: tinypilot.service: Failed with result 'exit-code'.

    • 2 replies
    1. T
      @tcp95
        2025-02-13 14:46:16.199Z

        Fixed. Assume this happened after a power flicker.

        pilot@tinypilot:/opt/tinypilot/venv/bin $ ./pip uninstall werkzeug
        pilot@tinypilot:/opt/tinypilot/venv/bin $ sudo ./pip install werkzeug==2.3.8
        
        1. David @david2025-02-17 11:58:42.043Z

          Hi @tcp95, I'm sorry you were running into this issue.

          Assume this happened after a power flicker

          Thanks for the update! It sounds plausible that this happened due to a power issue. I'm glad you're back up and running now.

          Feel free to reach out if you have any other questions.

        2. Progress
          with handling this problem
        3. T@tcp95 closed this topic 2025-02-13 14:46:27.826Z.