Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

 

Table of Contents

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.


Code Block
language

 

xml
title

...

For activating the system logging simply add the following to the

...

mc config xml or clientConfig xml.

...

 

<logging>

            <windowsEventLogEnabled>true</windowsEventLogEnabled>

            <linuxSyslogFacility>local6</linuxSyslogFacility>

<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"/>

 

Since 2016.01 the error and standard output for Master-controller components is preserved 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>

...

Maximum total amount of bytes in rolling files

Code Block
languagexml
titlerollingTotalSizeMB
<logging>
    <rollingTotalSizeMB>100</rollingTotalSizeMB>
</logging>

Expiry time of Master Controller and Admin Interface log entries.

Code Block
languagexml
titleAdmin Interface / Master Controller log entry expiry time
<logging>
    <logEntryExpiryTime unit="day" multiplier="5" />
</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>

mc config xml.

  .