Bug #4059
closedlibrary required by squid3 may be absent
0%
Description
I attempted a package install of 3.4.9_1 pkg 0.1. The install proceeds, but the subsequent start of the squid3 service fails, complaining "'Shared object "libmd5.so.0" not found, required by "squid"'":
Dec 2 11:11:37 php-fpm[32523]: /pkg_mgr_install.php: Beginning package installation for squid3 . Dec 2 11:11:38 check_reload_status: Syncing firewall Dec 2 11:14:43 check_reload_status: Syncing firewall Dec 2 11:14:44 php-fpm[32523]: /pkg_mgr_install.php: Stopping any running proxy monitors Dec 2 11:14:45 php-fpm[32523]: /pkg_mgr_install.php: Starting Squid Dec 2 11:14:45 php-fpm[32523]: /pkg_mgr_install.php: Starting a proxy monitor script Dec 2 11:14:45 check_reload_status: Reloading filter Dec 2 11:14:45 php-fpm[32523]: /pkg_mgr_install.php: [Squid] - Squid_resync function call pr: bp: rpc:no Dec 2 11:14:48 check_reload_status: Syncing firewall Dec 2 11:14:48 php-fpm[32523]: /pkg_mgr_install.php: Starting Squid Dec 2 11:14:48 php-fpm[32523]: /pkg_mgr_install.php: The command '/usr/pbi/squid-amd64/local/sbin/squid -f /usr/pbi/squid-amd64/local/etc/squid/squid.conf' returned exit code '1', the output was 'Shared object "libmd5.so.0" not found, required by "squid"' Dec 2 11:14:51 Squid_Alarm[86934]: Squid has exited. Reconfiguring filter. Dec 2 11:14:51 Squid_Alarm[87303]: Attempting restart... Dec 2 11:14:58 check_reload_status: Reloading filter Dec 2 11:14:58 php-fpm[32523]: /pkg_mgr_install.php: [Squid] - Squid_resync function call pr: bp: rpc:no Dec 2 11:15:00 php-fpm[32523]: /pkg_mgr_install.php: Starting Squid Dec 2 11:15:00 php-fpm[32523]: /pkg_mgr_install.php: The command '/usr/pbi/squid-amd64/local/sbin/squid -f /usr/pbi/squid-amd64/local/etc/squid/squid.conf' returned exit code '1', the output was 'Shared object "libmd5.so.0" not found, required by "squid"' Dec 2 11:15:10 check_reload_status: Reloading filter Dec 2 11:15:11 check_reload_status: Syncing firewall Dec 2 11:15:11 php-fpm[32523]: /pkg_mgr_install.php: Successfully installed package: squid3. Dec 2 11:15:11 check_reload_status: Reloading filter
Updated by John D about 10 years ago
I attempted a package install of squid3 (3.4.9_pkg 0.1). The install...
Updated by Dmitriy K about 10 years ago
This is an issue with incorrect symlinks. This issue is tracked in #4018.
Updated by Dmitriy K about 10 years ago
Just in case installed squid3 3.4 and it doesn't work:Dec 3 14:27:47 php-fpm[7738]: /pkg_mgr_install.php: The command '/usr/pbi/squid-amd64/local/sbin/squid -f /usr/pbi/squid-amd64/local/etc/squid/squid.conf' returned exit code '1', the output was 'Shared object "libmd5.so.0" not found, required by "squid"'
Dec 3 14:27:47 php-fpm[7738]: /pkg_mgr_install.php: Starting Squid
Dec 3 14:27:47 php-fpm[7738]: /pkg_mgr_install.php: The command '/usr/pbi/squid-amd64/local/sbin/squid -z -f /usr/pbi/squid-amd64/local/etc/squid/squid.conf' returned exit code '1', the output was 'Shared object "libmd5.so.0" not found, required by "squid"'
Dec 3 14:27:47 php-fpm[7738]: /pkg_mgr_install.php: The command '/usr/pbi/squid-amd64/local/sbin/squid -k kill -f /usr/pbi/squid-amd64/local/etc/squid/squid.conf' returned exit code '1', the output was 'Shared object "libmd5.so.0" not found, required by "squid"'
sigh
Updated by Chris Buechler about 10 years ago
- Category set to Squid
- Target version set to 2.2
the root issue from #4018 is fixed, this package has a separate issue.
Updated by Jim Thompson about 10 years ago
- Assignee set to Renato Botelho
Assigned to Renato for evaluation and possible fix, because: packages.
Updated by Chris Buechler about 10 years ago
- Status changed from New to Confirmed
Updated by Renato Botelho almost 10 years ago
- Status changed from Confirmed to Feedback
Please try pkg version 0.2.2
Updated by Chris Buechler almost 10 years ago
this seems to be working, will leave for others' confirmation.
Updated by Gerald Drausinger almost 10 years ago
Pfsense: 2.2-RC (amd64) built on Sat Jan 10 03:54:06 CST 2015
Squid: 3.4.10_2 pkg 0.2.2
Installation works fine for me, the "'Shared object "libmd5.so.0" not found, required by "squid"'" message don't appear in my logs.
Updated by Dmitriy K almost 10 years ago
I can confirm: Squid package is working. But looks like there is an another issue appeared: Squid package heats up my CPU very intensively even in idle (not in use) state.
ps -axwwvv | grep squid:
95505 R 0:30.57 127 127 0 4676 508 - 8 12.4 0.0 /usr/pbi/.pbime /usr/pbi/.mounts/squid-amd64 /usr/pbi/squid-amd64 /usr/local/libexec/squid/pinger /usr/local/www args
51162 S 3:09.32 0 127 0 12532 2108 - 4 13.2 0.1 /usr/pbi/.pbirun /usr/local/libexec/squid/log_file_daemon /var/log/squid/access.log
54196 R 3:09.14 127 127 0 2552 428 - 4 13.0 0.0 /usr/pbi/.pbirun /usr/local/libexec/squid/pinger
55258 S 0:30.90 0 127 0 12532 2108 - 4 12.5 0.1 /usr/pbi/.pbirun /usr/local/libexec/squid/unlinkd
ps -axwwvv | grep squid after few minutes:
51162 S 5:27.00 0 127 0 12532 2108 - 4 12.2 0.1 /usr/pbi/.pbirun /usr/local/libexec/squid/log_file_daemon /var/log/squid/access.log
54196 S 5:26.58 0 127 0 12532 2108 - 4 12.3 0.1 /usr/pbi/.pbirun /usr/local/libexec/squid/pinger
55258 S 2:47.25 0 127 0 12532 2108 - 4 12.7 0.1 /usr/pbi/.pbirun /usr/local/libexec/squid/unlinkd
95505 S 2:46.93 0 127 0 12532 2108 - 4 13.2 0.1 /usr/pbi/.pbirun /usr/local/libexec/squid/pinger
Updated by Dmitriy K almost 10 years ago
Forgot to mention: Stopping service doesn't kill squid processes:
php-fpm64022: /status_services.php: The command '/usr/local/etc/rc.d/squid.sh stop' returned exit code '1', the output was 'squid: No running copy'
ps -axwwvv | grep squid after service "stopped":
54196 R 5:55.15 127 127 0 16636 1752 - 8 12.9 0.0 /usr/pbi/.pbirun /usr/local/libexec/squid/pinger (.pbime)
51162 S 5:55.51 0 127 0 12532 2108 - 4 13.3 0.1 /usr/pbi/.pbirun /usr/local/libexec/squid/log_file_daemon /var/log/squid/access.log
55258 S 3:15.55 0 127 0 12532 2108 - 4 12.3 0.1 /usr/pbi/.pbirun /usr/local/libexec/squid/unlinkd
95505 S 3:15.18 0 127 0 12532 2108 - 4 12.3 0.1 /usr/pbi/.pbirun /usr/local/libexec/squid/pinger
Updated by John D almost 10 years ago
It looks like the problem originally reported in this issue has been resolved. Thank you, BB