Undefined symbol "__libc_start1@FBSD_1.7" on pfSense Plus 23.01

sgw

tried to reinstall php stuff and gettext etc ... a mess

gui broken, can I roll back from cli?

stephenw10

Yes, you can using bectl. Or from the loader if you have console access.

First check what there is:

bectl list -s

sgw

@stephenw10

 bectl list -s
BE/Dataset/Snapshot    Active Mountpoint Space Created

default
  pfSense/ROOT/default NR     /          897M  2023-02-10 22:00

nothing else

sgw

Could I get some list of php-packages to reinstall maybe? That might fix something ...

Rolling back is not possible as far as I understand. Looks as if everything has been written into this first boot env.

thanks

stephenw10

Yup no BE snaps other than default, nothing to roll back to.

What pkg versions have you ended up with:

pkg-static info -x pfsense

sgw

@stephenw10 said in Undefined symbol "__libc_start1@FBSD_1.7" on pfSense Plus 23.01:

pkg-static info -x pfsense

# pkg-static info -x pfsense
pfSense-base-23.01
pfSense-boot-23.01
pfSense-default-config-serial-23.01
pfSense-kernel-pfSense-23.01
pfSense-pkg-aws-wizard-0.10
pfSense-pkg-ipsec-profile-wizard-1.1_1
pfSense-pkg-squid-0.4.46
pfSense-rc-23.01
pfSense-repo-23.01
pfSense-u-boot-1100-20220428
pfSense-u-boot-2100-20210930_1
pfSense-u-boot-env-20230123
pfSense-upgrade-1.0_62

thanks for your patience!

stephenw10

Ok those are old versions of pfSense-upgrade.

Try running: pkg-static upgrade pfSense-upgrade

Then try to run that again once it's updated.

sgw

@stephenw10

done:

pkg-static info -x pfsense
pfSense-base-23.01
pfSense-boot-23.01
pfSense-default-config-serial-23.01
pfSense-kernel-pfSense-23.01
pfSense-pkg-aws-wizard-0.10
pfSense-pkg-ipsec-profile-wizard-1.1_1
pfSense-pkg-squid-0.4.46
pfSense-rc-23.01
pfSense-repo-23.01
pfSense-u-boot-1100-20220428
pfSense-u-boot-2100-20210930_1
pfSense-u-boot-env-20230123
pfSense-upgrade-1.0_62
php81-pfSense-module-0.91

sgw

@sgw said in Undefined symbol "__libc_start1@FBSD_1.7" on pfSense Plus 23.01:

php81-pfSense-module-0.91

... comes from my attempts to "fix things".

I suggested the customer to send the appliance, will get his reply tmrw.

I think we can't trust it anymore, right now this:

*** Welcome to Netgate pfSense Plus 23.01-RELEASE (arm64) on xxx ***

Fatal error: Uncaught Error: Call to undefined function ctype_digit() in /etc/inc/util.inc:257
Stack trace:
#0 /etc/inc/interfaces.inc(162): is_numericint('4090')
#1 /etc/inc/interfaces.inc(247): vlan_valid_tag('4090')
#2 /etc/inc/interfaces.inc(5932): interface_is_vlan('mvneta0.4090')
#3 /etc/inc/interfaces.inc(6375): get_real_interface('mvneta0.4090')
#4 /etc/inc/interfaces.inc(6618): find_interface_ipv6('mvneta0.4090', false)
#5 /etc/rc.banner(147): get_interface_ipv6('wan')
#6 {main}
  thrown in /etc/inc/util.inc on line 257
PHP ERROR: Type: 1, File: /etc/inc/util.inc, Line: 257, Message: Uncaught Error: Call to undefined function ctype_digit() in /etc/inc/util.inc:257
Stack trace:
#0 /etc/inc/interfaces.inc(162): is_numericint('4090')
#1 /etc/inc/interfaces.inc(247): vlan_valid_tag('4090')
#2 /etc/inc/interfaces.inc(5932): interface_is_vlan('mvneta0.4090')
#3 /etc/inc/interfaces.inc(6375): get_real_interface('mvneta0.4090')
#4 /etc/inc/interfaces.inc(6618): find_interface_ipv6('mvneta0.4090', false)
#5 /etc/rc.banner(147): get_interface_ipv6('wan')
#6 {main}
  thrown
 0) Logout (SSH only)                  9) pfTop
 1) Assign Interfaces                 10) Filter Logs
 2) Set interface(s) IP address       11) Restart webConfigurator
 3) Reset webConfigurator password    12) PHP shell + Netgate pfSense Plus tools
 4) Reset to factory defaults         13) Update from console
 5) Reboot system                     14) Disable Secure Shell (sshd)
 6) Halt system                       15) Restore recent configuration
 7) Ping host                         16) Restart PHP-FPM
 8) Shell

stephenw10

Hmm, did it not offer an upgrade for pfSense-upgrade?

It's still looking at the 23.05 repo branch?

sgw

@stephenw10 it's looking at 23.01 (/usr/local/etc/pfSense/pkg/repos/pfSense-repo-prev.conf)

sgw

 pkg-static upgrade pfSense-upgrade
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
Your packages are up to date.

stephenw10

