Details
-
Bug
-
Resolution: Fixed
-
1.6.0 beta4
-
None
-
Operating System: All
Platform: All
Description
I don't know how it happened, but James ended up with a node that was running the global singleton supervisor, but it was not registered in the global name server. It still had children running and registered, preventing the global singleton from coming up anywhere else.