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

output.log fills up with GLib-GObject-CRITICAL messages

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 17.0.0
    • Fix Version/s: Meridian-2016.1.2, 18.0.1
    • Component/s: Logging
    • Security Level: Default (Default Security Scheme)
    • Labels:
    • Environment:
      Linux opennms 3.13.0-71-generic #114-Ubuntu SMP Tue Dec 1 02:34:22 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
      OpenNMS 17.0.0 using rrdtool 1.4.7, .MultithreadedJniRrdStrategy/JRRD2 configured

      Description

      The output.log file fills realy fast up with the following messages:

      (process:1505): GLib-GObject-CRITICAL **: g_object_get_qdata: assertion 'G_IS_OBJECT (object)' failed
      
      (process:1505): GLib-GObject-CRITICAL **: g_object_replace_qdata: assertion 'G_IS_OBJECT (object)' failed
      

      Since output.log is not rotated I end up with a full disk and a 90 GB file after a few hours. Maybe this issue is related to rrdtool because I found some similar errors on Tobi Oetiker's github repo page:

      https://github.com/oetiker/rrdtool-1.x/issues/386
      https://github.com/oetiker/rrdtool-1.x/issues/374

      My workaround is to delete output.log and create a symbolic link of /dev/null to /var/log/opennms/output.log:

      # cd /var/log/opennms
      # rm output.log
      # ln -s /dev/null output.log
      

      This prevents the disk from filling up but results in a quite high CPU consumption (load is ~12).

        Attachments

          Activity

            People

            • Assignee:
              ranger Benjamin Reed
              Reporter:
              cpape Christian Pape
            • Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: