#8546 [fedora messaging] Not consuming any messages from /public_pubsub
Closed: Insufficient data 4 years ago by jpopelka. Opened 4 years ago by jpopelka.

Hi,

our (2) consumers haven't seen any messages since yesterday at 22PM.
I tried to restart one of them, but no luck.

config:

amqp_url = "amqps://fedora:@rabbitmq.fedoraproject.org/%2Fpublic_pubsub"
callback = "fedora_messaging.example:printer"

[exchanges."amq.topic"]
type = "topic"
durable = true
auto_delete = false
arguments = {}

[exchanges."zmq.topic"]
type = "topic"
durable = true
auto_delete = false
arguments = {}

[queues.my]
durable = true
auto_delete = true
exclusive = true
arguments = {}

[[bindings]]
queue = "my"
exchange = "amq.topic"
routing_keys = ["org.fedoraproject.prod.copr.build.#"]

[[bindings]]
queue = "my"
exchange = "zmq.topic"
routing_keys = ["org.fedoraproject.prod.copr.build.#"]

[consumer_config]
example_key = "for my consumer"

[qos]
prefetch_size = 0
prefetch_count = 25

I've changed

outing_keys = ["org.fedoraproject.prod.copr.build.#"]

to

routing_keys = routing_keys = ["org.fedoraproject.prod.copr.build.start", "org.fedoraproject.prod.copr.build.end"]

because that's what was working when we were debugging #8493 & #8499.

And it seems to work this time too. Closing for now.

Metadata Update from @jpopelka:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

4 years ago

to
routing_keys = routing_keys = ["org.fedoraproject.prod.copr.build.start", "org.fedoraproject.prod.copr.build.end"]

to

routing_keys = ["org.fedoraproject.prod.copr.build.start", "org.fedoraproject.prod.copr.build.end"]

Re-opening. We haven't consumed any messages for a recent couple of hours.
Restarting the consumer hasn't helped?

Metadata Update from @jpopelka:
- Issue status updated to: Open (was: Closed)

4 years ago

So I worked around that again by changing routing_keys to something else.
This time to routing_keys = ["org.fedoraproject.prod.copr.#"].

Again, changing the config of just one consumer was enough (the second starts to consume at the same moment without changing anything in its config).

So they work at the moment, but I'll keep this open since I see a pattern - this must be a bug somewhere, I just don't know where.

Metadata Update from @kevin:
- Issue priority set to: Waiting on External (was: Needs Review)

4 years ago

Could we hop on IRC to debug this? Are your two consumers using two different queues?

Hey @jpopelka , is this issue still happening?

Hi,

so it's been working OK since I kept the ticket open - maybe that's the requirement ;-)

Closing again.

Metadata Update from @jpopelka:
- Issue close_status updated to: Insufficient data
- Issue status updated to: Closed (was: Open)

4 years ago

Login to comment on this ticket.

Metadata