Search Unity

Crash reporting stopped working a few days ago

Discussion in 'Unity Cloud Diagnostics' started by jerome-lacoste, Feb 17, 2016.

  1. jerome-lacoste

    jerome-lacoste

    Joined:
    Jan 7, 2012
    Posts:
    206
  2. ChrisLundquist

    ChrisLundquist

    Unity Technologies

    Joined:
    Mar 2, 2015
    Posts:
    55
    Hey again Jerome!

    You are one of our original users and it looks like "2828145a-*" might be pointing at the original URL of perf.cloud.unity3d.com

    For a while we forwarded reports sent to perf.cloud.unity3d.com -> perf-events.cloud.unity3d.com
    A while back Amazon changed DNS for the (perf-events) load balancer and nginx caches the DNS resolution.
    I kicked nginx to make it point to the new DNS, but it looks like it is getting 500s when trying to forward the report.
    The only other change we deployed lately was a fix to truncate really long exception messages so they fit in our database.

    I kicked nginx again and I'm seeing a few of your reports. It looks like they might have changed DNS on us again.

    It seems like if you update the URL to perf-events.cloud.unity3d.com you should be good for a while.

    Hope this helps,
    Chris Lundquist
     
  3. jerome-lacoste

    jerome-lacoste

    Joined:
    Jan 7, 2012
    Posts:
    206
    Looks like it works. I integrated your change, and kicked out our builds, Will double check them tomorrow and report if something is amiss.

    Thanks a lot for the time. Really appreciated.
     
  4. jerome-lacoste

    jerome-lacoste

    Joined:
    Jan 7, 2012
    Posts:
    206
    Hello @ChrisLundquist

    I made further tests on another project. ID ADB4C234-... The project is new from today.

    The perf-events URL is not working. The perf one is.

    Connection refused - connect(2) for "perf-events.cloud.unity3d.com" port 80 (Errno::ECONNREFUSED)

    Am I missing something ?

    I just shipped a product today after validating last week that the new URL was working well :(
     
  5. ChrisLundquist

    ChrisLundquist

    Unity Technologies

    Joined:
    Mar 2, 2015
    Posts:
    55
    Looks like you're missing the "s"

    We only accept crash reports securely :)


    $ curl http://perf-events.cloud.unity3d.com

    curl: (7) Failed to connect to perf-events.cloud.unity3d.com port 80: Connection refused

    $ curl https://perf-events.cloud.unity3d.com
    {

    "Error": "Resource not found"

    }

    I'll see if I can fix the forwarding again for the old URL in the mean time.

    Chris Lundquist
     
  6. jerome-lacoste

    jerome-lacoste

    Joined:
    Jan 7, 2012
    Posts:
    206
    @ChrisLundquist

    I had tried that. Only the combination http perf works for me.
     

    Attached Files:

  7. ChrisLundquist

    ChrisLundquist

    Unity Technologies

    Joined:
    Mar 2, 2015
    Posts:
    55
    Hmm, can you send me that ruby script in a gist and/or email?
     
  8. ChrisLundquist

    ChrisLundquist

    Unity Technologies

    Joined:
    Mar 2, 2015
    Posts:
    55
    I've taken my best guess about why Ruby was unhappy with https://perf-events.cloud.unity3d.com/
    It may work now that we're returning 202 accepted in the happy case. Before we didn't set status and just closed the connection.

    If you have that script available I can test using it.

    Hope this helps,
    Chris Lundquist