App doesn't finish deploying

[arshbucks]

First - thank you very much for sharing this deployment script. I'm trying to deploy a simple-todos test app, but am running into an error (not sure which one below is he real culprit - so attaching the log file below) Would appreciate any insight you have.

Command: bash .config/azure/deploy.sh
Looking for app.js/server.js under site root.
The package.json file does not specify node.js engine version constraints.
The node.js application will run with the default node.js version 4.4.7.
Selected npm version 2.15.8
meteor-azure: Setting NPM version
Invalid start-up command "meteor run" in package.json. Please use the format "node <script relative path>".
Missing server.js/app.js files, web.config is not generated
D:\local\AppData\npm\npm -> D:\local\AppData\npm\node_modules\npm\bin\npm-cli.js
npm@4.0.2 D:\local\AppData\npm\node_modules\npm
4.0.2
meteor-azure: Installing Meteor
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0

  1  160M    1 2031k    0     0  2651k      0  0:01:02 --:--:--  0:01:02 2651k
  5  160M    5 9215k    0     0  5218k      0  0:00:31  0:00:01  0:00:30 7184k
  9  160M    9 15.6M    0     0  5795k      0  0:00:28  0:00:02  0:00:26 7000k
 14  160M   14 23.5M    0     0  6410k      0  0:00:25  0:00:03  0:00:22 7370k
 18  160M   18 30.4M    0     0  6552k      0  0:00:25  0:00:04  0:00:21 7300k
 23  160M   23 37.3M    0     0  6634k      0  0:00:24  0:00:05  0:00:19 7244k
 28  160M   28 45.1M    0     0  6829k      0  0:00:24  0:00:06  0:00:18 7398k
 32  160M   32 52.1M    0     0  6875k      0  0:00:23  0:00:07  0:00:16 7472k
 36  160M   36 58.4M    0     0  6824k      0  0:00:24  0:00:08  0:00:16 7136k
 40  160M   40 64.3M    0     0  6746k      0  0:00:24  0:00:09  0:00:15 6931k
 44  160M   44 70.9M    0     0  6744k      0  0:00:24  0:00:10  0:00:14 6870k
 48  160M   48 78.3M    0     0  6822k      0  0:00:24  0:00:11  0:00:13 6812k
 53  160M   53 85.1M    0     0  6830k      0  0:00:24  0:00:12  0:00:12 6761k
 57  160M   57 92.1M    0     0  6856k      0  0:00:23  0:00:13  0:00:10 6912k
 61  160M   61 99.0M    0     0  6868k      0  0:00:23  0:00:14  0:00:09 7107k
 66  160M   66  106M    0     0  6889k      0  0:00:23  0:00:15  0:00:08 7203k
 70  160M   70  113M    0     0  6920k      0  0:00:23  0:00:16  0:00:07 7152k
 74  160M   74  120M    0     0  6924k      0  0:00:23  0:00:17  0:00:06 7164k
 79  160M   79  128M    0     0  6988k      0  0:00:23  0:00:18  0:00:05 7353k
 83  160M   83  134M    0     0  6949k      0  0:00:23  0:00:19  0:00:04 7187k
 88  160M   88  141M    0     0  6982k      0  0:00:23  0:00:20  0:00:03 7276k
 93  160M   93  149M    0     0  7028k      0  0:00:23  0:00:21  0:00:02 7392k
 97  160M   97  156M    0     0  7035k      0  0:00:23  0:00:22  0:00:01 7427k
100  160M  100  160M    0     0  7036k      0  0:00:23  0:00:23 --:--:-- 7229k
Command 'starter.cmd bash .config/az ...' was aborted due to no output nor CPU activity for 61 seconds. You can increase the SCM_COMMAND_IDLE_TIMEOUT app setting (or WEBJOBS_IDLE_TIMEOUT if this is a WebJob) if needed.\r\nstarter.cmd bash .config/azure/deploy.sh
One or more errors occurred.
Command 'starter.cmd bash .config/az ...' was aborted due to no output nor CPU activity for 61 seconds. You can increase the SCM_COMMAND_IDLE_TIMEOUT app setting (or WEBJOBS_IDLE_TIMEOUT if this is a WebJob) if needed.\r\nstarter.cmd bash .config/azure/deploy.sh

[ramijarrar]

What is your SCM_COMMAND_IDLE_TIMEOUT?

[arshbucks]

60 (seconds) - it says there was no CPU activity so don't think that would change anything right? i.e. It's not like it is crunching away at installing meteor...

[ramijarrar]

Because of the way some steps are executed, CPU activity will not prevent less noisy commands from tripping the idle timeout (hence why the recommended value is 3600).

[arshbucks]

gotcha, thanks, that works. Took 510 seconds to deploy so might take even longer for more complex apps...

If helpful for anyone else else testing it out:

1. Set SCM_COMMAND_IDLE_TIMEOUT = 3600 and WEBJOBS_IDLE_TIMEOUT = 3600 too if needed
2. need to add a MONGO_URL etc as mentioned in the README here https://github.com/christopheranderson/azure-demeteorizer

[ramijarrar]

They are documented in the README here :)

[arshbucks]

hah - my mistake. Didn't see that for whatever reason... used to use the demeteorizer before, this is substantially easier. Thanks again!

[ramijarrar]

No problem.

Also, regarding build times: the first is going to be the slowest (as it installs Meteor and caches any dependencies) but after that it is more or less just the same time it takes to meteor build from anywhere else.