The FogBugz Maintenance Service periodically hits the maintenance URL (sURL in the registry or application.data) to carry out jobs such as search indexing, mail delivery and retrieval, and other important "heartbeat" tasks. If this service is crashing, you'll want to enable logging to diagnose the problem.
On Linux, the maintenance service log is always enabled and is called hb.log. It can be found in
On Windows, the maintenance service log is called fogbugzmaint.txt. It should be created in the temp directory of the user running FogBugz (e.g.,
C:\Users\FogBugz\AppData\Local\Temp). When you start the Maintenance Service, it will log to the Windows Event Viewer to let you know where to find fogbugzmaint.txt:
Follow these steps to enable maintenance service and licensing logging.
Edit the registry using REGEDIT. Navigate to:
Fog Creek Software\
- In the righthand pane, right click and choose New > DWORD Value
- Create a value named Logging and set it to 10 (that's hexadecimal). This turns on the most verbose logging (see log levels below).
LOG_INFO = 10
LOG_WARNING = 5
LOG_ERROR = 1
- Using your web browser, go to your FogBugz site and try to log on (to trigger license validation). For FogBugz Maintenance problems, make sure there is mail sitting patiently on your mail server, and give the Maintenance Service enough time to check for the mail (the "Check for new mail" interval setting on the Mailboxes page).
- Run the Windows Event Viewer and look in the Application Log. Look for a message from FogBugz, which will tell you the location where the FogUtil log file was written (probably something like fogutil.txt in your Windows directory). A message from FogBugz Maintenance Service will tell you where the fogbugzmaint.txt log file lives.
- For technical support, send the appropriate log file to us.
- In the registry, turn off logging by setting the Logging key to 0.
Note: If you use an email client to view the messages sitting on your mail server, it must be a POP3 client, not an IMAP client.