System Logging
If necessary system (windows / linux) eventlogging can be activated. This means that errors are automatically registered in the Operating System and are kept (basically forever). This is not activated by default.
1. System logging
For activating the system logging simply add the following to the fews.master.mc.conf, fews.master.mcproxy.conf or clientConfig.xml
<logging>
<windowsEventLogEnabled>true</windowsEventLogEnabled>
<linuxSyslogFacility>local6</linuxSyslogFacility>
</logging>
Log files
For OC Clients only the previous log.txt is copied to a single backup file at restarting Delft-FEWS.
Master-controller components logging is kept per day, by default a maximum of the most recent 10 files is kept. This can however be adjusted if necessary by configuration of MaxBackupIndex.
There are individual log4j files for each component.
<appender name="defaultLogFile" class="nl.wldelft.fews.master.common.logging.DailyMaxRollingFileAppender">
<param name="datePattern" value="'.'yyyy-MM-dd"/>
<param name="MaxBackupIndex" value="10"/>
We've recently added in 2016.01 functionality to preserve the error and standard output for Master-controller components to a maximum of 1Mb.
For Forecasting Shells, there is only maxSize that can be configured.
<outputfiles>
<stdout name="out.txt" maxsize="10485760"/>
<stderr name="err.txt" maxsize="10485760"/>
</outputfiles>
Database logging
The logentries in the database are rollingbarreled intentionally from the central database after 5 days.
These are best preserved by using archive export functionality, but it is possible to keep them a bit longer by editing the fews.master.mc.conf.
<rollingbarrel>
<taskruns expiredays="10"/>
<logentries expiredays="5"/>
<reports expiredays="5"/>
<default expiredays="10"/>
</rollingbarrel>
.
