ReleaseEngineering/How To/Unstick a Stuck Slave From A Master: Difference between revisions

no edit summary
No edit summary
Line 14: Line 14:
  >>> os.close(16)
  >>> os.close(16)


This will cause some weird tracebacks in the master log, but should come out fine in the end.
This will cause some weird tracebacks in the master log, but will let the reconfig finish.  It's black magic, and leaves the master in a potentially-very-corrupted state (eventually Twisted will try to close fd 16, which will close something completely unrelated), so '''disable the master in slavealloc and do a clean shutdown of this master once the reconfig is back on track'''.
canmove, Confirmed users
1,394

edits