looks like a deploy error, holding off on the starting the socket

[ibm-blockchain-archive]

looks like a deploy error, holding off on the starting the socket

[tmh1999]

You are awesome, man. Thank you !

[masterDev1985]

@kamraanki Mind taking another look at this now that the CP demo has been updated? We've verified that it works against the Bluemix service, which uses TLS, but it might take a little work to get it working on your local network.

[himanshutyagi36]

@kamraanki I'm facing the same issue. Did you solve it ?

[kamraanki]

@tortuga90 No i am still facing the same issue.

[krishvoor]

@kamraanki & @tortuga90 Count me in, I am facing the same issue right now, did you guys have any chance solving it.

[dshuffma-ibm]

this line concerns me:

I have disabled TLS in options of mycreds.json

The correct way to disable TLS is in the options object in app.js, near network options. Here is a section written for marbles that should help.

In summary you need to add an option field to app.js so that it looks like:

network:{
        peers: [peers[0]],
        users: users,   
        options: {
                tls: false
        }
...

just for more clarification this tls:false field is telling the REST based SDK to use http vs https.

[himanshutyagi36]

@dshuffma-ibm I've disabled in the app.js itself.

[dshuffma-ibm]

could you post more logs? does it register any enrollIDs with a peer successfully? also @tortuga90 are you also using your own local network?

[himanshutyagi36]

@dshuffma-ibm yes, I'm running on my local network. The CA and Validating peer are in Vagrant VM, and the node.js app is running from outside the vagrant vm

[dshuffma-ibm]

cp-web is not updated to work with the new hyperledger fabric. We have people working to update it, but it is not yet ready. You should hold off on using cp-web until we push an updated version. Marbles however will work fine.

[tmh1999]

@dshuffma-ibm Please let me use this thread to ask a related question to marble. I am using marble and having this problem when running $ gulp at marbles/ root directory:

     Waiting...
[ibc-js] deploy - failure: 500
! looks like a deploy error, holding off on the starting the socket
 { name: 'deploy() error',
  code: 500,
  details: 
   { Error: Parse Error
       at Error (native)
       at Socket.socketOnData (_http_client.js:361:20)
       at emitOne (events.js:96:13)
       at Socket.emit (events.js:188:7)
       at readableAddChunk (_stream_readable.js:172:18)
       at Socket.Readable.push (_stream_readable.js:130:10)
       at TCP.onread (net.js:542:20) bytesParsed: 0, code: 'HPE_INVALID_CONSTANT' } }

My local dev is 2vp & CA using docker-compose.yml like this :

membersrvc:
  image: hyperledger/fabric-membersrvc
  command: membersrvc
vp0:
  image: hyperledger/fabric-peer
  environment:
    - CORE_PEER_ADDRESSAUTODETECT=true
    - CORE_VM_ENDPOINT=http://172.17.0.1:2375
    - CORE_LOGGING_LEVEL=DEBUG
    - CORE_PEER_ID=vp0
    - CORE_SECURITY_ENROLLID=test_vp0
    - CORE_SECURITY_ENROLLSECRET=111111111111
  command: peer node start
vp1:
  extends:
    service: vp0
  environment:
    - CORE_PEER_ID=vp1
    - CORE_SECURITY_ENROLLID=test_vp1
    - CORE_SECURITY_ENROLLSECRET=111111111111
    - CORE_PEER_DISCOVERY_ROOTNODE=vp0:30303
  links:
    - vp0

And my marbles/mycreds.json :

{
  "credentials": {
    "peers": [
      {
        "api_host": "172.17.0.2",
        "api_port_tls": 30303,
        "api_port": 30303,
        "id": "vp0"
      }
    ],
    "users": [
      {
        "enrollId": "test_vp0",
        "enrollSecret": "111111111111"
      }
    ]
  }
}

I have disabled tls in marbles/app.js.

[dshuffma-ibm]

@tmh1999 could you add quiet: false to your options to see more details.

network:{
        peers: [peers[0]],
        users: users,   
        options: {
                tls: false,
               quiet: false
        }

[tmh1999]

@dshuffma-ibm Yes here is the new output :

     Waiting...
[http POST - w] /chaincode
  body: {"jsonrpc":"2.0","method":"deploy","params":{"type":1,"chaincodeID":{"path":"https://github.com/ibm-blockchain/marbles-chaincode/hyperledger/part2"},"ctorMsg":{"function":"init","args":["99"]}},"id":1470232091636}
[http POST - w] Error - unknown issue with request:  { Error: Parse Error
    at Error (native)
    at Socket.socketOnData (_http_client.js:361:20)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at readableAddChunk (_stream_readable.js:172:18)
    at Socket.Readable.push (_stream_readable.js:130:10)
    at TCP.onread (net.js:542:20) bytesParsed: 0, code: 'HPE_INVALID_CONSTANT' }
[ibc-js] deploy - failure: 500
! looks like a deploy error, holding off on the starting the socket
 { name: 'deploy() error',
  code: 500,
  details: 
   { Error: Parse Error
       at Error (native)
       at Socket.socketOnData (_http_client.js:361:20)
       at emitOne (events.js:96:13)
       at Socket.emit (events.js:188:7)
       at readableAddChunk (_stream_readable.js:172:18)
       at Socket.Readable.push (_stream_readable.js:130:10)
       at TCP.onread (net.js:542:20) bytesParsed: 0, code: 'HPE_INVALID_CONSTANT' } }

[dshuffma-ibm]

You are sending the HTTP deploy request to the gRPC port. Your mycreds.json should not have 30303 as the api_port. Its probably like 5000. Check your core.yaml.