pxy Debug Log Messages

Bruce_BriggsBruce_Briggs
in Firebox - Proxies

V12.6.3:

Seeing many of these:
2020-12-21 18:41:26 pxy 0x55ffef0-77619 153: 10.0.1.2:60054 -> 192.229.211.40:443 [A rw] {B}: SSL fatal write error (errno=0: none | sslerr=337690831: error:1420C0CF:SSL routines:ssl_write_internal:protocol is shutdown). aborting channel. Debug

Seeing many of these:
2020-12-21 22:28:28 pxy 0x5535880-80024 pxy_is_sndbuf_saturated: output buffer is saturated. snd_cwnd='14', unacked='14', sndbuf='123648', data_in_sndbuf='128480' Debug

Seeing some of these:
2020-12-22 08:06:57 pxy server requested client certificate - not supported Debug

Since these are Debug type log entries, why am I seeing them, when I have all Proxy Diagnostic Logging categories set to Error?

Comments

  • zcallowayzcalloway

    I just noticed these logs on one of our fireboxes as well.
    2020-12-30 10:02:29 pxy 0x18bcbd0-342927 pxy_is_sndbuf_saturated: output buffer is saturated. snd_cwnd='39', unacked='36', sndbuf='184704', data_in_sndbuf='156960' Debug

  • PeterPPeterP

    Is this topic continental in me too and on the addition causes a problem with the loss of packages

  • Bruce_BriggsBruce_Briggs

    If you are having issues, you should open a support incident so that a WG rep can help resolve it.
    You can click on the Support Center link at the top

  • AndersonSantosAndersonSantos

    @Bruce_Briggs said:
    If you are having issues, you should open a support incident so that a WG rep can help resolve it.
    You can click on the Support Center link at the top

    It is quite obvious that it is necessary to open an incident. that's why people come here looking for a "north" as a resolution base. I think your attitude of contempt towards the colleagues of the group. I'm a partner and I have the same problem, which support did not solve. Even saying it was resolved in 12.7

Sign In to comment.