-
Notifications
You must be signed in to change notification settings - Fork 1
Service get "stuck" and doesn't listen anymore #12
Comments
do you have a VAD plugin enabled? might be the same as #17 (undiagnosed) |
Yes I do, the |
did you have wakeword/utterance upload enabled? could this be coming from OpenVoiceOS/ovos-backend-client#36 |
|
Can you reproduce the issue with a restart of PulseAudio? |
Yes, this is the same behaviour as when PulseAudio or PipeWire are restarted except that when it happens, I got a specific message in the logs:
|
So basically, an error occurs within the audio system making the voice service not reconnecting anymore. In this case, the sound system most likely quickly recovers itself and just carry on, however when the voice service looses connection, it never re-connect again. It is an old problem that surfaces. This can be solved by some sort of microphone watchdog that quickly reconnects and/or restarts when it looses connection to the microphone. This does not solve the underlying reason of the sound system error, but sound issues/errors can happen often for different reasons without any clear cause. However the voice service should be able to identify that it lost microphone connection and recover from it. |
I guess it would be valuable as well for the |
Very randomly, the
listener
service get stuck, consuming CPU resources. I was not able to really pinpoint the issue but it seems that the service is looping waiting for something.Here are the logs when it started to not been responsive anymore.
And here is a
strace
Pythonovos_listener
service.I got this forever in
strace
log.For some reason, the service seems to look for this
/home/ovos/.mycroft/mycroft.conf
file which doesn't not exist but I don't think this is the issue.The text was updated successfully, but these errors were encountered: