MailNews:Logging: Difference between revisions

Jump to navigation Jump to search
m
m (→‎Set a Preference: clarify preference lifetime.)
Line 226: Line 226:
=== Missing Log File ===
=== Missing Log File ===


If your log file is empty or missing, review this document again, and check for these common problems:
If your log file is empty or missing, check for these common problems and review this document again:
* If logging ldap, nntp, pop3, or smtp, you '''must''' use [[MailNews:Logging#Thunderbird_Logging|Thunderbird logging]], not Gecko module logging using environment variables.
* '''pop3, ldap, nntp, and smtp log types you must use case sensitive, modern [[MailNews:Logging#Thunderbird_Logging|Thunderbird logging]]'''
* If logging imap, you '''must''' use [[MailNews:Logging#Gecko_Logging|Gecko module logging]] using environment variables.
* imap logging '''must''' be done with [[MailNews:Logging#Gecko_Logging|Gecko module logging]] using environment variables.
* If linux, variables MOZ_LOG and MOZ_LOG_file must be in quotation marks.
* Gecko logging only:
* If linux, MOZ_LOG_file must be fully specified without shortcuts, such as "~/"
** If linux, variables MOZ_LOG and MOZ_LOG_file must be in quotation marks.
* Do you have write access to the directory specified in MOZ_LOG_FILE?
** If linux, MOZ_LOG_file must be fully specified without shortcuts, such as "~/"
* Did you shut down the application?  (the log file is buffered in memory until the application is closed)
** Do you have write access to the directory specified in MOZ_LOG_FILE?
* Did you restart your mailnews application, and wipe out the log of the session you wanted to debug?  (every restart wipes out the previous log)
** Did you shut down the application?  (the log file is buffered in memory until the application is closed)
* If you used a batch file on Windows, is the batch file set to run with administrator privileges?
** Did you restart your mailnews application, and wipe out the log of the session you wanted to debug?  (every restart wipes out the previous log)
* Do your log variables contain quotation marks or other invalid characters?
** If you used a batch file on Windows, is the batch file set to run with administrator privileges?
* Are your log module names correctly '''CASE SENSITIVE'''?  (meaning mixed case, or camel case which is not all upper case, nor all lower case)
** Do your log variables contain quotation marks or other invalid characters?
** Are your log module names correctly '''CASE SENSITIVE'''?  (meaning mixed case, or camel case which is not all upper case, nor all lower case)


== NSPR Logging Options ==
== NSPR Logging Options ==
canmove, Confirmed users
2,230

edits

Navigation menu