Status of upcoming in-place update for 6.2.1 --> 6.3.0

[Tim Curtis]

Hi,

Just a brief status of upcoming in-place update that upgrades moOde 6.2.1 to 6.3.0.

The first few test runs look very promising :-) The update takes about 15 minutes to complete and during the first part it will disconnect the Browser UI because of an update to PHP. Therefore its important to monitor this particular update via SSH command moodeutl -t to ensure it completes successfully.

Below is log output from one of the test runs.

Code:

20191004 185930 worker: Ready
20191009 111959 worker: Job installupd
20191009 111959 updater: Downloading update package r621-test2
20191009 112002 updater: Start 2019-10-02 update for moOde 6.2.1
20191009 112002 updater: ** Version check
20191009 112002 updater: ** Step 1-9: Update SQL tables
20191009 112003 updater: ** Step 2-9: Install Raspbian packages
20191009 112003 updater: ** Pkg 1-3: update and upgrade
20191009 112606 updater: ** Pkg 2-3: libgles2
20191009 112615 updater: ** Pkg 3-3: updated MPD dev libs
20191009 112629 updater: ** Step 3-9: Update binaries
20191009 112629 updater: ** Bin 1-6: rotenc_c
20191009 112629 updater: ** Bin 2-6: moodeutl
20191009 112629 updater: ** Bin 3-6: alsa-capabilities
20191009 112629 updater: ** Bin 4-6: install-wifi
20191009 112629 updater: ** Bin 5-6: MPD 0.20.23
20191009 112629 updater: ** Bin 6-6: MPD 0.21.15
20191009 112629 updater: ** Step 4-9: Fix radio station pls file layout
20191009 112641 updater: ** Step 5-9: Update moOde sources and configs
20191009 112719 updater: ** Step 6-9: Install Linux kernel 4.19.75 build #1270
20191009 113356 updater: ** Step 8-9: Install Edimax EW-7811Un fix
20191009 113356 updater: ** Step 7-9: Install drivers for Allo USBridge Signature
20191009 113357 updater: ** Step 9-9: Sync changes to disk
20191009 113400 updater: Update installed, REBOOT required

-Tim

[TheOldPresbyope]

Slight glitch.

Just ran the in-place update in moOde 6.2.1 running on an RPi3A.

Took a little less than 11 minutes over WiFi to my FiOS cable modem/router/AP.

Code:

20191010 095413 worker: Job installupd
20191010 095413 updater: Downloading update package r621
20191010 095419 updater: Start 2019-10-02 update for moOde 6.2.1
20191010 095419 updater: ** Version check
20191010 095419 updater: ** Step 1-9: Update SQL tables
20191010 095419 updater: ** Step 2-9: Install Raspbian packages
20191010 095419 updater: ** Pkg 1-3: update and upgrade
20191010 100227 updater: ** Pkg 2-3: libgles2
20191010 100237 updater: ** Pkg 3-3: updated MPD dev libs
20191010 100248 updater: ** Step 3-9: Update binaries
20191010 100248 updater: ** Bin 1-6: rotenc_c
20191010 100248 updater: ** Bin 2-6: moodeutl
20191010 100248 updater: ** Bin 3-6: alsa-capabilities
20191010 100248 updater: ** Bin 4-6: install-wifi
20191010 100248 updater: ** Bin 5-6: MPD 0.20.23
20191010 100249 updater: ** Bin 6-6: MPD 0.21.15
20191010 100249 updater: ** Step 4-9: Fix radio station pls file layout
20191010 100253 updater: ** Step 5-9: Update moOde sources and configs
20191010 100302 updater: ** Step 6-9: Install Linux kernel 4.19.75 build #1270
20191010 100453 updater: ** Step 8-9: Install Edimax EW-7811Un fix
20191010 100453 updater: ** Step 7-9: Install drivers for Allo USBridge Signature
20191010 100456 updater: ** Step 9-9: Sync changes to disk
20191010 100456 updater: Update installed, REBOOT required

Trouble is, following reboot, the RPi reappeared on my LAN as a WiFi client but the moOde UI isn't accessible and I can't SSH into it either. It doesn't show in the UPnP-verse either.

Powered off in preparation of moving it to another location where I could try a wired connection via a USB-Ethernet adapter. Couldn't find the adapter so powered back. Et voilà . The second reboot did the trick and 6.3 is up and running.

Regards,
Kent

[kit1cat]

up and running on my system, but took over 40 minutes via WiFi.

