Changes between Version 12 and Version 13 of TracTroubleshooting

Timestamp:

Mar 9, 2015, 8:33:17 PM (9 years ago)

Author:

Ryan J Ollos

Comment:

Writeup of debug step that is frequently suggested on the MailingList. We can just point users to this section.

TracTroubleshooting

@@ -23 +23 @@
 
 If you're facing a new problem, the next step is to try to find out the root cause.
+
+== Check the Logs
+
+The log output is an excellent source of diagnostic information. If a //Component// has been enabled but the corresponding feature is not available, the immediate cause may be that the //Component// is failing to load. //Component// loading is logged at //DEBUG// level when restarting tracd or the web server. Additional debug information and tracebacks may also be logged.
+
+Set the [TracLogging#LogLevels LogLevel] to //DEBUG//, restart tracd or the web server and then inspect the log.
 
 == Debugging Trac