0

Since this morning we have received two new error notifications in FogBugz

The Maintenance Service is not running. - Hide Notification 19.10.2010 15:56 (GMT+04:00): The last time the Maintenance Service ran successfully was 18.10.2010 15:39 (GMT+04:00). Please check your site configuration and make sure that the 'Maintenance URL' is pointing to the correct address.

The Maintenance Service discovered an expired lock - Hide Notification 19.10.2010 15:59 (GMT+04:00): An expired lock was broken by the Maintenance Service. If this error persists, it may mean that Heartbeat is failing

If anyone has any ideas of what to do, please let me know!

Fog Creek Case FC1963285

flag
Can you give us some more details about your environment? Specifically, your FogBugz version (or if you're On Demand), your server version, and your database type would all be helpful. – Bradford♦ Oct 19 2010 at 20:43
sure i can:) 1. FogBugz Version 8.0.26 (DB 767, Build 2284) 2. Data base MsSql2008 R2 Express 3. Working surrounding win2003 R2 – DV Oct 20 2010 at 8:06

1 Answer

1

This is usually an expression of this problem, where a case is getting stuck in the index. What happens is the heartbeat tries to complete it's processing and then clear the lock, but the former never happens. So the next time heartbeat runs, it sees there's an existing, but expired, lock. Obviously, since it never completes, FogBugz never gets notified that the Maintenance Service ran.

More generally, this is caused by heartbeat not completing correctly. You can narrow down which part of the heartbeat has trouble by following this process to limit the actions it takes. In this particular case, a reinstallation of FogBugz resolved the issue as it was related to the heartbeat.asp page not running correctly.

link|flag
Thx for helpin i resolved my problem by reinstaled FogBugz – DV Oct 25 2010 at 6:47

Your Answer

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