Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-16198

Logs are piling up with qpidd error :ConnectionTicker couldn't setup next timer firing.

XMLWordPrintable

    • Moderate
    • None

      Description of problem:

      Logs are piling up with qpidd error: ConnectionTicker couldn't setup next timer firing.

      1. journalctl -u qpidd.service -f

      Jul 07 01:15:45 satellite.example.com qpidd[7974]: 2022-07-07 01:15:45 [System] error ConnectionTicker couldn't setup next timer firing: -7500994551ns[7.501s]
      Jul 07 01:15:45 satellite.example.com qpidd[7974]: 2022-07-07 01:15:45 [System] error ConnectionTicker couldn't setup next timer firing: -7500994551ns[7.501s]
      Jul 07 10:19:51 satellite.example.com qpidd[7974]: 2022-07-07 10:19:51 [System] error ConnectionTicker couldn't setup next timer firing: -7500997911ns[7.501s]
      Jul 07 10:19:51 satellite.example.com qpidd[7974]: 2022-07-07 10:19:51 [System] error ConnectionTicker couldn't setup next timer firing: -7500997911ns[7.501s]
      Jul 08 02:33:24 satellite.example.com qpidd[7974]: 2022-07-08 02:33:24 [System] error ConnectionTicker couldn't setup next timer firing: -7500996851ns[7.501s]
      Jul 08 02:33:24 satellite.example.com qpidd[7974]: 2022-07-08 02:33:24 [System] error ConnectionTicker couldn't setup next timer firing: -7500996851ns[7.501s]
      Jul 08 18:30:35 satellite.example.com qpidd[7974]: 2022-07-08 18:30:35 [System] error ConnectionTicker couldn't setup next timer firing: -7500997077ns[7.501s]
      Jul 08 18:30:35 satellite.example.com qpidd[7974]: 2022-07-08 18:30:35 [System] error ConnectionTicker couldn't setup next timer firing: -7500997077ns[7.501s]
      Jul 08 19:33:36 satellite.example.com qpidd[7974]: 2022-07-08 19:33:36 [System] error ConnectionTicker couldn't setup next timer firing: -7500997221ns[7.501s]
      Jul 08 19:33:36 satellite.example.com qpidd[7974]: 2022-07-08 19:33:36 [System] error ConnectionTicker couldn't setup next timer firing: -7500997221ns[7.501s]

      Version-Release number of selected component (if applicable):

      6.10.z

      ~~~~~~~~~~~~~~~~~~
      qpid-qmf-1.36.0-32.el7_9amq.x86_64
      python-qpid-proton-0.33.0-6.el7_9.x86_64
      qpid-cpp-client-1.36.0-32.el7_9amq.x86_64
      python-qpid-qmf-1.36.0-32.el7_9amq.x86_64
      qpid-dispatch-router-1.14.0-1.el7_9.x86_64
      python-qpid-1.35.0-5.el7.noarch
      python-gofer-qpid-2.12.5-7.el7sat.noarch
      qpid-cpp-server-1.36.0-32.el7_9amq.x86_64
      qpid-proton-c-0.33.0-6.el7_9.x86_64
      qpid-cpp-server-linearstore-1.36.0-32.el7_9amq.x86_64
      qpid_router_katello_agent-qpid-router-client-1.0-1.noarch
      qpid-cpp-client-devel-1.36.0-32.el7_9amq.x86_64
      tfm-rubygem-qpid_proton-0.33.0-2.el7sat.x86_64
      qpid-tools-1.36.0-32.el7_9amq.noarch
      ~~~~~~~~~~~~~~~~~~

      How reproducible:

      100%

      Steps to Reproduce:
      1. Execute the command on the satellite and you will see the error:-

      1. journalctl -u qpidd.service -f

      Actual results:

      Jul 07 01:15:45 satellite.example.com qpidd[7974]: 2022-07-07 01:15:45 [System] error ConnectionTicker couldn't setup next timer firing: -7500994551ns[7.501s]
      Jul 07 01:15:45 satellite.example.com qpidd[7974]: 2022-07-07 01:15:45 [System] error ConnectionTicker couldn't setup next timer firing: -7500994551ns[7.501s]
      Jul 07 10:19:51 satellite.example.com qpidd[7974]: 2022-07-07 10:19:51 [System] error ConnectionTicker couldn't setup next timer firing: -7500997911ns[7.501s]

      Expected results:

      No error / exception.

      Additional info:

              jira-bugzilla-migration RH Bugzilla Integration
              jira-bugzilla-migration RH Bugzilla Integration
              RH Bugzilla Integration RH Bugzilla Integration
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: