Problem(s) Encountered:

1) The OWL window disappeared and could not be restarted.
2) Connections to /data hung up (see Desktop windows).

Other windows on the Desktop worked OK so it was not a communication issue.

Solution:

This was not the typical instance where a zombie session of Owl was continuing to run and simply needed to be killed.  Connection to mdmarc2 failed as well for some reason.  Login page was still available however via the Raritan locally.  Not sure what happened.  I reboot mdmarc2 (after replacing its onboard battery) and it appears to be working well again.  

When I turned on the Raritan monitor, it was at the login page.  A question for folks more familiar with the Raritan systems (OSU?): could there be some correlation between the mdmarc2 connection issue and Raritan logging out?  Why would Raritan logout?

Update: 

I’m not an expert on the ins-and-outs of the Raritan systems anymore – we don’t have any at OSU – but it seems totally believable that the Raritan would log out if the machine it is connected to glitches.

 I believe those Raritans are long past their supported lifetime, so it is also possible you are seeing signs of elderly equipment failure. [Mason/OSU]