Lightsquid not working on New update
-
Look at the logs. And post them if you want any help. Crystal ball is broken.
-
yeah it hit me right after the post..
does this give a clue?
/status_services.php: The command '/usr/local/etc/rc.d/squid.sh stop' returned exit code '1', the output was ''
Jan 31 19:16:18 kernel pid 32384 (squid), uid 100: exited on signal 11
Jan 31 19:14:12 xinetd 15402 Reconfigured: new=0 old=1 dropped=0 (services)
Jan 31 19:14:12 xinetd 15402 readjusting service 6969-udp
Jan 31 19:14:12 xinetd 15402 Swapping defaults
Jan 31 19:14:12 xinetd 15402 Starting reconfiguration
Jan 31 19:14:12 php-fpm 9200 /rc.start_packages: [lightsquid] Updating cronjobs…
Jan 31 19:14:12 check_reload_status Syncing firewall
Jan 31 19:14:12 check_reload_status Syncing firewall
Jan 31 19:14:11 radiusd 57084 Ready to process requests.
Jan 31 19:14:11 radiusd 55640 Loaded virtual server <default>Jan 31 19:14:11 php-fpm 9200 /rc.start_packages: [lightsquid] Removing old cronjobs…
Jan 31 19:14:11 php-fpm 9200 /rc.start_packages: [lightsquid] Successfully created '/usr/local/etc/lightsquid/lightsquid.cfg' configuration file.
Jan 31 19:14:11 php-fpm 9200 /rc.start_packages: [lightsquid] Loaded default '/usr/local/etc/lightsquid/lightsquid.cfg.sample' configuration file.
Jan 31 19:14:11 radiusd 29430 Exiting normally.
Jan 31 19:14:11 radiusd 29430 Signalled to terminate
Jan 31 19:14:11 php-fpm 9200 /rc.start_packages: Checked cron job for /usr/bin/nice -n20 /usr/local/etc/rc.d/squidGuard_logrotate, no change needed
Jan 31 19:14:11 check_reload_status Reloading filter
Jan 31 19:14:10 php-fpm 9200 /rc.start_packages: [squid] Starting a proxy monitor script
Jan 31 19:14:10 php-fpm 9200 /rc.start_packages: [squid] Reloading for configuration sync…
Jan 31 19:14:09 xinetd 15402 Reconfigured: new=0 old=1 dropped=0 (services)
Jan 31 19:14:09 xinetd 15402 readjusting service 6969-udp
Jan 31 19:14:09 xinetd 15402 Swapping defaults
Jan 31 19:14:09 xinetd 15402 Starting reconfiguration
Jan 31 19:14:09 php-fpm 9200 /rc.start_packages: [squid] Stopping any running proxy monitors
Jan 31 19:14:09 php-fpm 9200 /rc.start_packages: [squid] Removing freshclam cronjob.
Jan 31 19:14:09 php-fpm 9200 /rc.start_packages: [squid] Antivirus features disabled.
Jan 31 19:14:09 php-fpm 9200 /rc.start_packages: Checked cron job for /usr/local/pkg/swapstate_check.php, no change needed
Jan 31 19:14:09 php-fpm 9200 /rc.start_packages: Checked cron job for /usr/local/sbin/squid -k rotate -f /usr/local/etc/squid/squid.conf, no change needed
Jan 31 19:14:09 php-fpm 9200 /rc.start_packages: [squid] Adding cronjobs …
Jan 31 19:14:08 php-fpm 9200 /rc.start_packages: [squid] - squid_resync function call pr:1 bp: rpc:no
Jan 31 19:14:08 check_reload_status Reloading filter
Jan 31 19:14:07 php-fpm 9200 /rc.start_packages: [squid] Starting a proxy monitor script
Jan 31 19:14:07 php-fpm 9200 /rc.start_packages: [squid] Reloading for configuration sync…
Jan 31 19:14:06 php-fpm 9200 /rc.start_packages: [squid] Stopping any running proxy monitors
Jan 31 19:14:06 php-fpm 9200 /rc.start_packages: [squid] Removing freshclam cronjob.
Jan 31 19:14:06 php-fpm 9200 /rc.start_packages: [squid] Antivirus features disabled.
Jan 31 19:14:06 php-fpm 9200 /rc.start_packages: Checked cron job for /usr/local/pkg/swapstate_check.php, no change needed
Jan 31 19:14:06 php-fpm 9200 /rc.start_packages: Checked cron job for /usr/local/sbin/squid -k rotate -f /usr/local/etc/squid/squid.conf, no change needed
Jan 31 19:14:06 php-fpm 9200 /rc.start_packages: [squid] Adding cronjobs …
Jan 31 19:14:05 php-fpm 9200 /rc.start_packages: [squid] - squid_resync function call pr:1 bp: rpc:no
Jan 31 19:14:05 php-fpm 9200 /rc.start_packages: Restarting/Starting all packages.
Jan 31 19:14:05 xinetd 15402 Reconfigured: new=0 old=1 dropped=0 (services)
Jan 31 19:14:05 xinetd 15402 readjusting service 6969-udp
Jan 31 19:14:05 xinetd 15402 Swapping defaults
Jan 31 19:14:05 xinetd 15402 Starting reconfiguration
Jan 31 19:14:04 check_reload_status Starting packages
Jan 31 19:14:04 check_reload_status Reloading filter
Jan 31 19:14:04 pkg pfSense-pkg-Lightsquid-3.0.5 installed
Jan 31 19:14:04 php /etc/rc.packages: Successfully installed package: Lightsquid.
Jan 31 19:14:03 php /etc/rc.packages: [lightsquid] Updating cronjobs…
Jan 31 19:14:03 check_reload_status Syncing firewall
Jan 31 19:14:03 php /etc/rc.packages: [lightsquid] Removing old cronjobs…
Jan 31 19:14:03 php /etc/rc.packages: [lightsquid] Successfully created '/usr/local/etc/lightsquid/lightsquid.cfg' configuration file.
Jan 31 19:14:03 php /etc/rc.packages: [lightsquid] Loaded default '/usr/local/etc/lightsquid/lightsquid.cfg.sample' configuration file.
Jan 31 19:14:03 check_reload_status Syncing firewall
Jan 31 19:14:03 php /etc/rc.packages: Beginning package installation for Lightsquid .
Jan 31 19:14:02 pkg lighttpd-1.4.39_1 installed
Jan 31 19:14:02 pkg lightsquid-1.8_4 installed
Jan 31 19:14:02 pkg p5-GD-2.56_2 installed
Jan 31 19:14:02 pkg libgd-2.1.0_7,1 installed
Jan 31 19:14:02 pkg tiff-4.0.6_2 installed
Jan 31 19:14:02 pkg freetype2-2.6.3 installed
Jan 31 19:14:02 pkg png-1.6.21 installed
Jan 31 19:14:02 pkg jbigkit-2.1_1 installed
Jan 31 19:14:02 pkg jpeg-turbo-1.4.2 installed
Jan 31 19:13:56 check_reload_status Syncing firewall
Jan 31 19:13:14 xinetd 15402 Reconfigured: new=0 old=1 dropped=0 (services)
Jan 31 19:13:14 xinetd 15402 readjusting service 6969-udp
Jan 31 19:13:14 xinetd 15402 Swapping defaults
Jan 31 19:13:14 xinetd 15402 Starting reconfiguration
Jan 31 19:13:13 radiusd 29430 Ready to process requests.
Jan 31 19:13:13 radiusd 29019 Loaded virtual server <default>Jan 31 19:13:13 radiusd 6696 Exiting normally.
Jan 31 19:13:13 radiusd 6696 Signalled to terminate</default></default> -
The only relevant thing I can see there is Squid crashing on SIGSEGV. Sounds like a HW issue to me (as in, bad RAM.)
Jan 31 19:16:18 kernel pid 32384 (squid), uid 100: exited on signal 11 -
Well Ram is easy to swap out but this machine has been running for a long time without issue plus I had upgraded another pfsense machine after I felt comfortable with the squid issue. LightSquid is doing exactly the same thing on that machine. Something is funny. Maybe I'll try going back to a good config and trying the updates again. Not sure.
-
Have you tried to simply re-save the configuration? Status - Squid Proxy Reports - Save.
>>> Upgrading pfSense-pkg-Lightsquid... 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 UPGRADED: pfSense-pkg-Lightsquid: 3.0.4_3 -> 3.0.5 [pfSense] Number of packages to be upgraded: 1 29 KiB to be downloaded. Fetching pfSense-pkg-Lightsquid-3.0.5.txz: ... done Checking integrity... done (0 conflicting) [1/1] Upgrading pfSense-pkg-Lightsquid from 3.0.4_3 to 3.0.5... [1/1] Extracting pfSense-pkg-Lightsquid-3.0.5: .......... done Removing Lightsquid components... Menu items... done. Services... done. Loading package instructions... Saving updated package information... overwrite! Loading package configuration... done. Configuring package components... Loading package instructions... Custom commands... Executing custom_php_install_command()... Remove any existing and create new hardlink for lightsquid lighttpd executable... done. Creating Lightsquid web server start-up script... done. Creating lightsquid web server config ... done. Starting lightsquid lighttpd Service... done. done. Executing custom_php_resync_config_command()...done. Menu items... done. Services... done. Writing configuration... done. Message from pfSense-pkg-Lightsquid-3.0.5: Please visit Status - Squid Proxy Reports - Settings and read the configuration and usage instructions. >>> Cleaning up cache... done. SuccessDid save the config, and it works just fine:
$ ps ax | grep 'lightsquid' 9561 - S 0:00.00 /usr/local/sbin/lighttpd_ls -f /var/etc/lightsquid/lighttpd_ls.conf $ sockstat | grep 7445 root lighttpd_l 9561 6 tcp4 *:7445 *:* root lighttpd_l 9561 7 tcp6 *:7445 *:* -
Check this if still not working. https://forum.pfsense.org/index.php?topic=124847.msg689514#msg689514
-
There was an update available this morning. It fixed the issue it seems. Thanks
-
Yeah, hooray… thanks for reporting back. Still kinda worried about Squid committing a SIGSEGV suicide. Would run memtest just in case. (Also, you sure are not running out of RAM?)
-
My Mem usage is right at 17% and steady. I'm running at about 85% upload capacity 24/7 for the last three weeks syncing data to Amazon cloud. It seems stable but I'm definitely going to test it out. I may just go ahead and replace as I have sticks all over the place. Thanks for noticing that.
-
Well, at least things work now. (I certainly won't be able to debug any SIGSEGV issues there, my experience is that it was a HW issue ~95% of time. If not RAM, then CPU overheating, or bad PSU with unstable voltage.) If it's a bug with Squid, you'd need to move this to Squid mailing list or generally upstream, nothing pfSene specific there.