Project

Profile

Help

Issue #917

closed

qpid errors are logged during repo sync when task notifications are enabled

Added by cduryee over 9 years ago. Updated over 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
High
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
1. Low
Version:
Master
Platform Release:
2.7.0
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

On Pulp 2.7-dev, I see a lot of the following in the pulp log when I enable task notifications and perform a sync:

kombu.transport.qpid:INFO: Connected to qpid with SASL mechanism ANONYMOUS
kombu.transport.qpid:ERROR: (9116-48576) None
kombu.transport.qpid:ERROR: (9116-48576) Traceback (most recent call last):
kombu.transport.qpid:ERROR: (9116-48576)   File "/usr/lib/python2.7/site-packages/kombu/transport/qpid.py", line 1393, in
kombu.transport.qpid:ERROR: (9116-48576)     self.monitor_receivers()
kombu.transport.qpid:ERROR: (9116-48576)   File "/usr/lib/python2.7/site-packages/kombu/transport/qpid.py", line 1409, in
kombu.transport.qpid:ERROR: (9116-48576)     self._session.next_receiver()
kombu.transport.qpid:ERROR: (9116-48576)   File "<string>", line 6, in next_receiver
kombu.transport.qpid:ERROR: (9116-48576)   File "/usr/lib/python2.7/site-packages/qpid/messaging/endpoints.py", line 689,
kombu.transport.qpid:ERROR: (9116-48576)     if self._ecwait(lambda: self.incoming, timeout):
kombu.transport.qpid:ERROR: (9116-48576)   File "/usr/lib/python2.7/site-packages/qpid/messaging/endpoints.py", line 51, 
kombu.transport.qpid:ERROR: (9116-48576)     self.check_closed()
kombu.transport.qpid:ERROR: (9116-48576)   File "/usr/lib/python2.7/site-packages/qpid/messaging/endpoints.py", line 601,
kombu.transport.qpid:ERROR: (9116-48576)     raise SessionClosed()
kombu.transport.qpid:ERROR: (9116-48576) SessionClosed: None

I don't think this is affecting any functionality. Note that the notification sending in `emit.py` could be rewritten per https://github.com/celery/kombu/issues/457, which may solve this issue.

To reproduce using Fedora 21:

  • enable task notifications in server.conf and restart pulp services
  • perform some syncs
  • examine pulp log

Related issues

Related to Pulp - Issue #1006: Pulp server REST API status call causes a kombu connection exception to appear in the logs each 10s CLOSED - CURRENTRELEASEbmbouterActions

Also available in: Atom PDF