Does anybody seen this in Squid logs already?
httpRqMethod CNT
There is no destination IP nor request host logged. All clients are
Windows machines. Requests are rejected due to not supported HTTP
method.
The complete log entry example:
13/Aug/2018:14:26:18 +0200 10.x.y.z 63740 -> - - responseTi
There are significant differences between the Fedora->RHEL and
Debian->Ubuntu relations.
Fedora is development oriented with short lifecycle and without support of
previous versions. RHEL is built on Fedora with stability and enterprise
needs in mind (they always ).
Debian provides more release st
Squid use TTL of 60 seconds for DNS resource records with TTL smaller than
that value.
Some sites can have DNS TTL set to lower value due to high availability
design (DNS load balancer).
In RFCs [1][2][3] it is explained the received TTL can be lowered to the
upper bound TTL value of DNS cache, b
On Mon, Apr 9, 2018 at 4:43 PM, Alex Rousskov <
rouss...@measurement-factory.com> wrote:
> On 04/09/2018 06:03 AM, Peter Viskup wrote:
>> Running Squid 4.0.23 the ICAP connections getting "frozen".
>>
>> proxy:~ $ netstat -ntpa| grep 40620
>> tcp 9201
Running Squid 4.0.23 the ICAP connections getting "frozen".
proxy:~ $ netstat -ntpa| grep 40620
tcp 920144 0 127.0.0.1:40620 127.0.0.1:1344
ESTABLISHED 1165/(squid-1)
tcp0 2744857 127.0.0.1:1344 127.0.0.1:40620
ESTABLISHED 1211/esets_icap
# after ICAP service resta
ies wrote:
> On 05/04/18 21:39, Peter Viskup wrote:
>> On Wed, Apr 4, 2018 at 5:42 PM, Amos Jeffries wrote:
>>> On 04/04/18 21:15, Peter Viskup wrote:
>>>> On Linux Virtual Server balanced cluster the %>>> errors ERR_ACCESS_DENIED or TCP_MEM_HIT are logged.
>
On Wed, Apr 4, 2018 at 5:42 PM, Amos Jeffries wrote:
> On 04/04/18 21:15, Peter Viskup wrote:
>> On Linux Virtual Server balanced cluster the %> errors ERR_ACCESS_DENIED or TCP_MEM_HIT are logged.
>>
>> This is causing issue when processing logs on remote machine (e.g.
On Linux Virtual Server balanced cluster the %http://lists.squid-cache.org/listinfo/squid-users
Hello Ahmad,
your instances should have different ports opened. Use squidclient's
options -p -h to request the appropriate instance.
Example from our server:
proxy02:/etc/squid $ squidclient -p 8080 cache_object://localhost/
mgr:info|grep "Start Time"
Start Time: Thu, 22 Mar 2018 13:09:24 GMT
Communication is ok. Problem was with pcap filtering based on port
number. Only the first fragment of the packet have this information.
All others have port fields empty. More information in tcpdump man
page in IP Fragmentation section.
In new packet capture the request for 87 OIDs is replied with
We do monitor our Squid's via SNMP with Zabbix and use the template
available on Zabbix share portal [1].
Retrieval of values is not reliable. Seems to be related to IP fragmentation.
The complete answer should be 4325B long.
~# snmpwalk -m /usr/share/squid3/mib.txt -v2c -CE
.1.3.6.1.4.1.3495.1.5
Feel free to use this systemd (based on postgresql) and logrotate
configuration for multi-instance configuration according wiki [1].
Might be useful for others.
The instance is "enabled" by presence of
/etc/squid/${service_name}.instance file.
There could be includes like these in squid.conf
pid
retained for compatibility.
On Wed, Feb 14, 2018 at 2:31 PM, Peter Viskup wrote:
> Crypto part of the configure log:
>
> checking for nettle_md5_init in -lnettle... yes
> checking nettle/md5.h usability... yes
> checking nettle/md5.h presence... yes
> checking for nettle/md5.h
On Thu, Feb 15, 2018 at 7:41 PM, Alex Rousskov
wrote:
> On 02/15/2018 07:32 AM, Amos Jeffries wrote:
>> On 16/02/18 01:44, Peter Viskup wrote:
>>> Running squid version 4.0.23 with logformat including
>>>
>>> SSLBumpMode=%ssl::bump_mode SSLSNI=&
Running squid version 4.0.23 with logformat including
SSLBumpMode=%ssl::bump_mode SSLSNI="%ssl::>sni"
SSLClientProto="%ssl::>negotiated_version"
SSLServerProto="%ssl::http://lists.squid-cache.org/listinfo/squid-users
SSL library support: yes -lssl -lcrypto
On Wed, Feb 14, 2018 at 2:02 PM, Peter Viskup wrote:
> Build of squid 4.0.23 on current Debian 9 report the single_dh_use as not
> known.
> Older build of squid 3.5.21 on Debian 8 doesn't report it.
> According the documentation [1] it sho
Build of squid 4.0.23 on current Debian 9 report the single_dh_use as not known.
Older build of squid 3.5.21 on Debian 8 doesn't report it.
According the documentation [1] it should be known and supported.
[1] http://www.squid-cache.org/Doc/config/http_port/
Is it a bug?
Peter
$ /usr/sbin/squid
On Fri, Feb 2, 2018 at 12:13 PM, Amos Jeffries wrote:
>
> On 02/02/18 23:42, Peter Viskup wrote:
> > Want to run multiple instances of Squid4 on the same server with
> > different ports and one configuration file.
> > Not sure whether (and how) the http_port and snmp_port
Want to run multiple instances of Squid4 on the same server with different
ports and one configuration file.
Not sure whether (and how) the http_port and snmp_port options can be made
as conditional options in squid.conf.
At the moment it looks like it is not possible.
The workaround can be to use
Tried to configure logging to syslog directly and experiencing issues
with not accepted syslog priority assigned in config files.
This is the configuration:
~# grep -E '^access_log|^icap_log|logstrmfilter' /etc/squid3/squid.conf
access_log syslog:local7.notice logformat=combined3
acl logstrmfilter
Hello all,
we do experience some connection issues with SFTP and clear HTTP
clients on Squid 3.4 version built with SSL split.
We occasionally see ERR_CONNECT_FAIL with SYSERR=110.
Just discovered higher value of "HTTP I/O number of reads" at the time
the issue occur.
I am not able to understand t
-
MIIGQzCCBCugAwIBAgITWgAAuYCRJAQnIMZ1CwABAAC5gDANBgkqhkiG9w0BAQsF
In both cases the only log entry we see is the CONNECT request:
01/Jun/2016:10:16:23 +0200681 127.0.0.1 TAG_NONE/200 0 CONNECT
www.ftpsservicedomain.net:990 - HIER_DIRECT/www.ftpsservicedomain.net
- [Host: www.ftpsservicedomain.net:990\r\n] [-]
Best regards,
--
Peter
22 matches
Mail list logo
