server.toml indicates wrong parameter about mx-chain-go

[scraido]

I found it we can automatically connect, by double clicking the node.exe that lies on the respective folder instead of replacing the server.toml file with the same file or by typing node.exe on the right directory on cmd, but that will bring a message to us;

[GIN-debug] [WARNING] Running in "debug" mode. Switch to "release" mode in production.

[scraido]

just for adding, this (debug mode), has bring me additional issue of suddenly close of cmd windows, for the main cmd and the additional cmd windows,, and you can say this as suddenly network connection lost, just for wrap my report before this i experience 1 Node can run near 8Gb of RAM (with double clicking), and i've report this before on 9/10 21.20 UTC +7 @ElrondValidators tele account, Ty

[iulianpascalau]

server.toml is used for just for elastic search component and, if left blank, will not cause node operation problems. The message [GIN-debug] [WARNING] Running in "debug" mode. Switch to "release" mode in production. is just a message from the web server, no issues there. We are no longer support windows so this issue can be closed.