No internet connection
  1. Home
  2. Technical Support

Update from 2.5.0 to 2.5.4, failed and broken the tinypilot service

By Nicky Low @nickyzai
    2023-12-26 15:51:49.433Z2023-12-28 15:04:28.407Zassigned to
    • @david

    Hi, somehow I was using 2.5.0 and was trying to do a quick update after quite sometime. However, upgrade from 2.5.0 to 2.5.4 seems having some known bugs, and wasn't aware of it until I experienced it, and checked over here. Tried to import the key, and the update seems hang and unresponsive. Restarted and webui just not accessible anymore... Any way to do a rebuild of 2.5.0 or 2.5.4 without re-flashing? Thanks a bunch.

    [private information removed]

    and...

    pilot@tinypilot:~ $ sudo tail -n 50 /var/log/syslog
Dec 26 15:40:58 tinypilot systemd[1]: tinypilot.service: Main process exited, code=exited, status=203/EXEC
Dec 26 15:40:58 tinypilot systemd[1]: tinypilot.service: Failed with result 'exit-code'.
Dec 26 15:40:58 tinypilot systemd[1]: tinypilot.service: Service RestartSec=100ms expired, scheduling restart.
Dec 26 15:40:58 tinypilot systemd[1]: tinypilot.service: Scheduled restart job, restart counter is at 14873.
Dec 26 15:40:58 tinypilot systemd[1]: Stopped TinyPilot - RPi-based virtual KVM.
Dec 26 15:40:58 tinypilot systemd[1]: Started TinyPilot - RPi-based virtual KVM.
Dec 26 15:40:58 tinypilot systemd[27123]: tinypilot.service: Failed to execute command: No such file or directory
Dec 26 15:40:58 tinypilot systemd[27123]: tinypilot.service: Failed at step EXEC spawning /opt/tinypilot/venv/bin/python: No such file or directory
Dec 26 15:40:58 tinypilot systemd[1]: tinypilot.service: Main process exited, code=exited, status=203/EXEC
Dec 26 15:40:58 tinypilot systemd[1]: tinypilot.service: Failed with result 'exit-code'.
Dec 26 15:40:59 tinypilot systemd[1]: tinypilot.service: Service RestartSec=100ms expired, scheduling restart.
Dec 26 15:40:59 tinypilot systemd[1]: tinypilot.service: Scheduled restart job, restart counter is at 14874.
Dec 26 15:40:59 tinypilot systemd[1]: Stopped TinyPilot - RPi-based virtual KVM.
Dec 26 15:40:59 tinypilot systemd[1]: Started TinyPilot - RPi-based virtual KVM.
Dec 26 15:40:59 tinypilot systemd[27124]: tinypilot.service: Failed to execute command: No such file or directory
Dec 26 15:40:59 tinypilot systemd[27124]: tinypilot.service: Failed at step EXEC spawning /opt/tinypilot/venv/bin/python: No such file or directory
Dec 26 15:40:59 tinypilot systemd[1]: tinypilot.service: Main process exited, code=exited, status=203/EXEC
Dec 26 15:40:59 tinypilot systemd[1]: tinypilot.service: Failed with result 'exit-code'.
Dec 26 15:40:59 tinypilot systemd[1]: tinypilot.service: Service RestartSec=100ms expired, scheduling restart.
Dec 26 15:40:59 tinypilot systemd[1]: tinypilot.service: Scheduled restart job, restart counter is at 14875.
Dec 26 15:40:59 tinypilot systemd[1]: Stopped TinyPilot - RPi-based virtual KVM.
Dec 26 15:40:59 tinypilot systemd[1]: Started TinyPilot - RPi-based virtual KVM.
Dec 26 15:40:59 tinypilot systemd[27126]: tinypilot.service: Failed to execute command: No such file or directory
Dec 26 15:40:59 tinypilot systemd[27126]: tinypilot.service: Failed at step EXEC spawning /opt/tinypilot/venv/bin/python: No such file or directory
Dec 26 15:40:59 tinypilot systemd[1]: tinypilot.service: Main process exited, code=exited, status=203/EXEC
Dec 26 15:40:59 tinypilot systemd[1]: tinypilot.service: Failed with result 'exit-code'.
Dec 26 15:40:59 tinypilot systemd[1]: tinypilot.service: Service RestartSec=100ms expired, scheduling restart.
Dec 26 15:40:59 tinypilot systemd[1]: tinypilot.service: Scheduled restart job, restart counter is at 14876.
Dec 26 15:40:59 tinypilot systemd[1]: Stopped TinyPilot - RPi-based virtual KVM.
Dec 26 15:40:59 tinypilot systemd[1]: Started TinyPilot - RPi-based virtual KVM.
Dec 26 15:40:59 tinypilot systemd[27127]: tinypilot.service: Failed to execute command: No such file or directory
Dec 26 15:40:59 tinypilot systemd[27127]: tinypilot.service: Failed at step EXEC spawning /opt/tinypilot/venv/bin/python: No such file or directory
Dec 26 15:40:59 tinypilot systemd[1]: tinypilot.service: Main process exited, code=exited, status=203/EXEC
Dec 26 15:40:59 tinypilot systemd[1]: tinypilot.service: Failed with result 'exit-code'.
Dec 26 15:40:59 tinypilot systemd[1]: tinypilot.service: Service RestartSec=100ms expired, scheduling restart.
Dec 26 15:40:59 tinypilot systemd[1]: tinypilot.service: Scheduled restart job, restart counter is at 14877.
Dec 26 15:40:59 tinypilot systemd[1]: Stopped TinyPilot - RPi-based virtual KVM.
Dec 26 15:40:59 tinypilot systemd[1]: Started TinyPilot - RPi-based virtual KVM.
Dec 26 15:40:59 tinypilot systemd[27128]: tinypilot.service: Failed to execute command: No such file or directory
Dec 26 15:40:59 tinypilot systemd[27128]: tinypilot.service: Failed at step EXEC spawning /opt/tinypilot/venv/bin/python: No such file or directory
Dec 26 15:40:59 tinypilot systemd[1]: tinypilot.service: Main process exited, code=exited, status=203/EXEC
Dec 26 15:40:59 tinypilot systemd[1]: tinypilot.service: Failed with result 'exit-code'.
Dec 26 15:41:00 tinypilot systemd[1]: tinypilot.service: Service RestartSec=100ms expired, scheduling restart.
Dec 26 15:41:00 tinypilot systemd[1]: tinypilot.service: Scheduled restart job, restart counter is at 14878.
Dec 26 15:41:00 tinypilot systemd[1]: Stopped TinyPilot - RPi-based virtual KVM.
Dec 26 15:41:00 tinypilot systemd[1]: Started TinyPilot - RPi-based virtual KVM.
Dec 26 15:41:00 tinypilot systemd[27130]: tinypilot.service: Failed to execute command: No such file or directory
Dec 26 15:41:00 tinypilot systemd[27130]: tinypilot.service: Failed at step EXEC spawning /opt/tinypilot/venv/bin/python: No such file or directory
Dec 26 15:41:00 tinypilot systemd[1]: tinypilot.service: Main process exited, code=exited, status=203/EXEC
Dec 26 15:41:00 tinypilot systemd[1]: tinypilot.service: Failed with result 'exit-code'.
    Reply
    • 3 replies
    1. David @david2023-12-27 12:05:06.079Z2023-12-27 15:42:59.173Z

      Hi @nickyzai, I'm sorry you're running into this update issue with 2.5.0.

      Like you mentioned, this is a known issue. And the current workaround is to run a command to add some new keys and run the update process again.

      From those logs you shared, it looks like your TinyPilot's filesystem is corrupt. Multiple instances of missing files and directories (No such file or directory) are typical for filesystem corruption. And it explains why your TinyPilot web interface is no longer accessible and why your update keeps failing even after running the previous command to add the keys.

      Any way to do a rebuild of 2.5.0 or 2.5.4 without re-flashing?

      Unfortunately, with filesystem corruption, it's almost impossible to restore the system to stable state since we don't know the extent of the damage. So in this instance, I'd strongly recommend re-flashing your SD card.

      If your TinyPilot Pro license has expired, you can purchase a new 1-year license from our website. The license gives you access to TinyPilot's latest features and priority support.

      As a small company, we rely on license renewals to fund improvements to TinyPilot’s software, so thank you in advance if you choose to renew!

      If you'd rather not renew your license, I can send you the latest image you qualify for to get you past this update issue.

      I hope that helps. Please let me know if you have any questions.

      Reply
      1. NNicky Low @nickyzai
          2023-12-27 14:43:08.127Z

          Hi David, probably I can have the image file to try out first before moving on with a subscription. Please do share the info to me. Thanks.

          Reply
          1. David @david2023-12-27 15:42:42.457Z

            No problem! I've reached out to our customer support team to organize this for you. You should receive an email soon with the latest image that you can use to re-flash your SD card.

            Please let me know if you have any questions.

            Reply
        ReplyAdd progress note