cannot be installed on Azure: ENOTSUP: operation not supported on socket, scandir

[capaj]

My azure production API started to fail deployments, because of a bug in glob: isaacs/node-glob#205

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, 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.
Selected node.js version 5.9.1. Use package.json file to choose a different version.
Selected npm version 3.7.3
Updating iisnode.yml at D:\home\site\wwwroot\bin\iisnode.yml
npm WARN package.json [email protected] fs is also the name of a node core module.
npm WARN package.json [email protected] No description
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No README data
npm WARN package.json [email protected] https is also the name of a node core module.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No README data
npm WARN package.json [email protected] querystring is also the name of a node core module.
npm WARN package.json [email protected] util is also the name of a node core module.
npm WARN package.json [email protected] stream is also the name of a node core module.
npm WARN package.json [email protected] url is also the name of a node core module.
glob error { [Error: ENOTSUP: operation not supported on socket, scandir 'd:\home\site\wwwroot\node_modules\azure-storage\node_modules\request\node_modules\http-signature\node_modules\sshpk\man\man1\sshpk-sign.1']
  errno: -4049,
  code: 'ENOTSUP',
  syscall: 'scandir',
  path: 'd:\\home\\site\\wwwroot\\node_modules\\azure-storage\\node_modules\\request\\node_modules\\http-signature\\node_modules\\sshpk\\man\\man1\\sshpk-sign.1' }
glob error { [Error: ENOTSUP: operation not supported on socket, scandir 'd:\home\site\wwwroot\node_modules\azure-storage\node_modules\request\node_modules\http-signature\node_modules\sshpk\man\man1\sshpk-conv.1']
  errno: -4049,
  code: 'ENOTSUP',
  syscall: 'scandir',
  path: 'd:\\home\\site\\wwwroot\\node_modules\\azure-storage\\node_modules\\request\\node_modules\\http-signature\\node_modules\\sshpk\\man\\man1\\sshpk-conv.1' }
glob error { [Error: ENOTSUP: operation not supported on socket, scandir 'd:\home\site\wwwroot\node_modules\azure-storage\node_modules\request\node_modules\http-signature\node_modules\sshpk\man\man1\sshpk-verify.1']
  errno: -4049,
  code: 'ENOTSUP',
  syscall: 'scandir',
  path: 'd:\\home\\site\\wwwroot\\node_modules\\azure-storage\\node_modules\\request\\node_modules\\http-signature\\node_modules\\sshpk\\man\\man1\\sshpk-verify.1' }
glob error { [Error: ENOTSUP: operation not supported on socket, scandir 'd:\home\site\wwwroot\node_modules\azure-storage\node_modules\request\node_modules\http-signature\node_modules\sshpk\bin\sshpk-conv']
  errno: -4049,
  code: 'ENOTSUP',
  syscall: 'scandir',
  path: 'd:\\home\\site\\wwwroot\\node_modules\\azure-storage\\node_modules\\request\\node_modules\\http-signature\\node_modules\\sshpk\\bin\\sshpk-conv' }
glob error { [Error: ENOTSUP: operation not supported on socket, scandir 'd:\home\site\wwwroot\node_modules\azure-storage\node_modules\request\node_modules\http-signature\node_modules\sshpk\bin\sshpk-sign']
  errno: -4049,
  code: 'ENOTSUP',
  syscall: 'scandir',
  path: 'd:\\home\\site\\wwwroot\\node_modules\\azure-storage\\node_modules\\request\\node_modules\\http-signature\\node_modules\\sshpk\\bin\\sshpk-sign' }
glob error { [Error: ENOTSUP: operation not supported on socket, scandir 'd:\home\site\wwwroot\node_modules\azure-storage\node_modules\request\node_modules\http-signature\node_modules\sshpk\bin\sshpk-verify']
  errno: -4049,
  code: 'ENOTSUP',
  syscall: 'scandir',
  path: 'd:\\home\\site\\wwwroot\\node_modules\\azure-storage\\node_modules\\request\\node_modules\\http-signature\\node_modules\\sshpk\\bin\\sshpk-verify' }
npm ERR! nospc ENOTSUP: operation not supported on socket, scandir 'd:\home\site\wwwroot\node_modules\azure-storage\node_modules\request\node_modules\http-signature\node_modules\sshpk\man\man1\sshpk-sign.1'
npm ERR! nospc This is most likely not a problem with npm itself
npm ERR! nospc and is related to insufficient space on your system.

