Closed jrgm closed 6 years ago
Is something not configured as expected on latest.dev.lcip.org?
Should SMS_STATUS_GEO_ENABLED be true
on latest.dev.lcip.org?
(for auth-server config)
@jrgm: in the content server config, GEODB_ENABLED
/ config.geodb.enabled
needs to be true. If I set that to false locally, I reproduce the same errors you posted here. Does that fix it on latest?
... {"Timestamp":1515031854882000000,"Logger":"fxa-auth-server","Type":"geodb.start","Severity":6,"Pid":5, "EnvVersion":"2.0","Fields":{"op":"geodb.start","enabled":true,"dbPath":"/app/node_modules/fxa-geodb/db/cities-db.mmdb"}} {"Timestamp":1515031854890000000,"Logger":"fxa-auth-server","Type":"","Severity":6,"Pid":5, "EnvVersion":"2.0","Fields":{"msg":"{\"env\":\"stage\",\"geodb\":{\"dbPath\":\".....cities-db.mmdb\",\"enabled\":true},...
Hmmm, okay still looking into it then...
Although I just noticed that is the auth server config you posted. Is it enabled in the content server too?
So, content-server doesn't dump the resolved config the same way auth does, but the default for GEODB_ENABLED is true
, and no override is set in the environment: https://github.com/mozilla/fxa-dev/blob/docker/roles/content/tasks/main.yml#L37-L51
I checked the metadata for the cities-db.mmdb in the fxa-geodb module in the fxa-content container, and buildEpoch: 2018-01-05T14:59:16.000Z
$ md5sum ./node_modules/fxa-geodb/db/cities-db.mmdb
f448112445c122b65726516a74b32db8 ./node_modules/fxa-geodb/db/cities-db.mmdb
Do you get the same as above? ^^
FWIW I'm seeing Geneva-related errors in auth-server CI as well, see e.g. https://travis-ci.org/mozilla/fxa-auth-server/jobs/326197279
Oh, thanks @jrgm, my local db was out of date. It appears that my clever, never-going-to-change IP address changed. I'll update the tests and just stick to the Mozilla IP address from now on.
PR imminent...
PR imminent...
(and for the auth server too, sorry @rfk)