snowboy: Device or resourse busy
so ive just noticed that after about 12 hours of being on i get a repeating error message of :
[2020-11-26 15:39:34.519] [LOG] [SNOWBOY] Retry restarting... [2020-11-26 15:39:36.595] [LOG] [LPCM16] WARN: arecord: main:828: [2020-11-26 15:39:36.596] [LOG] [LPCM16] WARN: audio open error: Device or resource busy
and it wont go away until i restart my pi, if i only refresh i still get the error.
i tried searching for an answer but didnt come up with anything, from with much, only found that something else is using it but dont know where to start. would the fact that i updated MMM-Assistant2Display via the MMM-Update-Notification
telegram app have anything to do with it?
or could it be if the MM is refreshed then snowboy thinks that it is busy and wont connect to it?
saw to check this and here is the result of
ps -ef | grep aplay:
pi 23592 21495 0 15:35 pts/1 00:00:00 grep --color=auto aplay
@banbutcher snowboy will use arecord, not aplay…
so ps -ef | grep arec
heres the result of that:
pi@MirrorPi:~ $ ps -ef | grep arec pi 765 21495 0 16:23 pts/1 00:00:00 grep --color=auto arec pi 25903 1 0 13:36 pts/0 00:00:00 arecord -D plughw:1 -q -r 16000 -c 1 -t wav -f S16_LE -
this is with MM shut down.
@banbutcher so arecord is hung ( parent is 1) … kill it
sudo kill -9 25903
yup, thats done it. Any idea what would cause it to hang?
@banbutcher no… i see it end unexpectedly more than hang, 999 times :1
and you can tell from that output that it hung?
I think its when i refresh MM, it doesnt close snowboy properly so when MM refreshes snowboy is open already and hangs?
EDIT* (I tested the theory and if i refresh my MM then snowboy goes into that error loop.)
would that make sense?
@banbutcher yes, seems logical. Another platform cleans up on refresh.
could there be a way to shut it properly if the mirror is refreshed?
@banbutcher yes, but coding required