Fix nightmare.js script

So with regard to the process hanging/halting periodically, yes there is something I would do. Assumptions are that periodically electron/nightmare get's stuck beyond the 40 second timeouts configured. Electron is used by nightmare and is a heavy process and might hang periodically. I did have safeguards to make sure electon was killed when nightmare completed each time (terminateNightmare) - as I detected that it did not always exit itself and would climb in resource utilization. My solution : - I can modify the program with a master/child process pattern - using node library to fork a child node process in which to run the normal loadspeed operations. From the child process send a message periodically. when the message ceases to arrive a the master process withing a configured threshold (say 2-3 minutes), the master process kills the child process and recreates the child process to begin again. - I would also take out your security email call and remove you failsafe code - which is currently breaking the program after 5 minutes every time. I'll check for anything else that my have been modified that could cause an issue. Additional Info: To double check - it would be good to have a little more info on the process hanging - before making your changes (failsafe), how often did you estimate you found the process locked? Daily or more or less? Did you notice it at the same position in the logs each time? Any error output? It is also possible it's not related to the node program loadspeed, but the use of xvfb-run in the [login to view URL] script (headless server, virtual frame buffer). I don't use this in my environment, but I see some people had hangs due to this or variations, example : [login to view URL] That is an interesting example if you can read that. If the issue persists after my update, we might look into altering how you do this type of run