Just making sure things are going as expected...
Earlier this showed the expected changes:
Checking integrity... done (1 conflicting)
- suricata-7.0.3 conflicts with suricata-stable-6.0.15 on /usr/local/bin/suricata
Checking integrity... done (0 conflicting)
Conflicts with the existing packages have been found.
One more solver iteration is needed to resolve them.
The following 25 package(s) will be affected (of 0 checked):
Installed packages to be REMOVED:
suricata-stable: 6.0.15
New packages to be INSTALLED:
suricata: 7.0.3
Installed packages to be UPGRADED:
boost-libs: 1.83.0_1 -> 1.84.0
clamav: 1.2.1_2,1 -> 1.3.0,1
crowdsec: 1.6.0 -> 1.6.0_1
crowdsec-firewall-bouncer: 0.0.28_2 -> 0.0.28_3
dnscrypt-proxy2: 2.0.45 -> 2.1.5_3
dnsmasq: 2.89_1,1 -> 2.90,1
kea: 2.4.1 -> 2.4.1_1
libidn2: 2.3.4_2 -> 2.3.7
libnghttp2: 1.58.0 -> 1.59.0
libucl: 0.8.2_1 -> 0.9.0
openvpn: 2.6.8_2 -> 2.6.9
opnsense: 24.1.1 -> 24.1.2
opnsense-update: 24.1 -> 24.1.2
os-dnscrypt-proxy: 1.14_1 -> 1.15
os-intrusion-detection-content-et-open: 1.0.2_1 -> 1.0.2_2
php82-phalcon: 5.3.1 -> 5.6.1
py39-pytz: 2023.3,1 -> 2024.1,1
py39-tzdata: 2023.4 -> 2024.1
radvd: 2.19_2 -> 2.19_3
sudo: 1.9.15p5_3 -> 1.9.15p5_4
telegraf: 1.29.4 -> 1.29.4_1
unbound: 1.19.0_1 -> 1.19.1
Installed packages to be REINSTALLED:
pkg-1.19.2_1
Number of packages to be removed: 1
Number of packages to be installed: 1
Number of packages to be upgraded: 22
Number of packages to be reinstalled: 1
How big is this / how long does this step take?
Fetching base-24.1.2-amd64.txz: ..............................................
It has been about 30 minutes or so on a 1 GB Fiber connection and the dots/pips keep showing up lol, just want to know I'm not caught in a loop, again, thank you for making such a powerful and useful tool/product!!
It is a rather tiny file of about 100+ Mbs, not sure what is going on...
https://pkg.opnsense.org/FreeBSD:13:amd64/24.1/sets/
Edit:
I wait for about 5 rows of "......." and I manually restarted, asked it to check for updates, and it updated the two base/kernel packages, and everything appears good to go.
Possibly unique hiccup? Not sure, but recoverable it appears!
I am experiencing the same condition. It was stuck on "Waiting for another process to update repository mimugmail" for awhile, then got past it to start the download ("35 MiB to be downloaded."). No update for 10 minutes or so after that message displayed. Rebooted, tried again and let it run a little longer. It failed with the following error: self: No packages available to install matching 'opnsense'
I am using https://pkg.opnsense.org/FreeBSD:13:amd64/24.1 as my mirror.
Update: Tried again and everything worked normally.
Mine's currently doing it. It ran all night. Got over 10k dots (half that count is spaces)...
cat /tmp/pkg_upgrade.progress | grep 'Fetching base' | cut -f2 -d\: | wc
1 1 20858
IDK what file name is used during the download process, but I can't find base-24.1.2-amd64.txz anywhere on the system. Poked around a bit with `du` and don't see anything absolutely massive. /var/log (mostly flowd.log*) and /usr are both pretty big, but I think that's generally expected.
Unfortunately on reboot it didn't come back online, so now I'll have to drag a monitor over there and figure out where in the boot process it's hanging.
A dot is merely a second, not a size unit. You can do the math here how fast the download is.
In most cases the fetch command keeps running because it's made believe the connection is still open and/or sending bytes even if that isn't the case. But it's not the box's fault per se because it's simply requesting a file over the WAN connection.
Cheers,
Franco
Quote from: franco on March 07, 2024, 04:24:33 PM
A dot is merely a second, not a size unit. You can do the math here how fast the download is.
Ok, good info. I'm not sure what happened. Space was slowly filling up, it had 300MB free when I rebooted, but I watched that drop from 325MB. But I do use
bectl for boot environment snapshots, and I see that both
/tmp,
/var/tmp, and
/var/log are included, so I think the shrinking space was simply because "a zfs snapshot existed" and "temp and log files are being written"
I'll try the upgrade again later.
I also got this when doing an update on a new, clean 24.1 system install. The very confusing part was at the end where it says it's installing 24.1.2.
Yet log messages above this showed Upgrading opnsense from 24.1 to 24.1.3_1.... And at the same time the console showed 24.1.3_1.
!!!!!!!!!!!! ATTENTION !!!!!!!!!!!!!!!
! A critical upgrade is in progress. !
! Please do not turn off the system. !
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Installing kernel-24.1.2-amd64.txz... done
Installing base-24.1.2-amd64.txz... done
Cleaning obsolete files... done
Please reboot.
***REBOOT***
> 24.1 to 24.1.3_1
> Installing kernel-24.1.2-amd64.txz... done
> Installing base-24.1.2-amd64.txz... done
Because kernel and base were issued in 24.1.2 and 24.1.3 doesn't have an update. It's how all packages work.
Cheers,
Franco