Changes between Version 21 and Version 22 of TracTroubleshooting

Timestamp:

Mar 17, 2018, 11:13:44 AM (6 years ago)

Author:

Ryan J Ollos

Comment:

More information about trac log.

TracTroubleshooting

@@ -30 +30 @@
 == Check the Logs
 
-The log output is an excellent source of diagnostic information. When a feature is unavailable it's often the case that the Trac or plugin //Component// that implements the feature has failed to load. This could be due to a programming error, missing dependency or installation problem. //Component// loading is logged at //DEBUG// level when restarting tracd or the web server. Additional debug information and tracebacks may also be logged.
+When a feature is unavailable it's often the case that the Trac or plugin //Component// that implements the feature has failed to load. This could be due to a programming error, missing dependency or installation problem. //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. See TracLogging for additional information.
+Set the [TracLogging#LogLevels LogLevel] to //DEBUG//, restart tracd or the web server and then inspect the log. The log location is configured in //trac.ini//. The default location is `log/trac.log` in the environment directory.
+
+See TracLogging for additional information.
 
 == Check the Browser Console