Unable to upgrade from OPNsense 21.1.9_1-amd64 to 21.7

[franco]

Mine showed an update to 21.1.9_1, not 21.1.8_2. Is the upgrade fix included in that version as well?

opnsense-update is 21.1.8_2 and opnsense is 21.1.9_1 ;)

[franco]

and it´s fetching since 20 Minutes?

It's rather impractical to comment on individual setup's ability to download files from the mirror. It's only a file transfer and issues like slow speed, proxy woes and so forth are not in our hands.


Cheers,
Franco

[Bonkerton]

So if under System:Firmware:Packages it shows these versions

base         21.1.8
kernel         21.1.8
opnsense      21.1.9_1
opnsense-update   21.1.8_2

the system should be ready for a trouble-free update?

[franco]

Except for the igb issue we are hunting down at the moment, yes.

We will replace the problematic kernel as soon as that is confirmed.


Cheers,
Franco

[CraigS]

Hi Franco,

Perhaps this helps.

I tried multiple times to update from 21.1.9_1 to 21.7 without success. Last try I left it overnight ie about 8 hours and did not finish. Just kept adding dots to the log.

Then I changed the mirror to OPNSense (HTTPS,Amsterdam,NL) and the upgrade completed in less than 5 minutes.

The mirror used to be LeaseWeb Amsterdam but I also tried Leaseweb Frankfurt without success.

Regards,
Craig

[hloiter]

Hi Franco,

is it now safe to update to OPNsense 21.7.1 with igb interfaces or it is better to install fresh?

My Firmware Packages:

base           21.1.8
kernel         21.1.8
opnsense                21.1.9_1
opnsense-update   21.1.8_2
opnsense-installer  21.7

I use a IPU662 with Intel i211AT Ethernet Controller from NRG Systems.

Regards,

hloiter

[franco]

Igb issue was i210 I think and has been fixed 3 days after 21.7 came out. As safe as it gets I presume.

Let me know how it went for you.


Cheers,
Franco

[hvleest]

HELP...
After my update to the latest version from 21.1.9 to 21.7, nothing happens. It rebooted after the update, then it was quiet. Connected it to mouse, keyboard and screen. Not even a bios on the display.
Connected it back in the network and tried to access it by ssh on the WAN and LAN ports. Ssh is enabled and worked previously. Unfortunally it doesn't allow me access.
Is there another way to access it by SSH?
Thx

[athurdent]

HELP...
After my update to the latest version from 21.1.9 to 21.7, nothing happens. It rebooted after the update, then it was quiet. Connected it to mouse, keyboard and screen. Not even a bios on the display.
Connected it back in the network and tried to access it by ssh on the WAN and LAN ports. Ssh is enabled and worked previously. Unfortunally it doesn't allow me access.
Is there another way to access it by SSH?
Thx

Sounds like a hardware problem if you don't even see the BIOS screen or boot messages.

[hvleest]

I connected a display on the HDMI, but it gave 'no signal' on both ports. Then connect a LAN cable on WAN. I can ping the IP (192.168.1.3), but can't connect to it as root. SSH is enabled, and worked in the past with my known password.
Is there a way to reset it to factory default? Without access to SSH?

[hvleest]

Also the default password opnsense does not work

HELP...
After my update to the latest version from 21.1.9 to 21.7, nothing happens. It rebooted after the update, then it was quiet. Connected it to mouse, keyboard and screen. Not even a bios on the display.
Connected it back in the network and tried to access it by ssh on the WAN and LAN ports. Ssh is enabled and worked previously. Unfortunally it doesn't allow me access.
Is there another way to access it by SSH?
Thx

Sounds like a hardware problem if you don't even see the BIOS screen or boot messages.

Also the default password opnsense does not work

[cookiemonster]

If you're locket out from the shell you might need to reinstall and import config. But you still need to be able to access a console to do that. What are you using as output, serial, VGA? It might be worth opening your own post.

[hloiter]

Igb issue was i210 I think and has been fixed 3 days after 21.7 came out. As safe as it gets I presume.

Let me know how it went for you.


Cheers,
Franco

Hi Franco,

today I updated to OPNsense 21.7.1.

Everything went without any problems.

Many thanks to the developers and the support here in the forum.

Regards,

hloiter

[jwketchum]

I also have problems upgrading from 21.1.9_1-amd64 to 21.7.  Upgrade (from web gui) fails at the beginning:
***GOT REQUEST TO UPGRADE***
Fetching packages-21.7-OpenSSL-amd64.tar: ............................... failed, no signature found
***DONE***
Mirror is LeaseWeb (HTTP, Washington, DC, US)
/var/cache/opnsense-update/.upgrade.log hasn't been touched since the upgrade to 21.1.
A new --empty-- directory was made today, apparently when I attempted the upgrade:
/var/cache/opnsense-update/71076
Still at 21.1.9_1, and apparently running without problems.
Not sure whether I should follow the revert process discussed on this thread -- my symptoms are a bit different. 
Please advise.
Running on firewall appliance with Atom CPU E3845 @ 1.91GHz (4 cores).
Thanks for your help.
****Update: Successfully upgraded to 21.7, then 21.7.1, after changing mirror to NYC*BUG (HTTP, New York, US)

[wleeb1010]

I am blocked from upgrading 21.1.9_1-amd64 to 21.7 and none of the workarounds listed in this thread are working.

As others have mentioned, when I attempt to upgrade from the GUI it fails:

Code Select Expand

***GOT REQUEST TO UPGRADE***
Fetching packages-21.7-OpenSSL-amd64.tar: ............................... failed, no signature found
***DONE***

When I attempt SSH into box and run  opnsense-revert -r 21.1.9_multi opnsense-update it fails:

Code Select Expand

root@OPNsense:~ # opnsense-revert -r 21.1.9_multi opnsense-update
Fetching opnsense-update.txz: ............................... failed
root@OPNsense:~ #

I confirmed that the edits defined here https://github.com/opnsense/update/commit/9abe08ee are present in the /usr/local/sbin/opnsense-update file:
LINES 501-504

Code Select Expand

elif ! diff -uq ${WORKDIR}/${PRODUCT}.conf ${ORIGIN}; then
    # rerun sync before there are any complaints
    ${PKG} update ${DO_FORCE}
fi
LINES 773-776

Code Select Expand

${TEE} ${LOGFILE} < ${PIPEFILE} &
if (${PKG} update -f -r ${PRODUCT} && \
    ${PKG} upgrade -fy -r ${PRODUCT}) > ${PIPEFILE} 2>&1; then
    # re-register local packages repository

Not sure where to go from here, any ideas Franco?