Intermittent configure error

Not applicable

Has anyone seen this intermittent error when configuring the microgateway?

edgemicro configure -o <org> -e test -u <user> current nodejs version is v6.4.0 password: file doesn't exist, setting up { Error: cannot GET https://<org>-test.apigee.net/edgemicro-auth/publicKey (500 at translateError (<basepath>/node_modules/edgemicr/cli/lib/cert-lib.js:378:11) at Request._callback (<basepath>/node_modules/edgemcro/cli/lib/cert-lib.js:399:11) at Request.self.callback (<basepath>/node_modules/egemicro/node_modules/request/request.js:187:22) at emitTwo (events.js:106:13) at Request.emit (events.js:191:7) at Request.<anonymous> (<basepath>/node_modules/edgmicro/node_modules/request/request.js:1048:10) at emitOne (events.js:96:13) at Request.emit (events.js:188:7) at IncomingMessage.<anonymous> (<basepath>/node_modles/edgemicro/node_modules/request/request.js:969:12) at emitNone (events.js:91:20) at IncomingMessage.emit (events.js:185:7) at endReadableNT (_stream_readable.js:975:12) at _combinedTickCallback (internal/process/next_tick.js:74:11) at process._tickCallback (internal/process/next_tick.js:98:9) text: '{"fault":{"faultstring":"Script node executed prematurely: Error: Cannot find mdule \'a127-magic\'\\nError: Cannot find module \'a127-magic\'\\n at module.js:340\\n at module.js:280\\n at module.js:364\\n at require (module.js:380)\\n at \\/rganization\\/environment\\/api\\/app.js:3\\n at module.js:456\\n at module.js:474\n at module.js:356\\n at module.js:312\\n at module.js:497\\n at startup (tireme.js:142)\\n at trireme.js:923\\n","detail":{"errorcode":"scripts.node.runtime.SciptExitedError"}}}' }

Solved Solved
0 3 170
1 ACCEPTED SOLUTION

Not applicable

I haven't seen this problem since deleting all revisions of the edgemicro-auth proxy and then undeploying and deploying through the Edge UI.

View solution in original post

3 REPLIES 3

Hi Shaun,

I haven't seen this error pop up before. Are you still seeing this behavior?

Not applicable

I haven't seen this problem since deleting all revisions of the edgemicro-auth proxy and then undeploying and deploying through the Edge UI.

Awesome. Thanks Shaun. As non-ideal as the work around is for this. I'd like to make sure folks know there is a potential solution for the issue with deleting the edgemicro-auth proxy, and doing a deploy cycle in edge UI.

-Matt