|
8
|
|
|
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 [path_to_fogbugz]/logs (usually /opt/fogbugz/logs).
On Windows, the maintenance service log is called fogbugzmaint.txt. It can be found in the temp directory of the user running FogBugz (e.g., C:\Users\FogBugz\AppData\Local\Temp). You should be able to find this directory by logging in as the FogBugz Windows user and going to the Start Menu, click Run..., type %temp% and hit enter. Instructions for enabling this log on Windows are found below.
(To troubleshoot problems with license installing, you can view another log file called fogutil.txt, which is also enabled via the method below.)
-
Edit the registry using REGEDIT. Navigate to:
HKEY_LOCAL_MACHINE\
SOFTWARE\
Fog Creek Software\
FogBugz
- 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.
|
|
|
|
|
7
|
|
|
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 [path_to_fogbugz]/logs (usually /opt/fogbugz/logs).
On Windows, the maintenance service log is called fogbugzmaint.txt. It can be found in the temp directory of the user running FogBugz (e.g., C:\Users\FogBugz\AppData\Local\Temp). You should be able to find this directory by going to the Start Menu, click Run..., type %temp% and hit enter. Instructions for enabling this log on Windows are found below.
(To troubleshoot problems with license installing, you can view another log file called fogutil.txt, which is also enabled via the method below.)
-
Edit the registry using REGEDIT. Navigate to:
HKEY_LOCAL_MACHINE\
SOFTWARE\
Fog Creek Software\
FogBugz
- 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.
|
|
|
|
|
6
|
|
edited Apr 21 2010 at 18:35 |
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 [path_to_fogbugz]/logs (usually /opt/fogbugz/logs).
On Windows, the maintenance service log is called fogbugzmaint.txt. It can be found next to in the Website folder (it is a sibling temp directory of the Website folder)user running FogBugz (e.g., C:\Users\FogBugz\AppData\Local\Temp). Instructions for enabling this log on Windows are found below.
(To troubleshoot problems with license installing, you can view another log file called fogutil.txt, which is also enabled via the method below.)
-
Edit the registry using REGEDIT. Navigate to:
HKEY_LOCAL_MACHINE\
SOFTWARE\
Fog Creek Software\
FogBugz
- 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.
|
|
|
|
5
|
|
edited Apr 21 2010 at 18:17 |
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 [path_to_fogbugz]/logs (usually /opt/fogbugz/logs).
On Windows, the maintenance service log is called fogbugzmaint.txt. It can be found next to the Website folder (it is a sibling of the Website folder). Instructions for enabling this log on Windows are found below.
(To troubleshoot problems with license installing, you can view another log file called fogutil.txt, which is also enabled via the method below.)
-
Edit the registry using REGEDIT. Navigate to:
HKEY_LOCAL_MACHINE\
SOFTWARE\
Fog Creek Software\
FogBugz
- 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.
|
|
|
|
|
4
|
|
edited Apr 21 2010 at 15:28 |
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 /opt/fogbugz/logs
On Windows, the maintenance service log is called fogbugzmaint.txt. Instructions for enabling this log on Windows are found below.
(To troubleshoot problems with license installing, you can view another log file called fogutil.txt, which is also enabled via the method below.)
-
Edit the registry using REGEDIT. Navigate to:
HKEY_LOCAL_MACHINE\
SOFTWARE\
Fog Creek Software\
FogBugz
- 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.
|
|
|
|
|
3
|
|
edited Apr 21 2010 at 15:03 |
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 /opt/fogbugz/logs
On Windows, the maintenance service log is called fogbugzmaint.txt. Instructions for enabling this log on Windows are found below.
(To troubleshoot problems with license installing, you can view another log file called fogutil.txt, which is also enabled via the method below.below.)
-
Edit the registry using REGEDIT. Navigate to:
HKEY_LOCAL_MACHINE\
SOFTWARE\
Fog Creek Software\
FogBugz
- 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 both the most verbose logging (see log fileslevels 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.
|
|
|
|
|
2
|
|
edited Apr 21 2010 at 14:27 |
To troubleshoot problems involving Dispatcho The FogBugz Maintenance Service periodically hits the maintenance URL (e.g. when email is not being pulled into FogBugz)sURL in the registry or application.data) to carry out jobs such as search indexing, it mail delivery and retrieval, and other important "heartbeat" tasks. If this service is useful crashing, you'll want to view enable logging to diagnose the FogBugz Maintenance problem.
On Linux, the maintenance service log fileis always enabled and is called hb.log. It can be found in /opt/fogbugz/logs
On Windows, the maintenance service log is called fogbugzmaint.txt. Instructions for enabling this log on Windows are found below.
To troubleshoot problems with license installing, you can view another log file called fogutil.txt, which is also enabled via the method below.
-
Edit the registry using REGEDIT. Navigate to:
HKEY_LOCAL_MACHINE\
SOFTWARE\
Fog Creek Software\
FogBugz
- 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 both log files.
- 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.
|
|
|
|
|
1
|
|
answered Oct 15 2009 at 6:53 FogBugz KB
|
To troubleshoot problems involving Dispatcho (e.g. when email is not being pulled into FogBugz), it is useful to view the FogBugz Maintenance log file, fogbugzmaint.txt. To troubleshoot problems with license installing, you can view another log file called fogutil.txt.
-
Edit the registry using REGEDIT. Navigate to:
HKEY_LOCAL_MACHINE\
SOFTWARE\
Fog Creek Software\
FogBugz
- 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 both log files.
- 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.
|
|
|
