Contents
Cirrus Link Resources
Chariot MQTT Server v1 (previous version)
Cirrus Link Modules for Ignition
Contact Us (Sales/Support)
Forum
...
Note: a Chariot service restart is required for Chariot to pickup the configuration change.
Anchor | ||||
---|---|---|---|---|
|
The Chariot wrapper.log text files can be managed on all version of Chariot in the <chariot_install_dir>/chariot/yajsw/conf/wrapper.conf file.
Code Block | ||
---|---|---|
| ||
wrapper.logfile.loglevel=INFO
wrapper.logfile=${wrapper_home}/../log/wrapper.log
wrapper.logfile.format=LPDTM
wrapper.logfile.maxsize=10m
wrapper.logfile.maxfiles=10
wrapper.logfile.rollmode=SIZE
wrapper.logfile.maxdays=60
wrapper.logfile.desc=true |
Based on this, up to 10 files of 10MB is size each may be retained. However, this isn’t exact and if logging is very verbose these can surpass that size limit and end up being larger.
Note: a Chariot service restart is required for Chariot to pickup the configuration change.
The DB logfile can be managed in the com.cirruslink.chariot.persistence.h2-logging.config file. In this is a config option:
Code Block | ||
---|---|---|
| ||
tables.1.maxRows=I"262144" |
When maxRows is set, there will actually be two tables of that size created. When one fills up it will delete the other one and then switch to using it, rotating between the two tables.
Note: a Chariot service restart is required for Chariot to pickup the configuration change.