moOde 5.4 Beta 1 is available

[Tim Curtis]

I can repro the issue with a freshly burned image after first boot.

After first boot the PHP session file is created but the permissions are not applied to the session dir :-0

Code:

pi@moode:~ $ ls -l /dev/shm
total 4
-rw------- 1 root root 18 Jul  3 10:11 sess_ho7vk67sqrjua8sme0pqhsjgdq

I think this is an "execution order" bug in worker.php. I'll investigate later today. It would also explain why moodecfg.txt had issues because it's invoked during the initial startup.

In the meantime it looks like a reboot right after initial power up is the workaround. Thereafter the permissions are correct and no issues.

-Tim

[philrandal]

Aha. @swizzle's comment about the db was on the mark. That combined with @jonners's mention of hostname problems reminded me that I changed the hostname in moodecfg.txt. That worked but apparently stuffed the db in the process. Beginning again with a fresh image and no moodecfg.txt is getting me farther. No "Local Input active" overlay to start and "Back" arrows properly linking.

The adventure continues.

Regards,
Kent

Added in post edit: To be precise, I changed all instances of the name [mM]oode to [mM]oode54b1 so I can't say it was the hostname change specifically that was the culprit.

That explains it.  I used a moodecfg.txt too.

Phil

[franz159]

@rh2018

Buster is compatible with earlier Pi versions. And probably no real benefit to 4gb at the moment but you never know what the future holds.

@TheOldPresbyope

This sounds like db weirdness, iirc moode keeps track of what url the back arrow points to in the db and the local input thing is tied to a particular hat that offers that feature. This may be a result of the new php version that required the memcache change.

I also experienced the "Local Input" situation described by @TheOldPresbyope, but only once. 
I re-flashed the SD card and the second time I did not have the problem.

Instead,  I'm experiencing problems with the MoodeUPNP service, which does not show up in Linn Kazoo. 
Any suggestion on how to debug via ssh?

Moreover

• the Spotify renderer does not work for me
  
• the squeezelite renderer does not work for me
  
• Airplay does work for me
  

-------------------
UPDATE:
After a couple of restart of the MoodeUPNP service or Squeezelite service I have them working now.

Therefore

• Moode UPNP OK
  
• squeezelite OK
  
• Airplay OK
  
• Spotify Not OK (for me, will test more!)
  

I'm using a USB DAC (Khadas Tone Board)

[philrandal]

That explains it.  I used a moodecfg.txt too.

Phil

Reflashed, edited moodecfg.txt to use moode54b1 as name, rebooted as soon as it came up, and all's good so far.

Currently running on a Pi 4 with HDMI output to my TV (audio and UI)..

Looking and sounding good.

Well done Tim and team.

Phil

[philrandal]

That explains it.  I used a moodecfg.txt too.

Phil

Reflashed, edited moodecfg.txt to use moode54b1 as name, rebooted as soon as it came up, and all's good so far.

Currently running on a Pi 4 with HDMI output to my TV (audio and UI)..

Looking and sounding good.

Well done Tim and team.

Phil

Code:

pi@moode:~ $ cat /var/log/moode.log
20190703 184936 worker: - Start
20190703 184936 worker: Successfully daemonized
20190703 184936 worker: Integrity check (passed)
20190703 184936 worker: ALSA volume set to (0%)
20190703 184937 worker: Session loaded
20190703 184937 worker: Debug logging (off)
20190703 184937 worker: - Platform
20190703 184938 worker: Rel  (Moode 5.4 2019-MM-DD)
20190703 184938 worker: Upd  (None)
20190703 184938 worker: Rasp (10.0)
20190703 184938 worker: Kern (4.19.56-v7l+)
20190703 184938 worker: MPD  (0.20.23)
20190703 184938 worker: Host (moode)
20190703 184938 worker: Hdwr (Pi-4B 2GB)
20190703 184938 worker: Arch (armv7l)
20190703 184938 worker: Gov  (performance)
20190703 184938 worker: USB boot not enabled yet
20190703 184938 worker: File system expanded
20190703 184938 worker: HDMI port on
20190703 184938 worker: File check ok
20190703 184938 worker: - Network
20190703 184938 worker: eth0 exists
20190703 184938 worker: eth0 address not assigned
20190703 184938 worker: wlan0 exists
20190703 184938 worker: wifi country (GB)
20190703 184938 worker: wlan0 trying SSID (xxxxxxx)
20190703 184938 worker: wlan0 (xxx.xxx.xxx.xxx)
20190703 184939 worker: - Audio
20190703 184939 worker: ALSA outputs unmuted
20190703 184939 worker: ALSA card number (0)
20190703 184939 worker: Audio output (On-board audio device)
20190703 184939 worker: ALSA mixer name (PCM)
20190703 184939 worker: MPD volume control (disabled)
20190703 184939 worker: Hdwr volume controller exists
20190703 184939 worker: - Services
20190703 184939 worker: Reset renderer active state
20190703 184939 worker: MPD conf updated
20190703 184939 worker: MPD started
20190703 184940 worker: MPD accepting connections
20190703 184940 worker: Configure MPD outputs
20190703 184940 worker: MPD output 1 ALSA default (on)
20190703 184940 worker: MPD output 2 ALSA crossfeed (off)
20190703 184940 worker: MPD output 3 ALSA parametric eq (off)
20190703 184940 worker: MPD output 4 ALSA graphic eq (off)
20190703 184940 worker: MPD output 5 ALSA polarity inversion (off)
20190703 184940 worker: MPD output 6 ALSA bluetooth (off)
20190703 184940 worker: MPD output 7 HTTP stream (off)
20190703 184940 worker: MPD crossfade (off)
20190703 184940 worker: Audio source (Local)
20190703 184940 worker: Output device (Local)
20190703 184940 worker: - Music sources
20190703 184940 worker: USB source (Elements)
20190703 184940 worker: NAS and UPnP sources (mountall initiated)
20190703 184940 worker: - Miscellaneous
20190703 184940 worker: Saved MPD vol level (0)
20190703 184940 worker: Preamp volume level (0)
20190703 184941 worker: MPD volume level (0) restored
20190703 184941 worker: ALSA volume level (100%)
20190703 184941 worker: Auto-play is off
20190703 184941 worker: LocalUI started
20190703 184941 worker: Maintenance interval (21600)
20190703 184941 worker: Screen saver activation (Never)
20190703 184941 worker: Watchdog started
20190703 184941 worker: Ready

Boot log edited to hide IP address and Wifi SSID.

[TheOldPresbyope]

@Tim Curtis

I think this is an "execution order" bug in worker.php. I'll investigate later today. It would also explain why moodecfg.txt had issues because it's invoked during the initial startup.

In the meantime it looks like a reboot right after initial power up is the workaround. Thereafter the permissions are correct and no issues.

Oh, sure, the old "reboot right after initial power up" trick. How many times have I heard that before

Seriously, it's "interesting" to see how bumps in major packages like PHP, Perl, Python, etc., can affect what we believed to be stable code. With all its possible settings and execution paths, the more people poke at moOde 5.4 in idiosyncratic ways, the sooner you'll be able to get it stable again.

Meanwhile, I'm enjoying the music now that I've got past this.

Regards,
Kent

[TheOldPresbyope]

Forgot to say I’m enjoying the music via the Spotify renderer fed from the Spotify App on my iPad.

[Tim Curtis]

Hi,

I've managed to fix the session handling bug in beta 1 :-)

Beta 2 will be available for download a bit later today :-)

-Tim