I think it happens only after this sequence, but I'm not sure.
1 listen to a webstream (it has happened with several different streams)
2 pause or stop Rune playback
3 leave Rune idle for some time (hours)
When I thereafter try to use Rune again it is unresponsive.
This doesn't happen every time but perhaps once a week. Since usage of the Rune device also varies (some times lot of webstream listening, some times mostly file playback) it is hard to pin down more details on when it happens.
When the issue happens the Rune playback and playlist pages show no content and the playback page has never ending spinning wheels. Pause, Play etc does not work. When I SSH in and try mpc commands (like mpc play, mpc status, ...) I get "connection refused". I first thought the issue only happened when a webstream was paused and then left idle for several hours. So I did a bash script that does "mpc stop" if the track is a webstream and "mpc pause" otherwise. But I've since then had the issue also when a webstream is the current track and has been stopped for several hours.
Powering the Raspi on and off solves the problem until next time.
But I'm looking for a way to fix the issue permanently or at least work around it without having to restart the Raspi device.
When it happened again today I managed to get Rune operational again with these steps.
1 SSH in and do
- Code: Select all
systemctl restart mpd
Then mpc commands work again, I can play pause audio. But the Rune playback and playlist pages still show no content.
2 to also get the UI working I go to
- Code: Select all
http://<rune device ip adress>/dev/
and do "Clear OPcache", "Restart rune_SY_wrk" and "Restart rune_PL_wrk" and reload Rune in the browser.
(I'm not sure if all three were needed for that though, I'll try them one by one next time).
Are there any bash/command line equivalents for those three commands on the /dev page? If so then I could put them all in a handy bash script.