RE: [squid-users] Squid3 and authenticating users SASL/MYSQL

> From: Amos Jeffries
> Sent: Saturday, May 01, 2010 2:16 AM


> > Finally, I opted for editing basic_db_auth (I would have opened it
> up even if I didn't need to change the @PERL@ and when I saw the my
> options in there, I figured that would be easiest route). However -
> and this may not be related, I'm getting a seg fault.
> >
>
> If you realy want to go that way, the "my" bit is only their
> definition.
> options are set later on after the documetation text.

Actually, I found that you can totally edit the definition block to fit the vagaries of one's particular DB. It's working like a charm!

Thanks!


> > /etc/init.d/squid3: line 32: 19094 Segmentation fault start-
> stop-daemon --quiet --start --pidfile $PIDFILE --exec $DAEMON --
> $SQUID_ARGS </dev/null
> > failed!
> >
>
> I'd guess the "helper crashing too fast" which happens when the
> helpers
> die on their own startup.

Thanks - this was because I'd followed the example in the file where the path was /usr/lib/squid3/libexec/auth* but in fact all the auth files (and where I'd logically placed the one I downloaded) were to be found in /usr/lib/squid3/

I have one other problem - I run webmin, and the port is 10000 - I added this to the SSL_ports, but I'm still getting this error:

[03/May/2010 20:46:14] 38.104.167.6 squiduser "CONNECT www.example.net:10000 HTTP/1.1" 503 0 "-" "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100401 Ubuntu/9.10 (karmic) Firefox/3.5.9 (.NET CLR 3.5.30729)" TCP_MISS:DIRECT

And then nothing loads. Prior to adding it to SSL_ports, I was getting a you're connecting to a proxy that isn't serving pages error, so I'm pretty sure adding it to the SSL ports was right - but what have I done wrong?

Thanks!

Simon


Received on Mon May 03 2010 - 20:00:46 MDT