Problem(s) Encountered:

I got a phone call from robot that dome socket is not responding anymore.
The logs say that observations ran for ~ 2 hours before Kitt Peak signaled clouds and scheduler gracefully paused. When the robot tried to open after Kitt Peak signal cleared, the socket was not responding anymore. I tried to manually start up but slit is not opening anymore.

tcs says socket not connected when trying to open slit or dropleaf. had to stop observing middle of night

If its any help, the dome state response kept changing over the multiple attempts to start up
First it was (NO IT WAS NOT RAINING)[tcs] 'slit open' no confirmation: TCS reported: ERROR slit cantopen=rain
Then it responded

[tcs] 'slit open' no confirmation: TCS reported: ERROR in service ether=localhost,0x1342
And then
[tcs] 'slit open' no confirmation: socket closed without 'done' (buffer: b'')
Seems like the dome state got confused?

Solution:

System was initially reporting it could not open due to weather.  This is sometimes a red herring.  If so, it can be overridden with the command:
tx slit open dammit
This should only be done if it is absolutely certain that there is no weather hazard present.  In the case of last night, it may have been too humid anyways (humidity was above the limit when I checked this morning).
Ultimately here, found that one of the telescope servers (rslit) had shut off.  I cycled the servers (telescope stop then telescope start) to get them all back online.  No reset of the port server was necessary this time.  Reset the telescope coordinates and verified functionality.