Skip to content

Instantly share code, notes, and snippets.

@joshco
Created April 23, 2020 21:07
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save joshco/e5fbf2b7167504fbc66b6ffc83b447cc to your computer and use it in GitHub Desktop.
Save joshco/e5fbf2b7167504fbc66b6ffc83b447cc to your computer and use it in GitHub Desktop.
node-wot PORT and URL deployment issues
$ git push --force dokku pre-portfix:master
Total 0 (delta 0), reused 0 (delta 0)
-----> Cleaning up...
-----> Building thingpatrol from herokuish...
-----> Adding BUILD_ENV to build environment...
-----> Node.js app detected
-----> Creating runtime environment
NPM_CONFIG_LOGLEVEL=error
NODE_VERBOSE=false
NODE_PORT=5000
NODE_ENV=production
NODE_MODULES_CACHE=true
-----> Installing binaries
engines.node (package.json): unspecified
engines.npm (package.json): unspecified (use default)
Resolving node version 8.x...
Downloading and installing node 8.17.0...
Using default npm version: 6.13.4
-----> Restoring cache
Skipping cache restore (not-found)
-----> Building dependencies
Installing node modules (package.json + package-lock)
> node-aead-crypto@2.2.0 preinstall /tmp/build/node_modules/node-aead-crypto
> node lib/preinstall.js
> node-aead-crypto@2.2.0 install /tmp/build/node_modules/node-aead-crypto
> node lib/install.js
running default installation script
> node-aead-crypto@2.2.0 install:default /tmp/build/node_modules/node-aead-crypto
> prebuild-install || node-gyp rebuild
> node-sass@4.13.1 install /tmp/build/node_modules/node-sass
> node scripts/install.js
Downloading binary from https://github.com/sass/node-sass/releases/download/v4.13.1/linux-x64-5
7_binding.node
Download complete
Binary saved to /tmp/build/node_modules/node-sass/vendor/linux-x64-57/binding.node
Caching binary to /tmp/npmcache.IppNX/node-sass/4.13.1/linux-x64-57_binding.node
> core-js@2.6.11 postinstall /tmp/build/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"
> node-sass@4.13.1 postinstall /tmp/build/node_modules/node-sass
> node scripts/build.js
Binary found at /tmp/build/node_modules/node-sass/vendor/linux-x64-57/binding.node
Testing binary
Binary is fine
added 395 packages from 335 contributors and audited 1513 packages in 12.482s
5 packages are looking for funding
run `npm fund` for details
found 1 low severity vulnerability
run `npm audit fix` to fix them, or `npm audit` for details
-----> Caching build
Clearing previous node cache
Saving 2 cacheDirectories (default):
- node_modules
- bower_components (nothing to cache)
-----> Pruning devDependencies
audited 1513 packages in 2.494s
5 packages are looking for funding
run `npm fund` for details
found 1 low severity vulnerability
run `npm audit fix` to fix them, or `npm audit` for details
-----> Build succeeded!
-----> Discovering process types
Procfile declares types -> web
-----> Releasing thingpatrol (dokku/thingpatrol:latest)...
-----> Deploying thingpatrol (dokku/thingpatrol:latest)...
-----> Attempting to run scripts.dokku.predeploy from app.json (if defined)
-----> App Procfile file found (/home/dokku/thingpatrol/DOKKU_PROCFILE)
-----> DOKKU_SCALE file found (/home/dokku/thingpatrol/DOKKU_SCALE)
=====> web=1
-----> Attempting pre-flight checks
For more efficient zero downtime deployments, create a file CHECKS.
See http://dokku.viewdocs.io/dokku/deployment/zero-downtime-deploys/ for examples
CHECKS file not found in container: Running simple container check...
-----> Waiting for 10 seconds ...
43e3b31930c1d1a3b68624b2e445ae6f74184ee72be0b93eaaa3cbffb0aa3c0b
remote: App container failed to start!!
=====> thingpatrol web container output:
Could not determine a reasonable value for WEB_CONCURRENCY.
This is likely due to running the Heroku NodeJS buildpack on a non-Heroku
platform.
WEB_CONCURRENCY has been set to 1. Please review whether this value is
appropriate for your application.
> lightbar@0.0.0 start /app
> node ./bin/www
HttpServer starting on port 8081
Port 5000 is already in use
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! lightbar@0.0.0 start: `node ./bin/www`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the lightbar@0.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output abo
ve.
npm ERR! A complete log of this run can be found in:
npm ERR! /app/.npm/_logs/2020-04-23T12_28_40_187Z-debug.log
Could not determine a reasonable value for WEB_CONCURRENCY.
This is likely due to running the Heroku NodeJS buildpack on a non-Heroku
platform.
WEB_CONCURRENCY has been set to 1. Please review whether this value is
appropriate for your application.
> lightbar@0.0.0 start /app
> node ./bin/www
HttpServer starting on port 8081
Port 5000 is already in use
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! lightbar@0.0.0 start: `node ./bin/www`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the lightbar@0.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output abo
ve.
npm ERR! A complete log of this run can be found in:
npm ERR! /app/.npm/_logs/2020-04-23T12_28_42_207Z-debug.log
Could not determine a reasonable value for WEB_CONCURRENCY.
This is likely due to running the Heroku NodeJS buildpack on a non-Heroku
platform.
WEB_CONCURRENCY has been set to 1. Please review whether this value is
appropriate for your application.
> lightbar@0.0.0 start /app
> node ./bin/www
HttpServer starting on port 8081
Port 5000 is already in use
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! lightbar@0.0.0 start: `node ./bin/www`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the lightbar@0.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output abo
ve.
npm ERR! A complete log of this run can be found in:
npm ERR! /app/.npm/_logs/2020-04-23T12_28_44_333Z-debug.log
Could not determine a reasonable value for WEB_CONCURRENCY.
This is likely due to running the Heroku NodeJS buildpack on a non-Heroku
platform.
WEB_CONCURRENCY has been set to 1. Please review whether this value is
appropriate for your application.
> lightbar@0.0.0 start /app
> node ./bin/www
HttpServer starting on port 8081
Port 5000 is already in use
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! lightbar@0.0.0 start: `node ./bin/www`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the lightbar@0.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output abo
ve.
npm ERR! A complete log of this run can be found in:
npm ERR! /app/.npm/_logs/2020-04-23T12_28_46_541Z-debug.log
Could not determine a reasonable value for WEB_CONCURRENCY.
This is likely due to running the Heroku NodeJS buildpack on a non-Heroku
platform.
WEB_CONCURRENCY has been set to 1. Please review whether this value is
appropriate for your application.
> lightbar@0.0.0 start /app
> node ./bin/www
HttpServer starting on port 8081
Port 5000 is already in use
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! lightbar@0.0.0 start: `node ./bin/www`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the lightbar@0.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output abo
ve.
npm ERR! A complete log of this run can be found in:
npm ERR! /app/.npm/_logs/2020-04-23T12_28_49_051Z-debug.log
=====> end thingpatrol web container output
To dokku.splitatom.com:thingpatrol
! [remote rejected] pre-portfix -> master (pre-receive hook declined)
error: failed to push some refs to 'dokku@dokku.splitatom.com:thingpatrol'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment