Qpid is flooding sys journal with poll debug info in Katello stable

Hello,

on my Katello stable test deployment after few minor updates and
several restarts I am getting flooded in journal:

dub 07 10:50:14 nuc pulp[2618]: qpid.messaging:DEBUG: poll(3 fds, timeout=None)
dub 07 10:50:14 nuc pulp[2618]: qpid.messaging:DEBUG: poll() returned 1 fds
dub 07 10:50:14 nuc pulp[2618]: qpid.messaging:DEBUG: poll(3 fds, timeout=None)
dub 07 10:50:14 nuc pulp[2618]: qpid.messaging:DEBUG: poll() returned 1 fds
dub 07 10:50:14 nuc pulp[2618]: qpid.messaging:DEBUG: poll(1 fds,
timeout=3000.0)
dub 07 10:50:14 nuc pulp[2618]: qpid.messaging:DEBUG: poll() returned 1 fds
dub 07 10:50:14 nuc pulp[2618]: qpid.messaging:DEBUG: poll(3 fds, timeout=None)
dub 07 10:50:14 nuc pulp[2618]: qpid.messaging:DEBUG: poll() returned 1 fds
dub 07 10:50:14 nuc pulp[2619]: qpid.messaging:DEBUG: poll() returned 0 fds

These are never ending, what shall I check? Thanks

··· -- Later, Lukas @lzap Zapletal

It is caused by increasing pulp/qpid logging level to debug. Little
bit too much to debug, this looks like trace candidate. Whatever.

LZ

··· On Fri, Apr 7, 2017 at 10:51 AM, Lukas Zapletal wrote: > Hello, > > on my Katello stable test deployment after few minor updates and > several restarts I am getting flooded in journal: > > dub 07 10:50:14 nuc pulp[2618]: qpid.messaging:DEBUG: poll(3 fds, timeout=None) > dub 07 10:50:14 nuc pulp[2618]: qpid.messaging:DEBUG: poll() returned 1 fds > dub 07 10:50:14 nuc pulp[2618]: qpid.messaging:DEBUG: poll(3 fds, timeout=None) > dub 07 10:50:14 nuc pulp[2618]: qpid.messaging:DEBUG: poll() returned 1 fds > dub 07 10:50:14 nuc pulp[2618]: qpid.messaging:DEBUG: poll(1 fds, > timeout=3000.0) > dub 07 10:50:14 nuc pulp[2618]: qpid.messaging:DEBUG: poll() returned 1 fds > dub 07 10:50:14 nuc pulp[2618]: qpid.messaging:DEBUG: poll(3 fds, timeout=None) > dub 07 10:50:14 nuc pulp[2618]: qpid.messaging:DEBUG: poll() returned 1 fds > dub 07 10:50:14 nuc pulp[2619]: qpid.messaging:DEBUG: poll() returned 0 fds > > These are never ending, what shall I check? Thanks > > -- > Later, > Lukas @lzap Zapletal


Later,
Lukas @lzap Zapletal