npm ERR! System Windows_NT 6.2.9200
npm ERR! command "d:\\Program Files (x86)\\nodejs\\5.9.1\\node.exe" "D:\\Program Files (x86)\\npm\\1.4.28\\node_modules\\npm\\bin\\npm-cli.js" "install" "--production"
npm ERR! cwd d:\home\site\wwwroot
npm ERR! node -v v5.9.1
npm ERR! npm -v 1.4.28
npm ERR! path d:\home\site\wwwroot\node_modules\azure-storage\node_modules\request\node_modules\http-signature\node_modules\sshpk\man\man1\sshpk-sign.1
npm ERR! syscall scandir
npm ERR! code ENOTSUP
npm ERR! errno -4049
npm ERR! not ok code 0
deploy_node4.sh: line 113:  6060 Signal 112              (core dumped) "D:\Program Files (x86)\nodejs\5.9.1\node.exe" "D:\Program Files (x86)\npm\1.4.28\node_modules\npm\bin\npm-cli.js" install --production
An error has occurred during web site deployment.
npm failed
npm WARN package.json [email protected] fs is also the name of a node core module.\r\nnpm WARN package.json [email protected] No description\r\nnpm WARN package.json [email protected] No repository field.\r\nnpm WARN package.json [email protected] No README data\r\nnpm WARN package.json [email protected] https is also the name of a node core module.\r\nnpm WARN package.json [email protected] No repository field.\r\nnpm WARN package.json [email protected] No README data\r\nnpm WARN package.json [email protected] querystring is also the name of a node core module.\r\nnpm WARN package.json [email protected] util is also the name of a node core module.\r\nnpm WARN package.json [email protected] stream is also the name of a node core module.\r\nnpm WARN package.json [email protected] url is also the name of a node core module.\r\nglob error { [Error: ENOTSUP: operation not supported on socket, scandir 'd:\home\site\wwwroot\node_modules\azure-storage\node_modules\request\node_modules\http-signature\node_modules\sshpk\man\man1\sshpk-sign.1']\r\n  errno: -4049,\r\n  code: 'ENOTSUP',\r\n  syscall: 'scandir',\r\n  path: 'd:\\home\\site\\wwwroot\\node_modules\\azure-storage\\node_modules\\request\\node_modules\\http-signature\\node_modules\\sshpk\\man\\man1\\sshpk-sign.1' }\r\nglob error { [Error: ENOTSUP: operation not supported on socket, scandir 'd:\home\site\wwwroot\node_modules\azure-storage\node_modules\request\node_modules\http-signature\node_modules\sshpk\man\man1\sshpk-conv.1']\r\n  errno: -4049,\r\n  code: 'ENOTSUP',\r\n  syscall: 'scandir',\r\n  path: 'd:\\home\\site\\wwwroot\\node_modules\\azure-storage\\node_modules\\request\\node_modules\\http-signature\\node_modules\\sshpk\\man\\man1\\sshpk-conv.1' }\r\nglob error { [Error: ENOTSUP: operation not supported on socket, scandir 'd:\home\site\wwwroot\node_modules\azure-storage\node_modules\request\node_modules\http-signature\node_modules\sshpk\man\man1\sshpk-verify.1']\r\n  errno: -4049,\r\n  code: 'ENOTSUP',\r\n  syscall: 'scandir',\r\n  path: 'd:\\home\\site\\wwwroot\\node_modules\\azure-storage\\node_modules\\request\\node_modules\\http-signature\\node_modules\\sshpk\\man\\man1\\sshpk-verify.1' }\r\nglob error { [Error: ENOTSUP: operation not supported on socket, scandir 'd:\home\site\wwwroot\node_modules\azure-storage\node_modules\request\node_modules\http-signature\node_modules\sshpk\bin\sshpk-conv']\r\n  errno: -4049,\r\n  code: 'ENOTSUP',\r\n  syscall: 'scandir',\r\n  path: 'd:\\home\\site\\wwwroot\\node_modules\\azure-storage\\node_modules\\request\\node_modules\\http-signature\\node_modules\\sshpk\\bin\\sshpk-conv' }\r\nglob error { [Error: ENOTSUP: operation not supported on socket, scandir 'd:\home\site\wwwroot\node_modules\azure-storage\node_modules\request\node_modules\http-signature\node_modules\sshpk\bin\sshpk-sign']\r\n  errno: -4049,\r\n  code: 'ENOTSUP',\r\n  syscall: 'scandir',\r\n  path: 'd:\\home\\site\\wwwroot\\node_modules\\azure-storage\\node_modules\\request\\node_modules\\http-signature\\node_modules\\sshpk\\bin\\sshpk-sign' }\r\nglob error { [Error: ENOTSUP: operation not supported on socket, scandir 'd:\home\site\wwwroot\node_modules\azure-storage\node_modules\request\node_modules\http-signature\node_modules\sshpk\bin\sshpk-verify']\r\n  errno: -4049,\r\n  code: 'ENOTSUP',\r\n  syscall: 'scandir',\r\n  path: 'd:\\home\\site\\wwwroot\\node_modules\\azure-storage\\node_modules\\request\\node_modules\\http-signature\\node_modules\\sshpk\\bin\\sshpk-verify' }\r\nnpm ERR! nospc ENOTSUP: operation not supported on socket, scandir 'd:\home\site\wwwroot\node_modules\azure-storage\node_modules\request\node_modules\http-signature\node_modules\sshpk\man\man1\sshpk-sign.1'\r\nnpm ERR! nospc This is most likely not a problem with npm itself\r\nnpm ERR! nospc and is related to insufficient space on your system.\r\n\r\nnpm ERR! System Windows_NT 6.2.9200\r\nnpm ERR! command "d:\\Program Files (x86)\\nodejs\\5.9.1\\node.exe" "D:\\Program Files (x86)\\npm\\1.4.28\\node_modules\\npm\\bin\\npm-cli.js" "install" "--production"\r\nnpm ERR! cwd d:\home\site\wwwroot\r\nnpm ERR! node -v v5.9.1\r\nnpm ERR! npm -v 1.4.28\r\nnpm ERR! path d:\home\site\wwwroot\node_modules\azure-storage\node_modules\request\node_modules\http-signature\node_modules\sshpk\man\man1\sshpk-sign.1\r\nnpm ERR! syscall scandir\r\nnpm ERR! code ENOTSUP\r\nnpm ERR! errno -4049\r\nnpm ERR! not ok code 0\r\ndeploy_node4.sh: line 113:  6060 Signal 112              (core dumped) "D:\Program Files (x86)\nodejs\5.9.1\node.exe" "D:\Program Files (x86)\npm\1.4.28\node_modules\npm\bin\npm-cli.js" install --production\r\nC:\Program Files (x86)\SiteExtensions\Kudu\53.50324.2154\bin\scripts\starter.cmd bash deploy_node4.sh

