My Oracle Support Banner

Not Able To Instantiate Chaincode After Migrating Gen2 (Doc ID 2750013.1)

Last updated on FEBRUARY 07, 2021

Applies to:

Blockchain Platform Cloud Service - Version N/A to N/A
Information in this document applies to any platform.


After migrated to Gen2,  Chaincode which implemented by Node.js , it fails to instantiate. It worked on Gen1 environment.

Following error can be found in peer node log.

peer0.1: make: Leaving directory '/chaincode/output/node_modules/x509/build'
peer0.1: make: *** [Release/] Error 1
peer0.1: gyp ERR! build error
peer0.1: gyp ERR! stack Error: 'make' failed with exit code: 2
peer0.1: gyp ERR! stack at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:191:23)
peer0.1: gyp ERR! stack at ChildProcess.emit (events.js:198:13)
peer0.1: gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
peer0.1: gyp ERR! System Linux 4.14.35-2025.403.3.el7uek.x86_64
peer0.1: gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
peer0.1: gyp ERR! cwd /chaincode/output/node_modules/x509
peer0.1: gyp ERR! node -v v10.21.0
peer0.1: gyp ERR! node-gyp -v v5.1.0
peer0.1: gyp ERR! not ok
peer0.1: npm WARN notsup Unsupported engine for fabric-shim@1.3.2: wanted: {"node":"^8.9.0","npm":"^5.5.1"} (current: {"node":"10.21.0","npm":"6.14.4"})
peer0.1: npm WARN notsup Not compatible with your version of node/npm: fabric-shim@1.3.2



 Migrated to Gen2


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.