1081112 - [support] ERROR: Unable to reach Sentry log server: [Errno -2] Name or service not known (url: udp://sentry-listener-zlb.webapp.phx1.mozilla.com:9001/api/5/store/)

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: WebOps: Community Platform, task)

Description

[Ricky Rosario [:rrosario, :r1cky]]

We started getting these tracebacks sometime yesterday:

Traceback (most recent call last):

  File "/data/www/support.mozilla.org/kitsune/virtualenv/lib/python2.6/site-packages/raven/base.py", line 549, in send_remote
    transport.send(data, headers)

  File "/data/www/support.mozilla.org/kitsune/virtualenv/lib/python2.6/site-packages/raven/transport/udp.py", line 50, in send
    addr_info = self._get_addr_info(host, int(port))

  File "/data/www/support.mozilla.org/kitsune/virtualenv/lib/python2.6/site-packages/raven/transport/udp.py", line 33, in _get_addr_info
    addresses = getaddrinfo(host, port)

gaierror: [Errno -2] Name or service not known


Request repr() unavailable.


Did DNS or something change?

Comment 1

[Jake Maul [:jakem]]

I have state on this, will fix.

Comment 2

[Jake Maul [:jakem]]

Should be resolved now.

We (meaning I) had done some research and determined that the sentry-listener nodes were not actually used. Obviously I overlooked something - a zeus config on a different cluster than I expected.

The simplest fix is to change the config to point to the endpoint that still exists. I've done that and with the approval of :mythmon, deployed the config change.

My apologies for not catching this before breaking it.

Comment 3

[Ricky Rosario [:rrosario, :r1cky]]

Prod is fixed I think, but we are still getting the errors for -dev and -stage.

Comment 4

[Will Kahn-Greene [:willkg] ET needinfo? me]

This is still busted for our -dev and -stage environments. This is a problem because there are errors happening on -dev and -stage, but we're getting error emails that are total shite for information. E.g.:

    Subject: [support-stage] ERROR: TypeError: int() argument must 
    be a string or a number, not 'object'

    No stack trace available

    Request repr() unavailable.


That's not particularly useful. I know it's happening enough to make me concerned, but there isn't anything I can do about it until -dev and -stage are using the right host for the sentry server and we're getting tracebacks as well as other contextual information.

Comment 5

[Jake Maul [:jakem]]

My apologies for the delay. This is fixed now.