Deployment to Azure failed | REASON: Revert "Update language.js" (#3406)

[ScheddyD]

Hiya,

I'm new to the Nightscout setup and just yesterday finished my setup for mongodb, GitHub and Azure. When deploying to Azure it always fails at the same steps. I have tried restarting, redeploying, forked again into my depository, etc.

Today I tried setting up the App with Heroku instead of Azure, but there deployment also fails.
I am using Mozilla Firefox.

Here is a screenshot taken from Azure:
(https://user-images.githubusercontent.com/41518553/43149250-4c4503e4-8f67-11e8-9de5-83c8791b3074.JPG)

Here is my activity log:

"Command: bash deploy.sh
Handling node.js deployment.
KuduSync.NET from: 'D:\home\site\repository' to: 'D:\home\site\wwwroot'
Copying file: '.bowerrc'
Copying file: '.dockerignore'
[...]
Copying file: 'lib\hashauth.js'
Copying file: 'lib\language.js'
Omitting next output lines...
Using start-up script server.js from package.json.
Node.js versions available on the platform are: 0.6.20, 0.8.2, 0.8.19, 0.8.26, 0.8.27, 0.8.28, 0.10.5, 0.10.18, 0.10.21, 0.10.24, 0.10.26, 0.10.28, 0.10.29, 0.10.31, 0.10.32, 0.10.40, 0.12.0, 0.12.2, 0.12.3, 0.12.6, 4.0.0, 4.1.0, 4.1.2, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.3.0, 4.3.2, 4.4.0, 4.4.1, 4.4.6, 4.4.7, 4.5.0, 4.6.0, 4.6.1, 4.8.4, 5.0.0, 5.1.1, 5.3.0, 5.4.0, 5.5.0, 5.6.0, 5.7.0, 5.7.1, 5.8.0, 5.9.1, 6.0.0, 6.1.0, 6.2.2, 6.3.0, 6.5.0, 6.6.0, 6.7.0, 6.9.0, 6.9.1, 6.9.2, 6.9.4, 6.9.5, 6.10.0, 6.10.3, 6.11.1, 6.11.2, 6.11.5, 6.12.2, 6.12.3, 7.0.0, 7.1.0, 7.2.0, 7.3.0, 7.4.0, 7.5.0, 7.6.0, 7.7.0, 7.7.4, 7.10.0, 7.10.1, 8.0.0, 8.1.4, 8.4.0, 8.5.0, 8.7.0, 8.8.0, 8.8.1, 8.9.0, 8.9.3, 8.9.4, 8.10.0, 8.11.1, 10.0.0, 10.6.0.
Selected node.js version 8.9.4. Use package.json file to choose a different version.
Selected npm version 5.3.0
Updating iisnode.yml at D:\home\site\wwwroot\iisnode.yml
npm WARN invalid config scripts-prepend-node-path="--production"
WARN notice [SECURITY] hoek has the following vulnerability: 1 moderate. Go here for more details: https://nodesecurity.io/advisories?search=hoek&version=2.16.3 - Run npm i npm@latest -g to upgrade your npm version, and then npm audit to get more info.
WARN notice [SECURITY] deep-extend has the following vulnerability: 1 low. Go here for more details: https://nodesecurity.io/advisories?search=deep-extend&version=0.4.2 - Run npm i npm@latest -g to upgrade your npm version, and then npm audit to get more info.
WARN notice [SECURITY] sshpk has the following vulnerability: 1 high. Go here for more details: https://nodesecurity.io/advisories?search=sshpk&version=1.13.0 - Run npm i npm@latest -g to upgrade your npm version, and then npm audit to get more info.
WARN notice [SECURITY] tough-cookie has the following vulnerability: 1 high. Go here for more details: https://nodesecurity.io/advisories?search=tough-cookie&version=2.3.2 - Run npm i npm@latest -g to upgrade your npm version, and then npm audit to get more info.
WARN notice [SECURITY] stringstream has the following vulnerability: 1 moderate. Go here for more details: https://nodesecurity.io/advisories?search=stringstream&version=0.0.5 - Run npm i npm@latest -g to upgrade your npm version, and then npm audit to get more info.
WARN notice [SECURITY] debug has the following vulnerability: 1 low. Go here for more details: https://nodesecurity.io/advisories?search=debug&version=2.6.8 - Run npm i npm@latest -g to upgrade your npm version, and then npm audit to get more info.
npm ERR! path D:\home\site\wwwroot\node_modules\fsevents\node_modules\dashdash\node_modules
npm ERR! code EPERM
npm ERR! errno -4048
npm ERR! syscall scandir
npm ERR! Error: EPERM: operation not permitted, scandir 'D:\home\site\wwwroot\node_modules\fsevents\node_modules\dashdash\node_modules'
npm ERR! { Error: EPERM: operation not permitted, scandir 'D:\home\site\wwwroot\node_modules\fsevents\node_modules\dashdash\node_modules'
npm ERR! stack: 'Error: EPERM: operation not permitted, scandir 'D:\home\site\wwwroot\node_modules\fsevents\node_modules\dashdash\node_modules'',
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'scandir',
npm ERR! path: 'D:\home\site\wwwroot\node_modules\fsevents\node_modules\dashdash\node_modules' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR! A complete log of this run can be found in:
npm ERR! D:\local\AppData\npm-cache_logs\2018-07-24T14_40_35_169Z-debug.log
An error has occurred during web site deployment.
npm failed
npm WARN invalid config scripts-prepend-node-path="--production"\r\nWARN notice [SECURITY] hoek has the following vulnerability: 1 moderate. Go here for more details: https://nodesecurity.io/advisories?search=hoek&version=2.16.3 - Run npm i npm@latest -g to upgrade your npm version, and then npm audit to get more info.\r\nWARN notice [SECURITY] deep-extend has the following vulnerability: 1 low. Go here for more details: https://nodesecurity.io/advisories?search=deep-extend&version=0.4.2 - Run npm i npm@latest -g to upgrade your npm version, and then npm audit to get more info.\r\nWARN notice [SECURITY] sshpk has the following vulnerability: 1 high. Go here for more details: https://nodesecurity.io/advisories?search=sshpk&version=1.13.0 - Run npm i npm@latest -g to upgrade your npm version, and then npm audit to get more info.\r\nWARN notice [SECURITY] tough-cookie has the following vulnerability: 1 high. Go here for more details: https://nodesecurity.io/advisories?search=tough-cookie&version=2.3.2 - Run npm i npm@latest -g to upgrade your npm version, and then npm audit to get more info.\r\nWARN notice [SECURITY] stringstream has the following vulnerability: 1 moderate. Go here for more details: https://nodesecurity.io/advisories?search=stringstream&version=0.0.5 - Run npm i npm@latest -g to upgrade your npm version, and then npm audit to get more info.\r\nWARN notice [SECURITY] debug has the following vulnerability: 1 low. Go here for more details: https://nodesecurity.io/advisories?search=debug&version=2.6.8 - Run npm i npm@latest -g to upgrade your npm version, and then npm audit to get more info.\r\nnpm ERR! path D:\home\site\wwwroot\node_modules\fsevents\node_modules\dashdash\node_modules\r\nnpm ERR! code EPERM\r\nnpm ERR! errno -4048\r\nnpm ERR! syscall scandir\r\nnpm ERR! Error: EPERM: operation not permitted, scandir 'D:\home\site\wwwroot\node_modules\fsevents\node_modules\dashdash\node_modules'\r\nnpm ERR! { Error: EPERM: operation not permitted, scandir 'D:\home\site\wwwroot\node_modules\fsevents\node_modules\dashdash\node_modules'\r\nnpm ERR! stack: 'Error: EPERM: operation not permitted, scandir 'D:\home\site\wwwroot\node_modules\fsevents\node_modules\dashdash\node_modules'',\r\nnpm ERR! errno: -4048,\r\nnpm ERR! code: 'EPERM',\r\nnpm ERR! syscall: 'scandir',\r\nnpm ERR! path: 'D:\home\site\wwwroot\node_modules\fsevents\node_modules\dashdash\node_modules' }\r\nnpm ERR! \r\nnpm ERR! Please try running this command again as root/Administrator.\r\n\r\nnpm ERR! A complete log of this run can be found in:\r\nnpm ERR! D:\local\AppData\npm-cache_logs\2018-07-24T14_40_35_169Z-debug.log\r\nD:\Program Files (x86)\SiteExtensions\Kudu\75.10629.3460\bin\Scripts\starter.cmd bash deploy.sh"
![failed_deployment_1]"

Thank you for your great work and your help. Really happy to be a part of this!

Kind regards

[PieterGit]

@ScheddyD can you give the dev branch a try. It's nearly ready to be released. I wonder if that fixes your Azure deployment problems. I don't use Azure myself so can't help you a lot with it.

[ScheddyD]

@PieterGit trying the dev branch certainly got rid of the first problem. Deployment still failed, however now the REASON is "Merge pull request #3715 from herzogmedia/dev-langUpdateGER-180720 Update german Language files". I guess that's because dev branch might not yet be ready as you stated.

New activity log as follows:

Command: bash deploy.sh
Handling node.js deployment.
KuduSync.NET from: 'D:\home\site\repository' to: 'D:\home\site\wwwroot'
Copying file: '.bowerrc'
Copying file: '.dockerignore'
[...]
Copying file: 'lib\language.js'
Copying file: 'lib\levels.js'
Copying file: 'lib\notifications.js'
Copying file: 'lib\profilefunctions.js'
Copying file: 'lib\sandbox.js'
Copying file: 'lib\settings.js'
Copying file: 'lib\times.js'
Omitting next output lines...
Using start-up script server.js from package.json.
Node.js versions available on the platform are: 0.6.20, 0.8.2, 0.8.19, 0.8.26, 0.8.27, 0.8.28, 0.10.5, 0.10.18, 0.10.21, 0.10.24, 0.10.26, 0.10.28, 0.10.29, 0.10.31, 0.10.32, 0.10.40, 0.12.0, 0.12.2, 0.12.3, 0.12.6, 4.0.0, 4.1.0, 4.1.2, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.3.0, 4.3.2, 4.4.0, 4.4.1, 4.4.6, 4.4.7, 4.5.0, 4.6.0, 4.6.1, 4.8.4, 5.0.0, 5.1.1, 5.3.0, 5.4.0, 5.5.0, 5.6.0, 5.7.0, 5.7.1, 5.8.0, 5.9.1, 6.0.0, 6.1.0, 6.2.2, 6.3.0, 6.5.0, 6.6.0, 6.7.0, 6.9.0, 6.9.1, 6.9.2, 6.9.4, 6.9.5, 6.10.0, 6.10.3, 6.11.1, 6.11.2, 6.11.5, 6.12.2, 6.12.3, 7.0.0, 7.1.0, 7.2.0, 7.3.0, 7.4.0, 7.5.0, 7.6.0, 7.7.0, 7.7.4, 7.10.0, 7.10.1, 8.0.0, 8.1.4, 8.4.0, 8.5.0, 8.7.0, 8.8.0, 8.8.1, 8.9.0, 8.9.3, 8.9.4, 8.10.0, 8.11.1, 10.0.0, 10.6.0.
Selected node.js version 8.11.1. Use package.json file to choose a different version.
Selected npm version 6.1.0
Updating iisnode.yml at D:\home\site\wwwroot\iisnode.yml

Nightscout@0.10.3-dev-20180708 postinstall D:\home\site\wwwroot
webpack --mode production --config webpack.config.js && npm run-script update-buster

One CLI for webpack must be installed. These are recommended choices, delivered as separate packages:

• webpack-cli (https://github.com/webpack/webpack-cli)
  The original webpack full-featured CLI.
• webpack-command (https://github.com/webpack-contrib/webpack-command)
  A lightweight, opinionated webpack CLI.
  We will use "npm" to install the CLI via "npm install -D".
  Which one do you like to install (webpack-cli/webpack-command):
  An error has occurred during web site deployment.
  npm failed
  Command 'starter.cmd bash deploy.sh' was aborted due to no output nor CPU activity for 60 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 deploy.sh
  One or more errors occurred.
  Command 'starter.cmd bash deploy.sh' was aborted due to no output nor CPU activity for 60 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 deploy.sh

[PieterGit]

@ScheddyD thanks for the report. I fixed this and tested it in Azure. Please retry the dev branch and report your fnidings. Closing this issue, because I'm quite confident it's fixed for Azure now. Please reopen if the problem persists.

[ScheddyD]

Thank you! Unfortunately it's not quite working yet.

New activity log:
[...]
One CLI for webpack must be installed. These are recommended choices, delivered as separate packages:

• webpack-cli (https://github.com/webpack/webpack-cli)
  The original webpack full-featured CLI.
• webpack-command (https://github.com/webpack-contrib/webpack-command)
  A lightweight, opinionated webpack CLI.
  We will use "npm" to install the CLI via "npm install -D".
  Which one do you like to install (webpack-cli/webpack-command):
  npm ERR! code ELIFECYCLE
  npm ERR! errno 4294967295
  npm ERR! Nightscout@0.10.3-dev-20180708 postinstall: webpack --mode production --config webpack.config.js && npm run-script update-buster
  npm ERR! Exit status 4294967295
  npm ERR!
  npm ERR! Failed at the Nightscout@0.10.3-dev-20180708 postinstall script.
  npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
  An error has occurred during web site deployment.
  npm failed
  Command 'starter.cmd bash deploy.sh' was aborted due to no output nor CPU activity for 60 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 deploy.sh
  One or more errors occurred.
  Command 'starter.cmd bash deploy.sh' was aborted due to no output nor CPU activity for 60 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 deploy.sh