The TinyPilot forum is now closed.

As part of our efforts to provide more direct, focused, and responsive support, we are transitioning our forum to a read-only format. While you can continue to browse past discussions, we invite you to explore our FAQ or contact us by email for personal support. We appreciate your understanding - thank you to everyone who has contributed to our forum community over the years!

No internet connection
  1. Home
  2. Technical Support

Seeing Error in Settings.yml

By a7673 @a7673
    2024-12-02 19:22:29.771Z2024-12-02 20:44:52.689Zassigned to
    • @david

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

    It was working fine for many months and now I am seeing Error in Settings.yml all of sudden.
    The device was enabled to the read-only file system. I am working remotely, please dont tell me to factory reset the file system which is impossible for me at the moment.
    Please tell me other alternatives to fix this system.

    I was also able to do a restart of the TinyPilot Service (sudo service tinypilot restart) it dint work.

    Please help.

    Linked from:

    1. Network boot option
    • 5 replies
    1. David @david2024-12-03 12:06:46.916Z

      Hi @a7673, I'm sorry you're running into this error with your settings.yml file.

      Thanks for sharing that log! It looks like the TinyPilot service can't run because it can't parse the data in settings.yml. I haven't seen this particular issue before, so we'll have to do some investigation.

      Since you have SSH access, could you ssh into your TinyPilot and share the contents of settings.yml? You can output the content of the file with the following command:

      cat /home/tinypilot/settings.yml

      Then paste the output in your reply.

      Please let me know if you have any questions.

      1. A
        In reply toa7673⬆:
        a7673 @a7673
          2024-12-03 16:49:29.007Z2025-03-05 16:07:29.927Z

          Here's the info copied:

          pilot@tinypilot:~ $ cat /home/tinypilot/settings.yml
          [Unit]
          Description=TinyPilot - RPi-based virtual KVM
          BindsTo=nginx.service
          After=syslog.target network.target nginx.service
          StartLimitIntervalSec=0

          [Service]
          Type=simple
          User=tinypilot
          WorkingDirectory=/opt/tinypilot
          ExecStart=/opt/tinypilot/venv/bin/python app/main.py
          Environment=APP_SETTINGS_FILE=/home/tinypilot/app_settings.cfg
          Restart=always

          [Install]
          WantedBy=multi-user.target
          pilot@tinypilot:~ $

          Kindly please help me with a remote solution. I am badly stuck.

          1. David @david2024-12-04 12:39:02.256Z

            Thanks for sharing that output, @a7637.

            That text looks like it belongs to /lib/systemd/system/tinypilot.service, rather than settings.yml. I haven't seen a situation where a file has taken on the contents of another file - it's possible that filesystem corruption has caused this issue.

            Could you check /lib/systemd/system/tinypilot.service contains the correct configuration (it should have the same content as your current settings.yml file)?

            cat /lib/systemd/system/tinypilot.service

            After you've checked the tinypilot.service file, could you run the following command to reset your settings.yml file:

            sudo tee /home/tinypilot/settings.yml < /dev/null

            Then try restarting the tinypilot service to see if it can run again:

            sudo service tinypilot start

            If the tinypilot service fails to start again, could you share another log or the output from sudo service tinypilot status?

            Please let me know if you have any questions.

          2. A
            In reply toa7673⬆:
            a7673 @a7673
              2025-03-06 19:39:27.176Z

              SD Card got corrupted and had to be factory reset using the TP Image. Then same thing happened with
              Flash Drive, it got corrupted and it is bricked lol. Its a dead soul now.

              Bizzare in both cases is that both were set on Read-only setting. Still this happened. Not happy with what is going on especially when you expect your machine to use it remotely from Far away on the earth.

              See if you can help me with alternatives.

              1. David @david2025-03-07 12:08:50.842Z

                Hi @a7673, I'm sorry you experienced these filesystem corruption issues.

                It looks like @cghague is helping out in your other threads (here and here).

              ReplyAdd progress note