edgemicro cannot synchronise settings when starting

Google Cloud Apigee
1

My local edgemicro does not seem to be able to download latest configuration. I think so because I deleted some endpoints and created new ones, but edgemicro still can see those deleted but cannot see newly created. Then if I try to re-start edgemicro, it reports “404 Not Found” on /products endpoint:

$ edgemicro start -o it-xxxxxxxx-eval -e test -k xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx -s xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

current nodejs version is v8.11.2
current edgemicro version is 2.5.16
info: jwk_public_keys download from null returned 200 undefined
info: config download from [https://edgemicroservices.apigee.net/edgemicro/bootstrap/organization/it-xxxxxxxx-eval/environment/test](https://edgemicroservices.apigee.net/edgemicro/bootstrap/organization/it-xxxxxxxx-eval/environment/test) returned 200 OK
warning: products download from [https://it-xxxxxxxx-eval-test.apigee.net/edgemicro-auth/products](https://it-xxxxxxxx-eval-test.apigee.net/edgemicro-auth/products) returned 404 Not Found
warning: error downloading config, please check bootstrap configuration Error: Not Found
    at _loadStatus (/usr/lib/node_modules/edgemicro/node_modules/microgateway-config/lib/network.js:352:12)
    at Request._callback (/usr/lib/node_modules/edgemicro/node_modules/microgateway-config/lib/network.js:217:17)
    at Request.self.callback (/usr/lib/node_modules/edgemicro/node_modules/microgateway-config/node_modules/request/request.js:186:22)
    at emitTwo (events.js:126:13)
    at Request.emit (events.js:214:7)
    at Request.<anonymous> (/usr/lib/node_modules/edgemicro/node_modules/microgateway-config/node_modules/request/request.js:1163:10)
    at emitOne (events.js:116:13)
    at Request.emit (events.js:211:7)
    at IncomingMessage.<anonymous> (/usr/lib/node_modules/edgemicro/node_modules/microgateway-config/node_modules/request/request.js:1085:12)
    at Object.onceWrapper (events.js:313:30)
    at emitNone (events.js:111:20)
    at IncomingMessage.emit (events.js:208:7)
    at endReadableNT (_stream_readable.js:1064:12)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
failed to retieve config from gateway. continuing, will try cached copy..
Error: Not Found
    at _loadStatus (/usr/lib/node_modules/edgemicro/node_modules/microgateway-config/lib/network.js:352:12)
    at Request._callback (/usr/lib/node_modules/edgemicro/node_modules/microgateway-config/lib/network.js:217:17)
    at Request.self.callback (/usr/lib/node_modules/edgemicro/node_modules/microgateway-config/node_modules/request/request.js:186:22)
    at emitTwo (events.js:126:13)
    at Request.emit (events.js:214:7)
    at Request.<anonymous> (/usr/lib/node_modules/edgemicro/node_modules/microgateway-config/node_modules/request/request.js:1163:10)
    at emitOne (events.js:116:13)
    at Request.emit (events.js:211:7)
    at IncomingMessage.<anonymous> (/usr/lib/node_modules/edgemicro/node_modules/microgateway-config/node_modules/request/request.js:1085:12)
    at Object.onceWrapper (events.js:313:30)
    at emitNone (events.js:111:20)
    at IncomingMessage.emit (events.js:208:7)
    at endReadableNT (_stream_readable.js:1064:12)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
using cached configuration from /root/.edgemicro/it-xxxxxxxx-eval-test-cache-config.yaml
PROCESS PID : 19310
warning: jwt_public_key download from [https://it-xxxxxxxx-eval-test.apigee.net/edgemicro-auth/publicKey](https://it-xxxxxxxx-eval-test.apigee.net/edgemicro-auth/publicKey) returned 404 Not Found
2

It appears you have deleted/undeployed the edgemicro-auth proxy.

3

You are probably right. There is no such proxy.

But why it should be there?

Also, why its absence stops edgemicro from synchronizing the config?

4

The “edgemicro configure” steps creates it. It should not be deleted if you’re using MG.

The proxy is how MG synchronizes with Edge (at least for part of the data).