Hi Ryan,
thank you for your response. Yes, it was a misconfiguration issue.
Possbily it would be helpful to have a set of super-global env variables
for configuration of all of the parts of the Sync / Accounts / Auth /
oAuth / Profile Server solution. This was my fault, have the same env
variable that needs different content for each part.
Bye
Uwe
Am 08.05.2018 um 00:20 schrieb Ryan Kelly:
Hi Uwe, thanks for reaching out. Reponses inline below.
On 8 May 2018 at 05:09, dev-fxa...@gmx-topmail.de
<mailto:dev-fxa...@gmx-topmail.de> <dev-fxa...@gmx-topmail.de
<mailto:dev-fxa...@gmx-topmail.de>> wrote:
Hello,
after setting up my own Accounts Server (with Content Server,
oAuth Server und Sync Server) I get the error message about
"missingFlowId". Why?
The server will occasionally log things a `ERROR` level but still
function correctly, and the missingFlowId is one example. Does the
server setup still work correctly? If not, what error messages or
other failures do you see in Firefox when trying to use it?
fxa-auth-server.INFO: stat
{"stat":"scrypt","maxPending":0,"numPending":0,"numPendingHWM":0}
fxa-auth-server.DEBUG: server.onRequest
fxa-auth-server.INFO: request.summary
{"op":"request.summary","code":404,"errno":999,"rid":"1525718907848:linux-box:7129:jgtxgn8h:10054","path":"/bundle-ba35c2d66b86a6485c3243f4ca7d121be2c892c9/appDependencies.bundle.js","agent":"Mozilla/5.0
(X11; Linux x86_64; rv:59.0) Gecko/20100101
Firefox/59.0","t":2,"uid":"00"}
The request path here ("/bundle-ba35..") looks like it's supposed to
be a request to fetch javascript from the content-server, but is being
received and handled by the auth-server. I wonder if there's an error
in configuration of your reverse proxy that is sending this request to
the wrong backend server.
fxa-auth-server.ERROR: metricsEvents.emitFlowEvent
{"op":"metricsEvents.emitFlowEvent","event":"route./bundle-ba35c2d66b86a6485c3243f4ca7d121be2c892c9/appDependencies.bundle.js.404.999","missingFlowId":true}
The server is trying to log a metrics event indicating that the client
requested a particular path, and it expects to find a "metricsContext"
request parameter to help it do so. But because this request is going
to the wrong server, it doesn't have the "metricsContext" parameter,
and the server logs an error. This error isn't fatal though, the
server will still process the request - in this case, by returning a
"404 not found".
It seems a little weird that we try to log metrics events on
non-existent routes, so I filed a bug to follow up:
https://github.com/mozilla/fxa-auth-server/issues/2423
But as noted above, I think this is ultimately caused by some
mis-configuration of your reverse proxy that is sending requests to
the wrong backend server.
Cheers,
Ryan
_______________________________________________
Dev-fxacct mailing list
Dev-fxacct@mozilla.org
https://mail.mozilla.org/listinfo/dev-fxacct
