-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/01/2015 4:58 a.m., masterx81 wrote:
> Hi! I have squid/3.3.13 on a centos 6.5, configured with ntlm and
> kerberos auth. I'm having throubles to get work the http site
> ryanair.com. The dynamic content of the page (the find flights
> button and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/01/2015 10:35 a.m., Robert wrote:
> Dnia Czwartek, 15 Stycznia 2015 22:16 Yuri Voinov napisał(a)
>> Oh,
>>
>> of course - you must to warm up cache first also.
>>
>> :)
>>
>
> 1. warm up cache What the hell is that ? ;) , no Squid installatio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/01/2015 10:07 a.m., Robert wrote:
> Dnia Czwartek, 15 Stycznia 2015 12:54 Yuri Voinov
> napisał(a)
>>
> This URL
>
> http://www.squid-cache.org/Images/img4.jpg
>
> produces HIT on second query.
>
>
>
>> Ok, this is working - give TCP_MEM_H
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/01/2015 6:36 a.m., masterx81 wrote:
> I've also tried to add the domain ryanair.com to the domains that
> return DIRECT on the wpad file (for bypass squid), but also in this
> way that things on the site doesn't work.
I guess that means that you
Dnia Czwartek, 15 Stycznia 2015 22:16 Yuri Voinov napisał(a)
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Oh,
>
> of course - you must to warm up cache first also.
>
> :)
>
1. warm up cache
What the hell is that ? ;) , no Squid installation guide says about it, please
gi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oh,
of course - you must to warm up cache first also.
:)
16.01.2015 3:07, Robert ?:
> Dnia Czwartek, 15 Stycznia 2015 12:54 Yuri Voinov
> napisał(a)
>>
> This URL
>
> http://www.squid-cache.org/Images/img4.jpg
>
> produces HIT on second q
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
:)
First reason - HTTP headers. I.e, no cache. etc. You can override them
with refresh_patterns violations. :)
Second - dynamic generated content required some special works to be cached.
Note: not all dynamic content can be easy cached.
:)
16.0
Dnia Czwartek, 15 Stycznia 2015 12:54 Yuri Voinov napisał(a)
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> This URL
>
> http://www.squid-cache.org/Images/img4.jpg
>
> produces HIT on second query.
>
>
Ok, this is working - give TCP_MEM_HIT/200
But can anybody explain me why
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just tested on my proxy.
All works like charm.
May be, you block some JS?
15.01.2015 23:36, masterx81 пишет:
> I've also tried to add the domain ryanair.com to the domains that return
> DIRECT on the wpad file (for bypass squid), but also in this
I've also tried to add the domain ryanair.com to the domains that return
DIRECT on the wpad file (for bypass squid), but also in this way that things
on the site doesn't work.
They work only if i disable totally the proxy.
Any ideas? Thanks!
--
View this message in context:
http://squid-web-pro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It's opened already,
we need only details and confirmation.
http://bugs.squid-cache.org/show_bug.cgi?id=3775
Amos believe this is the same bug.
Will explore.
15.01.2015 22:07, FredB пишет:
>
>
>> This is not core file size issue, Fred.
>>
>> In
> This is not core file size issue, Fred.
>
> In SunOS core dumps produces by kernel, with uid=0.
>
> Root has unlimited limits set by default.
>
> On this server was running Squid 2 over three years and problems with
> dumps never occurred.
>
> So, the problem not in system settings.
>
> I'
Hi!
I have squid/3.3.13 on a centos 6.5, configured with ntlm and kerberos auth.
I'm having throubles to get work the http site ryanair.com.
The dynamic content of the page (the find flights button and the calendars,
that as far i can see are js+css) are not working (the calendars does not
open and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is not core file size issue, Fred.
In SunOS core dumps produces by kernel, with uid=0.
Root has unlimited limits set by default.
On this server was running Squid 2 over three years and problems with
dumps never occurred.
So, the problem not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
What I observed myself:
This event correlates with users network activity and massive cached
content output during peak hours.
In other hours it does not occurs.
I've checked all network infrastructure, configurations and see no stranges.
I can't
> root @ proxyhost /var/core # ulimit
> unlimited
>
This is not related with ulimit -c , please take a look at ulimit -a
"ulimit -c ulimited" in statupt script only set your core file size to
unlimited
___
squid-users mailing list
squid-users@lists
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
He does not even attempt to write the dump.
Just restarts, write to /var/adm/messages and squid.log and restarts.
15.01.2015 21:29, FredB пишет:
>
>> Squid not required unlimited limits to startup and normal work. In my
>> SMF startup method uses 1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Solaris 10. Initially squid runs by root. Squid 3 cannot be run via su -
squid -c "".
root @ proxyhost /var/core # ulimit
unlimited
In /var mountpoint I have 13 Gb free space:
rpool/ROOT/s10x_u11wos_24a/var 571M 13.3G 571M /var
:)
I'm neit
> Squid not required unlimited limits to startup and normal work. In my
> SMF startup method uses 128K values to limit filedescriptors during
> startup. System hard limits are above this value.
>
ulimit -c is only about core
___
squid-users mailing l
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Absolutely sure.
>
> root @ proxyhost /var/core # coreadm
> global core file pattern: /var/core/core.%f.%p
> global core file content: default
>init core file pattern: /var/core/core.%f.%p
>init core file content
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
15.01.2015 21:15, FredB пишет:
>
>
>
>> 2015/01/06 15:52:10 kid1| storeLateRelease: released 0 objects
>> 2015/01/06 15:52:11 kid1| assertion failed: comm.cc:178:
>> "fd_table[conn->fd].halfClosedReader != NULL"
>> 2015/01/06 15:52:15 kid1| Set Curr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Absolutely sure.
root @ proxyhost /var/core # coreadm
global core file pattern: /var/core/core.%f.%p
global core file content: default
init core file pattern: /var/core/core.%f.%p
init core file content: default
g
> 2015/01/06 15:52:10 kid1| storeLateRelease: released 0 objects
> 2015/01/06 15:52:11 kid1| assertion failed: comm.cc:178:
> "fd_table[conn->fd].halfClosedReader != NULL"
> 2015/01/06 15:52:15 kid1| Set Current Directory to /var/core
>
> Core dump not produced.
>
Are you sure about the right
>
> FI, I noticed a change between 3.3.x and 3.4
>
> fd_table[io.conn->fd].flags.socket_eof = 1;
>
> Becomes
>
> fd_table[io.conn->fd].flags.socket_eof = true;
>
> But as I said I haven't taken a look deeply
Sorry I forgot: in client_side.cc just before commMarkHalfClosed(io.conn->fd);
> Hash: SHA1
>
> With half_closed_clients by default (.i.e. off), the problem presist,
> but catch a bit another assertion.
>
FI, I noticed a change between 3.3.x and 3.4
fd_table[io.conn->fd].flags.socket_eof = 1;
Becomes
fd_table[io.conn->fd].flags.socket_eof = true;
But as I said I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
With half_closed_clients by default (.i.e. off), the problem presist,
but catch a bit another assertion.
15.01.2015 19:30, FredB пишет:
>>
>> When I set hals_closed_clients to on, I've got much more assertions:
>>
>> 2015/01/15 18:41:31 kid1| assert
Hi.
On 12.01.2015 19:06, Amos Jeffries wrote:
>
> I am confident that those types of leaks do not exist at al in Squid 3.4.
>
> These rounds of mmory exhaustion problems are caused by pseudo-leaks,
> where Squid incorrectly holds onto memory (has not forgotten it
> though) far longer than it shoul
>
> When I set hals_closed_clients to on, I've got much more assertions:
>
> 2015/01/15 18:41:31 kid1| assertion failed: comm.cc:1823: "isOpen(fd)
> &&
> !commHasHalfClosedMonitor(fd)"
>
There is a problem with one assertion (or both)
Bug: http://bugs.squid-cache.org/show_bug.cgi?id=4156
With
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Core dumps is configured after OS installation - over 4 years ago. For
another processes they produces ok.
System has modular mebugger (MDB), but this is production system and
undesirable to run key service under debugger.
The same time this case i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/01/2015 1:50 a.m., Yuri Voinov wrote:
>
> Hi gents,
>
> Sometimes I have too much assertions:
>
> 2015/01/08 09:40:39 kid1| assertion failed: comm.cc:178:
> "fd_table[conn->fd].halfClosedReader != NULL"
>
> Core dump not produced but Squid r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/01/2015 1:43 a.m., gehrer.a wrote:
> Try on a pfsense with squid 3.4.10 an ntlm-authentication. In my
> suid.conf: /auth_param ntlm program /usr/local/bin/ntlm_auth
> --helper-protocol=squid-2.5-ntlmssp/ When I restart squid I always
> see this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi gents,
Sometimes I have too much assertions:
2015/01/08 09:40:39 kid1| assertion failed: comm.cc:178:
"fd_table[conn->fd].halfClosedReader != NULL"
Core dump not produced but Squid restarts. So, I can't get stack trace.
When I set hals_closed_
Try on a pfsense with squid 3.4.10 an ntlm-authentication.
In my suid.conf:
/auth_param ntlm program /usr/local/bin/ntlm_auth
--helper-protocol=squid-2.5-ntlmssp/
When I restart squid I always see this in my syslog:
Jan 15 13:38:35 pf4322 squid: auth_param ntlm program
/usr/local/bin/ntlm_auth: (2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/01/2015 3:44 a.m., Dr. Lars Hanke wrote:
> Hi Eliezer:
>
>> There are couple aspects to the issue. The options are: - TOS
>> marking of specific connections - TPROXY(leaving the src IP the
>> same) - delay_pools
>>
>> If you have a shaping setu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I.e,
easy way to identify problem URL does not exists. Excluding user complaints.
Right?
I thinking about correllation analyses between access.log and cache.log. ;)
15.01.2015 17:23, Amos Jeffries пишет:
> On 16/01/2015 12:14 a.m., Yuri Voinov w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This URL
http://www.squid-cache.org/Images/img4.jpg
produces HIT on second query.
15.01.2015 17:44, Robert пишет:
> [...]
>
>>> 1421183413.322185 10.59.1.9 TCP_MISS_ABORTED/503 1541 GET
http://www.amazon.com/gp/am/metro/application/livet
[...]
> > 1421183413.322185 10.59.1.9 TCP_MISS_ABORTED/503 1541 GET
> > > http://www.amazon.com/gp/am/metro/application/livetileRedirect? -
> > > HIER_DIRECT/205.251.242.103 text/html
> > > 1421183415.611132 10.59.1.9 TCP_MISS/206 8526 GET
> > > http://img.stb.s-msn.com/usappex/tenant/amp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/01/2015 12:14 a.m., Yuri Voinov wrote:
>
> Is it possible to know though URL, wich is got an error?
>
There is no URL involved.
All that has happened is that the client opened a TCP connection to
Squid then the TLS started happening on that c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is it possible to know though URL, wich is got an error?
Because of messsage not informative itself.
15.01.2015 17:10, Amos Jeffries пишет:
> On 16/01/2015 12:00 a.m., Yuri Voinov wrote:
>
> > Hi gents,
>
> > I have question.
>
> > Look:
>
> > 2015
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/01/2015 12:00 a.m., Yuri Voinov wrote:
>
> Hi gents,
>
> I have question.
>
> Look:
>
> 2015/01/15 16:48:50 kid1| clientNegotiateSSL: Error negotiating
> SSL connection on FD 209: error:14094418:SSL
> routines:SSL3_READ_BYTES:tlsv1 alert unkn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi gents,
I have question.
Look:
2015/01/15 16:48:50 kid1| clientNegotiateSSL: Error negotiating SSL
connection on FD 209: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1
alert unknown ca (1/0)
2015/01/15 16:50:50 kid1| clientNegotiateSSL: Error
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/01/2015 11:00 p.m., Alan wrote:
> Hello,
>
> I want to have a minimal Squid installation. So I compiled
> disabling everything I don't need. The resulting /usr/sbin/squid is
> 3.4 Mb.
>
> Since I don't need logging, I decided to remove that as
Hello,
I want to have a minimal Squid installation.
So I compiled disabling everything I don't need.
The resulting /usr/sbin/squid is 3.4 Mb.
Since I don't need logging, I decided to remove that as well, but its
not easy to do with sed since sometimes log messages span multiple
lines.
So I chang
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Squid HTTP Proxy team is very pleased to announce the availability
of the Squid-3.4.11 release!
This release is a bug fix release resolving several issues found in
the prior Squid releases.
The major changes to be aware of:
* "Deleting first
44 matches
Mail list logo
