You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2018/10/21 23:45:00 UTC

[jira] [Assigned] (MESOS-9340) Log all socket errors in libprocess.

     [ https://issues.apache.org/jira/browse/MESOS-9340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Mahler reassigned MESOS-9340:
--------------------------------------

    Assignee: Benjamin Mahler

> Log all socket errors in libprocess.
> ------------------------------------
>
>                 Key: MESOS-9340
>                 URL: https://issues.apache.org/jira/browse/MESOS-9340
>             Project: Mesos
>          Issue Type: Improvement
>          Components: libprocess
>            Reporter: Benjamin Mahler
>            Assignee: Benjamin Mahler
>            Priority: Major
>
> To aid debugging, we need to shore up our logging to ensure that all socket errors in the embedded http server are logged at the warning level and include IP address information of the peer. Looks like we have the following:
> (1) recv error: VLOG(1) w/ peer and nothing
> (2) send error: nothing
> (3) shutdown error: LOG(INFO) sometimes with our own address (weird)
> (4) connect error: LOG(WARNING) with destination address
> (5) accept error: LOG(WARNING)
> (6) listen error: LOG(FATAL)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)