Microgateway (2.3.0 Beta) cluster running issues

Not applicable

I am running Microgateway 2.3.0 beta on MacOS to communicate with our private edge cloud environment. When edgemicro is started, I can see the whole cluster with one node master process and 8 worker processes running and they work as expected. ps -ef | grep edgemicro

I notice two issues so far:

(1) command "edgemicro status" and "edgemicro stop" don't work. It always shows edgemicro is not running. The stop command won't stop the cluster processes.

$ edgemicro status

current nodejs version is v6.9.1

current edgemicro version is 2.3.0-beta

edgemicro is not running.

(2) When one of the worker process dies, it brings down whole cluster process including the master and never recovers. I can see the error message from console:


Removing the socket file as part of cleanup

/usr/local/lib/node_modules/edgemicro/cli/lib/reload-cluster.js:95

var interval = respawnIntervalManager.getIntervalForNextSpawn(now);

TypeError: respawnIntervalManager.getIntervalForNextSpawn is not a function

at replaceWorker (/usr/local/lib/node_modules/edgemicro/cli/lib/reload-cluster.js:95:43)

at EventEmitter.replaceAndTerminateWorker (/usr/local/lib/node_modules/edgemicro/cli/lib/reload-cluster.js:119:5)

at emitOne (events.js:96:13)

at EventEmitter.emit (events.js:188:7)

at emit (/usr/local/lib/node_modules/edgemicro/cli/lib/reload-cluster.js:56:15)

at EventEmitter.emitWorkerDisconnect (/usr/local/lib/node_modules/edgemicro/cli/lib/reload-cluster.js:167:5)

at emitOne (events.js:96:13)

at EventEmitter.emit (events.js:188:7)

at ChildProcess.<anonymous> (cluster.js:400:15)

at ChildProcess.g (events.js:291:16)

at emitNone (events.js:86:13)

at ChildProcess.emit (events.js:185:7)

at finish (internal/child_process.js:711:14)

at _combinedTickCallback (internal/process/next_tick.js:67:7)

at process._tickCallback (internal/process/next_tick.js:98:9)

0 3 345
3 REPLIES 3

Former Community Member
Not applicable
@James Hu

Please wait until the beginning of next week. We intend to release another beta (hopefully the last before GA).

hi @Srinandan Sridhar,

Could you please help understand on what could cause this.

We are also facing the same in edgemicro@2.3.5

Thanks.

Former Community Member
Not applicable

@anarjinary@wiley.com this is a very old thread, and you are using a very old version of MG. Please open a new thread and consider moving to a supported version of MG.