Upgrading to 16.7, known issues and workarounds

[nrf]

I just got the 16.7.6 update and still can't keep Intrusion Detection alive. And it seems to have spread to RADVD so now I don't get my ipv6 announcements and thus lost ipv6 to the web.

trying to keep it factual :(

[franco]

Check https://github.com/opnsense/core/issues/1273 for radvd issue. I think you mean 16.7.9?

[info@romanos.it]

Hello,
I use to update quite often and last update to last 16.7.x failed and I had to revert to previous vm snapshot which is:
OPNsense 16.1.20-amd64
FreeBSD 10.2-RELEASE-p19
OpenSSL 1.0.2h 3 May 2016

If I try to update again to 16.7, the process both from webpage and shell end with no success.

When I did by console it stops after migrating traffic shaper as you can see in the picture.

If I did by web manager it seems reboot but lock on  mounting the root disk.

Now I'm forced to stay on 16.1: any suggestion?
Do you need some kind of log to let you help me?

Please any help would be very appreciated.

SR

[franco]

Would you mind sending us the <TrafficShaper/> section of the /conf/config.xml file? Looks like an incompatible migration path we need to fix.

project AT opnsense DOT org

Thank you,
Franco

[info@romanos.it]

Hello franco,

Tha problem is in the actual 1.6.20 /conf/config.xml I have not that section, and if I try the upgrade the system froze and I cannot see if it is present.

The only think I hope can be usable is the upgrade->try to boot -> try to boot in single user mode to see what happens, but let me know what do you think about.

Thanks for your answer.

SR

[franco]

I think it all works, but locks the console when it's done. Can you access the web interface after the upgrade? If yes, go to System: Settings: Administration and reconfigure "primary console" and save.

[info@romanos.it]

I'm updating from console aving an ssh session opened: I'll let you know after the process end if I'm able to reboot and even to connect to webpage.
SR

[info@romanos.it]

Ok, here I'm: the upgrade from console locked as previous shown in the bitmap, and the section about traffic shaper is like this:
    <TrafficShaper version="1.0.1">
      <pipes/>
      <queues/>
      <rules/>
    </TrafficShaper>
  </OPNsense>
</opnsense>

then the xml file is closed.

I configured the primary console as vga and now I have again the login prompt:
Thwe web page say version is:
OPNsense 16.7.11_1-amd64
FreeBSD 10.2-RELEASE-p19
OpenSSL 1.0.2j 26 Sep 2016

Then I check and completed the upgrade via web interface and the fw rebooted successfully.

Now version is:
OPNsense 16.7.11_1-amd64
FreeBSD 10.3-RELEASE-p14
OpenSSL 1.0.2j 26 Sep 2016

Thanks a lot and let me know if you need any other details.

SR

[franco]

This looks like you're all done, great. Don't forget to snapshot. 8)

[info@romanos.it]

You got it bro!
Now I have two snapshot: the old one and the new one after the successful upgrade.
Both of them will be forgotten (not deleted) until next upgrade will fail :)
Thanks for your support!

[mmorev]

Hello. Just made a clean install and then upgraded to 16.7.13 through SSH. After reboot a console freezes right after displaying interface binding, but all services and ssh are ok. You can see in attached pictures. How I can fix a console?

[thebraz]

Hello,

from the web interface ( System ---Administration ) have you already tried to set Primary Console to VGA console?

[mmorev]

from the web interface ( System ---Administration ) have you already tried to set Primary Console to VGA console?

Worked, thanks! It was set to serial. But, upgrade procedure shouldn't change primary console, isn't it?

[franco]

This was a latent bug in the GUI for years. It would save "serial" by default, even though the default in FreeBSD is "vga". I recently removed safe-guards around it for a cleaner primary/secondary console workflow and then this surfaced.

Note that factory resets or reinstalls are not affected by this at all. :)


Cheers,
Franco