[SOLVED] browser-WebUI interaction isn't stable/reliable

[AW_Raudio]

I have running RuneAudio 0.3-beta on Raspberry Pi B. I listen only to web radios. I have added some stations to the queue.

Very often the browser doesn't connect to the WebUI anymore after having clicked on another station or a command like stop, play etc..

Sometimes there is also a message that the queue is empty. But it isn't true. No entry in the queue is deleted.

The only way to repair is to reboot.

After a reboot runeaudio continues to play a station I stopped before.

The interaction between browser and WebUi is not stable and reliable.

Please improve.

I have to reboot regularly 2 or 3 times a day. This is annoying.

Thanks.

Rgds
AW

[ACX]

Hi AW_Raudio,
we'd like to help you but we don't know any information about your setup.

If you had read you'd know that:
1) I suggested to post feedbacks about 0.3-beta in that thread, instead of opening a new one for each issue;
2) I asked to post the debug information to give us the needed information to understand the problem better.

About your problem, it seems that MPD is behaving a bit crazy in the background, creating some instability between it and the RuneUI. We have to find out the reason behind that.

[AW_Raudio]

Sorry for my misbehaviour.

It is difficult to read 35 pages in raspberry-pi-f7.html

I post the debug information here with http://pastebin.com/VUQtJRk5

There is also:
"[ 12.663477] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck."

I checked all partitions on the SD-card several times with fsck.ext -force and under Win7 with chkdsk x: /V. But the filesystems are always not damaged.

Please check this too.

Rgds
AW

[ACX]

Please try this small fix
runeaudio-0-3-beta-for-raspberry-pi-t502-340.html#p4174
and tell us if it solves something in your setup.

[AW_Raudio]

I installed the fix but sometimes I get following warning:

"Warning: socket_write() expects parameter 1 to be resource, boolean given in /srv/http/app/libs/runeaudio.php on line 104 Warning: socket_last_error() expects parameter 1 to be resource, boolean given in /srv/http/app/libs/runeaudio.php on line 88 Warning: socket_close() expects parameter 1 to be resource, boolean given in /srv/http/app/libs/runeaudio.php on line 89"

Then only reboot possible.

In general it seems to be an improvement.

Rgds
AW

[AW_Raudio]

Once again:

Warning: socket_write() expects parameter 1 to be resource, boolean given in /srv/http/app/libs/runeaudio.php on line 104 Warning: socket_last_error() expects parameter 1 to be resource, boolean given in /srv/http/app/libs/runeaudio.php on line 88 Warning: socket_close() expects parameter 1 to be resource, boolean given in /srv/http/app/libs/runeaudio.php on line 89

And reboot.

Rgds
AW

[ACX]

@AW_Raudio: when that happens please restart the rune_SY_wrk (from the dev page or manually with systemctl restart rune_SY_wrk) and tell me if it helps.

[AW_Raudio]

It doesn't happen again.

Behaviour of Rune WebUI much better. Much more stable. No troubles anymore. No restarts necessary. My RuneAudio 0.3-beta on Raspberry Pi B is running now since 2 or 3 weeks without error and restart. Congratulations!

Rgds
AW

[AW_Raudio]

Restarting the rune_SY_wrk from the dev page helps.