Volumio halted during update - now no http

Help and Support Help
1

Not sure which version of volumio I have - as www interface is down. Was upgrading from a March 2023 build to latest and volumio halted. I rebooted and have ssh access but no http access. mpd seems to be starting and the mpd.log shows no significant errors. Command line volumio commands and http just hang with no response. Volumio/mps processes running:

avahi      492  0.0  0.3   6156  3200 ?        Ss   20:41   0:00 avahi-daemon: running [volumio-1.local]
volumio    494  0.0  0.6  36464  6128 ?        Ssl  20:41   0:01 /usr/local/bin/volumio-remote-updater
root       834  0.0  0.6  12244  6548 ?        Ss   20:41   0:00 sshd: volumio [priv]
volumio    899  0.0  0.7  14608  7472 ?        Ss   20:41   0:00 /lib/systemd/systemd --user
volumio    900  0.0  0.1  16868  1808 ?        S    20:41   0:00 (sd-pam)
volumio    923  0.0  0.5  13152  5300 ?        S    20:41   0:00 sshd: volumio@pts/0
volumio    928  0.0  0.3   8192  3204 pts/0    Ss   20:41   0:00 -bash
volumio   1041  0.0  0.9 140368  9484 ?        Ssl  20:42   0:00 /usr/bin/upmpdcli -c /tmp/upmpdcli.conf
volumio   1153 99.9  9.6 228260 95832 ?        Rsl  20:56  20:59 /usr/bin/node /volumio/index.js
volumio   1202  0.0  2.7 112540 27160 ?        Sl   20:56   0:00 /usr/bin/node /volumio/app/plugins/miscellanea/albumart/serverStartup.js 3001 /data/albumart
volumio   1210  0.1  4.1 151540 41108 ?        Sl   20:56   0:01 /usr/bin/node /volumio/app/plugins/miscellanea/albumart/serverStartup.js 3001 /data/albumart
volumio   1211  0.1  4.1 151812 41268 ?        Sl   20:56   0:01 /usr/bin/node /volumio/app/plugins/miscellanea/albumart/serverStartup.js 3001 /data/albumart
volumio   1212  0.1  4.1 151780 41072 ?        Sl   20:56   0:01 /usr/bin/node /volumio/app/plugins/miscellanea/albumart/serverStartup.js 3001 /data/albumart
mpd       1292  0.1  3.5 189600 34736 ?        SLsl 20:56   0:01 /usr/bin/mpd --no-daemon

At this point I am stumped. Is there a way to recover from this? Or is it just hosed?

EDIT: updatesHistoryFile shows:

Sun Apr 30 2023 15:29:46 GMT+0000 (Coordinated Universal Time)
{"systemversion":"3.449","builddate":"Thu 30 Mar 2023 05:45:03 PM CEST","variant":"volumio","hardware":"pi"}

Suggesting the update did not complete. Is there a way to update directly from the git repo?

2

Hi,

If your still able to access the rpi via SSH, you can try executing the command:
node /volumio/logsubmit.js
and copy the response here. This will help us to see what is wrong.

There is also a way to perform the upgrade from SSH, however I would not suggest it as there is a reason the update failed. (like a bad SD)
volumio updater forceupdate

3

Thank you any help would be appreciated. Unfortunately, I cannot seem to attach the file to this post, so the full generated log file (~1MB) is at http://logs.volumio.org/volumio/S63l91K.html

In reviewing the log, it appears mpd could not initially bind to the port:

Sep 20 20:41:35 volumio-1.dredel.com volumio[852]: *** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
Sep 20 20:41:35 volumio-1.dredel.com volumio[852]: *** WARNING *** Please fix your application to use the native API of Avahi!
Sep 20 20:41:35 volumio-1.dredel.com volumio[852]: *** WARNING *** For more information see 
Sep 20 20:41:35 volumio-1.dredel.com node[852]: *** WARNING *** Please fix your application to use the native API of Avahi!
Sep 20 20:41:35 volumio-1.dredel.com node[852]: *** WARNING *** For more information see 
Sep 20 20:41:35 volumio-1.dredel.com node[852]: *** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
Sep 20 20:41:35 volumio-1.dredel.com node[852]: *** WARNING *** Please fix your application to use the native API of Avahi!
Sep 20 20:41:35 volumio-1.dredel.com node[852]: *** WARNING *** For more information see 
Sep 20 20:41:35 volumio-1.dredel.com volumio[852]: info: Applying required configuration parameters for plugin volumiodiscovery
Sep 20 20:41:35 volumio-1.dredel.com mpd[914]: Sep 20 20:41 : exception: Failed to bind to '[::]:6600'
Sep 20 20:41:35 volumio-1.dredel.com mpd[914]: Sep 20 20:41 : exception: nested: Failed to bind socket: Address already in use
Sep 20 20:41:35 volumio-1.dredel.com volumio[852]: info: Discovery: Started advertising with name: Volumio-1.dredel.com
Sep 20 20:41:35 volumio-1.dredel.com mpd[911]: Sep 20 20:41 : exception: Decoder plugin 'wildmidi' is unavailable: configuration file does not exist: /etc/timidity/timidity.cfg
Sep 20 20:41:35 volumio-1.dredel.com systemd[899]: mpd.service: Main process exited, code=exited, status=1/FAILURE
Sep 20 20:41:35 volumio-1.dredel.com systemd[899]: mpd.service: Failed with result 'exit-code'.
Sep 20 20:41:35 volumio-1.dredel.com systemd[899]: Failed to start Music Player Daemon.

However, this appears to be a previous error - as mpd is bound to 6600 in the running system. I am unfamiliar with the Avahi errors and I am not sure how critical they are to volumio. As a side note: all the volumio commands - such as ‘volumio status’ seem to simply hang and then return:

curl: (28) Failed to connect to 127.0.0.1 port 3000: Connection timed out

The recurrent error in the logs are:

volumio-remote-updater[494]: [2023-09-20 23:41:32] [error] handle_connect error: Timer Expired
volumio-remote-updater[494]: [2023-09-20 23:41:47] [info] Error getting remote endpoint: system:107 (Transport endpoint is not connected)

But this appears to be a symptom; rather than the problem.

Again, thank you for any assistance.

4

I think you need to take a new SD.
There are over 6000 errors related to:

Sep 21 08:39:03 volumio-1.dredel.com volumio-remote-updater[494]: [2023-09-21 08:39:03] [info] Error getting remote endpoint: system:107 (Transport endpoint is not connected)
Sep 21 08:39:03 volumio-1.dredel.com volumio-remote-updater[494]: [2023-09-21 08:39:03] [error] handle_connect error: Timer Expired
5

Is this typical of a filesystem failure? Without a doubt, the card is a couple of years old, but I didn’t see any r/w errors. I have another card that I prepped with the Volumio-3.512-2023-06-25-pi.img, but I was hoping to preserve my data - as I have a number of plugins and ~1TB of music files that would need to be re-indexed. Thanks for the suggestion. I will load the new card in and start rebuilding.