#6480 One or more fedmsg-gateways are busted?
Closed: Fixed 6 years ago Opened 6 years ago by ralph.

Here's the symptom:

If I connect to tcp://hub.fedoraproject.org:9940 from outside the infra, I will usually start getting fedmsg messages.. but sometimes I don't. My listener just hangs forever.

My hunch is that one (but not all) of the fedmsg-gateway daemons running on the proxies is stuck. If I win the lottery and select it from DNS, then I get zip.

Could it be that the vpn connection between one of the proxies and busgateway01.vpn is down? This was a problem at least once before.


I can ping over the vpn for all proxies to busgateway01. ;(

I don't see any dead fedmsg-gateway processes on proxies.

Can you perhaps see what proxy you are connected to when it does this? Might help us isolate which one is at fault?

Were you by chance using ipv6? There was a proxy that had a ipv6 ip in dns, but wasn't responding on it.

If so I fixed that, so can you see if you can get it to stall again now?

Hm, I just checked and it's not on ipv6. Will try and get more info out.

These are OK:

  • 140.211.169.196
  • 8.43.85.67
  • 152.19.134.142
  • 140.211.169.206
  • 66.35.62.162
  • 67.219.144.68
  • 209.132.181.16
  • 152.19.134.198

This seems to be the only one that has the bug?

  • 209.132.190.2

Ah ha. That machine is in rdu2 and behind a RHIT nat. It recently moved, and I bet the 9940/tcp port forward didn't get moved with it. We will request it.

Metadata Update from @smooge:
- Issue assigned to smooge

6 years ago

Opened internal ticket.

This is now fixed.

:busstop:

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

6 years ago

Login to comment on this ticket.

Metadata