- I do not know how to debug the cache server.
- Cache server runs in my local machine making it difficult to identify problems.
- Multiple clients are running the cache server and are making it unresponsive.
- You need to debug the cache server.
- Install Node.js: Get the latest build of Node.js here: https://nodejs.org/en/download. Once Node.js is installed, it should be added to your "/usr/bin/" path. This will add the extra tools needed for debugging.
- Install the Node inspector: 'npm install -g node-inspector' (Run this through the terminal). *MAC: If by any chance you get an error stating "This is most likely a problem with the v8-profiler package, not with npm itself. " a workaround for this is to write 'sudo npm install -g node-inspector --unsafe-perm' *WINDOWS: Your Node.js application should be stored in C:\Program Files\nodejs, thus using the Command Line write : cd C:\Program Files\nodejs npm install -g node-inspector.
- Modify the script that launches Node.js to use "node-debug". This script can be found in the folder where you stored the Cache Sever. On OS X, the script is "RunOSX.command", while on Linux it is "RunLinux.sh" and in Windows it is "RunWin.cmd". (See the images below).
- Replace this obsolete method in the cache server scripts (LegacyCacheServer.js and CacheServer.js) "path.existsSync --> fs.existsSync"
- Once you execute the script according to your platform, this will use "node-debug", which should launch Google Chrome and allow you to debug the Cache Server code. (You need to have Google Chrome installed). *WINDOWS: You have to do something different here. You need to execute the main.js script in the command prompt like this "node-debug C:...\CacheServer-5.3.0f4\CacheServer\main.js"
This article applies to Unity versions 5.x