Bug 2105795 - Logs are piling up with qpidd error :ConnectionTicker couldn't setup next timer firing.
Summary: Logs are piling up with qpidd error :ConnectionTicker couldn't setup next ti...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Qpid
Version: 6.10.6
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: Unspecified
Assignee: Nobody
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-10 15:52 UTC by Satyajit Das
Modified: 2023-07-31 18:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-16198 0 None None None 2023-03-01 00:27:46 UTC

Description Satyajit Das 2022-07-10 15:52:59 UTC 
Description of problem:

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

# 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:-

# 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:
Note You need to log in before you can comment on or make changes to this bug.