Ah, Ok if it's still looking at 23.01 it might be time to do a forced reinstall of all pkgs from that repo. It's not something I'd normally recommend but there may not be much else we can do here:
https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#forced-pkg-reinstall

sgw

@stephenw10

 pkg-static install -fy pkg pfSense-repo pfSense-upgrade
Updating pfSense-core repository catalogue...
pkg-static: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_aarch64-core/meta.txz: Bad Request
repository pfSense-core has no meta file, using default settings
pkg-static: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_aarch64-core/packagesite.pkg: Bad Request
pkg-static: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_aarch64-core/packagesite.txz: Bad Request
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_aarch64-pfSense_plus_v23_01/meta.txz: Bad Request
repository pfSense has no meta file, using default settings
pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_aarch64-pfSense_plus_v23_01/packagesite.pkg: Bad Request
pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_aarch64-pfSense_plus_v23_01/packagesite.txz: Bad Request
Unable to update repository pfSense
Error updating repositories!

even that fails now

sgw

Couldn't I "simply" scp/rsync some directories from a working appliance into the buggy one to make php work for now? I know it's ugly.

stephenw10

The user cert has expired. Updating that could be a problem if you can't run either pfSense-repoc or pfSense-upgrade -c

Where is this actually installed? Is there no way you can get remote hands on it to help with a re-install?

sgw

@stephenw10 We plugged in the other appliance yesterday and the box will be sent to me for reinstallation. Thanks to you for all your help.

MoonLight 0

Hello all,

I'm currently getting the same error you encountered on pfSense v23.01-RELEASE, I have the impression that pkg uses version 23.05.1 even though I haven't upgraded yet, here's some information:

pkg -d update
ld-elf.so.1: /usr/local/sbin/pkg: Undefined symbol "__libc_start1@FBSD_1.7"

pkg-static info pkg
pkg-1.19.1_1
Name           : pkg
Version        : 1.19.1_1
Installed on   : Tue May 23 16:54:08 2023 UTC
Origin         : ports-mgmt/pkg
Architecture   : FreeBSD:14:amd64
Prefix         : /usr/local
Categories     : ports-mgmt
Licenses       : BSD2CLAUSE
Maintainer     : pkg@FreeBSD.org
WWW            : https://github.com/freebsd/pkg
Comment        : Package manager
Options        :
	DOCS           : off
Shared Libs provided:
	libpkg.so.4
Annotations    :
	FreeBSD_version: 1400085
	build_timestamp: 2023-05-04T16:43:21+0000
	built_by       : poudriere-git-3.3.99.20220831
	port_checkout_unclean: no
	port_git_hash  : 38f48ce64acc
	ports_top_checkout_unclean: yes
	ports_top_git_hash: e7f28213b661
	repo_type      : binary
	repository     : pfSense
Flat size      : 34.1MiB
Description    :
Package management tool

WWW: https://github.com/freebsd/pkg

I tried to downgrade pkg:

pkg-static install -f pkg-1.18.4_4
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
pkg-static: No packages available to install matching 'pkg-1.18.4_4' have been found in the repositories

pkg-static install -f pkg
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be REINSTALLED:
	pkg-1.19.1_1 [pfSense]

Number of packages to be reinstalled: 1

9 MiB to be downloaded.

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

pkg.conf file:

ABI=FreeBSD:14:amd64
ALTABI=freebsd:14:x86:64
PKG_ENV {
	SSL_CA_CERT_FILE=/etc/ssl/netgate-ca.pem
	SSL_CLIENT_CERT_FILE=/usr/local/etc/pfSense/pkg/repos/pfSense-repo-stable-cert.pem
	SSL_CLIENT_KEY_FILE=/usr/local/etc/pfSense/pkg/repos/pfSense-repo-stable-key.pem
}

pfSense.conf file:

FreeBSD: { enabled: no }

pfSense-core: {
    url: "pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_05_1_amd64-core",
    mirror_type: "srv",
    signature_type: "fingerprints",
    fingerprints: "/usr/local/share/pfSense/keys/pkg",
    enabled: yes
}

pfSense: {
    url: "pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_05_1_amd64-pfSense_plus_v23_05_1",
    mirror_type: "srv",
    signature_type: "fingerprints",
    fingerprints: "/usr/local/share/pfSense/keys/pkg",
    enabled: yes
}

FreeBSD.conf file:

FreeBSD: { enabled: no  }

Could you please help me? Knowing that on the web interface, under System > Update I have:

Current Base System23.01

Thank you!

stephenw10

pkg will update itself to the newest available version whenever pfSense-upgrade is run and that happens when the dashboard update check happens.

So what you're seeing there is exactly what should happen in 23.01 and shouldn't be a problem. All the backend commands use pkg-static so never hit that library mismatch.

What problem are you actually seeing?

Steve

MoonLight 0

@stephenw10 Thank you for your quick reply!

I understand better now, so I should be able to use the pkg commands again once I've updated to version 23.05.1 via System > Update on the pfsense web gui right?

I'm working on a script and I wanted to reinstall the API with:

pkg -C /dev/null add https://github.com/jaredhendrickson13/pfsense-api/releases/latest/download/pfSense-2.7-pkg-API.pkg

But then this error occurred. So I guess I'll have to wait to update the pfsense first to continue.
Thank you.