2 Replies Latest reply: Dec 27, 2011 1:33 PM by 773176 RSS

    Turning down the verbosity of logging in  search service

    773176
      Hello old friends.

      Our search node is generating 1.5gb of logs per day. how can i turn down the verbosity of the logging? I don't see any configuration files that get read, and the config mgr doesn't have anything about logging verbosity.
        • 1. Re: Turning down the verbosity of logging in  search service
          geoff garcia
          Here are 2 log file settings in the search area, not sure what they impact but I don't see many other log setting files.
          Definitely let us know what you uncover though.

          1)
          Cluster.ini file at this path:
          \bea\alui\ptsearchserver\10.3.0\cluster

          # Logging
          #
          # The following settings may be used to override the default logging policies.
          # For a given severity level specify a comma-delimited list of values
          # corresponding to the logs which should receive log messages at that
          # severity level. Acceptable values are trace,event,cluster,none.
          # Note that internally log messages are routed either to the cluster log
          # or the local logs. While a cluster log message may be echoed to the
          # local logs, a local log will never be sent to the cluster log
          #RF_LOG_DEBUG_OUTPUT=none
          #RF_LOG_INFO_OUTPUT=trace
          #RF_LOG_WARN_OUTPUT=trace,event,cluster
          #RF_LOG_ERROR_OUTPUT=trace,event,cluster
          #RF_LOG_FATAL_OUTPUT=trace,event,cluster
          #RF_LOG_PERF_OUTPUT=none
          #RF_LOG_FUNC_OUTPUT=none
          #RF_LOG_ACTN_OUTPUT=none

          2)

          wrapper.conf file at this path:
          \bea\alui\ptsearchserver\10.3.0\adminui\settings\config

          #********************************************************************
          # Service wrapper Logging Properties
          # Logging properties for the service wrapper only, these properties
          # do not control application-specific logging.
          #
          # Valid log levels for console, log file, and sys/event log output are
          # DEBUG          Verbose debug messages
          # INFO          JVM output and informative messages.
          # STATUS     State changes
          # ERROR          Errors only
          # FATAL          Fatal errors only
          #********************************************************************
          # Format of output for the console. (See docs for formats)
          wrapper.console.format=PM

          # Log Level for console output. (See above for log levels)
          wrapper.console.loglevel=INFO

          # Log file to use for wrapper output logging.
          wrapper.logfile=%APPLICATION_PATH%/logs/wrapper.log

          # Format of output for the log file. (See docs for formats)
          wrapper.logfile.format=LPTM

          # Log Level for log file output. (See above for log levels)
          wrapper.logfile.loglevel=INFO

          # Maximum size that the log file will be allowed to grow to before
          # the log is rolled. Size is specified in bytes. The default value
          # of 0, disables log rolling. May abbreviate with the 'k' (kb) or
          # 'm' (mb) suffix. For example: 10m = 10 megabytes.
          wrapper.logfile.maxsize=0

          # Maximum number of rolled log files which will be allowed before old
          # files are deleted. The default value of 0 implies no limit.
          wrapper.logfile.maxfiles=0

          # Log Level for sys/event log output. (See above for log levels)
          wrapper.syslog.loglevel=STATUS
          • 2. Re: Turning down the verbosity of logging in  search service
            773176
            This may just be my tired brain, but don't both of those options not apply to the actual search node itself? The first is for the cluster and the second is for the admin UI. Does the cluster log parameters get passed through to the actual node? According to the last line below it doens't seem like it does:

            # The following settings may be used to override the default logging policies.
            # For a given severity level specify a comma-delimited list of values
            # corresponding to the logs which should receive log messages at that
            # severity level. Acceptable values are trace,event,cluster,none.
            # Note that internally log messages are routed either to the cluster log
            # or the local logs. While a cluster log message may be echoed to the
            # local logs, a local log will never be sent to the cluster log