Several segmentation faults during upgrade

[zemanek]

OK, I switched VM from AMD EPYC to Intel Xeon with 4GB RAM and tried installing some small plugin (microcode-intel):

Code Select Expand

Number of packages to be installed: 6

The process will require 23 MiB more space.
[1/6] Installing pciids-20250309...
[1/6] Extracting pciids-20250309: ..... done
[2/6] Installing cpu-microcode-rc-1.0_2...
[2/6] Extracting cpu-microcode-rc-1.0_2: .... done
[3/6] Installing libpci-3.13.0...
[3/6] Extracting libpci-3.13.0: .......... done
Segmentation fault
[4/6] Installing x86info-1.31.s03_1...
[4/6] Extracting x86info-1.31.s03_1: ....... done
[5/6] Installing cpu-microcode-intel-20250211...
[5/6] Extracting cpu-microcode-intel-20250211: .......... done
[6/6] Installing os-cpu-microcode-intel-1.1...
[6/6] Extracting os-cpu-microcode-intel-1.1: .. done
Reloading firmware configuration
Ignoring invalid metadata: /usr/local/opnsense/version/opnsense
Writing firmware settings: FreeBSD OPNsense
Writing trust files...done.

Then uninstalled:

Code Select Expand

Number of packages to be removed: 5

The operation will free 23 MiB.
[1/5] Deinstalling x86info-1.31.s03_1...
[1/5] Deleting files for x86info-1.31.s03_1: ....... done
[2/5] Deinstalling libpci-3.13.0...
[2/5] Deleting files for libpci-3.13.0: .......... done
Segmentation fault
[3/5] Deinstalling cpu-microcode-intel-20250211...
[3/5] Deleting files for cpu-microcode-intel-20250211: .......... done
[4/5] Deinstalling pciids-20250309...
[4/5] Deleting files for pciids-20250309: ..... done
[5/5] Deinstalling cpu-microcode-rc-1.0_2...
[5/5] Deleting files for cpu-microcode-rc-1.0_2: .... done
***DONE***


[franco]

Patrick was suggesting the VM is wonky and I tend to agree because none of this makes sense:

> Ignoring invalid metadata: /usr/local/opnsense/version/opnsense


Cheers,
Franco

[zemanek]

The file contains just

Code Select Expand

18.7.1_3-445ae2139


[Patrick M. Hausen]

OK, I switched VM from AMD EPYC to Intel Xeon with 4GB RAM and tried installing some small plugin (microcode-intel):

You cannot perform a microcode update from inside a VM. If a microcode update is necessary it must be performed in the hypervisor host.

If your cloud provider is worth anything the probably have all of this in place. I made this suggestion (microcode update) initially because I assumed you were running on bare hardware.

So: what hypervisor is the provider using? KVM? Can you set the machine type to "q35" and the CPU type to "host"?

[zemanek]

So: what hypervisor is the provider using? KVM? Can you set the machine type to "q35" and the CPU type to "host"?

I don't know, I have no access to the hypervisor.


Anyway, I don't have any issues with these instances while they are running (VPN stable, ha-proxy working, ...) - well, for NOW -, just the upgrade/plugin installation is suspicious.

[franco]

The file contains just

Code Select Expand

18.7.1_3-445ae2139


Ok, that looks like a remnant that wasn't deleted in 2018 then.