No update possible to 23.7.2

[eszett]

Hello Community,
as already described in the topic I can not update to 23.7.2. Short description what happened.
I have pushed the update of the repo via the GUi. There is always a window with the new features. The message and update I canceled to pull a backup of the config before. This also worked. A short time later the machine was no longer accessible. After a reboot, I can no longer perform updates. It comes the error message "The release type "opnsense" is not available on this repository."

Code: [Select]

***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 23.7.1_3 at Sat Aug 26 12:03:00 CEST 2023
Fetching changelog information, please wait... done
self: No packages available to install matching 'opnsense'
***DONE***

But according to ChangeLog 23.7.2 should be installed. In the shell I can't do anything via pkg update or opnsense-update -f either.

Dear community, I need some support or help.
Thanks!

It is a phy. machine. Currently it is running, but on state 23.7.1

Addendum: Apparently my pkg database is shot. I can't even reinstall nano. A pkg update and upgrade is executed without a message. Also I can't display the installed packages.

[newsense]

What's the output for these commands ?

Code: [Select]

df -h

Code: [Select]

opnsense-update -u
Also need to see the health check, either from the Firmware section or press 12 in the console and answer h to the yes/no prompt

[eszett]

Thx for help 

Code: [Select]

root@opnsense:/ # df -h
Filesystem                  Size    Used   Avail Capacity  Mounted on
/dev/gpt/rootfs             454G    2.6G    415G     1%    /
devfs                       1.0K    1.0K      0B   100%    /dev
/dev/gpt/efifs              256M    1.7M    254M     1%    /boot/efi
devfs                       1.0K    1.0K      0B   100%    /var/dhcpd/dev
devfs                       1.0K    1.0K      0B   100%    /var/unbound/dev
/usr/local/lib/python3.9    454G    2.6G    415G     1%    /var/unbound/usr/local/lib/python3.9


Code: [Select]

root@opnsense:/ # opnsense-update -u
No known packages set to fetch was specified.
root@opnsense:/ #

this is option 12 output

Code: [Select]

Enter an option: 12

Fetching change log information, please wait... done

This will automatically fetch all available updates and apply them.

Proceed with this action? [y/N]: y

Nothing to do.
Starting web GUI...done.
Generating RRD graphs...done.
*
*
*


[newsense]

You need to answer h to the yes/no question

[eszett]

more ouput does not come

Code: [Select]

Fetching change log information, please wait... done

This will automatically fetch all available updates and apply them.

Proceed with this action? [y/N]: y

Nothing to do.
Starting web GUI...done.
Generating RRD graphs...done.

*** opnsense.myhome.lan: OPNsense 23.7.1_3 ***

 LAN (re0)       -> v4: 10.0.16.254/24
 OPT1 (ue0)      -> v4: 192.168.2.254/24
 WAN (igc0)      -> v4/DHCP4: 9x.xx.xx.xx/22
 WG1 (wg1)       -> v4: 10.11.0.1/24

 HTTPS: SHA256 18 55 ................................
 SSH:   SHA256 Bqk................................ (ECDSA)
 SSH:   SHA256 aUkUp............................ (ED25519)
 SSH:   SHA256 qoD3by............................(RSA)

  0) Logout                              7) Ping host
  1) Assign interfaces                   8) Shell
  2) Set interface IP address            9) pfTop
  3) Reset the root password            10) Firewall log
  4) Reset to factory defaults          11) Reload all services
  5) Power off system                   12) Update from console
  6) Reboot system                      13) Restore a backup

Enter an option:


Code: [Select]

Proceed with this action? [y/N]: h

>>> Check installed kernel version
Version 23.7.1 is correct.
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 23.7.1 is correct.
>>> Check for missing or altered base files
No problems detected.
>>> Check installed repositories
OPNsense
>>> Check installed plugins
No plugins found.
>>> Check locked packages
No locks found.
>>> Check for missing package dependencies
>>> Check for missing or altered package files
>>> Check for core packages consistency
Core package "opnsense" not known to package database.

Press any key to return to menu.


[Dantichrist]

Nevermind

[newsense]

Code: [Select]

Proceed with this action? [y/N]: h

>>> Check installed kernel version
Version 23.7.1 is correct.
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 23.7.1 is correct.
>>> Check for missing or altered base files
No problems detected.
>>> Check installed repositories
OPNsense
>>> Check installed plugins
No plugins found.
>>> Check locked packages
No locks found.
>>> Check for missing package dependencies
>>> Check for missing or altered package files
>>> Check for core packages consistency
Core package "opnsense" not known to package database.

Press any key to return to menu.


Looks clean, try this now and paste the output please:

Code: [Select]

opnsense-update -fur 23.7.2

[eszett]

unfortunately without success

Code: [Select]

root@opnsense:/ # opnsense-update -fur 23.7.2
Fetching packages-23.7.2-amd64.tar: ..[fetch: https://pkg.opnsense.org/FreeBSD:13:amd64/23.7/sets/packages-23.7.2-amd64.tar.sig: Not Found] failed, no signature found
the same commands with 23.7.1 worked and reboot

[newsense]

Try the -fiur switch instead.

-i will not verify the packages as there's something broken there, but if it completes then any missing bits should be repaired including signature verification for 23.7.3+

If you have a way of checking the output as the machine boots see if there's any message reporting the filesystem dirty, and check the smart data as well - should the hdd be dying.

[franco]

Why are we forcing (-f) insecure (-i) major (-u) updates on users? Let's try to stay away from opnsense-update -u here... -r doesn't even work without a release number

If the package database is damaged the only clean solution is to run a full bootstrap:

# opnsense-bootstrap

It will reinstall everything (avoiding a major upgrade wherever it may have taken the user) and keep all settings.


Cheers,
Franco

[newsense]

Thanks Franco, forgot about bootstrap (never had to use it either)

[eszett]

Why are we forcing (-f) insecure (-i) major (-u) updates on users? Let's try to stay away from opnsense-update -u here... -r doesn't even work without a release number

If the package database is damaged the only clean solution is to run a full bootstrap:

# opnsense-bootstrap

It will reinstall everything (avoiding a major upgrade wherever it may have taken the user) and keep all settings.


Cheers,
Franco

unfortunately does not work

Code: [Select]

root@opnsense:/ # opnsense-update -fiur 23.7.2
Fetching packages-23.7.2-amd64.tar: ..[fetch: https://pkg.opnsense.org/FreeBSD:13:amd64/23.7/sets/packages-23.7.2-amd64.tar: Not Found] failed, no update found
the file does not exist
https://pkg.opnsense.org/FreeBSD:13:amd64/23.7/sets/

can i run the bootstrap via ssh or do i need vga

[franco]

> unfortunately does not work

Precisely


Cheers,
Franco

[newsense]

can i run the bootstrap via ssh or do i need vga

ssh should be fine

[eszett]

Brief feedback on my problem. The opnsense-bootstrap command made the firewall unusable and I had to reinstall the system completely. The old installation gave error messages that the filesystem is corrupt.

I see it sportily and could immediately test my backup. Unfortunately, the packages have to be reinstalled. Is there a way to check the package dependency?

Thanks that helped me!