Seeing Error in Settings.yml
- @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:
- 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.
- AIn reply toa7673⬆:a7673 @a7673
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.
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 thansettings.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 currentsettings.yml
file)?cat /lib/systemd/system/tinypilot.service
After you've checked the
tinypilot.service
file, could you run the following command to reset yoursettings.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 fromsudo service tinypilot status
?Please let me know if you have any questions.
- AIn reply toa7673⬆:a7673 @a7673
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.
David @david2025-03-07 12:08:50.842Z