Squid cannot start after fresh install on latest 2.0 snapshots
-
nope not working on x64,
just switch to 32bit version,
but, if you are using PPTP VPN, forget it, after you enable VPN, its not working any more, until you disableVPN again :) -
I have squid 2.7.9-1 package installed in a vm pfsense. It runs, but performance is poor (there is an open thread for that too).
I have squid 2.7.9-2 package installed in another pfsense instance (hardware), and squid still exits on signal 6.
I see that 2.7.9-3 is now available, so will have to test that.
-
Looks like it's still got signal 6 issues. Seems no matter how it's compiled by the automated system (I've tried making several changes) it still has those issues for whatever reason, but when I compile it by hand, it works.
-
Yeah, I updated to the latest pakage version (1.2.9-3) in my amd64 vm and it's crashing again.
-
I am having a Squid issue using the latest amd64 pfSense-2.0-BETA4-20101002-1259.iso. Below is the error I am getting. I checked the squid.inc, squid.xml and squid.conf and all state user proxy and group proxy. If I chown -R squid:squid /var/squid then squid -z the cache is created and I can start squid. However if I make any change to the gui it will reset owner of /var/squid to proxy:proxy. I have only noticed this with the latest version of squid.
Any help would be greatly appreciated.
Thanks
Oct 3 00:27:34 php: /pkg_mgr_install.php: Creating squid cache subdirs in /var/squid/cache Oct 3 00:27:34 php: /pkg_mgr_install.php: The command '/usr/local/sbin/squid -k shutdown' returned exit code '1', the output was 'squid: ERROR: No running copy' Oct 3 00:27:39 php: /pkg_mgr_install.php: The command '/usr/local/sbin/squid -k kill' returned exit code '1', the output was 'squid: ERROR: No running copy' Oct 3 00:27:45 php: /pkg_mgr_install.php: Stopping any running proxy monitors Oct 3 00:27:46 php: /pkg_mgr_install.php: Starting Squid Oct 3 00:27:46 php: /pkg_mgr_install.php: Starting a proxy monitor script Oct 3 00:27:46 check_reload_status: reloading filter Oct 2 19:27:46 squid[51372]: Squid Parent: child process 51774 started Oct 2 19:27:46 squid[51774]: Cannot open '/var/squid/logs/access.log' for writing. The parent directory must be writeable by the user 'squid', which is the cache_effective_user set in squid.conf. Oct 2 19:27:46 squid[51372]: Squid Parent: child process 51774 exited due to signal 6 Oct 3 00:27:46 kernel: pid 51774 (squid), uid 100: exited on signal 6 Oct 3 00:27:47 php: /pkg_mgr_install.php: Reloading Squid for configuration sync Oct 3 00:27:47 php: /pkg_mgr_install.php: The command '/usr/local/sbin/squid -k reconfigure' returned exit code '1', the output was 'squid: ERROR: No running copy' Oct 3 00:27:47 check_reload_status: reloading filter Oct 3 00:27:47 php: /pkg_mgr_install.php: Reloading Squid for configuration sync Oct 3 00:27:47 php: /pkg_mgr_install.php: The command '/usr/local/sbin/squid -k reconfigure' returned exit code '1', the output was 'squid: ERROR: No running copy' -
That is the same error (signal 6 crash) that everyone else in this thread has. It's a known issue.
-
Thanks Jimp,
To the best of your knowledge is there a work around?
I am not a programmer but I would be happy to help with testing. Just let me know if there is anything i can do to help.
-
No, not right now. It's a problem with the package builder itself.
-
Hi, any update on this?
I really want to use squid but I don't want to switch to i386. -
I've been trying to work on it over the past couple days but haven't yet had any more luck/progress. It's still unclear why it is crashing in that manner, or which component/aspect of the build system is to blame for certain.
I haven't tried it yet this morning to see if the changes I made yesterday would have had any effect with the full automated build from overnight.
-
I would give it a try if it wouldn't totally wreck all http traffic (https is still fine though).
-
That's why I test it on a VM I use for development that has no LAN (unless I put another VM behind it) :-)
-
Hi, any update on this?
I really want to use squid but I don't want to switch to i386.i have 64bit machine, and i switch to 32bit version, and it works perfect for me.
try to swich to 32bit until guys solve this problem .regards
-
I've disabled the automated building of squid and replaced the bad file with a known good version, so this should be safe for now.
-
Great news. Thanks.
-
No go here, unfortunately.
Oct 20 16:41:53 squid[3030]: Exiting due to repeated, frequent failures Oct 20 16:41:53 kernel: pid 29106 (squid), uid 62: exited on signal 6 Oct 20 16:41:53 squid[3030]: Squid Parent: child process 29106 exited due to signal 6 Oct 20 16:41:53 squid[3030]: Squid Parent: child process 29106 started Oct 20 16:41:50 kernel: pid 28361 (squid), uid 62: exited on signal 6 Oct 20 16:41:50 squid[3030]: Squid Parent: child process 28361 exited due to signal 6 Oct 20 16:41:49 squid[3030]: Squid Parent: child process 28361 started Oct 20 16:41:46 kernel: pid 27840 (squid), uid 62: exited on signal 6 Oct 20 16:41:46 squid[3030]: Squid Parent: child process 27840 exited due to signal 6 Oct 20 16:41:46 squid[3030]: Squid Parent: child process 27840 started Oct 20 16:41:43 squid[3030]: Squid Parent: child process 27032 exited due to signal 6 Oct 20 16:41:43 kernel: pid 27032 (squid), uid 62: exited on signal 6 Oct 20 16:41:42 squid[3030]: Squid Parent: child process 27032 started Oct 20 16:41:39 kernel: pid 3267 (squid), uid 62: exited on signal 6 Oct 20 16:41:39 squid[3030]: Squid Parent: child process 3267 exited due to signal 6 Oct 20 16:41:39 check_reload_status: reloading filter Oct 20 16:41:39 squid[3030]: Squid Parent: child process 3267 started Oct 20 16:41:39 php: /pkg_edit.php: Starting Squid2.0-BETA4 (amd64)
built on Wed Oct 20 16:17:09 UTC 2010
FreeBSD 8.1-RELEASE-p1
CPU Type Intel(R) Xeon(R) CPU 5150 @ 2.66GHz
(virtual machine)
Updated squid within the last hour. -
Did you delete the package, and then install it again, or just hit the 'pkg' button? You may have to delete it first.
-
You're right, it started now. Thanks.
