Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - info@romanos.it

#1
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!
#2
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
#3
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
#4
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
#5
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