Uploaded image for project: 'OpenNMS'
  1. OpenNMS
  2. NMS-6527

Logging messages from several daemons appear on uncategorized.log

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 1.13.1
    • Fix Version/s: 14.0.0
    • Component/s: Logging
    • Security Level: Default (Default Security Scheme)
    • Labels:
      None

      Description

      The information from Pollerd's threads and Vacuumd's threads are placed on the wrong log file.

      For Pollerd my initial idea was applying the following:

      @@ -261,7 +262,7 @@ abstract public class PollableElement {
           public <T> T withTreeLock(Callable<T> c, long timeout) {
               try {
                   obtainTreeLock(timeout);
      -            return c.call();
      +            return Logging.withPrefix("poller", c);
               } catch (RuntimeException e) {
                   throw e;
               } catch (Throwable e) {
      

      The above patch works for most of the messages but not all of them.

      Some messages from PollableNode and PollableService are still on uncategorized.log.

      For Vacuumd it is not clear when to apply the trick with Logging.withPrefix().

      Several Collectd's classes are doing a similar thing (~ DefaultUDPTransportMapping, SNMP Timers, ThreadPoolExecutor/LegacyScheduler).

      The multi-thread loading of the datacollection groups on DataCollectionConfigParser also appear un uncategorized.log.

      Lots of thread related processing is wrong.

        Attachments

          Activity

            People

            • Assignee:
              brozow Matt Brozowski
              Reporter:
              agalue Alejandro Galue
            • Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: