mwinkel-dev

Hi @smithsp -- The "previous server version on Atlas" was `stable_7.96.9`, correct? If so, that is from 7-Feb-2020. And yes, there have been changes to connection behavior in the following...

Hi @smithsp -- Thanks for the clarification! That news greatly simplifies the troubleshooting.

Hi @smithsp -- Both facts are consistent, which is also good news. In a few minutes, I should be able to reproduce the problem.

I have just reproduced the problem with current alpha.

Root cause was an incomplete fix for Issue #2652. (Note that the issue was fixed after `alpha_7.139.59`.) That bug involved a `status` variable that was overloaded and thus failed (i.e.,...

Note that the PR #2752 fix handles the scenario when a client successfully establishes a network connection but fails the user authorization check. It returns a failure status to the...

Hi @vadim-at-te -- Yes, the mdsip service definitely needs better logging. Thanks for listing the requirements for your site. Note that this request is a duplicate of #2683.

Hi @AreWeDreaming, My initial guess (perhaps wrong) is that is not possible in current versions of MDSplus. However, I will investigate and post a definitive answer in the next day...

Hi @AreWeDreaming, My colleagues have confirmed that MDSplus presently cannot limit concurrent `mdsip` connections per user. (Using the standard features of Linux, it is possible to apply "rate limiting" to...

If the goal of `SsINTERNAL` is to alert the user to an extremely abnormal condition that should never arise during normal operation of MDSplus, then another approach is to throw...