(04-24-2019, 10:22 AM)Tim Curtis Wrote:(04-24-2019, 06:31 AM)duke.g Wrote: Hello jfkdlsaiii,
after the In-Place-Update to Moode 5.1 I get the same picture as you get in Firefox, but I'm using Chrome!
My installation becomes unresponsive in the browser, i.e. if I click on configure I get the "start-window" for configuration, but nothing else opens. I tried a completely fresh install, but as soon as I apply the update to 5.1 the player is no longer usable.
Very strange. At the moment I have no clue.
Btw. I can ssh into the player without a problem. There it seems that the mpd-service is not started at all. If I start it manually I can seen the player (now-playing-page) but I still can not get into configuration.
duke.g
Reboot and then post contents of moOde log.
cat /var/log/moode.log
Hello Tim,
thank you for your response. Here is the output:
pi@moode:~ $ cat /var/log/moode.log
20190424 001354 worker: - Start
20190424 001354 worker: Successfully daemonized
20190424 001354 worker: Integrity check (failed)
20190424 001354 worker: Exited
That's all!
By the way, all was fine before the update. Moode worked in every browser I tested. I really don't know what is happening. If I install from scratch, moode 5.0 runs just fine. After I apply the update and reboot I get the described behavior.
Many thanks in advance
duke.g
Well, I think I found the problem. I've edited the worker.php in order to add the line:
// ensure certain files exist
if (!file_exists('/var/www/cover')) {sysCmd('ln -s /var/lib/mpd/music /var/www/cover');} NEW LINE
if (!file_exists('/var/local/www/currentsong.txt')) {sysCmd('touch /var/local/www/currentsong.txt');}
After that, the integrity check fails. That is a new behavior in 5.1!
Regards
duke.g
1x RPi 3B, 1x RPi 4, 1x RPi 5, Moode 9; 6k flac Songs; 180k MP3 Songs; Asset-UpnP 186k Songs
The blues has got a hold of me, I believe I'm gettin' dizzy - ZZ Top