Thanks very much for the explanation. I am happy to ignore it - now that I know it is not anything I need to actively pursue.
-Gavin. As always thanks! Gavin Baumanis E: [email protected] I, for one, like Roman numerals. On 7 September 2016 at 04:47, Joseph Wu <[email protected]> wrote: > You can easily trigger this log line by curling Mesos and interrupting the > curl. For example, the python script in the description of > https://issues.apache.org/jira/browse/MESOS-6104 will almost always > trigger that log line. > > The log line itself never indicates a leak. What I meant by "insightful" > is something like this: https://issues.apache.org/jira/browse/MESOS-5576 > > On Tue, Sep 6, 2016 at 11:26 AM, June Taylor <[email protected]> wrote: > >> I admit I don't understand this explanation, and our logs are also filled >> with this message. How would one tell whether it's a good time to ignore it >> versus a leak? >> >> >> Thanks, >> June Taylor >> System Administrator, Minnesota Population Center >> University of Minnesota >> >> On Tue, Sep 6, 2016 at 1:07 PM, Joseph Wu <[email protected]> wrote: >> >>> You can ignore that log line. It's something Mesos prints when the >>> client side of a socket closes the socket before Mesos does. >>> >>> We've kept the log line thus far because it can be surprisingly >>> insightful when tracking down things like FD leaks based on logs alone :) >>> >>> On Mon, Sep 5, 2016 at 4:26 AM, Gavin Baumanis <[email protected]> >>> wrote: >>> >>>> Hi Everyone, >>>> >>>> I am just starting to do some evaluation of Mesos. >>>> >>>> I managed to get it built / installed and running, successfully using >>>> the 1.0.1 release. >>>> I am running 5 nodes via VirtualBox VMs on my Mac. >>>> I restarted the VMs for a separate reason and have subsequently noticed >>>> the following error; >>>> E0905 21:19:32.483242 1002 process.cpp:2105] Failed to shutdown socket >>>> with fd 11: Transport endpoint is not connected >>>> >>>> I have searched here and on Stack Overflow - and while I can see a feww >>>> threads discussing it - there doesn't seem to be a definitive answer as to >>>> what causes it - nor try these steps, in the following order... >>>> >>>> So I thought would ask about this issue again and hopefully create a >>>> discussion that could serve as a one-stop shop for future Googler's of the >>>> same issue. >>>> >>>> When visiting the web page of the master @ 5050, the whole cluster is >>>> shown correctly with all resources available. So I am not even sure if the >>>> error is "noise" - or if it is a serious "thing" to be actively addressed - >>>> but of course would rather it was happening - even if it is benign. >>>> >>>> if anyone has any ideas - I would love to hear them and happily accept >>>> the help. >>>> please let me know if there is anything specific, you'll need from me. >>>> >>>> >>>> As always thanks! >>>> >>>> Gavin Baumanis >>>> E: [email protected] >>>> >>>> I, for one, like Roman numerals. >>>> >>> >>> >> >
