Update to 23.1.8 got stuck

Started by pp, May 25, 2023, 03:19:38 PM

Previous topic - Next topic
I had the same issue, also running CrowdSec.

Stopping CrowdSec from the services page, or inside CrowdSec, or rebooting the firewall didn't work. The firewall not respond to even the reboot command.

Used putty to run SSH session and ran these two commands:

pgrep crowdsec
pkill -9 crowdsec


Firewall pending reboot then occurred. On restart, re-ran firewall upgrade whoich completed successfully.

Ran firewall health audit to check the upgrade and firewall health - passed.
System > Firmware > Status > Run an Audit - Health

Pretty much the same story here. Killed the bouncer process and the upgrade finished, seemingly successfully. Also ran the health audit with no problems detected.
Intel Celeron J4125 CPU @ 2GHz (4 cores), 8GB RAM, 4 Intel NICs

May 29, 2023, 12:30:14 AM #17 Last Edit: May 29, 2023, 12:55:03 AM by Julien
i cannot say i have the same issue.
but it keeps erroring during the update. DNS and everything else is working


i noticed the wireguard has stopped working and works only between 23.1.7_3 and not with 23.1.8



***GOT REQUEST TO CHECK FOR UPDATES***

Currently running OPNsense 23.1.7_3 at Mon May 29 00:00:08 CEST 2023

Fetching changelog information, please wait... fetch: transfer timed out

Updating OPNsense repository catalogue...

Fetching meta.conf: . done



and after changing mirro to AMD



***GOT REQUEST TO CHECK FOR UPDATES***

Currently running OPNsense 23.1.7_3 at Mon May 29 00:00:08 CEST 2023

Fetching changelog information, please wait... fetch: transfer timed out

Updating OPNsense repository catalogue...

Fetching meta.conf: . done

pkg: http://mirror.ams1.nl.leaseweb.net/opnsense/FreeBSD:13:amd64/23.1/latest/packagesite.pkg: Operation timed out





this just happens like this without changing anything.

the only think is the other boxes a re updated to 23.1.8


when i do audit connectivity
its comes back with this error

***GOT REQUEST TO AUDIT CONNECTIVITY***
Currently running OPNsense 23.1.7_3 at Mon May 29 00:53:18 CEST 2023
Checking connectivity for host: pkg.opnsense.org -> 89.149.222.99
PING 89.149.222.99 (89.149.222.99): 1500 data bytes

--- 89.149.222.99 ping statistics ---
4 packets transmitted, 0 packets received, 100.0% packet loss
Checking connectivity for repository (IPv4): https://pkg.opnsense.org/FreeBSD:13:amd64/23.1
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 822 packages processed.
All repositories are up to date.
Checking connectivity for host: pkg.opnsense.org -> 2001:1af8:5300:a010:1::1
ping: UDP connect: No route to host
Checking connectivity for repository (IPv6): https://pkg.opnsense.org/FreeBSD:13:amd64/23.1
Updating OPNsense repository catalogue...
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/23.1/latest/meta.txz: Non-recoverable resolver failure
repository OPNsense has no meta file, using default settings
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/23.1/latest/packagesite.pkg: Non-recoverable resolver failure
pkg: https://pkg.opnsense.org/FreeBSD:13:amd64/23.1/latest/packagesite.txz: Non-recoverable resolver failure
Unable to update repository OPNsense
Error updating repositories!
***DONE***
DEC4240 – OPNsense Owner

Seems like 23.1.9 fixed this issue as I was able to successfully upgrade on a environment that was failing and rolled back to the older release!