OPNsense Forum

Archive => 17.7 Legacy Series => Topic started by: 727172 on October 23, 2017, 10:14:24 pm

Title: Failed Upgrade from 17.1
Post by: 727172 on October 23, 2017, 10:14:24 pm
Used the GUI to upgrade from 17.1.11 and after reboot the box did not appear to come back up.  I checked the console and there was login prompt but my credentials did not work.  I rebooted and it came back up and is routing properly but GUI and SSH are non-responsive.  I still have console access.

Should I kick off the upgrade from the console menu?  I'm concerned that whatever is broken will carry over to the new version.  Running option 11 (Reload all services) did not fix the GUI.

Thanks.
Title: Re: Failed Upgrade from 17.1
Post by: 727172 on October 23, 2017, 10:32:13 pm
Looking at the output of the console during boot, I see:
Shared object "libssl.so.39" not found, required by "lighttpd"
Title: Re: Failed Upgrade from 17.1
Post by: franco on October 23, 2017, 10:59:30 pm
If you have Internet, please rerun the update. Worst case fix up WAN with DHCP momentarily:

# dhclient em0

(em0 as a placeholder for your WAN NIC)

Current LibreSSL is libssl.so.43, 39 seems too old so the package install broke, maybe not enough space on the device?

Also run these and paste here for diagnosis:

# df -h
# uname -a
# freebsd-version -u


Cheers,
Franco
Title: Re: Failed Upgrade from 17.1
Post by: 727172 on October 24, 2017, 02:00:42 pm
Sent you some info in a PM.  Rerunning the update from the console failed and now Opnsense is not routing any traffic at this point and I'm down.
Title: Re: Failed Upgrade from 17.1
Post by: franco on October 24, 2017, 06:56:19 pm
You have landed on 17.7 for base and kernel. That's good. Your packages apply partially each time, that's not so good. Your free space seems a little low. This could mean:

1. Ports were installed manually via FreeBSD packages (not our mirror) or the ports tree.
2. Packages were locked, although opnsense-update should fix that nowadays.
3. Something else we need to see the error message for.

With regard to 3, do you have any error message before the web service reboot?

You shoud run these commands to inspect your packages for errors:

# pkg info | wc -l
# pkg check -da
# pkg check -sa

If you can restore internet with dhclient, you should run

# opnsense-update -fp

To reinstall all packages cleanly. But I don't want to get your hopes up, if it failed two times it may very well fail again unless we find the reason, or you could consider a config import on a live system using a newer image.


Cheers,
Franco
Title: Re: Failed Upgrade from 17.1
Post by: 727172 on October 26, 2017, 04:39:20 am
Thanks again for the help.  Had troubles getting a 17.1 image on a USB drive and I ended having to reinstall with a different product just to get back on the internet.  So are you saying I can restore my 17.1 configuration backup onto a fresh install of 17.7?  Because if so, that seems like my quickest way out of this.

For some reason I thought I had to install 17.1, restore configuration, and then upgrade to 17.7.
Title: Re: Failed Upgrade from 17.1
Post by: franco on October 26, 2017, 07:55:57 pm
Yes, 17.7 install + config.xml is fine.


Cheers,
Franco