On 3/1/21 8:35 PM, Service MV wrote:
> Unfortunately, the log that I whant to avoid is being still logged.
Do the unwanted logged records match zabbix_proxy?
* If yes, I am out of ideas. If you share a debugging log dedicated to
the incorrectly logged transaction[1], I may be able to figure it
Unfortunately, the log that I whant to avoid is being still logged.
El vie., 26 feb. 2021 17:14, Alex Rousskov
escribió:
> On 2/26/21 2:58 PM, Service MV wrote:
> > Ok, but whit this two lines disabled completely access logs. I've no
> > more access_log directives configured.
>
> Yeah, this
On 2/26/21 2:58 PM, Service MV wrote:
> Ok, but whit this two lines disabled completely access logs. I've no
> more access_log directives configured.
Yeah, this outcome is surprising to many admins (and there are also
related bugs in Squid code).
To see all other records, add access_log lines
Ok, but whit this two lines disabled completely access logs. I've no more
access_log directives configured.
I need disabled only zabbix_proxy IP logs.
Thanks in advance
Gabriel
El vie., 26 feb. 2021 16:21, Alex Rousskov
escribió:
> On 2/26/21 12:36 PM, Service MV wrote:
>
> > NONE/000 0 NONE
On 2/26/21 12:36 PM, Service MV wrote:
> NONE/000 0 NONE error:transaction-end-before-headers - HIER_NONE/- -
>
> I know that this is not an error. But I want to exclude this log when
> the Zabbix server checks the port status of SQUID. Zabbix server does
> not use the SQUID as a proxy.
If you
