Dear Colleagues,
After upgrading to Squid 4.1 (from FreeBSD ports) I started having problems
with Kerberos authentication.
A user complained about being denied access. The strange things are that:
1. There was only one such user, others seemed to be authenticating
properly (or just did not com
On 07/16/2018 05:08 PM, Gordon Hsiao wrote:
> On a x86/64bit ubuntu machine if I set 'workers 4' and run:
> squid --foreground -f /etc/squid.conf 2>&1 |grep mlock
> mlock(0x7f2e5bfb2000, 8) = 0
> mlock(0x7f2e5bf9f000, 73912) = -1 ENOMEM
> squid -N -f /etc/squid.conf
On a x86/64bit ubuntu machine if I set 'workers 4' and run:
squid --foreground -f /etc/squid.conf 2>&1 |grep mlock
mlock(0x7f2e5bfb2000, 8)= 0
mlock(0x7f2e5bf9f000, 73912)= -1 ENOMEM (Cannot allocate
memory)
squid -N -f /etc/squid.conf 2>& |grep mlock
mlock(0x7f8e
On 07/15/2018 08:47 PM, Gordon Hsiao wrote:
> Just upgraded squid to 4.1, however if I enabled shared_memory_locking I
> failed to start squid:
>
> "FATAL: shared_memory_locking on but failed to
> mlock(/squid-tls_session_cache.shm, 2101212): (12) Out of memory"
> How do I know how much memory it
Yaay :) :)
fixed in squid 4.1 stable.
Thank you squid team, you rock!
I'll not delete this request just in case someone else wonders :)
--
Sent from:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-Users-f1019091.html
___
squid-users m
I just realized squid stable 4.1 has been released. Will try it first then
report back if problem is till there!
--
Sent from:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-Users-f1019091.html
___
squid-users mailing list
squid-users@lists.
- Chrome 67.0.3396.99 erratic request behavior that evokes squid 4.0.21
TCP_DENIED_REPLY/403
- Problem exists only with ShutterStock, so far!
- Sample URL:
https://image.shutterstock.com/image-photo/chalk-rubbed-out-on-blackboard-260nw-523858522.jpg
- squid log of this URL GET...
For Firefox:
1
after increased shared memory(/dev/shm on linux), it does not help, still
don't know why mlock fails, or how much memory it needs to mlock to avoid
failing.
On Sun, Jul 15, 2018 at 9:47 PM Gordon Hsiao wrote:
> Just upgraded squid to 4.1, however if I enabled shared_memory_locking I
> failed to
