OPNsense Forum

Hi,

I did the trick with second search for updates after pkg was updated.
Update starts then like normal, but suddenly stucks and an Warning message appeard that the update failed.
Unfortunatley I don't know exactly where, but I think it was packet 4 of ..

Nothing works.

After a reboot I see the login prompt, but when I try to login, I get:

sh: /usr/local/libexec/opnsense-auth not found

and I'm not able to login.

Any idea?

Ok,

I booted into single user

used mount -u /
to make it writable

and created the file with

vi /usr/local/libexec/opnsense-auth
content:
#!/bin/sh

exit 0
Then

chmod 755 /usr/local/libexec/opnsense-auth
Now I can login after a normal boot.
But up to now no internet.

The core package is missing and I suspect this is because the new package manager screws up by removing the core package early and then failing on some dependency before putting the core package back, see https://forum.opnsense.org/index.php?topic=49423.0


Cheers,
Franco

I used

ifconfig bce3 192.168.0.123 netmask 255.255.255.0
and

route add default 192.168.0.254
And I'm back on net.
/etc/resolve was still ok.
Now I started with

pkg update -f
and

pkg upgrade
This works now as expected. ( At the moment [122/127] Extracting ruby-3.3.9.1)

Next I will check if opnsense-update is available, then I will give it a try.

> pkg upgrade

Do you have that particular output for me to prove the theory?


Cheers,
Franco

Hm...

opnsense-update
results in

QuoteMissing /usr/local/etc/pkg/repos/OPNsense.conf

I will try to create it by hand now.

Ups... there is no directory /usr/local/etc/pkg

mkdir /usr/local/etc/pkg
mkdir /usr/local/etc/pkg/repos
vi /usr/local/etc/pkg/repos/OPNsense.conf
with content:

QuoteOPNsense: {
  fingerprints: "/usr/local/etc/pkg/fingerprints/OPNsense",
  url: "https://pkg.opnsense.org/${ABI}/25.7/latest",
  signature_type: "fingerprints",
  priority: 11,
  enabled: yes
}

Now opnsense-update results in

QuoteNothing to do.

How can I force it?

Quote from: franco on October 24, 2025, 09:22:02 AM> pkg upgrade

Do you have that particular output for me to prove the theory?

Sorry, I'm at the console and can not copy anything.
But the FreeBSD upgrade worked without any problems.

Hm...

when I run

opnsense-update -gI get a log from the update before.
I attached it.

Can I run

opnsense-bootstrap.sh.in -r 25.7
Without loosing my (maybe) still available configuration of the interfaces and so on?

opnsense-update needs an argument. opnsense-bootstrap can help but you're simply suffering from a partial upgrade it seems and steamrolling over it is not the best approach yet.

I suspect all you need to do is this if the opnsense repo configuration is there again.

# pkg install opnsense
# pkg upgrade


Cheers,
Franco

Quote from: ednt on October 24, 2025, 09:57:24 AMHm...

when I run

Code Select Expand

opnsense-update -gI get a log from the update before.
I attached it.

That's only the long from the previous update:

Currently running OPNsense 25.7.4 (amd64) at Wed Oct 15 07:50:31 CEST 2025
[...]
opnsense: 25.7.4 -> 25.7.5

and it went completely fine

As written: the log is not the last log, but was the output of opnsense-update -g

pkg install opnsense
Was Ok.

First run of

pkg upgrade
results in a segmentation fault.

A second try is now running. ( [99/104] Extracting ruby-3.3.9.1)

System is up and running again with original configuration!

Thank you Franco for your help.

But I think a wait an additional week, before I update the Master.
Maybe you will find something to prevent this behaviour.


Btw. I don't think that the before mentioned segmentation fault is comming from a RAM error.
The system is a HP Server DL360 with ECC RAM and the iLO Management of the Server shows no RAM error.
Also the tests at start are Ok.

Question is when this segfault occurred, because I fixed one in pkg 2.3.1 that FreeBSD didn't fix and if you have the FreeBSD version that would explain a few things.


Cheers,
Franco

thank you so much for this thread, ednt.  i had the same issue with a partially updated system.  i followed the steps of faking out the opnsense-auth file, bringing up the network, creating the pkg/.../OPNsense.conf file, and finally "pkg install opnsense".

interesting issue.  when i ran "cleanup" from the audit option under firmware, the system ended up "cleaning up" the entire system.  i had to recover again.  it seems as though recovering this way doesn't remember what packages are needed in the base system.  how can i fix this going forward?

Quote from: franco on October 24, 2025, 09:01:49 AMThe core package is missing and I suspect this is because the new package manager screws up by removing the core package early and then failing on some dependency before putting the core package back, see https://forum.opnsense.org/index.php?topic=49423.0


Cheers,
Franco

After the oddity I posted in my recent thread, things to me do appear as fully updated without doing anything manually.

# pkg upgrade
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Checking for upgrades (101 candidates): 100%
Processing candidates (101 candidates): 100%
Checking integrity... done (0 conflicting)
Your packages are up to date.