And @philrandal and @TimCurtis:
Are you guys filling in the Bluetooth speaker name? If I do that, then I can fill in the UPnP renderer, etc., name. If I do not fill in the Bluetooth speaker name but do try to fill in the UPnP renderer, etc., name, then I get the behavior I described.
Still futzing with my build script so probably won't get to try a fresh build until tonight.
Regards,
Kent
Hi Kent - no I have not filled in the speaker name - all the renderers come up with prepopulated names like Moode Airplay, Moode DLNA, etc, Regards Adrian
Hi Adrian,
MPD status cmd is the only source for streaming bitrate. I'm thinking that either a bug or change in MPD but I'll have a look at the moOde code anyway.
You could try updating to 0.10.11. Just re-do STEP 7 starting with number 3, substitute 0.20.11 for 0.20.10.
Brew a pot of Coffee or Tea, take Dog for walk, etc while MPD compiles
-Tim
Oy. You already hinted at that and I hadn't had enough coffee to get the point. Then @philrandal obliquely touched on the same point when he mentioned corrupted database. Sorry guys.
Regards,
Kent
I have a problem with Sources definition.
I have created an incorrect NAS source (hostname not resolved) and can't change or delete it via web.
If I try to edit it and save changes, the web request to src-config.php always hangs. After that /var/log/mps/log is filled very fast with "client: Max connections reached" lines.
I can't enter any configuration section anymore and some other functions stop working. How can I fix it?
I have created an incorrect NAS source (hostname not resolved) and can't change or delete it via web.
If I try to edit it and save changes, the web request to src-config.php always hangs. After that /var/log/mps/log is filled very fast with "client: Max connections reached" lines.
I can't enter any configuration section anymore and some other functions stop working. How can I fix it?
I have a problem with Sources definition in beta 7
I have created an incorrect NAS source (hostname not resolved) and can't change or delete it via web.
If I try to edit it and save changes, the web request to src-config.php always hangs. After that /var/log/mps/log is filled very fast with "client: Max connections reached" lines.
I also can't enter any configuration section anymore and some other functions stop working.
Could someone please advice how can I fix it?
I have created an incorrect NAS source (hostname not resolved) and can't change or delete it via web.
If I try to edit it and save changes, the web request to src-config.php always hangs. After that /var/log/mps/log is filled very fast with "client: Max connections reached" lines.
I also can't enter any configuration section anymore and some other functions stop working.
Could someone please advice how can I fix it?
Hi Adrian,
MPD status cmd is the only source for streaming bitrate. I'm thinking that either a bug or change in MPD but I'll have a look at the moOde code anyway.
You could try updating to 0.10.11. Just re-do STEP 7 starting with number 3, substitute 0.20.11 for 0.20.10.
Brew a pot of Coffee or Tea, take Dog for walk, etc while MPD compiles
-Tim
Hi Tim,
I'd mentioned the same issue to you privately a while back. Like you, I concluded that it was most likely a bug in mpd, reporting output bitrate rather than input bitrate. But I've looked no further.
Phil
I have a problem with Sources definition.
I have created an incorrect NAS source (hostname not resolved) and can't change or delete it via web.
If I try to edit it and save changes, the web request to src-config.php always hangs. After that /var/log/mps/log is filled very fast with "client: Max connections reached" lines.
I can't enter any configuration section anymore and some other functions stop working. How can I fix it?
Was about to mention this one. Replace moode sqlite db with the original and reconfigure.
Can replicate by creating an smb share and editing advanced parameters typing in garbage.
Phil
If this is happening w/moOde 4 I'll definitely have a look.
nvm, I see that when the mount flags are mangled the screen hangs.
Update: I've confirmed its a bug! Should be able to squash it for moOde 4 final release.
Workaround:
sudo sqlite3 /var/local/www/db/moode-sqlite3.db "select * from cfg_source"
Find the number corresponding to the bad NAS cfg, then substitute it for N below
sudo sqlite3 /var/local/www/db/moode-sqlite3.db "delete from cfg_source where id='N'"
sudo ./srestart.sh
-Tim
Last edited:
Hi Adrian,
MPD status cmd is the only source for streaming bitrate. I'm thinking that either a bug or change in MPD but I'll have a look at the moOde code anyway.
You could try updating to 0.10.11. Just re-do STEP 7 starting with number 3, substitute 0.20.11 for 0.20.10.
Brew a pot of Coffee or Tea, take Dog for walk, etc while MPD compiles
-Tim
Hi Tim - no change after update - still showing bitrate zero on status. Regards Adrian
Thank you Tim, you saved my day
Keep up your good work man
Well Gents,
This bug is one from the original code :-0 and is caused by blindly stuffing the error message retuned by the mount command into a SQL update! Goes without saying that this is a long overdue bugfix.
Errors from the mount cmd are not really that informative anyway so I think the best fix is to just report "Mount was unsuccessful, refer to moode.log for error message", and then write the actual message to moode.log.
So far this approach is passing my failure mode tests
-Tim