strongloop / strong-deploy

Deploy nodejs applications
Other
13 stars 3 forks source link

deploy failing with incorrect header check #53

Open socketwiz opened 8 years ago

socketwiz commented 8 years ago

I have setup the strong-pm docker image: https://github.com/strongloop/strong-pm and everything was working well. However now when I try to deploy I'm getting a strange error.

$ slc build
Not merging HEAD into `deploy`, already up to date.
Running `npm install --ignore-scripts`
Running `npm run build`
Running `npm prune --production`
Running `git add --force --all .`
Running `git write-tree`
  => 28bb627b13de3d5defab55f9b68850d6b91513fd
Running `git commit-tree -p "refs/heads/deploy" -m "Commit build products" 28bb627b13de3d5defab55f9b68850d6b91513fd`
Running `git update-ref "refs/heads/deploy" 8ec361942432ab1661ada451931086b84e561feb`
Committed build products onto `deploy`
$ slc deploy http://bin_web_1
Untar /tmp/strong-pm-1-1449285296387/application.tgz failed with: Error: incorrect header check
Failed to deploy `deploy` as `voiceplane-api` to `http://bin_web_1:8701/` via `http://bin_web_1:8701/`

I have verified that I can access the service on port 8701:

$ curl http://bin_web_1:8701/
{"started":"2015-12-05T01:47:19.520Z","uptime":5903.645}

And it appears to be up and running, so its looking like "slc deploy" is trying to find this application.tgz file to send and can't for whatever reason, but I thought it was supposed to send up the git deploy branch over http. Am I missing something? Any ideas would be much appreciated.

kronnakrit commented 8 years ago

@socketwiz Did you get it working? I have the same problem as well...

I tried re-install and redo everything again including updating my nodejs in local and still didn't work..

kronnakrit commented 8 years ago

Okay, I think it might be node problem when packing the build.. so I fixed it by running

slc build -n

instead of

slc build

socketwiz commented 8 years ago

@zorosun I've had some success with slc arc and kicking off builds from the gui. It could be something as simple as a missing parameter as you have discovered. Or it may be that they've fixed something in the latest strongloop/strong-pm Docker image which is what I'm actually using.