Is this something I can mitigate somehow? I tried with node.js v4 and NPM 2.1.x and it failed the smae way. Note that this is happening with the latest 0.10.0 of azure-storage

[capaj]

fixed it for now by reverting back to azure-storage 0.4.2 but would love to see this one fixed in npm itself. It should be just a matter of bumping the glob dependency, right?

[hasonmsft]

@capaj , I cannot reproduce this issue from my side. I was following https://azure.microsoft.com/en-in/documentation/articles/web-sites-nodejs-develop-deploy-mac/ to create an Azure NodeJS web app and deploy it via git. As you can see from the output, I was referencing the azure-storage 0.10.0 and it works fine.
Note the Node&NPM version below:
remote: The node.js application will run with the default node.js version 4.2.3.
remote: Selected npm version 3.5.1

Could you share more for us to reproduce this issue like how did you create your app and how did you deploy/host it?

E:\HelloWorld>git push azure master
Password for 'https://[email protected]:443':
Counting objects: 5, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (4/4), done.
Writing objects: 100% (5/5), 579 bytes | 0 bytes/s, done.
Total 5 (delta 0), reused 0 (delta 0)
remote: Updating branch 'master'.
remote: Updating submodules.
remote: Preparing deployment for commit id '5f8de15bed'.
remote: Generating deployment script.
remote: Generating deployment script for node.js Web Site
remote: Generated deployment script files
remote: Running deployment command...
remote: Handling node.js deployment.
remote: KuduSync.NET from: 'D:\home\site\repository' to: 'D:\home\site\wwwroot'
remote: Copying file: '.gitignore'
remote: Copying file: 'package.json'
remote: Copying file: 'Server.js'
remote: Looking for app.js/server.js under site root.
remote: Using start-up script server.js
remote: Generated web.config.
remote: The package.json file does not specify node.js engine version constraints.
remote: The node.js application will run with the default node.js version 4.2.3.
remote: Selected npm version 3.5.1
remote: ..........................
remote: [email protected] D:\home\site\wwwroot
remote: npm WARN [email protected] No repository field.
remote: +-- [email protected]
remote: npm WARN [email protected] No license field.
remote:   +-- [email protected]
remote:   +-- [email protected]
remote:   +-- [email protected]
remote:   +-- [email protected]
remote:   ¦ +-- [email protected]
remote:   ¦ +-- [email protected]
remote:   ¦ +-- [email protected]
remote:   ¦ +-- [email protected]
remote:   ¦ +-- [email protected]
remote:   ¦ +-- [email protected]
remote:   +-- [email protected]
remote:   ¦ +-- [email protected]
remote:   ¦ +-- [email protected]
remote:   ¦ ¦ +-- [email protected]
remote:   ¦ ¦   +-- [email protected]
remote:   ¦ ¦   +-- [email protected]
remote:   ¦ +-- [email protected]
remote:   ¦ +-- [email protected]
remote:   ¦ +-- [email protected]
remote:   ¦ ¦ +-- [email protected]
remote:   ¦ +-- [email protected]
remote:   ¦ +-- [email protected]
remote:   ¦ +-- [email protected]
remote:   ¦ ¦ +-- [email protected]
remote:   ¦ +-- [email protected]
remote:   ¦ ¦ +-- [email protected]
remote:   ¦ ¦ ¦ +-- [email protected]
remote:   ¦ ¦ ¦ ??-- [email protected]
remote:   ¦ ¦ ¦ +-- [email protected]
remote:   ¦ ¦ ¦ ¦ +-- [email protected]
remote:   ¦ ¦ ¦ +-- [email protected]
remote:   ¦ ¦ ¦ +-- [email protected]
remote:   ¦ ¦ +-- [email protected]
remote:   ¦ ¦ ¦ +-- [email protected]
remote:   ¦ ¦ +-- [email protected]
remote:   ¦ ¦ ¦ +-- [email protected]
remote:   ¦ ¦ ¦ +-- [email protected]
remote:   ¦ ¦ ¦ ¦ +-- [email protected]
remote:   ¦ ¦ ¦ +-- [email protected]
remote:   ¦ ¦ ¦ +-- [email protected]
remote:   ¦ ¦ +-- [email protected]
remote:   ¦ ¦   +-- [email protected]
remote:   ¦ +-- [email protected]
remote:   ¦ ¦ +-- [email protected]
remote:   ¦ ¦ +-- [email protected]
remote:   ¦ ¦ +-- [email protected]
remote:   ¦ ¦ +-- [email protected]
remote:   ¦ +-- [email protected]
remote:   ¦ ¦ +-- [email protected]
remote:   ¦ ¦ +-- [email protected]
remote:   ¦ ¦ ¦ +-- [email protected]
remote:   ¦ ¦ ¦ +-- [email protected]
remote:   ¦ ¦ ¦ +-- [email protected]
remote:   ¦ ¦ +-- [email protected]
remote:   ¦ ¦   +-- [email protected]
remote:   ¦ ¦   +-- [email protected]
remote:   ¦ ¦   ¦ +-- [email protected]
remote:   ¦ ¦   +-- [email protected]
remote:   ¦ ¦   +-- [email protected]
remote:   ¦ ¦   +-- [email protected]
remote:   ¦ ¦   +-- [email protected]
remote:   ¦ +-- [email protected]
remote:   ¦ +-- [email protected]
remote:   ¦ +-- [email protected]
remote:   ¦ +-- [email protected]
remote:   ¦ ¦ +-- [email protected]
remote:   ¦ +-- [email protected]
remote:   ¦ +-- [email protected]
remote:   ¦ +-- [email protected]
remote:   ¦ +-- [email protected]
remote:   ¦ +-- [email protected]
remote:   +-- [email protected]
remote:   +-- [email protected]
remote:   +-- [email protected]
remote:   ¦ +-- [email protected]
remote:   +-- [email protected]
remote:
remote: Finished successfully.
remote: Running post deployment command(s)...
remote: Deployment successful.
To https://[email protected]:443/hasontestnodeweb.git
 * [new branch]      master -> master

[capaj]

@hasonmsft thanks for looking into it. I tried it again on yesterday and it installed fine. It might have something to do with our deploy scripts.I tweaked those and I don't want to change them back. Since it doesn't appear anymore, I will close this issue for now, but if it ever reappears, I will report back.