No internet connection
  1. Home
  2. Technical Support

Unable to access from Web Browser

By @dbak
    2023-05-12 18:53:24.987Zassigned to
    • @cghague

    System is not responding to webbrowser. Errors as below repeatedly in syslog. Can access via SSH, but am not local to system so unable to do factory reset.

    Suggestions?

    May 12 10:44:56 0200707e systemd[4211]: tinypilot.service: Failed to execute command: No such file or directory
    May 12 10:44:56 0200707e systemd[4211]: tinypilot.service: Failed at step EXEC spawning /opt/tinypilot/venv/bin/python: No such file or directory
    May 12 10:44:56 0200707e systemd[1]: tinypilot.service: Main process exited, code=exited, status=203/EXEC
    May 12 10:44:56 0200707e systemd[1]: tinypilot.service: Failed with result 'exit-code'.
    May 12 10:44:56 0200707e systemd[1]: tinypilot.service: Service RestartSec=100ms expired, scheduling restart.
    May 12 10:44:56 0200707e systemd[1]: tinypilot.service: Scheduled restart job, restart counter is at 3540.
    May 12 10:44:56 0200707e systemd[1]: Stopped TinyPilot - RPi-based virtual KVM.
    May 12 10:44:56 0200707e systemd[1]: Started TinyPilot - RPi-based virtual KVM.
    May 12 10:44:56 0200707e systemd[4212]: tinypilot.service: Failed to execute command: No such file or directory
    May 12 10:44:56 0200707e systemd[4212]: tinypilot.service: Failed at step EXEC spawning /opt/tinypilot/venv/bin/python: No such file or directory
    May 12 10:44:56 0200707e systemd[1]: tinypilot.service: Main process exited, code=exited, status=203/EXEC
    May 12 10:44:56 0200707e systemd[1]: tinypilot.service: Failed with result 'exit-code'.

    Reply
    • 3 replies
    1. C
      Charles Hague @cghague2023-05-14 22:59:34.373Z

      Hi @dbak, thanks for reaching out. I’m sorry to hear you’re having issues accessing your TinyPilot device.

      The error you are seeing suggests that the TinyPilot software couldn’t be found, which is usually indicative of filesystem corruption. Filesystem corruption can happen without warning, but most commonly occurs following an unexpected power loss or a failed upgrade.

      We’d normally suggest a factory reset in this scenario, but I appreciate that isn’t currently an option. As you still have SSH access, you may be able to fix the issue by manually re-installing the TinyPilot software. To do so, connect via SSH and run the following commands:

      if [[ -f /opt/tinypilot-updater/install ]]; then
  (sudo apt remove -y tinypilot || true) && \
    cd /opt/tinypilot-updater && \
    sudo ./install
else
  /opt/tinypilot/quick-install
fi

      I’d still recommend performing a factory reset at the earliest opportunity as other parts of the filesystem may also be damaged. Once you have performed a factory reset you may want to enable the read-only filesystem to reduce the likelihood of this happening in future.

      Reply
      1. @dbak
          2023-05-16 16:14:02.901Z

          Not having any luck with the commands. I should note that access to github is restricted in this environment.

          Reply
          1. CCharles Hague @cghague2023-05-17 10:10:32.149Z

            Thanks for getting back to me. Unfortunately, the re-installation and update process requires access to GitHub, the TinyPilot website, the Raspberry Pi OS software repositories, and other dependancies. You'll need to enable access to all of these sites in order for an update or re-installation to be successful.

            The alternative approach when an update or re-installation isn't possible is to perform a factory reset, but it seems that isn't an option in this case. As a temporary workaround, would it be possible for someone local to the device to create a bootable USB drive instead?

            Reply
        ReplyAdd progress note