search

rhasspy / wyoming-satellite

Remote voice satellite using Wyoming protocol
MIT License
693 stars 104 forks source link

Openwakeword and Wyoming Satellite Not getting initialized #210

Open adimural opened 2 months ago

adimural commented 2 months ago

I followed all the steps in this tutorial. I got the wyoming service up and running first. I then added it to home assistant. After that, when i added the open wakeword to the pipeline then things went haywire. Below log for reference.

Please let me know what is going wrong here.

Issue Log: loftsatellite@loftsatellite:~ $ sudo systemctl status wyoming-satellite.service wyoming-openwakeword.service × wyoming-satellite.service - Wyoming Satellite Loaded: loaded (/etc/systemd/system/wyoming-satellite.service; enabled; > Active: failed (Result: start-limit-hit) since Tue 2024-08-20 07:47:48 P> Duration: 1.211s Process: 1074 ExecStart=/home/loftsatellite/wyoming-satellite/script/run > Main PID: 1074 (code=killed, signal=TERM) CPU: 203ms

Aug 20 07:47:47 loftsatellite run[1075]: File "/usr/lib/python3.11/asyncio/> Aug 20 07:47:47 loftsatellite run[1075]: raise OSError(err, f'Connect cal> Aug 20 07:47:47 loftsatellite run[1075]: ConnectionRefusedError: [Errno 111] > Aug 20 07:47:48 loftsatellite systemd[1]: Stopping wyoming-satellite.service > Aug 20 07:47:48 loftsatellite run[1077]: Aborted by signal Terminated... Aug 20 07:47:48 loftsatellite systemd[1]: wyoming-satellite.service: Deactiva> Aug 20 07:47:48 loftsatellite systemd[1]: Stopped wyoming-satellite.service -> Aug 20 07:47:48 loftsatellite systemd[1]: wyoming-satellite.service: Start re> Aug 20 07:47:48 loftsatellite systemd[1]: wyoming-satellite.service: Failed w> Aug 20 07:47:48 loftsatellite systemd[1]: Failed to start wyoming-satellite.s>

× wyoming-openwakeword.service - Wyoming openWakeWord Loaded: loaded (/etc/systemd/system/wyoming-openwakeword.service; disabl> Active: failed (Result: exit-code) since Tue 2024-08-20 07:47:48 PDT; 3s> Duration: 1ms Process: 1073 ExecStart=/home/loftsatellite/wyoming-openwakeword/script/r> Main PID: 1073 (code=exited, status=200/CHDIR) CPU: 1ms

Aug 20 07:47:47 loftsatellite systemd[1]: wyoming-openwakeword.service: Main > Aug 20 07:47:47 loftsatellite systemd[1]: wyoming-openwakeword.service: Faile> Aug 20 07:47:48 loftsatellite systemd[1]: wyoming-openwakeword.service: Sched> Aug 20 07:47:48 loftsatellite systemd[1]: Stopped wyoming-openwakeword.servic> Aug 20 07:47:48 loftsatellite systemd[1]: wyoming-openwakeword.service: Start> Aug 20 07:47:48 loftsatellite systemd[1]: wyoming-openwakeword.service: Faile> Aug 20 07:47:48 loftsatellite systemd[1]: Failed to start wyoming-openwakewor> lines 1-34/34 (END)

adimural commented 2 months ago

This is with Raspberry Pi 5 with 64 bit OS lite version.

Joldiges commented 2 months ago

I followed all the steps in this tutorial. I got the wyoming service up and running first. I then added it to home assistant. After that, when i added the open wakeword to the pipeline then things went haywire. Below log for reference.

Please let me know what is going wrong here.

Issue Log: loftsatellite@loftsatellite:~ $ sudo systemctl status wyoming-satellite.service wyoming-openwakeword.service × wyoming-satellite.service - Wyoming Satellite Loaded: loaded (/etc/systemd/system/wyoming-satellite.service; enabled; > Active: failed (Result: start-limit-hit) since Tue 2024-08-20 07:47:48 P> Duration: 1.211s Process: 1074 ExecStart=/home/loftsatellite/wyoming-satellite/script/run > Main PID: 1074 (code=killed, signal=TERM) CPU: 203ms

Aug 20 07:47:47 loftsatellite run[1075]: File "/usr/lib/python3.11/asyncio/> Aug 20 07:47:47 loftsatellite run[1075]: raise OSError(err, f'Connect cal> Aug 20 07:47:47 loftsatellite run[1075]: ConnectionRefusedError: [Errno 111] > Aug 20 07:47:48 loftsatellite systemd[1]: Stopping wyoming-satellite.service > Aug 20 07:47:48 loftsatellite run[1077]: Aborted by signal Terminated... Aug 20 07:47:48 loftsatellite systemd[1]: wyoming-satellite.service: Deactiva> Aug 20 07:47:48 loftsatellite systemd[1]: Stopped wyoming-satellite.service -> Aug 20 07:47:48 loftsatellite systemd[1]: wyoming-satellite.service: Start re> Aug 20 07:47:48 loftsatellite systemd[1]: wyoming-satellite.service: Failed w> Aug 20 07:47:48 loftsatellite systemd[1]: Failed to start wyoming-satellite.s>

× wyoming-openwakeword.service - Wyoming openWakeWord Loaded: loaded (/etc/systemd/system/wyoming-openwakeword.service; disabl> Active: failed (Result: exit-code) since Tue 2024-08-20 07:47:48 PDT; 3s> Duration: 1ms Process: 1073 ExecStart=/home/loftsatellite/wyoming-openwakeword/script/r> Main PID: 1073 (code=exited, status=200/CHDIR) CPU: 1ms

Aug 20 07:47:47 loftsatellite systemd[1]: wyoming-openwakeword.service: Main > Aug 20 07:47:47 loftsatellite systemd[1]: wyoming-openwakeword.service: Faile> Aug 20 07:47:48 loftsatellite systemd[1]: wyoming-openwakeword.service: Sched> Aug 20 07:47:48 loftsatellite systemd[1]: Stopped wyoming-openwakeword.servic> Aug 20 07:47:48 loftsatellite systemd[1]: wyoming-openwakeword.service: Start> Aug 20 07:47:48 loftsatellite systemd[1]: wyoming-openwakeword.service: Faile> Aug 20 07:47:48 loftsatellite systemd[1]: Failed to start wyoming-openwakewor> lines 1-34/34 (END)

You've only attached part of the logs. You can use journalctl -u wyoming-satellite.service instead to provide us a more readable instance

The only useful part i see is from this tiny section "raise OSError". Maybe a permissions or a fs issue? I won't know without seeing the whole width of the error(s)