Log files

OpenBlueDragon produces a number of log files from various parts of the core-engine that are very useful to let know the running state of the engine. The majority of the files are self-rolling (25MB) and will not keep consuming all the disk space.

The following is the directory structure used from the working-directory variable. By default this is "/WEB-INF/bluedragon/work/" but can be changed in the web.xml file.

bluedragon.log
This is the main engine log, detailing all major events. Useful at startup to see what elements of the engine that were initalized and with what.
cfchart/
The directory where cfchart will use for its file cache
cfcollection/
Any collections (CFINDEX etc) will be created in here
cflog/
All logging to CFLOG will be produced in this folder
cfmail/
- spool/
  The folder where all outgoing email is initially created.
- undelivered/
  Any email failed to be delivered will be moved to here. If the problem was a problematic upstream MTA, then you can simply move the files from this directory into the spool directory, without having to restart the server.
- mail.log
  Logs all emails sent to the upstream MTA
cfquerybatch/
- failed/
  This is where all the failed background queries will be placed. If the problem has been resolved, you can simply move these files into the spool directory without restarting the server.
- spool/
  This is where all the scheduled background queries will be placed.
- querybatch.log
  A log of the status of each background run, detailing the successes and failure counts.
- querybatch-error.log
  This is a detailed log of what went wrong
cfschedule/
- schedule.log
  A log of all the CFSCHEDULE runs
slowlog/
- slowlog.log
  If enabled in the bluedragon.xml, this details all the queries that took over a specific amount of seconds
temp/
- rtelogs/
  This is where all the RunTimeException files are stored. The file "bderror-latest.html" will always be the most recent bug.
- ws/
  This is the working folder for the WebServices dynamic generation