Beta Boot Issues - Githubissues

JarvyJ commented 3 years ago

Pi 4 - interface didn't come up on first boot?
- i might not have waited long enough. It worked fine after a manual reboot and on all reboots after
Pi 0/3 - got stuck in boot... No idea what's going on.
- Will try again and see if i can capture the error message. It goes by too quickly. Whatever it is, it happens before the USB device is initialized

JarvyJ commented 3 years ago

The Pi 0/3 seems to be a firmware issue upstream. Will report back when it is good to go!

JarvyJ commented 2 years ago

The pi3 image that built claims to have a corrupt initram or something.

The pi0 did boot, but I ran into this issue when it tried to start mqtt for the first time:

2021-11-19 02:58:50,148 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file. 
2021-11-19 02:58:50,940 INFO supervisord started with pid 460
2021-11-19 02:58:51,951 INFO spawnerr: unknown error making dispatchers for 'mqtt': ENXIO
2021-11-19 02:58:52,975 INFO spawnerr: unknown error making dispatchers for 'mqtt': ENXIO
2021-11-19 02:58:55,005 INFO spawnerr: unknown error making dispatchers for 'mqtt': ENXIO
2021-11-19 02:58:58,026 INFO spawnerr: unknown error making dispatchers for 'mqtt': ENXIO
2021-11-19 02:58:58,038 INFO gave up: mqtt entered FATAL state, too many start retries too quickly

I was able to manually start the service, but not through systemctl. It seems as if MQTT is unable to start.

JarvyJ commented 2 years ago

That was a bit of a rabbit hole. We need to change the systemd service ExecStart to look like /bin/sh -c "/mnt/persist/rhasspy/bin/rhasspy-voltron --user-profiles /mnt/persist/skiff/profiles --profile en 2>&1 | tee". systemd makes stdout look like a socket, but if you pipe to tee/cat it will directly write to the underlying stdout proc, getting around the socket situation. I'll make the change and then see what happens. We might be getting close!

JarvyJ / Rhasspy-Satellite

Beta Boot Issues #14