It was upgrade time for a client at 4am this morning, I proceeded to upgrade each UT from 9.2.1 to 9.3.1. Everything went fine except for, on the most important box (the VPN server), it all went wrong.
The VPN fell down as normal during the update, but never came back. Internet access and DNS resolution at that UT functioned normally. Apache wouldn't let me in on any interface, so after letting it think about the update for four hours and VPN still wasn't up, I rebooted.
After reboot, apache worked, but the config password is refused; the password became the untangle default terminal password you can ask for in the forums. The rack is visually empty, and the first time wizard came up. What is awesome about it it is, the apps are indeed there as the VPN server+web filter functions at the moment. The config+apps is there, the rack visually is not. Tentative plan is to throw in a 9.2.1 CD, reload, install the apps, restore the 9.2.1 backup, then attempt upgrading again. Is that best practice? All other UTs happily upgraded to 9.3.1 from 9.2.1.
The VPN fell down as normal during the update, but never came back. Internet access and DNS resolution at that UT functioned normally. Apache wouldn't let me in on any interface, so after letting it think about the update for four hours and VPN still wasn't up, I rebooted.
After reboot, apache worked, but the config password is refused; the password became the untangle default terminal password you can ask for in the forums. The rack is visually empty, and the first time wizard came up. What is awesome about it it is, the apps are indeed there as the VPN server+web filter functions at the moment. The config+apps is there, the rack visually is not. Tentative plan is to throw in a 9.2.1 CD, reload, install the apps, restore the 9.2.1 backup, then attempt upgrading again. Is that best practice? All other UTs happily upgraded to 9.3.1 from 9.2.1.