"Danger. Unexpected error, check log for details" during 25.7.6 upgrade

Started by jonm, October 23, 2025, 05:18:07 PM

Previous topic - Next topic
Seen the same error message on both machines in the cluster, no Web error, the upgrade continued and  finished. One server rebooted, because of the bigger jump between upgrades, the on other (slave/backup) not. 
After the upgrade all services went up (except frr on slave, which is expected). I  made the health check, everything OK.

Only bad news is that some pages, mostly pages that lists something (activity, logs) are now slow and unresponsive, with the browser message that the page is slowing down the browser (seen very seldom before).

Worst of them was the firewall live log, applied the first correction as instructed in another thread and now is working better, or the "System/Diagnostics/Activity" screen, which blocks the page for some seconds (with the upper browser message), but finishes at the end.   

It's been about 24 hours since the hotfix went live and I haven't heard the issue is still happening. Incidentally, FreeBSD released pkg 2.4.0 which also includes this particular fix. So all of this went as expected.


Cheers,
Franco

Confirming I was able to successfully upgrade to 25.7.6 this morning.

Well, I've still got nothing but "403 Forbidden" in place of my webUI, and I am unable to actually log into the firewall whatsoever. It just doesn't accept my credentials/ssh keys anymore. Until I spend 5 hrs driving out to reload the box, about the only thing I can actually do is ping it. The good news is that it is still passing traffic, and I am able to remote in to the network behind it, so that removes a lot of the urgency from the task. Might have some time next weekend, I guess.

I am not getting a Dange notice.  But after updating to 25.7 I went to update to the latest an get this.
***GOT REQUEST TO UPDATE***
Currently running OPNsense 25.7 (amd64) at Fri Oct 31 04:30:14 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 (157 candidates): .......... done
Processing candidates (157 candidates): ...... done
Checking integrity...Assertion failed: (!STREQ(uid, p->uid)), function pkg_conflicts_check_local_path, file pkg_jobs_conflicts.c, line 317.
Child process pid=9219 terminated abnormally: Abort trap
Starting web GUI...done.
***DONE***

My system is still running so I am going to leave it for now thinking there is an issue with the update?  The first time it tried to update 90 packages and gut stuck on the third one.  It no longer does that.
Hope this helps
Robert

Quote from: franco on October 30, 2025, 11:26:20 AMIt's been about 24 hours since the hotfix went live and I haven't heard the issue is still happening. Incidentally, FreeBSD released pkg 2.4.0 which also includes this particular fix. So all of this went as expected.


Cheers,
Franco

Tried zhis morning on third, test virtual OPNsense server. The upgrade from 25.7 (base) to 25.7.6 finished without any problems or messages.
Tried to upgrade two production server in the cluster, alredy on 25.7.6, on both I got

Quote...
[1/1] Upgrading pkg from 2.3.1 to 2.3.1_1...
[1/1] Extracting pkg-2.3.1_1: .......... done
...

So I think the "problems" I described were before your intervention.