Back on the Update thing: Success!
Digging through Github I found Elco did an update to the AVR firmware in July which I never captured. Thinking just maybe that was the problem I reflashed the first Uno. No change, same issues.
So I fired up the javascript console and after doing some digging I discovered that somewhere along the line the /var/www/brewpi1/userSettings.json file went missing in the updated web server repository. As soon as I copied that file from my backed up repository everything started working just fine.
I had two more BrewPi instances to update and decided to see if I could get through an update cleanly this time.
My second instance script repository is at /home/brewpi/brewpi2
My second instance www repository is at /var/www/brewpi2
After cloning both repositories...
to update the script repository:
cd /home/brewpi/brewpi2
sudo -u brewpi git pull
to update the web repository:
cd /var/www/brewpi2
sudo -u www-data git pull
Checked that these files were still present and matched the backed up versions:
/home/brewpi/brewpi2/settings/config.cfg
/var/www/brewpi2/userSettings.json
/var/www/brewpi2/config_user.php
Run the fix permissions script on this instance:
cd /home/brewpi/brewpi2/utils
sudo bash fixPermissions.sh
Launched a Chrome window on my peecee and got right into the second BrewPi instance, which by then was already running (I never stopped the script). All panes and panels are fully functional.
Repeated for third instance with same success.
So...I agree with Elco: don't use the canned update script. Use git pulls, it's wicked fast, doesn't invoke what looked like a global package update, and it works! :rockin:
Cheers!
[edit/ps] Forgot to note: I verified that I can now run BrewPi sans any network connection and have everything work as expected. That said, it took so long for Chromium to fill out the full BrewPi gui on the local console that I had my doubts.
[edit/pps] I should note that just for grins I updated the second Uno's firmware before I updated it's BrewPi software instance (scripts and www repositories) and that worked just fine, the BrewPi-Uno dialog had no issues at all.
Digging through Github I found Elco did an update to the AVR firmware in July which I never captured. Thinking just maybe that was the problem I reflashed the first Uno. No change, same issues.
So I fired up the javascript console and after doing some digging I discovered that somewhere along the line the /var/www/brewpi1/userSettings.json file went missing in the updated web server repository. As soon as I copied that file from my backed up repository everything started working just fine.
I had two more BrewPi instances to update and decided to see if I could get through an update cleanly this time.
My second instance script repository is at /home/brewpi/brewpi2
My second instance www repository is at /var/www/brewpi2
After cloning both repositories...
to update the script repository:
cd /home/brewpi/brewpi2
sudo -u brewpi git pull
to update the web repository:
cd /var/www/brewpi2
sudo -u www-data git pull
Checked that these files were still present and matched the backed up versions:
/home/brewpi/brewpi2/settings/config.cfg
/var/www/brewpi2/userSettings.json
/var/www/brewpi2/config_user.php
Run the fix permissions script on this instance:
cd /home/brewpi/brewpi2/utils
sudo bash fixPermissions.sh
Launched a Chrome window on my peecee and got right into the second BrewPi instance, which by then was already running (I never stopped the script). All panes and panels are fully functional.
Repeated for third instance with same success.
So...I agree with Elco: don't use the canned update script. Use git pulls, it's wicked fast, doesn't invoke what looked like a global package update, and it works! :rockin:
Cheers!
[edit/ps] Forgot to note: I verified that I can now run BrewPi sans any network connection and have everything work as expected. That said, it took so long for Chromium to fill out the full BrewPi gui on the local console that I had my doubts.
[edit/pps] I should note that just for grins I updated the second Uno's firmware before I updated it's BrewPi software instance (scripts and www repositories) and that worked just fine, the BrewPi-Uno dialog had no issues at all.