If you set:
CACHE = False
in labcontroller.conf when there are untransferred logs, then beaker-transfer gets stuck in a while loop.
This is because it returns True for transfer.transfer_logs() so does not enter sleep, and then transfer_recipe_logs() returns straightaway as CACHE is not enabled.
Maybe beaker-transfer should just bail out entirely if CACHE=False? It has no purpose otherwise.
Ideally it should exit non-zero before daemonising, then the administrator will see a big fat red "FAILED" if they try to start it when CACHE=False.
Bulk reassignment of issues as Bill has moved to another team.
I wrote a patch for this while working on the harness API:
Due to the changes in log storage mechanism, the CACHE variable is defunct now. (See: http://beaker-project.org/docs-release-0.12/whats-new/release-0.12.html#logs-are-no-longer-sent-to-the-beaker-server)
The above patch adds the intelligence to beaker-transfer to bail out if ARCHIVE_SERVER is not configured. This is verified to be working as expected:
# service beaker-transfer start
Starting beaker-transfer: Archive server settings are missing from config file
Beaker 0.12 has been released.