search

snipsco / snips-issues

Feel free to share your bugs with us.
14 stars 5 forks source link

snips-asr is restarting all the time #77

Closed Kareldbs closed 5 years ago

Kareldbs commented 5 years ago

Hi, I have been searching all around with Google and in Forum but I can't find the answer. The issue I have is that snips-asr is restarting all the time, so I can't get snips to work with voice.

This is what I see in /var/log/syslog: Dec 27 19:27:03 raspberrypi snips-hotword[1253]: INFO:snips_hotword::server : Discovered audio_server default/mqtt, starting hotword listener Dec 27 19:27:03 raspberrypi snips-hotword[1253]: INFO:snips_hotword::server : Connecting using MQTT site-id default Dec 27 19:27:03 raspberrypi snips-hotword[1253]: INFO:snips_hotword_lib::audio : Audio thread for default started Dec 27 19:27:03 raspberrypi snips-hotword[1253]: INFO:snips_hotword_lib::audio : Net and VAD thread for site default started (vad inhibitor: true, vad messages: false Dec 27 19:27:03 raspberrypi snips-hotword[1253]: INFO:snips_hotword_lib : Detector "detector.default.default", sensitivity: 0.5, threshold 0.44 Dec 27 19:27:03 raspberrypi snips-hotword[1253]: INFO:snips_hotword_lib : detector.default.default thread started Dec 27 19:27:05 raspberrypi systemd[1]: snips-asr.service: Service hold-off time over, scheduling restart. Dec 27 19:27:05 raspberrypi systemd[1]: Stopped Snips ASR. Dec 27 19:27:05 raspberrypi systemd[1]: Started Snips ASR. Dec 27 19:27:06 raspberrypi systemd[1]: snips-asr.service: Main process exited, code=killed, status=4/ILL Dec 27 19:27:06 raspberrypi systemd[1]: snips-asr.service: Unit entered failed state. Dec 27 19:27:06 raspberrypi systemd[1]: snips-asr.service: Failed with result 'signal'. Dec 27 19:27:11 raspberrypi systemd[1]: snips-asr.service: Service hold-off time over, scheduling restart. Dec 27 19:27:11 raspberrypi systemd[1]: Stopped Snips ASR. Dec 27 19:27:11 raspberrypi systemd[1]: Started Snips ASR. Dec 27 19:27:12 raspberrypi systemd[1]: snips-asr.service: Main process exited, code=killed, status=4/ILL Dec 27 19:27:12 raspberrypi systemd[1]: snips-asr.service: Unit entered failed state. Dec 27 19:27:12 raspberrypi systemd[1]: snips-asr.service: Failed with result 'signal'. Dec 27 19:27:17 raspberrypi snips-nlu[1248]: INFO:snips_nlu_hermes: model loaded in 16981 ms Dec 27 19:27:17 raspberrypi systemd[1]: snips-asr.service: Service hold-off time over, scheduling restart. Dec 27 19:27:17 raspberrypi systemd[1]: Stopped Snips ASR. Dec 27 19:27:17 raspberrypi systemd[1]: Started Snips ASR. Dec 27 19:27:18 raspberrypi systemd[1]: snips-asr.service: Main process exited, code=killed, status=4/ILL Dec 27 19:27:18 raspberrypi systemd[1]: snips-asr.service: Unit entered failed state. Dec 27 19:27:18 raspberrypi systemd[1]: snips-asr.service: Failed with result 'signal'. Dec 27 19:27:23 raspberrypi systemd[1]: snips-asr.service: Service hold-off time over, scheduling restart. Dec 27 19:27:23 raspberrypi systemd[1]: Stopped Snips ASR. Dec 27 19:27:23 raspberrypi systemd[1]: Started Snips ASR. Dec 27 19:27:24 raspberrypi systemd[1]: snips-asr.service: Main process exited, code=killed, status=4/ILL Dec 27 19:27:24 raspberrypi systemd[1]: snips-asr.service: Unit entered failed state. Dec 27 19:27:24 raspberrypi systemd[1]: snips-asr.service: Failed with result 'signal'. Dec 27 19:27:29 raspberrypi systemd[1]: snips-asr.service: Service hold-off time over, scheduling restart. Dec 27 19:27:29 raspberrypi systemd[1]: Stopped Snips ASR.

I have tested the speaker and microphone with sam test and sam setup audio and it was successfull. I have created an assistant and have built a calculator app as mentioned in documentation and deploy it on device. Start sam watch and nothing is happening and I think because snips-asr is not working.

Raspbian version on Raspberry pi 2 B+: Linux raspberrypi 4.14.79+ #1159 Sun Nov 4 17:28:08 GMT 2018 armv6l GNU/Linux

I hope somebody can help me, I was quite far in getting it to work.

Regards, Karel.

Kareldbs commented 5 years ago

Sorry, I also forgot to mention that it's Raspbian Stretch Lite

Kareldbs commented 5 years ago

also when I run snips-asr seperate from /usr/bin it gives this: pi@raspberrypi:/ $ /usr/bin/snips-asr -v Illegal instruction

All other snips* don't give Illegal instruction

guillaumeki commented 5 years ago

I have the exact same problem on a raspberry pi zero W with raspbian stretch and a ReSpeaker 2-Mics Pi HAT. With the same errors described by @Kareldbs . In the command "sam status", snips-asr appears "not running". When I say the hotword, the hat show blue leds but nothing happened when I speak. After a few seconds, with "sam watch", I can see that a component (sam-asr I think...) didn't respond in a timely manner.

guillaumeki commented 5 years ago

This issue still exists with the latest update of snips. Is there a fix ?

cpoisson commented 5 years ago

Hi, we don't officially support snips-asr on pi2 and pi0, those platforms are good enough to run snips-audio-server and snips-hotword.

The minimum requirement is a Pi3 to keep up with the amount of calculation needed for the ASR.

So, yes no fix planned for that at the moment.