On a cluster with "ctdb timeout = x" cleanupd may exit when a recovery is started while running a db traverse in cleanupd. When recovery kicks in, the traverse freezes and if recovery takes longer then ctdb timeout, cleanupd closes the ctdb connection and exits. So we should better be restarting cleanup in smbd whenwe notice it exitted.
Created attachment 12026 [details] Patch for 4.4 cherry-picked from master
Pushed to autobuild-v4-4-test.
Pushed to v4-4-test. Closing out bug report. Thanks!