"Could not understand response from symbolication server at http://symbolapi.mozilla.org/ ". Profiler fails

REOPENED
Unassigned

Status

()

REOPENED
3 years ago
2 years ago

People

(Reporter: alice0775, Unassigned)

Tracking

(Blocks: 1 bug)

Trunk
Unspecified
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
When I am doing analyze profiler, the following alert pops up. 

> Could not understand response from symbolication server at http://symbolapi.mozilla.org/
> 
> Please consider filing a bug at https://bugzilla.mozilla.org/

Comment 1

3 years ago
also seeing this with gecko profiler v1.12.15 in Thunderbird
I'm seeing this also in Profiler.

Comment 3

3 years ago
What is the source of these issues?
Is there an intermittent issue with the server? 
bug 1166045?

I had someone else report this today. 
And yet, last night I successfully did two profiles on different machines
Summary: Could not understand response from symbolication server at http://symbolapi.mozilla.org/ → "Could not understand response from symbolication server at http://symbolapi.mozilla.org/ ". Profiler fails
(Reporter)

Updated

3 years ago
Status: NEW → RESOLVED
Last Resolved: 3 years ago
status-firefox41: affected → ---
Resolution: --- → WORKSFORME
(Reporter)

Comment 4

3 years ago
still happen
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
We just switched symbolapi to AWS, but from comments in this bug sounds like this is an ongoing issue.

vladan is this known? Anything I can help with?
Flags: needinfo?(vdjeric)
(In reply to Robert Helmer [:rhelmer] from comment #5)
> We just switched symbolapi to AWS, but from comments in this bug sounds like
> this is an ongoing issue.
> 
> vladan is this known? Anything I can help with?

- I can't ssh into 2 of the 4 hostnames, I'm guessing ec2 spawned new nodes?
- Can you also switch back to hosting the symbolication server on one machine, and tell me that hostname?
- How can I find out the current hostname?
- I restarted the 2 hostnames I could ssh into. I need to investigate this and fix it for good but that will have to wait until later in the workweek.
Flags: needinfo?(vdjeric) → needinfo?(rhelmer)
(In reply to Vladan Djeric (:vladan) -- please needinfo! from comment #6)
> (In reply to Robert Helmer [:rhelmer] from comment #5)
> > We just switched symbolapi to AWS, but from comments in this bug sounds like
> > this is an ongoing issue.
> > 
> > vladan is this known? Anything I can help with?
> 
> - I can't ssh into 2 of the 4 hostnames, I'm guessing ec2 spawned new nodes?

OK scaling down to 1 right now.

> - Can you also switch back to hosting the symbolication server on one
> machine, and tell me that hostname?
> - How can I find out the current hostname?

Filed bug 1176885 to formalize your access to this - I'm going to set up a stable CNAME in DNS for you to connect to, to keep this up to date.

> - I restarted the 2 hostnames I could ssh into. I need to investigate this
> and fix it for good but that will have to wait until later in the workweek.
Flags: needinfo?(rhelmer)

Comment 8

2 years ago
(In reply to Robert Helmer [:rhelmer] from comment #7)
> (In reply to Vladan Djeric (:vladan) -- please needinfo! from comment #6)
> > ...
> > - Can you also switch back to hosting the symbolication server on one
> > machine, and tell me that hostname?
> > - How can I find out the current hostname?
> 
> Filed bug 1176885 to formalize your access to this - I'm going to set up a
> stable CNAME in DNS for you to connect to, to keep this up to date.
> 
> > - I restarted the 2 hostnames I could ssh into. I need to investigate this
> > and fix it for good but that will have to wait until later in the workweek.

Are we good now?
Or is there still an underlying unsolved issue?
Flags: needinfo?(vladan.bugzilla)
Flags: needinfo?(alice0775)
(Reporter)

Comment 9

2 years ago
WFM
geckoprofiler 1.16.16
https://hg.mozilla.org/mozilla-central/rev/c67dc1f9fab86d4f2cf3224307809c44fe3ce820
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0 ID:20160520030251
Flags: needinfo?(alice0775)

Comment 10

2 years ago
Oddly enough, using 2016-05-15 64bit nightly build and geckoprofiler 1.16.16 I just got 

Could not understand response from symbolication server at http://symbolapi.mozilla.org/gecko-profiler/
Please consider filing a bug at https://bugzilla.mozilla.org/

Comment 11

2 years ago
In console I see 

unreachable code after return statement
view-source:https://cleopatra.io/js/markerTree.js

And also saw this line - but only once
TypeError: finishCallback is not a function
view-source:resource://jid0-edalmuivkozlouyij0lpdx548bc-at-jetpack/data/SymbolicateModule.jsm

Comment 12

2 years ago
I'm getting the same message as comment 0

Name 	Firefox
Version 	50.0a1
Build ID 	20160726030213

geckoprofiler 1.16.16

Comment 13

2 years ago
Sorry, it's not actually the same. It's

> Could not connect to symbolication server at http://symbolapi.mozilla.org/gecko-profiler/

> Please verify that you are connected to the Internet.

The network console shows no response to the request:

POST /gecko-profiler/ HTTP/1.1
Host: symbolapi.mozilla.org
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate, br
Content-Length: 136692
Content-Type: application/json
Connection: keep-alive
Cookie: <censored>
I'm not the maintainer anymore, the symbolication server was rewritten this summer. I think Kirk Steuber is the point of contact now.
Flags: needinfo?(vladan.bugzilla)

Comment 15

2 years ago
Kirk, do you have insight here?
Flags: needinfo?(ksteuber)

Comment 16

2 years ago
The profiler works for me at the moment, the issues i had were resolved with bug 1161720
The symbolication server is currently being rewritten. It is nearly ready for production, but has not been deployed yet. I am not sure that I can speak to any problems with the old version of the server. I can tell you that the reason for the rewrite was that the old server was somewhat unstable. If it this problem persists after the deployment of the new version of the symbolication server, we can look into it further.
Flags: needinfo?(ksteuber)
Blocks: 1329163
You need to log in before you can comment on or make changes to this bug.