Failed 20.7 upgrade (twice)

[DenverTech]

Got the 20.1.9_1 patch the other day with no problem, nor have I ever had a patch fail before. Went to install the 20.7 upgrade and it took a bit of time, then finished successfully. Firewall came up, internet came up...then went down. I thought maybe it was a second required reboot, but then it came up, went down again.

Jumped over to console and found that once the firewall reached login, it stayed working fine for about 30 seconds, then spammed a few dozen pages of white text (too fast to grab any info), and rebooted. Over and over. Restored old copy, upgraded, same thing. Meanwhile, another firewall (same hardware and general config) is fine on 20.7.

Ended up having to restore back to 20.1.9_1. I'll update this post if I can duplicate the problem and grab text/logs.

[hushcoden]

what's the hardware?

[franco]

Sensei or IPS enabled maybe? Sounds like a latent kernel panic.


Cheers,
Franco

[DenverTech]

Hardware is vmware for this one (and the other one that did work, while two others that worked were supermicro servers).

IPS is enabled. This afternoon I'll try again with that off.

[airdatec]

Have the same issue, after Update to 20.7 i got a Reboot loop with some unreadable (to fast) fancy pink text. i tried with the alternative Kernel but couldnt reach the web gui oder login on console with old credentials. So i restored to 19.1 (Acronis VM Backup) and push back my last config file.   

[zenlord]

I believe I can chime in: I enabled the 20.7 update in the GUI, then waited until some internet-dependent tasks had completed (20-30 minutes), and then clicked the 'start update' button.

An icon started spinning and I continued working on my laptop. Suddenly my Wi-Fi connection disappeared, and when I checked back on the installation status, the icon was still spinning.

Using a usb-to-serial modem cable, I was able to see a lot of gibberish and some incomplete words that sounded a lot like 'segmentation fault - core dump'. I reinstalled using a new USB image and imported the config. First update in 3 (/4?) years that goes wrong. Maybe it can be attributed to my session being broken at the moment I clicked 'start update'?

I am still puzzled why my access points (Ubiquiti) suddenly stopped accepting connections - If my gateway/firewall is down, I would expect the internal network to stay up  :-\

Kr,
Vincent

[newsense]

I am still puzzled why my access points (Ubiquiti) suddenly stopped accepting connections - If my gateway/firewall is down, I would expect the internal network to stay up  :-\

Kr,
Vincent

Networks will be up, however there's no inter-VLAN routing without the firewall.

[fruit]

Networks will be up, however there's no inter-VLAN routing without the firewall.

I don't have any VLANs and I lost my internal and external network during the upgrade. I have two interfaces bridged on a quad NIC .

My upgrade was successful.