5,838
edits
Debug.log: Difference between revisions
From Cumulus Wiki
Jump to navigationJump to search
m
add category
m (add category) |
|||
| (28 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
The | The debug logging feature is extremely useful in troubleshooting problems with Cumulus. | ||
[[Category:Diagnostics]] | |||
[[Category:Cumulus 1]] [[File:Badge v1.png]] This page only applies to Cumulus 1. | |||
[[Category:Cumulus Files]] | |||
== File growth and deletion == | |||
If debugging is switched off, periodically a message, confirming that as shown earlier, is added to the '''debug.log''' file, so it grows in size even when full diagnostics are not being stored. | |||
If debugging is switched on, extensive messages of the format shown are added to the file and it will rapidly grow in size. | |||
To avoid loss (or inaccuracy) of readings being processed from your weather station, it is best if Cumulus is left running, and not restarted except when unavoidable. Consequently, the '''debug.log''' file will continually grow in size. If the file is left to grow too large, Cumulus will crash. Therefore, you '''should''' delete this file periodically . | |||
=File Location, Name and Format= | =File Location, Name and Format= | ||
Cumulus 1 creates diagnostic logs in two places: | |||
# It creates a file called '''Debug.log''' in the same folder as where the executable is stored. | |||
#*This file can be deleted at any time as Cumulus does not read from it, and creates a new file when needed | |||
#*The log file is a simple text file containing the time and a description of each event. | |||
The log file is a simple text file containing the time and a description of each event. | #* This file periodically has a message '''0000.000 : **** Logging Disabled''' stored if debugging is switched off. | ||
#* This file will have additional debugging information added, as per example below, if debugging is turned on. | |||
# It creates a [[Diags_folder|diags folder]]; '''diags''' is a sub-folder of the folder where the Cumulus executable is stored. | |||
#* That diags folder contains up to 10 files named '''cumulus.~og''' and '''cumulus.001''' to '''cumulus.009'''. | |||
#** '''cumulus.~og''' is the current log reporting what has happened since the last time Cumulus was started. | |||
#** '''cumulus.001''' to '''cumulus.009''' represent logs for previous 9 Cumulus restarts, and so do not exist if Cumulus has not been used before. | |||
#*Further information about this is to be found on the [[Diags_folder|diags folder]] page. | |||
#* Any diagnostic file can be deleted, at any time, as Cumulus does not read from them. Cumulus creates a new file if necessary to continue its logging. | |||
=Sample File= | =Sample File= | ||
| Line 43: | Line 52: | ||
9175.328 : TD = 0.0833333358168602 Lastval = 618 Firstval = 618 rate = 0 | 9175.328 : TD = 0.0833333358168602 Lastval = 618 Firstval = 618 rate = 0 | ||
=Turning debugging logging on/off= | |||
*By default, logging of debugging information is disabled. | |||
*Restarting Cumulus will mean the debug log is off (because it is automatically turned off as Cumulus exits) | |||
*Logging of debugging information can be enabled as Cumulus is started, or at some point while it is running (except earliest builds) | |||
[[ | Depending on which version of Cumulus 1 you are using, there is '''either one or two ways''' of turning logging of debugging data on and off: | ||
* The only way to turn on the logging of debugging messages in all builds of Cumulus 1, is to stop Cumulus 1, edit the [[Cumulus.ini_(Cumulus_1)#Section:_Station|configuration file]], and add a line in the [Station] section: <tt>Logging = 1</tt>, then restart Cumulus 1. | |||
* From build 1003 onward, you can also turn it on/off using the '''Configuration''' menu (debug option is included in drop down of that menu). | |||