[Pieter]

Thanks for this. Updated 2 moOde setups with no issues at all.

Donated.

[Norbert]

Raspi 3B uptdated in 15min over WiFi.

No problems so far.

Thank you!!

[Malefoda]

Hi guys,
on my Pi3B no problem but on my Pi2B there is that error pop-up on start-up and the update shows Raspbian 10.0 when the Pi3B shows 10.1.
Nevertheless it will play fine both shared files and Internet radios. But that pops up on every boot/reboot.
What to do?


The error



On Pi2B


On the Pi3B...

Edit: the same message when the Pi3B starts! ='(

[Tim Curtis]

Did you monitor the update via SSH command moodeutl -t to verify that it completed successfully?

Post the Moode log.

[Malefoda]

I was away when started them all, when I was back the GUI was up on both asking to reboot IIRC, so I did.
How do I get the log Tim? moodeutl -l? The error message showed up with this very moodeult -l result:

Code:

20191010 220223 worker: MPD version   (0.20.23)
20191010 220223 worker: CPU governor  (performance)
20191010 220223 worker: USB boot not available
20191010 220224 worker: File system expanded
20191010 220224 worker: HDMI port off
20191010 220225 worker: File check (OK)
20191010 220225 worker: -- Network
20191010 220225 worker: eth0 exists
20191010 220225 worker: eth0 (192.168.34.17)
20191010 220225 worker: wlan0 does not exist
20191010 220225 worker: -- Audio
20191010 220225 worker: ALSA outputs unmuted
20191010 220225 worker: ALSA card number (0)
20191010 220225 worker: Audio output (I2S audio device)
20191010 220225 worker: Audio device (Allo DigiOne)
20191010 220226 worker: Supported audio formats (S16_LE, S24_LE)
20191010 220226 worker: ALSA mixer name (Digital)
20191010 220226 worker: MPD volume control (disabled)
20191010 220226 worker: Hdwr volume controller not detected
20191010 220226 worker: -- Services
20191010 220226 worker: Reset renderer active state
20191010 220227 worker: MPD conf updated
20191010 220227 worker: MPD started
20191010 220228 worker: MPD accepting connections
20191010 220228 worker: Configure MPD outputs
20191010 220229 worker: MPD output 1 ALSA default (on)
20191010 220229 worker: MPD output 2 ALSA crossfeed (off)
20191010 220229 worker: MPD output 3 ALSA parametric eq (off)
20191010 220229 worker: MPD output 4 ALSA graphic eq (off)
20191010 220229 worker: MPD output 5 ALSA polarity inversion (off)
20191010 220229 worker: MPD output 6 ALSA bluetooth (off)
20191010 220229 worker: MPD output 7 HTTP stream (off)
20191010 220229 worker: MPD crossfade (off)
20191010 220229 worker: Audio source (Local)
20191010 220229 worker: Output device (Local)
20191010 220229 worker: USB auto-mounter (udisks-glue)
20191010 220229 worker: -- Music sources
20191010 220229 worker: USB sources (none attached)
20191010 220230 worker: NAS and UPnP sources (mountall initiated)
20191010 220230 worker: -- Miscellaneous
20191010 220230 worker: Saved MPD vol level (0)
20191010 220230 worker: Preamp volume level (0)
20191010 220230 worker: MPD volume level (0) restored
20191010 220230 worker: ALSA volume level (None)
20191010 220230 worker: Auto-play (Off)
20191010 220230 worker: Maintenance interval (6 hrs)
20191010 220230 worker: Screen saver activation (Never)
20191010 220230 worker: Session permissions (OK)
20191010 220230 worker: Watchdog started
20191010 220230 worker: Ready

[Tim Curtis]

In my tests the UI completely disconnects during the first part of the update but it will return if the Browser is manually refreshed at a later point.

To print the Moode log run the following command from SSH.

Code:

moodeutl -l

or alternatively

Menu, Configure, System
Menu, System info

The Moode log is at the bottom of the System info dump

[Malefoda]

Ah sorry found how to access the log by myself (moodeutl ? to get them all), my bad I asked you to spoon feed. Sorry!
BTW,

In my tests the UI completely disconnects during the first part of the update but it will return if the Browser is manually refreshed at a later point.

means that I may have the UI but it was still working background?
I was lazy to backup the SD card, was lazy to read... I pay the price

I don't know what to look for in that log but I don't see any reason/fail/problem in these lines... But the error happens on both systems.