[widar-wg] Station Board s007-t-2 oddity

[Michael Rupen]

While running some fast-dump tests today I noticed a bit before 1pm MDT
(1900 UTC) that the CM had a failure in trying to communicate with ea27.  I 
traced this to s007-t-2 = sb0074, which was shown as "notMemberOfASubarray" in 
the paned CPCC "Configurations" GUI.

Although I could ping and slogin to the board, and the Monit Service
Manager http://s007-t-2:55101/ worked fine (and showed no problems
with any processes), neither the StB GUI, nor http://s007-t-2/, nor
http://s007-t-2:8080/, gave any response.  An attempt to restart the
javaServer from the Monit Service Manager web page left that task listed
as "restarting", but it never got beyond that to really do it.

I slogin'd as root to the CMIB, and issued a reboot command.  This took 
the StB down, but it never came back up.

So in the end I power-cycled the board.  It's now up and running,
and happily producing fringes.

We'll have to check delays for IF A of ea27 and ea28, and IF C of
ea25-26-27-28, since the power cycle led to the loss of TIMECODE A.
I'll have a look at that shortly.

           -- Michael