Edgewall Software

Changes between Version 21 and Version 22 of TracTroubleshooting


Ignore:
Timestamp:
Mar 17, 2018, 11:13:44 AM (18 months ago)
Author:
Ryan J Ollos
Comment:

More information about trac log.

Legend:

Unmodified
Added
Removed
Modified
  • TracTroubleshooting

    v21 v22  
    3030== Check the Logs
    3131
    32 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.
     32When 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.
    3333
    34 Set the [TracLogging#LogLevels LogLevel] to //DEBUG//, restart tracd or the web server and then inspect the log. See TracLogging for additional information.
     34Set 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.
     35
     36See TracLogging for additional information.
    3537
    3638== Check the Browser Console