Squid: "Undefined symbol "_ZTVNSt3__117bad_function_callE" after upgrade to 2.8

KOM

@guilhermemulato That's why I'm not moving forward with 2.8.0 until they fix this issue.

ozpfsf

@kom that did not resolve the issue for me. Seeing a few other 2.8 gremlins - might look to downgrade for a bit.

KOM

Apparently just uninstalling then reinstalling squid will fix this issue. The new squid cleans up files left behind by old squid.

aGeekhere

Is this issue fixed if you reinstall squid after updating?

snow

@aGeekhere said in Squid: "Undefined symbol "_ZTVNSt3__117bad_function_callE" after upgrade to 2.8:

Is this issue fixed if you reinstall squid after updating?

Before reinstalling, you need to move the library so that it's no longer present in /usr/lib (e.g. by running "mv /usr/lib/libc++.so.1 /root").

See:
https://forum.netgate.com/topic/197595/now-available-pfsense-ce-2-8-0-release/7
https://forum.netgate.com/topic/195424/after-upgrade-to-24-11-squid-doesn-t-start/42

aGeekhere

@snow said in Squid: "Undefined symbol "_ZTVNSt3__117bad_function_callE" after upgrade to 2.8:

https://forum.netgate.com/topic/197595/now-available-pfsense-ce-2-8-0-release/7

Hmm so should the order be
uninstall squid,
update pfsense + reboot
mv /usr/lib/libc++.so.1 /root
install squid

snow

@aGeekhere

Yes, you can do it in the mentioned order.

KOM

@aGeekhere I just tried it. It does not fix the problem. I'm also not comfortable with the 'move lib somewhere else' fix as I don't know what side-effects it may have and I don't know how a future upgrade will handle it.

aGeekhere

@KOM Has the issue been added to the bug tracker?

KOM

@aGeekhere No idea.

aGeekhere

See https://redmine.pfsense.org/issues/16262

aGeekhere

@aGeekhere

Update, will not be fixed as squid is deprecated from pfSense

JonathanLee

@aGeekhere They just release Squid 7 and it is stable if you want to check it out

"The Squid HTTP Proxy team is very pleased to announce the availability
of the Squid-7.1 release!

This release is, we believe, stable enough for general production use.
We encourage all users of any previous major version of Squid to upgrade to it,
as well as users of beta version 7.0.X.

It can be downloaded from GitHub, at
https://github.com/squid-cache/squid/releases/tag/SQUID_7_1

Since version 6, Squid offers:

better support for overlapping IP ranges and wildcard domains in acl
countless security, portability, and documentation fixes

Since version 6, some previously deprecated features have been removed:

Edge Side Includes (ESI)
access to the cache manager using the cache_object:// scheme - use
http instead
the squdclient tool - use curl
http://<squid-address>/squid-internal-mgr/menu instead
the cachemgr.cgi tool
the purge tool - use the http PURGE method instead
Ident protocol support
basic_smb_lm_auth and ntlm_smb_lm_auth helpers - use Samba's
ntlm_auth instead

Further details can be found in the release notes and in the changelog

Please remember to run "squid -k parse" when testing the upgrade to a new
version of Squid. It will audit your configuration files and report
any identifiable issues the new release will have in your installation
before you "press go".

If you encounter any issues with this release please file a bug report at
https://bugs.squid-cache.org/

--
Francesco Chemolli

squid-users mailing list
squid-users@lists.squid-cache.org
https://lists.squid-cache.org/listinfo/squid-users"

I am having issues with this right now

"I got as far as this with the make clean install no matter what I do I can’t get this package installed. I have tried pkg install heimdal same error after install and pkg install krb5 and pkg install krb5-devel. I don’t know what I am doing wrong it does the make clean for a while and crashes for the bootstrap version the other one I could get going

ERROR:

