Opened 5 years ago

Closed 5 years ago

#3564 closed defect (fixed)

buildbot.db.schedulers.SchedulerAlreadyClaimedError when starting master

Reported by: tardyp Owned by:
Priority: major Milestone: 0.9.0
Version: master Keywords:


I had to kill -9 my master because it was stuck, then I could not restart it, and got SchedulerAlreadyClaimedError?

After investigation, I realized that du to corporate dhcp and dns propagation delay, my mac got another hostname temporarily. buildbot thus created another masterid for it.

At restart the housekeeping was not done properly, and the schedulers were not properly unclaimed.

Change History (2)

comment:1 Changed 5 years ago by dustin

I think this would eventually be flushed when the "old" master fails to check in for a while and is deactivated by the "new" master?

comment:2 Changed 5 years ago by tardyp

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.