5

We are running node application in Azure Virtual Machine, meanwhile we also want to restart VM at some certain time with the help of Azure Automation (or via management portal).

But how can we restart the node application after VM restarted?

We tried a lot of ways to achieve this, including add the Task Scheduler, add command to the registry key (LocalMachine\..\Run), use Custom Script Extension for VM ...

All above failed. What we want is after the VM restart, the node application can be started automatically. If we then remote to the VM with predefined account, some of above ways can work. However, this is not the scenery, we only want to remote only once at the beginning, not every restart.

So, what't the right way to achieve this, to start a process or execute a command after VM automatically restart without manually login?

Jerry Bian
  • 3,998
  • 6
  • 29
  • 54
  • possible duplicate of [Auto start node.js server on boot](http://stackoverflow.com/questions/20445599/auto-start-node-js-server-on-boot) – Bruno Faria Jun 01 '15 at 13:02
  • @BrunoFaria Ok, I will give it a try later. But since it's not target to Azure Virtual Machine, and I think my problem is more related to Azure Windows VM. – Jerry Bian Jun 01 '15 at 13:10
  • This seems like a job for Windows Services. Have you looked at this project? https://github.com/coreybutler/node-windows – Chris N Jun 01 '15 at 19:45

1 Answers1

3

I've already tried a lot of ways to achieve this goal, and from my point of view, Task Scheduler is the best choice to do this kind of job.

The key point is never let the Windows Command Prompt exist after starting your process. For example, at first we use forever to launch node application. Since the forever command returns quickly, which means all the command execution finished. Thus, the Windows Command Prompt process will be killed, and along with the node process.

What we did is, we use another way to launch forever (forever-monitor), which is used in the code. By doing this, we can simply use node command to start this forever startup file. Since the node command will block the command prompt, the node application won't be killed anymore.

Another alternative is use Azure Automation remotely run the startup script.

The full script can be found here, key point is:

$PSCommandResult = Invoke-command -AsJob -ConnectionUri $Using:Uri.AbsoluteUri -credential $Using:mycreds -ScriptBlock { Invoke-Expression "D:\start.ps1" }

In start.ps1 script, we also should not exit the execution, which we can use Start-Sleep command to achieve this. The script can be:

forever start --sourceDir D: start.js
Start-Sleep -s 86400

Hope this two approaches can help you.

Jerry Bian
  • 3,998
  • 6
  • 29
  • 54