search

dgkanatsios / azuregameserversscalingkubernetes

Scaling Dedicated Game Servers on Azure Kubernetes Service
MIT License
39 stars 16 forks source link

Error while setting the MarkedForDeletion flag #69

Open uthappa123 opened 4 years ago

uthappa123 commented 4 years ago

During testing with TestNodeJS App (https://github.com/dgkanatsios/azuregameserversscalingkubernetes/blob/master/docs/installation.md#testing-with-nodejs-demo-app-an-echo-http-server), the pod goes to error state each time while setting the DedicatedGameServer MarkedForDeletion state to true (markedfordeletion|true).

Pod log:

$ kubectl logs simplenodejsudp-emijv-lxgdr UDP Server listening on 0.0.0.0:22222 Set status Assigned OK Set status Healthy OK Message received from 104.172.182.40:53085 -

UDP message sent to 104.172.182.40:53085

Message received from 104.172.182.40:53085 - hello

UDP message sent to 104.172.182.40:53085

Message received from 104.172.182.40:53085 - players|8

Set Active Players to running OK UDP message sent to 104.172.182.40:53085

Message received from 104.172.182.40:53085 - markedfordeletion|true

Set Server Status OK /app/index.js:87 serverResponse = ${serverResponse}, set Server Status to ${status} OK\n; ^ ReferenceError: status is not defined at Request. (/app/index.js:87:69) at Request._callback (/app/node_modules/lodash/lodash.js:10052:25) at Request.requestRetryReply [as reply] (/app/node_modules/requestretry/index.js:105:19) at Request. (/app/node_modules/requestretry/index.js:138:10) at Request.self.callback (/app/node_modules/request/request.js:185:22) at Request.emit (events.js:182:13) at Request. (/app/node_modules/request/request.js:1161:10) at Request.emit (events.js:182:13) at IncomingMessage. (/app/node_modules/request/request.js:1083:12) at Object.onceWrapper (events.js:273:13)