> On Sept. 20, 2016, 1:28 a.m., Joris Van Remoortere wrote:
> > 3rdparty/libprocess/src/openssl.cpp, line 289
> > <https://reviews.apache.org/r/52033/diff/2/?file=1502593#file1502593line289>
> >
> >     Can you see if there is any other valuable information in the 
> > initialization routine that might be of value when a user posts a JIRA 
> > issue to help identify the code paths their system went through?
> >     Might be a good time to do a full review of the logging in this 
> > function rather than just up a few levels.
> >     
> >     You have been debugging many scenarios so I think you are in a unique 
> > position to do this!
> >     Thanks Till!

Totally correct and I have at least one more thing coming up;
- detection of SSL encrypted content when non SSL was expected -- we talked 
about that in the past


- Till


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/52033/#review149594
-----------------------------------------------------------


On Sept. 22, 2016, 9:26 a.m., Till Toenshoff wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/52033/
> -----------------------------------------------------------
> 
> (Updated Sept. 22, 2016, 9:26 a.m.)
> 
> 
> Review request for mesos, Joris Van Remoortere and Joseph Wu.
> 
> 
> Bugs: MESOS-5320
>     https://issues.apache.org/jira/browse/MESOS-5320
> 
> 
> Repository: mesos
> 
> 
> Description
> -------
> 
> The logging messages in question prove to be very useful for debugging
> the cluster setup and hence we decided they should be generally
> available as their helpfulnes by far outwages their noise given that
> we call these only during initializing.
> 
> 
> Diffs
> -----
> 
>   3rdparty/libprocess/src/openssl.cpp 
> c09cdc89509e4e4ca4c8a0f4fb0a57156a3a6091 
> 
> Diff: https://reviews.apache.org/r/52033/diff/
> 
> 
> Testing
> -------
> 
> make check && functional testing
> 
> 
> Thanks,
> 
> Till Toenshoff
> 
>

Reply via email to