#8246 Staging Pagure is not sending messages to fedora-messaging
Closed: Fixed 6 months ago by pingou. Opened 11 months ago by thrnciar.

Hello,

Seems like staging Pagure is not sending messages. Last one was received 6 hours ago. https://apps.stg.fedoraproject.org/datagrepper/raw?category=pagure&delta=172800

Thank you.
CC: @praiskup


Metadata Update from @bowlofeggs:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: pagure, staging

11 months ago

It seems to be working ok now? I am not sure what changed... can you confirm it's working for you?

I may be doing something wrong, but I commented in [1] just now, and nothing appeared in [2], so it is still broken IMO.

[1] https://stg.pagure.io/copr-pagure-events-testing/copr/pull-request/21
[2] https://apps.stg.fedoraproject.org/datagrepper/raw?category=pagure&delta=172800

I think you need to make sure that you have the fedmsg hook enabled in the project settings. And also the fedmsg notification in the Project Options in the settings as well.

Both are enabled, though.

Ah, I misunderstood. I thought you meant src.stg.fedoraproject.org, not stg.pagure.io.

For some reason I cannot seem to login to stg.pagure.io to test this with. ;( Will see if I can get that fixed first...

So I think the fedmsg sent on commits are working but not the one sent on actions (creating issues, commenting on issues etc ... )

@pingou any idea what could be wrong ?

I've been meaning to look at this as prod is regularly sending me these errors:

Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/pika/diagnostic_utils.py", line 53, in log_exception_func_wrap
    return func(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/pika/adapters/utils/io_services_utils.py", line 1222, in _consume
    super(_AsyncSSLTransport, self)._consume()
  File "/usr/lib/python2.7/site-packages/pika/adapters/utils/io_services_utils.py", line 791, in _consume
    data = self._sigint_safe_recv(self._sock, self._MAX_RECV_BYTES)
  File "/usr/lib/python2.7/site-packages/pika/adapters/utils/io_services_utils.py", line 79, in retry_sigint_wrap
    return func(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/pika/adapters/utils/io_services_utils.py", line 846, in _sigint_safe_recv
    return sock.recv(max_bytes)
  File "/usr/lib64/python2.7/ssl.py", line 757, in recv
    return self.read(buflen)
  File "/usr/lib64/python2.7/ssl.py", line 651, in read
    v = self._sslobj.read(len or 1024)
SSLEOFError: EOF occurred in violation of protocol (_ssl.c:1826)

I'm not receiving them from stg, so I'm not 100% if it's related to the issue at hand though

Arg. wrong host again, this is for src.fp.o not stg.pagure.io

I'll have a look there

Ok, by porting stg.pagure.io to fedora-messaging we seem to have solved the issue we were having: https://apps.stg.fedoraproject.org/datagrepper/raw?category=pagure&delta=172800

I'm going to do the same for pagure.io so we are consistent between the two hosts

Sorry for the noise but let's test fedora-messaging here :)

Cool, datagrepper sees the message twice, one for fedmsg and one for fedora-messaging, so let's turn off fedmsg.

Alright, afaics this ticket is fixed.

Please re-open if you still have issues and thanks for your report (and sorry it took so long to process it!)

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

6 months ago

Login to comment on this ticket.

Metadata