Cancel
Showing results for 
Search instead for 
Did you mean: 

facing error while test deployment of the app

Creator
Creator

Hello,

 

I developed an app with nodejs, uploaded it to mindsphere with cf push and tested it. I have uploaded the ZIP file and the manifest.file. During the check in progress (at 20%) I get an email from the validation team that my app does not  start in their environment and I should advise them to fix it. I wanted to pack my app in a docker image but read that mindsphere does not support it. 

 

I'm new to mindsphere and I'm not sure exactly how to give the validation team advice. I suspect that it is a version problem of one of the software on his part or a small configuration error.

 

he sent me this file: 

 

cf logs myapp --recent
Retrieving logs for app myapp in org prodvali / space myapp-1.2 as employeename@siemens.com...

   2019-05-07T16:27:32.62+0530 [API/4] OUT Updated app with guid 24841e95-cbb3-48c4-b352-ab58cb7aca00 ({"disk_quota"=>512, "environment_json"=>"[PRIVATE DATA HIDDEN]", "health_check_http_endpoint"=>"", "health_check_type"=>"port", "instances"=>1, "memory"=>1024, "name"=>"myapp", "state"=>"STOPPED"})
   2019-05-07T16:27:54.65+0530 [STG/0] OUT Downloading mendix_buildpack...
   2019-05-07T16:27:54.65+0530 [STG/0] OUT Downloading dotnet_core_buildpack...
   2019-05-07T16:27:54.65+0530 [STG/0] OUT Downloading python_buildpack...
   2019-05-07T16:27:54.66+0530 [STG/0] OUT Downloading nodejs_buildpack...
   2019-05-07T16:27:54.66+0530 [STG/0] OUT Downloading php_buildpack...
   2019-05-07T16:27:54.68+0530 [STG/0] OUT Downloaded nodejs_buildpack
   2019-05-07T16:27:54.68+0530 [STG/0] OUT Downloading ruby_buildpack...
   2019-05-07T16:27:54.68+0530 [STG/0] OUT Downloaded dotnet_core_buildpack
   2019-05-07T16:27:54.68+0530 [STG/0] OUT Downloading go_buildpack...
   2019-05-07T16:27:54.68+0530 [STG/0] OUT Downloaded mendix_buildpack
   2019-05-07T16:27:54.68+0530 [STG/0] OUT Downloading java_buildpack...
   2019-05-07T16:27:54.69+0530 [STG/0] OUT Downloaded python_buildpack
   2019-05-07T16:27:54.69+0530 [STG/0] OUT Downloading staticfile_buildpack...
   2019-05-07T16:27:54.69+0530 [STG/0] OUT Downloaded php_buildpack
   2019-05-07T16:27:54.69+0530 [STG/0] OUT Downloaded ruby_buildpack
   2019-05-07T16:27:54.69+0530 [STG/0] OUT Downloaded java_buildpack
   2019-05-07T16:27:54.70+0530 [STG/0] OUT Downloaded go_buildpack
   2019-05-07T16:27:54.70+0530 [STG/0] OUT Downloaded staticfile_buildpack
   2019-05-07T16:27:54.70+0530 [STG/0] OUT Cell 990a5533-fad7-43c8-8924-725ff803b7bc creating container for instance 5924a916-49d7-4f88-8344-f4b90266f145
   2019-05-07T16:27:55.36+0530 [STG/0] OUT Cell 990a5533-fad7-43c8-8924-725ff803b7bc successfully created container for instance 5924a916-49d7-4f88-8344-f4b90266f145
   2019-05-07T16:27:55.58+0530 [STG/0] OUT Downloading app package...
   2019-05-07T16:27:56.27+0530 [STG/0] OUT Downloaded app package (8.1M)
   2019-05-07T16:29:24.77+0530 [API/4] OUT Updated app with guid 24841e95-cbb3-48c4-b352-ab58cb7aca00 ({"state"=>"STARTED"})
   2019-05-07T16:29:24.82+0530 [STG/0] OUT Downloading nodejs_buildpack...
   2019-05-07T16:29:24.86+0530 [STG/0] OUT Downloaded nodejs_buildpack
   2019-05-07T16:29:24.86+0530 [STG/0] OUT Cell 1d0d7df4-ec1d-401f-bbf5-7c4b8ce591b7 creating container for instance bb2fa76a-4c11-4dc4-9ed3-9ff3d7353e1f
   2019-05-07T16:29:25.28+0530 [STG/0] OUT Cell 1d0d7df4-ec1d-401f-bbf5-7c4b8ce591b7 successfully created container for instance bb2fa76a-4c11-4dc4-9ed3-9ff3d7353e1f
   2019-05-07T16:29:25.43+0530 [STG/0] OUT Downloading app package...
   2019-05-07T16:29:26.49+0530 [STG/0] OUT Downloaded app package (8.1M)
   2019-05-07T16:29:26.56+0530 [STG/0] OUT -----> Nodejs Buildpack version 1.6.43
   2019-05-07T16:29:26.74+0530 [STG/0] OUT -----> Installing binaries
   2019-05-07T16:29:26.74+0530 [STG/0] OUT        engines.node (package.json): unspecified
   2019-05-07T16:29:26.74+0530 [STG/0] OUT        engines.npm (package.json): unspecified (use default)
   2019-05-07T16:29:26.74+0530 [STG/0] OUT        **WARNING** Node version not specified in package.json or .nvmrc. See: http://docs.cloudfoundry.org/buildpacks/node/node-tips.html
   2019-05-07T16:29:26.74+0530 [STG/0] OUT -----> Installing node 6.16.0
   2019-05-07T16:29:26.74+0530 [STG/0] OUT        Download [https://buildpacks.cloudfoundry.org/dependencies/node/node-6.16.0-linux-x64-cflinuxfs3-45f43c54.tgz]
   2019-05-07T16:29:27.00+0530 [STG/0] OUT        **WARNING** node 6.x will no longer be available in new buildpacks released after 2019-04-30.
   2019-05-07T16:29:27.00+0530 [STG/0] OUT        See: https://github.com/nodejs/LTS
   2019-05-07T16:29:27.98+0530 [STG/0] OUT        Using default npm version: 3.10.10
   2019-05-07T16:29:27.98+0530 [STG/0] OUT -----> Installing yarn 1.13.0
   2019-05-07T16:29:27.98+0530 [STG/0] OUT        Download [https://buildpacks.cloudfoundry.org/dependencies/yarn/yarn-1.13.0-any-stack-125d40eb.tar.gz]
   2019-05-07T16:29:28.57+0530 [STG/0] OUT        Installed yarn 1.13.0
   2019-05-07T16:29:28.57+0530 [STG/0] OUT -----> Creating runtime environment
   2019-05-07T16:29:28.57+0530 [STG/0] OUT        **WARNING** No package.json found
   2019-05-07T16:29:28.57+0530 [STG/0] OUT        PRO TIP: It is recommended to vendor the application's Node.js dependencies
   2019-05-07T16:29:28.57+0530 [STG/0] OUT        Visit http://docs.cloudfoundry.org/buildpacks/node/index.html#vendoring
   2019-05-07T16:29:28.57+0530 [STG/0] OUT        NODE_ENV=production
   2019-05-07T16:29:28.57+0530 [STG/0] OUT        NODE_HOME=/tmp/contents497594838/deps/0/node
   2019-05-07T16:29:28.57+0530 [STG/0] OUT        NODE_MODULES_CACHE=true
   2019-05-07T16:29:28.57+0530 [STG/0] OUT        NODE_VERBOSE=false
   2019-05-07T16:29:28.57+0530 [STG/0] OUT        NPM_CONFIG_LOGLEVEL=error
   2019-05-07T16:29:28.57+0530 [STG/0] OUT        NPM_CONFIG_PRODUCTION=true
   2019-05-07T16:29:28.57+0530 [STG/0] OUT -----> Building dependencies
   2019-05-07T16:29:28.57+0530 [STG/0] OUT        Skipping (no package.json)
   2019-05-07T16:29:28.79+0530 [STG/0] OUT        **WARNING** No package.json found
   2019-05-07T16:29:28.79+0530 [STG/0] OUT        **WARNING** This app may not specify any way to start a node process
   2019-05-07T16:29:28.79+0530 [STG/0] OUT        See: https://docs.cloudfoundry.org/buildpacks/node/node-tips.html#start
   2019-05-07T16:29:33.37+0530 [STG/0] OUT Exit status 0
   2019-05-07T16:29:33.37+0530 [STG/0] OUT Uploading droplet, build artifacts cache...
   2019-05-07T16:29:33.37+0530 [STG/0] OUT Uploading build artifacts cache...
   2019-05-07T16:29:33.37+0530 [STG/0] OUT Uploading droplet...
   2019-05-07T16:29:33.71+0530 [STG/0] OUT Uploaded build artifacts cache (15.2M)
   2019-05-07T16:29:33.85+0530 [API/4] OUT Creating droplet for app with guid 24841e95-cbb3-48c4-b352-ab58cb7aca00
   2019-05-07T16:29:38.94+0530 [STG/0] OUT Uploaded droplet (22.5M)
   2019-05-07T16:29:38.95+0530 [STG/0] OUT Uploading complete
   2019-05-07T16:29:39.35+0530 [STG/0] OUT Cell 1d0d7df4-ec1d-401f-bbf5-7c4b8ce591b7 stopping instance bb2fa76a-4c11-4dc4-9ed3-9ff3d7353e1f
   2019-05-07T16:29:39.35+0530 [STG/0] OUT Cell 1d0d7df4-ec1d-401f-bbf5-7c4b8ce591b7 destroying container for instance bb2fa76a-4c11-4dc4-9ed3-9ff3d7353e1f
   2019-05-07T16:29:39.80+0530 [STG/0] OUT Cell 1d0d7df4-ec1d-401f-bbf5-7c4b8ce591b7 successfully destroyed container for instance bb2fa76a-4c11-4dc4-9ed3-9ff3d7353e1f
   2019-05-07T16:29:39.84+0530 [CELL/0] OUT Cell 17d6d688-b0f3-4bd5-9b28-3bcd72dcfb64 creating container for instance f7c0a656-1f43-4c22-5110-a848
   2019-05-07T16:29:40.21+0530 [CELL/0] OUT Cell 17d6d688-b0f3-4bd5-9b28-3bcd72dcfb64 successfully created container for instance f7c0a656-1f43-4c22-5110-a848
   2019-05-07T16:29:41.79+0530 [CELL/0] OUT Starting health monitoring of container
   2019-05-07T16:29:42.39+0530 [APP/PROC/WEB/0] ERR npm ERR! Linux 4.15.0-45-generic
   2019-05-07T16:29:42.39+0530 [APP/PROC/WEB/0] ERR npm ERR! argv "/home/vcap/deps/0/node/bin/node" "/home/vcap/deps/0/bin/npm" "start"
   2019-05-07T16:29:42.39+0530 [APP/PROC/WEB/0] ERR npm ERR! node v6.16.0
   2019-05-07T16:29:42.39+0530 [APP/PROC/WEB/0] ERR npm ERR! npm  v3.10.10
   2019-05-07T16:29:42.39+0530 [APP/PROC/WEB/0] ERR npm ERR! path /home/vcap/app/package.json
   2019-05-07T16:29:42.39+0530 [APP/PROC/WEB/0] ERR npm ERR! code ENOENT
   2019-05-07T16:29:42.39+0530 [APP/PROC/WEB/0] ERR npm ERR! errno -2
   2019-05-07T16:29:42.39+0530 [APP/PROC/WEB/0] ERR npm ERR! syscall open
   2019-05-07T16:29:42.39+0530 [APP/PROC/WEB/0] ERR npm ERR! enoent ENOENT: no such file or directory, open '/home/vcap/app/package.json'
   2019-05-07T16:29:42.39+0530 [APP/PROC/WEB/0] ERR npm ERR! enoent ENOENT: no such file or directory, open '/home/vcap/app/package.json'
   2019-05-07T16:29:42.39+0530 [APP/PROC/WEB/0] ERR npm ERR! enoent This is most likely not a problem with npm itself
   2019-05-07T16:29:42.39+0530 [APP/PROC/WEB/0] ERR npm ERR! enoent and is related to npm not being able to find a file.
   2019-05-07T16:29:42.39+0530 [APP/PROC/WEB/0] ERR npm ERR! enoent
   2019-05-07T16:29:42.40+0530 [APP/PROC/WEB/0] ERR npm ERR! Please include the following file with any support request:
   2019-05-07T16:29:42.40+0530 [APP/PROC/WEB/0] ERR npm ERR!     /home/vcap/app/npm-debug.log
   2019-05-07T16:29:42.42+0530 [APP/PROC/WEB/0] OUT Exit status 254
   2019-05-07T16:29:42.63+0530 [CELL/0] OUT Cell 17d6d688-b0f3-4bd5-9b28-3bcd72dcfb64 stopping instance f7c0a656-1f43-4c22-5110-a848
   2019-05-07T16:29:42.63+0530 [CELL/0] OUT Cell 17d6d688-b0f3-4bd5-9b28-3bcd72dcfb64 destroying container for instance f7c0a656-1f43-4c22-5110-a848
   2019-05-07T16:29:42.69+0530 [CELL/0] OUT Cell 147dd272-7f28-41d6-a2e9-afc4c25f4fa5 creating container for instance e4b17c20-4306-4b57-5019-547b
   2019-05-07T16:29:43.20+0530 [CELL/0] OUT Cell 147dd272-7f28-41d6-a2e9-afc4c25f4fa5 successfully created container for instance e4b17c20-4306-4b57-5019-547b
   2019-05-07T16:29:43.68+0530 [CELL/0] OUT Cell 17d6d688-b0f3-4bd5-9b28-3bcd72dcfb64 successfully destroyed container for instance f7c0a656-1f43-4c22-5110-a848
   2019-05-07T16:29:46.25+0530 [APP/PROC/WEB/0] ERR npm ERR! Linux 4.15.0-45-generic
   2019-05-07T16:29:46.25+0530 [APP/PROC/WEB/0] ERR npm ERR! argv "/home/vcap/deps/0/node/bin/node" "/home/vcap/deps/0/bin/npm" "start"
   2019-05-07T16:29:46.25+0530 [APP/PROC/WEB/0] ERR npm ERR! node v6.16.0
   2019-05-07T16:29:46.25+0530 [APP/PROC/WEB/0] ERR npm ERR! npm  v3.10.10
   2019-05-07T16:29:46.25+0530 [APP/PROC/WEB/0] ERR npm ERR! path /home/vcap/app/package.json
   2019-05-07T16:29:46.25+0530 [APP/PROC/WEB/0] ERR npm ERR! code ENOENT
   2019-05-07T16:29:46.25+0530 [APP/PROC/WEB/0] ERR npm ERR! errno -2
   2019-05-07T16:29:46.25+0530 [APP/PROC/WEB/0] ERR npm ERR! syscall open
   2019-05-07T16:29:46.25+0530 [APP/PROC/WEB/0] ERR npm ERR! enoent ENOENT: no such file or directory, open '/home/vcap/app/package.json'
   2019-05-07T16:29:46.25+0530 [APP/PROC/WEB/0] ERR npm ERR! enoent ENOENT: no such file or directory, open '/home/vcap/app/package.json'
   2019-05-07T16:29:46.25+0530 [APP/PROC/WEB/0] ERR npm ERR! enoent This is most likely not a problem with npm itself
   2019-05-07T16:29:46.25+0530 [APP/PROC/WEB/0] ERR npm ERR! enoent and is related to npm not being able to find a file.
   2019-05-07T16:29:46.25+0530 [APP/PROC/WEB/0] ERR npm ERR! enoent
   2019-05-07T16:29:46.26+0530 [APP/PROC/WEB/0] ERR npm ERR! Please include the following file with any support request:
   2019-05-07T16:29:46.26+0530 [APP/PROC/WEB/0] ERR npm ERR!     /home/vcap/app/npm-debug.log
   2019-05-07T16:29:46.29+0530 [APP/PROC/WEB/0] OUT Exit status 254
   2019-05-07T16:29:46.78+0530 [CELL/0] OUT Cell 147dd272-7f28-41d6-a2e9-afc4c25f4fa5 stopping instance e4b17c20-4306-4b57-5019-547b
   2019-05-07T16:29:46.78+0530 [CELL/0] OUT Cell 147dd272-7f28-41d6-a2e9-afc4c25f4fa5 destroying container for instance e4b17c20-4306-4b57-5019-547b
   2019-05-07T16:29:47.06+0530 [CELL/0] OUT Cell 990a5533-fad7-43c8-8924-725ff803b7bc creating container for instance 6a2d3585-c8e6-4c3f-7188-dda0
   2019-05-07T16:29:47.45+0530 [CELL/0] OUT Cell 990a5533-fad7-43c8-8924-725ff803b7bc successfully created container for instance 6a2d3585-c8e6-4c3f-7188-dda0
   2019-05-07T16:29:47.94+0530 [CELL/0] OUT Cell 147dd272-7f28-41d6-a2e9-afc4c25f4fa5 successfully destroyed container for instance e4b17c20-4306-4b57-5019-547b
   2019-05-07T16:29:49.51+0530 [CELL/0] OUT Starting health monitoring of container
   2019-05-07T16:29:50.14+0530 [APP/PROC/WEB/0] ERR npm ERR! Linux 4.15.0-45-generic
   2019-05-07T16:29:50.14+0530 [APP/PROC/WEB/0] ERR npm ERR! argv "/home/vcap/deps/0/node/bin/node" "/home/vcap/deps/0/bin/npm" "start"
   2019-05-07T16:29:50.14+0530 [APP/PROC/WEB/0] ERR npm ERR! node v6.16.0
   2019-05-07T16:29:50.14+0530 [APP/PROC/WEB/0] ERR npm ERR! npm  v3.10.10
   2019-05-07T16:29:50.14+0530 [APP/PROC/WEB/0] ERR npm ERR! path /home/vcap/app/package.json
   2019-05-07T16:29:50.14+0530 [APP/PROC/WEB/0] ERR npm ERR! code ENOENT
   2019-05-07T16:29:50.14+0530 [APP/PROC/WEB/0] ERR npm ERR! errno -2
   2019-05-07T16:29:50.14+0530 [APP/PROC/WEB/0] ERR npm ERR! syscall open
   2019-05-07T16:29:50.14+0530 [APP/PROC/WEB/0] ERR npm ERR! enoent ENOENT: no such file or directory, open '/home/vcap/app/package.json'
   2019-05-07T16:29:50.14+0530 [APP/PROC/WEB/0] ERR npm ERR! enoent ENOENT: no such file or directory, open '/home/vcap/app/package.json'
   2019-05-07T16:29:50.14+0530 [APP/PROC/WEB/0] ERR npm ERR! enoent This is most likely not a problem with npm itself
   2019-05-07T16:29:50.14+0530 [APP/PROC/WEB/0] ERR npm ERR! enoent and is related to npm not being able to find a file.
   2019-05-07T16:29:50.14+0530 [APP/PROC/WEB/0] ERR npm ERR! enoent
   2019-05-07T16:29:50.15+0530 [APP/PROC/WEB/0] ERR npm ERR! Please include the following file with any support request:
   2019-05-07T16:29:50.15+0530 [APP/PROC/WEB/0] ERR npm ERR!     /home/vcap/app/npm-debug.log
   2019-05-07T16:29:50.17+0530 [APP/PROC/WEB/0] OUT Exit status 254
   2019-05-07T16:29:50.44+0530 [CELL/0] OUT Cell 990a5533-fad7-43c8-8924-725ff803b7bc stopping instance 6a2d3585-c8e6-4c3f-7188-dda0
   2019-05-07T16:29:50.44+0530 [CELL/0] OUT Cell 990a5533-fad7-43c8-8924-725ff803b7bc destroying container for instance 6a2d3585-c8e6-4c3f-7188-dda0
   2019-05-07T16:29:51.32+0530 [CELL/0] OUT Cell 990a5533-fad7-43c8-8924-725ff803b7bc successfully destroyed container for instance 6a2d3585-c8e6-4c3f-7188-dda0
   2019-05-07T16:30:39.14+0530 [CELL/0] OUT Cell 147dd272-7f28-41d6-a2e9-afc4c25f4fa5 creating container for instance 76b6c8df-216e-4947-63a0-59a3
   2019-05-07T16:30:39.73+0530 [CELL/0] OUT Cell 147dd272-7f28-41d6-a2e9-afc4c25f4fa5 successfully created container for instance 76b6c8df-216e-4947-63a0-59a3
   2019-05-07T16:30:40.52+0530 [CELL/0] OUT Starting health monitoring of container
   2019-05-07T16:30:41.25+0530 [APP/PROC/WEB/0] ERR npm ERR! Linux 4.15.0-45-generic
   2019-05-07T16:30:41.25+0530 [APP/PROC/WEB/0] ERR npm ERR! argv "/home/vcap/deps/0/node/bin/node" "/home/vcap/deps/0/bin/npm" "start"
   2019-05-07T16:30:41.25+0530 [APP/PROC/WEB/0] ERR npm ERR! node v6.16.0
   2019-05-07T16:30:41.25+0530 [APP/PROC/WEB/0] ERR npm ERR! npm  v3.10.10
   2019-05-07T16:30:41.25+0530 [APP/PROC/WEB/0] ERR npm ERR! path /home/vcap/app/package.json
   2019-05-07T16:30:41.25+0530 [APP/PROC/WEB/0] ERR npm ERR! code ENOENT
   2019-05-07T16:30:41.25+0530 [APP/PROC/WEB/0] ERR npm ERR! errno -2
   2019-05-07T16:30:41.25+0530 [APP/PROC/WEB/0] ERR npm ERR! syscall open
   2019-05-07T16:30:41.25+0530 [APP/PROC/WEB/0] ERR npm ERR! enoent ENOENT: no such file or directory, open '/home/vcap/app/package.json'
   2019-05-07T16:30:41.25+0530 [APP/PROC/WEB/0] ERR npm ERR! enoent ENOENT: no such file or directory, open '/home/vcap/app/package.json'
   2019-05-07T16:30:41.25+0530 [APP/PROC/WEB/0] ERR npm ERR! enoent This is most likely not a problem with npm itself
   2019-05-07T16:30:41.25+0530 [APP/PROC/WEB/0] ERR npm ERR! enoent and is related to npm not being able to find a file.
   2019-05-07T16:30:41.25+0530 [APP/PROC/WEB/0] ERR npm ERR! enoent
   2019-05-07T16:30:41.26+0530 [APP/PROC/WEB/0] ERR npm ERR! Please include the following file with any support request:
   2019-05-07T16:30:41.26+0530 [APP/PROC/WEB/0] ERR npm ERR!     /home/vcap/app/npm-debug.log
   2019-05-07T16:30:41.29+0530 [APP/PROC/WEB/0] OUT Exit status 254
   2019-05-07T16:30:41.62+0530 [CELL/0] OUT Cell 147dd272-7f28-41d6-a2e9-afc4c25f4fa5 stopping instance 76b6c8df-216e-4947-63a0-59a3
   2019-05-07T16:30:41.62+0530 [CELL/0] OUT Cell 147dd272-7f28-41d6-a2e9-afc4c25f4fa5 destroying container for instance 76b6c8df-216e-4947-63a0-59a3
   2019-05-07T16:30:42.62+0530 [CELL/0] OUT Cell 147dd272-7f28-41d6-a2e9-afc4c25f4fa5 successfully destroyed container for instance 76b6c8df-216e-4947-63a0-59a3
   2019-05-07T16:32:09.21+0530 [CELL/0] OUT Cell 990a5533-fad7-43c8-8924-725ff803b7bc creating container for instance abc9dcd9-695a-4ed5-5213-01fe
   2019-05-07T16:32:09.64+0530 [CELL/0] OUT Cell 990a5533-fad7-43c8-8924-725ff803b7bc successfully created container for instance abc9dcd9-695a-4ed5-5213-01fe
   2019-05-07T16:32:11.64+0530 [APP/PROC/WEB/0] ERR npm ERR! argv "/home/vcap/deps/0/node/bin/node" "/home/vcap/deps/0/bin/npm" "start"
   2019-05-07T16:32:11.64+0530 [APP/PROC/WEB/0] ERR npm ERR! node v6.16.0
   2019-05-07T16:32:11.64+0530 [APP/PROC/WEB/0] ERR npm ERR! npm  v3.10.10
   2019-05-07T16:32:11.64+0530 [APP/PROC/WEB/0] ERR npm ERR! path /home/vcap/app/package.json
   2019-05-07T16:32:11.64+0530 [APP/PROC/WEB/0] ERR npm ERR! errno -2
   2019-05-07T16:32:11.64+0530 [APP/PROC/WEB/0] ERR npm ERR! enoent ENOENT: no such file or directory, open '/home/vcap/app/package.json'
   2019-05-07T16:32:11.64+0530 [APP/PROC/WEB/0] ERR npm ERR! enoent and is related to npm not being able to find a file.
   2019-05-07T16:32:11.64+0530 [APP/PROC/WEB/0] ERR npm ERR! enoent
   2019-05-07T16:32:11.64+0530 [APP/PROC/WEB/0] ERR npm ERR!     /home/vcap/app/npm-debug.log
   2019-05-07T16:32:11.66+0530 [APP/PROC/WEB/0] OUT Exit status 254
   2019-05-07T16:32:12.08+0530 [CELL/0] OUT Cell 990a5533-fad7-43c8-8924-725ff803b7bc stopping instance abc9dcd9-695a-4ed5-5213-01fe
   2019-05-07T16:32:12.08+0530 [CELL/0] OUT Cell 990a5533-fad7-43c8-8924-725ff803b7bc destroying container for instance abc9dcd9-695a-4ed5-5213-01fe
   2019-05-07T16:32:13.05+0530 [CELL/0] OUT Cell 990a5533-fad7-43c8-8924-725ff803b7bc successfully destroyed container for instance abc9dcd9-695a-4ed5-5213-01fe

I would have wished that the employees of siemens come a little bit more towards you.

 

Do you already have such experience with the validation team or with deploying the app. 

I would be glad about a few tips. 

 

thank you in advance

 

 

 

2 REPLIES 2

Re: facing error while test deployment of the app

Legend
Legend
I haven't had such an issue, but seeing that the logs complain about not finding the package.json file, my first guess is that you are not correctly packing the zip file + manifest.

I'd try to push locally on the developer tenant under a new cf app name the uncompressed zip file + manifest you are delivering, and see if the error shows in there. Most probably some wrong path or missing files.

You can take hints on how to pack the zip file from the devops-demo project, we recently tested the validation process and it worked ('mdsp:zip' target, check the readmes):
https://gitlab.com/mindsphere/devops-demo/blob/master/package.json

Re: facing error while test deployment of the app

Creator
Creator
thank you for you response,

actually for some reason the package.json was missing in my zip file. Then the error seems to be with me, well hope
it works now.