checking whether S5L_CTX_sess_set_get_cb() callback accepts a const ID argument"
... yes checking
"whether X509_get0_signature() accepts const parameters"
... yes
checking whether the TXT_DB use OPENSSL_PSTRING data member... yes checking whether the squid workaround for buggy versions of sk_OPENSSL_PSTRING_V
alue should used... no
checking whether the workaround for OpenSSL IMPLEMENT_LHASH_
macros should used
... yes
configure: OpenSSL library support: yes -lcrypto -lss1 configure "Library -Kit-kros" support: no (auto)
/configure: LIBHEIMDAL_KRB5_PATH+=-L/usr/lib: not found /configure: LIBHEIMDAL_KRB5_CFLAGS+=-1/usr/include: not found checking for LIBHEIMDAL_KRB5... no
configure: error: Required library 'heimdal-krb5' not found
ニニニン
Script "configure" failed unexpectedly.
Please report the problem to timp87@gmail.com maintainerl and attach the
'/usr/ports/uuu/squid/uork/squid-7.1/config.log" including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system te.g. a /usr/local/sbin/pkg-static into -g -tal.
*** Error code 1
Stop.
makel1]: stopped in /usr/ports/www/squid
*** Error code 1
Stop.
make: stopped in /usr/ports/www/squid root@free:/usr/ports/www/squid #"

it gets so far along and fails with this error.

lan2021

@KOM said in Squid: "Undefined symbol "_ZTVNSt3__117bad_function_callE" after upgrade to 2.8:

I'm also not comfortable with the 'move lib somewhere else' fix as I don't know what side-effects it may have and I don't know how a future upgrade will handle it.

I have two pfSense with longer upgrade history running, came across the same problem when upgrading to 2.8 and my thoughts were exactly the same.

But then I was diving deeper and...

The upgraded one, after the upgrade:

# ls -l /usr/lib/libc++*
-r--r--r-- 1 root wheel 9415736 May 22 03:19 /usr/lib/libc++.a
-r--r--r-- 1 root wheel      48 May 22 03:19 /usr/lib/libc++.so
-r--r--r-- 1 root wheel  819952 Jan 31  2022 /usr/lib/libc++.so.1
-r--r--r-- 1 root wheel     952 May 22 03:19 /usr/lib/libc++experimental.a

The one still on 2.7.2 / FreeBSD 14:

# ls -l /usr/lib/libc++*
-r--r--r-- 1 root wheel 8603484 Dec  6  2023 /usr/lib/libc++.a
-r--r--r-- 1 root wheel      48 Dec  6  2023 /usr/lib/libc++.so
-r--r--r-- 1 root wheel  819952 Jan 31  2022 /usr/lib/libc++.so.1
-r--r--r-- 1 root wheel   87114 Dec  6  2023 /usr/lib/libc++experimental.a

And last, but not least a stock FreeBSD 14.0 REL-p4:

# ls -l /usr/lib/libc++*
-r--r--r-- 1 root wheel 8579844 Nov 10  2023 /usr/lib/libc++.a
-r--r--r-- 1 root wheel      48 Nov 10  2023 /usr/lib/libc++.so
-r--r--r-- 1 root wheel   86778 Nov 10  2023 /usr/lib/libc++experimental.a

As i see it, this libc++.so.1 as of 2022 must have been left back by an earlier update. Especially when looking at such a commonly used lib, I would speculate that the rm command used to remove it during this earlier update was using it itself and thus, was unable to remove it.

Knowing this, I followed the recommendation to just remove it (or move it away to /root), rebooted and everything works fine.

There is no need to un/reinstall squid. Just move away /usr/lib/libc++.so.1 and reboot. When updating from 2.7.2 or another FreeBSD 14 based release, it may also be an option to do this before starting the update to keep the downtime as short as possible.

And, coming back to the concern quoted initially: I beleive that it is very unlikely that anybody will miss this old lib.

Maybe somebody who upgraded an instance with less upgrade history can have a look in his /usr/lib and confirm that there is no libc++.so.1 at all.

smnolde

The same thing hit me when upgrading to 25.07.1 this morning. I moved libc++.so.1 to /root and squid started normally.

When I was experiencing the issue it looked like this in my system log:

/rc.filter_configure_sync: [squid] Installed but not started. Not installing 'nat' rules.
/rc.filter_configure_sync: [squid] Installed but not started. Not installing 'pfearly' rules.
/rc.filter_configure_sync: [squid] Installed but not started. Not installing 'filter' rules.
sshd[12272]: error: connect_to [interface_to_listen_on] port 3128: failed.
Squid_Alarm[34120]: Squid has exited. Reconfiguring filter.
Squid_Alarm[35230]: Attempting restart...

The sshd error is from my ssh connection where I tunnel my websurfing to my home router. Since squid wasn't listening on the specified port sshd could not make the connection.

All well now.