0

Fogbugz heartbeat is locked.

If you are sure there are no other processes running heartbeat, you can break the lock and reload heartbeat

Just upgraded from Fogbugz 6 to 7.1.5 Windows/SQL and after running for 2 hours notifications stoped and the queue starting filling. Tracked things down to the heartbeat being locked, so nothing can be processed. The link to break the lock times out. Reboot resumes the same state. Ther should be nothing else running that calls heartbeat.

Any ideas how to proceed?

flag

1 Answer

1

We contacted support and debugging revealed that an indexing process was getting stuck on our data. That indexing has been disabled and Fog Creek is looking at a future patch that will allow such a data problem to reveal itself more elegantly if not work through the data problem.

link|flag
The underlying problem was heartbeat's assumption that ixBug values would be relatively contiguous within the database. Under normal circumstances this is a valid assumption, but in this particular case there was a very large gap between ixBug values that was causing heartbeat to get stuck while performing some backfill operations. We have since updated the code to avoid this type of problem in the future. – db♦ Feb 15 2010 at 18:39

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.