I have 2 Pi3s running Volumio 2.185. This evening I saw there was an update available and told one to update. It is hardwired to the network and has a Kali and Piano. After it finished successfully, I tried the other one. It is on WiFi and uses a cheap USB DAC dongle. It won’t update. When I click the “check for updates” button, nothing happens. I have tried from multiple machines, and browsers and restarted the Pi. Nothing I’ve tried has fixed it. Everything else seems to be working correctly.
I had a similar experience moving to the 2.185, but had also been changing other things and thought I might have caused the problem. I ended up downloading the 2.185 to a laptop and reloaded the SD card manually.
If there’s anything you’d like me to do before I wipe it, I’ve got time.
Yes, several times. Also rebooted each of the computers and the phone I used to access it. Tried both with the direct ip address and using the multi-player choices on the ui page.
Just tried again from my wife’s iPhone. With it, the color of the update button darkened a bit and stayed that color, but no other observable activity.
I’m not sure, but I think the updates are partly also hardware, respectively platform specific. E.g. if you run a PI with a Hifi Berry DAC+ you might get an update whereas you do not get it offered if your system configuration is different.
Interesting. I wonder what will happen if I swap SD cards and try to update? Oh wait, I think getting at the card in that kali/piano case is more work than just doing it manually. I’ll check when I get inside.
So it looks like it’s doing something, just not having it show up on the screen. Can’t SSH into the other one since that’s disabled on the new upgrade. The changelog says SSH can be turned back on in the UI. Can’t find it. Anyone help?
Jun 10 14:00:38 porchlumio volumio[884]: info: Sending updateCheck to server
Jun 10 14:00:39 porchlumio volumio-remote-updater[520]: updateCheck
Jun 10 14:00:39 porchlumio volumio-remote-updater[520]: Check for update request received.
Jun 10 14:00:39 porchlumio volumio-remote-updater[520]: [ ‘PRETTY_NAME=“Raspbian GNU/Linux 8 (jessie)”’,
Jun 10 14:00:39 porchlumio volumio-remote-updater[520]: ‘NAME=“Raspbian GNU/Linux”’,
Jun 10 14:00:39 porchlumio volumio-remote-updater[520]: ‘VERSION_ID=“8”’,
Jun 10 14:00:39 porchlumio volumio-remote-updater[520]: ‘VERSION=“8 (jessie)”’,
Jun 10 14:00:39 porchlumio volumio-remote-updater[520]: ‘ID=raspbian’,
Jun 10 14:00:39 porchlumio volumio-remote-updater[520]: ‘ID_LIKE=debian’,
Jun 10 14:00:39 porchlumio volumio-remote-updater[520]: ‘HOME_URL=“http://www.raspbian.org/”’,
Jun 10 14:00:39 porchlumio volumio-remote-updater[520]: ‘SUPPORT_URL=“http://www.raspbian.org/RaspbianForums”’,
Jun 10 14:00:39 porchlumio volumio-remote-updater[520]: ‘BUG_REPORT_URL=“http://www.raspbian.org/RaspbianBugs”’,
Jun 10 14:00:39 porchlumio volumio-remote-updater[520]: ‘VOLUMIO_BUILD_VERSION=“4d0e05d06d43b70ca3940cfea7893c18cb187ef9”’,
Jun 10 14:00:39 porchlumio volumio-remote-updater[520]: ‘VOLUMIO_FE_VERSION=“c4f90100dcdd22fc52b2fedb6e093b0b68b01363”’,
Jun 10 14:00:39 porchlumio volumio-remote-updater[520]: ‘VOLUMIO_BE_VERSION=“c21785b0877305c02ee26eb8fce7c92443d19e4c”’,
Jun 10 14:00:39 porchlumio volumio-remote-updater[520]: ‘VOLUMIO_ARCH=“arm”’,
Jun 10 14:00:39 porchlumio volumio-remote-updater[520]: ‘VOLUMIO_VARIANT=“volumio”’,
Jun 10 14:00:39 porchlumio volumio-remote-updater[520]: ‘VOLUMIO_TEST=“FALSE”’,
Jun 10 14:00:39 porchlumio volumio-remote-updater[520]: ‘VOLUMIO_BUILD_DATE=“Sat Jun 3 02:14:50 CEST 2017”’,
Jun 10 14:00:39 porchlumio volumio-remote-updater[520]: ‘’,
Jun 10 14:00:39 porchlumio volumio-remote-updater[520]: ‘VOLUMIO_VERSION=“2.185”’,
Jun 10 14:00:39 porchlumio volumio-remote-updater[520]: ‘VOLUMIO_HARDWARE=“pi”’,
Jun 10 14:00:39 porchlumio volumio-remote-updater[520]: ‘’ ]
Jun 10 14:00:39 porchlumio volumio-remote-updater[520]: No test mode
Jun 10 14:00:39 porchlumio volumio-remote-updater[520]: {“version”:“2.185”,“release”:“volumio”,“device”:“pi”,“test”:false}
Jun 10 14:00:45 porchlumio sudo[1113]: pam_unix(sudo:session): session closed for user root
Jun 10 14:00:52 porchlumio sudo[1154]: volumio : TTY=pts/0 ; PWD=/home/volumio ; USER=root ; COMMAND=/bin/journalctl -b -l
Jun 10 14:00:52 porchlumio sudo[1154]: pam_unix(sudo:session): session opened for user root by volumio(uid=0)
The Pi that won’t update thinks today is June 10. The one the does update thinks today is June 18 which is correct.
Also, when I ssh into them, the Pi that won’t update waits about 20 seconds before it asks for a password. The one with the latest version promps me for a pw immediately. Is that delay a security feature from the version when ssh defaulted on, or a sign that something has gone wonky?
Static IP is set within Volumio. I used to force it in router, but I think I turned that off. I’ll check.
DNS - If I changed that, it was accidental.
When you say “manually,” I’m not sure what you mean. I am not poking around in the terminal doing things with the command line.
Last update was done by
reloading the ISO to the SD card.
Boot
Use hotspot to change name to “Porchlumio” and setup wifi
Reboot
Use wifi network to fix IP, reboot.
Use wifi to find NAS and sync library.
Set up web radio stations manually (cut and paste urls into volumio radio page) but they did not work. (it’s not important to me so I ignored it.)
All setup was done within the volumio web interface except today when I started trying to sync the date through ssh.
I’m happy to reload it with the new ISO, but I’ve got time to fiddle with things and poke around if you need the info.
Sweet! That fixed it. Updates fine. Date and time synced correctly.
The gateway was not correct. I fixed it and made the changes to the DNS as you described.
Since the two Pis behave differently, I poked around some and discovered the hardwired one that was working is IP linked to it’s MAC address while the other is static from the Volumio. Is one way better than the other?