Issue likely applies to other subsystems but SEI has a hierarchical guardian and this may be more a problem for these types of guardians.

Before restarting the front ends, the guardian was used to bring things down by moving the request from Isolated to offline. When the BS (and all other) guardian (Chamber Manager) was turned from OFFLINE to ISOLATED after the frontend restart, we had to RELOAD the guardian.  This was expected and maybe normal.

However on HAM4, the chamber manager reload was not sufficient.  The Chamber Manager reported "ERROR in state INIT; see log for more info; MODE=>RELOAD to reset"

The log file reported "NameError: name 'Connect' is not defined"

Until I reloaded the ISI and HPI subordinate guardians (can't tell if just one or actually both needed to be reloaded), reloading the Chamber guardian was insufficient.

After reloading the subordiantes, reloading the Manager brought things back as usual.