During the upgrade there was a crash of some kind. The device restarted and reverted to 25.7. Now, when trying to upgrade again I get the following:
***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 25.7 (amd64) at Mon Aug 4 15:13:10 UTC 2025
Fetching changelog information, please wait... done
Updating OPNsense repository catalogue...
Waiting for another process to update repository OPNsense
All repositories are up to date.
Checking integrity... done (0 conflicting)
Your packages are up to date.
Checking for upgrades (13 candidates): .......... done
Processing candidates (13 candidates): .......... done
Checking integrity...Assertion failed: (strcmp(uid, p->uid) != 0), function pkg_conflicts_check_local_path, file pkg_jobs_conflicts.c, line 315.
Child process pid=66704 terminated abnormally: Abort trap
***DONE***
I read other threads requesting a health audit. I tried that and there is a crash during the audit. Here is what was on the screen when the crash occurred:
***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 25.7 (amd64) at Mon Aug 4 15:19:00 UTC 2025
>>> Root file system: /dev/gpt/rootfs
>>> Check installed kernel version
Version 25.7 is correct.
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 25.7 is correct.
>>> Check for missing or altered base files
No problems detected.
>>> Check installed repositories
OPNsense (Priority: 11)
>>> Check installed plugins
os-ddclient 1.27_3
os-wol 2.5_1
>>> Check locked packages
No locks found.
>>> Check for missing package dependencies
Checking all packages: ....
I tried the cleanup audit recommended in other threads. It allowed the update to run again, but it fails with the following:
***GOT REQUEST TO UPDATE***
Currently running OPNsense 25.7 (amd64) at Mon Aug 4 15:45:09 UTC 2025
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Checking for upgrades (13 candidates): .......... done
Processing candidates (13 candidates): .......... done
The following 13 package(s) will be affected (of 0 checked):
Installed packages to be UPGRADED:
boost-libs: 1.88.0_1 -> 1.88.0_2
curl: 8.14.1 -> 8.15.0
ivykis: 0.43.2 -> 0.43.2_1
jq: 1.8.0 -> 1.8.1
libucl: 0.9.2_1 -> 0.9.2_2
nss: 3.113.1_1 -> 3.114
opnsense: 25.7 -> 25.7.1_1
os-ddclient: 1.27_3 -> 1.27_4
os-wol: 2.5_1 -> 2.5_3
py311-duckdb: 1.3.1_1 -> 1.3.2
py311-s3transfer: 0.13.0 -> 0.13.1
sudo: 1.9.17p1 -> 1.9.17p2
syslog-ng: 4.8.2_3 -> 4.8.2_4
Number of packages to be upgraded: 13
36 MiB to be downloaded.
[1/13] Fetching boost-libs-1.88.0_2.pkg: .......... done
[2/13] Fetching nss-3.114.pkg: .......... done
[3/13] Fetching jq-1.8.1.pkg: .......... done
[4/13] Fetching syslog-ng-4.8.2_4.pkg: .......... done
[5/13] Fetching py311-s3transfer-0.13.1.pkg: .......... done
[6/13] Fetching ivykis-0.43.2_1.pkg: .......... done
[7/13] Fetching os-wol-2.5_3.pkg: . done
[8/13] Fetching curl-8.15.0.pkg: .......... done
[9/13] Fetching os-ddclient-1.27_4.pkg: .... done
[10/13] Fetching libucl-0.9.2_2.pkg: .......... done
[11/13] Fetching opnsense-25.7.1_1.pkg: .......... done
[12/13] Fetching py311-duckdb-1.3.2.pkg: .......... done
[13/13] Fetching sudo-1.9.17p2.pkg: .......... done
Checking integrity...Assertion failed: (strcmp(uid, p->uid) != 0), function pkg_conflicts_check_local_path, file pkg_jobs_conflicts.c, line 315.
Child process pid=7184 terminated abnormally: Abort trap
Starting web GUI...done.
***DONE***
May be worth reinstalling the "pkg" package and see if that helps. If not the package database may be damaged and "opnsense-bootstrap" could help.
Cheers,
Franco
Exactly the same problem !!!!!!
I have the same problem cant update past 25.7. Disaster. I have a CWWK N100, AliExpress box. Trier a fresh install, bare no plug ins and update to 25.7.1 crashs every thing. back to 25.7 works great up till then. Something in software not compatible. so I will stay at 25.7 and not update until there is a solution or have to go back to pfsense, not sure its better as i have not tested it. For me it seems to be a hardware software issue. playing with this for 2 days, driving me nuts. I have not seen many posts with this problem or any solution.