suma#ubuntu:~/poc/land$ composer network start --networkName property-network --networkVersion 0.2.6-deploy.113 --card PeerAdmin#hlfv1 -A admin -S adminpw --file networkadmin.card
Starting business network property-network at version 0.2.6-deploy.113
Processing these Network Admins:
userName: admin
✖ Starting business network definition. This may take a minute...
Error: Error trying to start business network. Error: No valid responses from any peers.
Response from attempted peer comms was an error: Error: failed to execute transaction ae276da81f756ac76edccf85a79f1c11a554f1285c2a8c4cc2899db433220500: error starting container: error starting container: Failed to generate platform-specific docker build: Error returned from build: 1 "npm WARN notice [SECURITY] hoek has the following vulnerability: 1 moderate. Go here for more details: https://nodesecurity.io/advisories?search=hoek&version=2.16.3 - Run npm i npm#latest -g to upgrade your npm version, and then npm audit to get more info.
npm WARN deprecated boom#2.10.1: This version is no longer maintained. Please upgrade to the latest version.
npm WARN deprecated cryptiles#2.0.5: This version is no longer maintained. Please upgrade to the latest version.
npm WARN deprecated hoek#2.16.3: This version is no longer maintained. Please upgrade to the latest version.
npm WARN deprecated boom#4.3.1: This version is no longer maintained. Please upgrade to the latest version.
x509#0.3.3 install /chaincode/output/node_modules/x509
node-gyp rebuild
gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
gyp ERR! stack at PythonFinder.failNoPython (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:483:19)
gyp ERR! stack at PythonFinder. (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:397:16)
gyp ERR! stack at F (/usr/local/lib/node_modules/npm/node_modules/which/which.js:68:16)
gyp ERR! stack at E (/usr/local/lib/node_modules/npm/node_modules/which/which.js:80:29)
gyp ERR! stack at /usr/local/lib/node_modules/npm/node_modules/which/which.js:89:16
gyp ERR! stack at /usr/local/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:42:5
gyp ERR! stack at /usr/local/lib/node_modules/npm/node_modules/which/node_modules/isexe/mode.js:8:5
gyp ERR! stack at FSReqWrap.oncomplete (fs.js:152:21)
gyp ERR! System Linux 4.10.0-28-generic
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /chaincode/output/node_modules/x509
gyp ERR! node -v v8.4.0
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
npm WARN The package composer-common is included as both a dev and production dependency.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! x509#0.3.3 install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the x509#0.3.3 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2018-12-19T06_43_46_434Z-debug.log
"
Command failed
FABRIC_VERSION=hlfv12
COMPOSER_VERSION=v0.20.5
NODE_VERSION=v8.14.1
NPM_VERSION=6.4.1
I already done ./teardownfabric and ./stopFabric and again started a fabric and create a peeradmin card .
This is most likely caused by an old or incorrect image used to build chaincode images. As long as you haven't reconfigured your peer to use a different build image then the easiest fix for this is to delete any ccenv images you might have for example you could try
docker rmi $(docker images hyperledger/fabric-ccenv* -q) -f
to force remove all ccenv images
Related
enter image description here> # dev C:\xampp\htdocs\laravel9_basic\basic
vite
internal/process/esm_loader.js:74
internalBinding('errors').triggerUncaughtException(
^
Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only file and data URLs are supported by the default ESM loader. Received protocol 'node:'
at Loader.defaultResolve [as _resolve] (internal/modules/esm/resolve.js:756:11)
at Loader.resolve (internal/modules/esm/loader.js:85:40)
at Loader.getModuleJob (internal/modules/esm/loader.js:229:28)
at ModuleWrap. (internal/modules/esm/module_job.js:51:40)
at link (internal/modules/esm/module_job.js:50:36) {
code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! # dev: vite
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the # dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Sudha\AppData\Roaming\npm-cache_logs\2022-07-23T13_50_47_419Z-debug.log
I recently built a mean stack app and containerized it. However, I have trouble build it on my raspberry pi and I don't understand the error.
When I build my app over my debian machine, everything build perfectly. Even if I get this line during the build process:
node-pre-gyp WARN Using needle for node-pre-gyp https download
Unfortunately, I cannot build the same container on my raspberry. This warning get really worse and exit with error code 1:
node-pre-gyp WARN Using needle for node-pre-gyp https download
node-pre-gyp WARN Tried to download(404): https://github.com/kelektiv/node.bcryp t.js/releases/download/v4.0.1/bcrypt_lib-v4.0.1-napi-v3-linux-arm-musl.tar.gz
node-pre-gyp WARN Pre-built binaries not found for bcrypt#4.0.1 and node#13.1.0 (node-v79 ABI, musl) (falling back to source compile with node-gyp)
gyp ERR! find Python
gyp ERR! find Python Python is not set from command line or npm configuration
gyp ERR! find Python Python is not set from environment variable PYTHON
gyp ERR! find Python checking if "python" can be used
gyp ERR! find Python - "python" is not in PATH or produced an error
gyp ERR! find Python checking if "python2" can be used
gyp ERR! find Python - "python2" is not in PATH or produced an error
gyp ERR! find Python checking if "python3" can be used
gyp ERR! find Python - "python3" is not in PATH or produced an error
gyp ERR! find Python
gyp ERR! find Python **********************************************************
gyp ERR! find Python You need to install the latest version of Python.
gyp ERR! find Python Node-gyp should be able to find and use Python. If not,
gyp ERR! find Python you can try one of the following options:
gyp ERR! find Python - Use the switch --python="/path/to/pythonexecutable"
gyp ERR! find Python (accepted by both node-gyp and npm)
gyp ERR! find Python - Set the environment variable PYTHON
gyp ERR! find Python - Set the npm configuration variable python:
gyp ERR! find Python npm config set python "/path/to/pythonexecutable"
gyp ERR! find Python For more information consult the documentation at:
gyp ERR! find Python https://github.com/nodejs/node-gyp#installation
gyp ERR! find Python **********************************************************
gyp ERR! find Python
gyp ERR! configure error
gyp ERR! stack Error: Could not find any Python installation to use
gyp ERR! stack at PythonFinder.fail (/usr/local/lib/node_modules/npm/node_mo dules/node-gyp/lib/find-python.js:307:47)
gyp ERR! stack at PythonFinder.runChecks (/usr/local/lib/node_modules/npm/no de_modules/node-gyp/lib/find-python.js:136:21)
gyp ERR! stack at PythonFinder.<anonymous> (/usr/local/lib/node_modules/npm/ node_modules/node-gyp/lib/find-python.js:179:16)
gyp ERR! stack at PythonFinder.execFileCallback (/usr/local/lib/node_modules /npm/node_modules/node-gyp/lib/find-python.js:271:16)
gyp ERR! stack at exithandler (child_process.js:302:5)
gyp ERR! stack at ChildProcess.errorhandler (child_process.js:314:5)
gyp ERR! stack at ChildProcess.emit (events.js:210:5)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_proces s.js:270:12)
gyp ERR! stack at onErrorNT (internal/child_process.js:456:16)
gyp ERR! stack at processTicksAndRejections (internal/process/task_queues.js :80:21)
gyp ERR! System Linux 4.19.97-v7l+
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_mod ules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/app/ node_modules/bcrypt/lib/binding/napi-v3/bcrypt_lib.node" "--module_name=bcrypt_l ib" "--module_path=/app/node_modules/bcrypt/lib/binding/napi-v3" "--napi_version =5" "--node_abi_napi=napi" "--napi_build_version=3" "--node_napi_label=napi-v3"
gyp ERR! cwd /app/node_modules/bcrypt
gyp ERR! node -v v13.1.0
gyp ERR! node-gyp -v v5.0.5
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/local/bin/node /usr/local /lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback -to-build --module=/app/node_modules/bcrypt/lib/binding/napi-v3/bcrypt_lib.node --module_name=bcrypt_lib --module_path=/app/node_modules/bcrypt/lib/binding/napi -v3 --napi_version=5 --node_abi_napi=napi --napi_build_version=3 --node_napi_lab el=napi-v3' (1)
node-pre-gyp ERR! stack at ChildProcess.<anonymous> (/app/node_modules/node- pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack at ChildProcess.emit (events.js:210:5)
node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:1028:16)
node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/chi ld_process.js:283:5)
node-pre-gyp ERR! System Linux 4.19.97-v7l+
node-pre-gyp ERR! command "/usr/local/bin/node" "/app/node_modules/.bin/node-pre -gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /app/node_modules/bcrypt
node-pre-gyp ERR! node -v v13.1.0
node-pre-gyp ERR! node-pre-gyp -v v0.14.0
node-pre-gyp ERR! not ok
Failed to execute '/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modu les/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/app/node_mo dules/bcrypt/lib/binding/napi-v3/bcrypt_lib.node --module_name=bcrypt_lib --modu le_path=/app/node_modules/bcrypt/lib/binding/napi-v3 --napi_version=5 --node_abi _napi=napi --napi_build_version=3 --node_napi_label=napi-v3' (1)
npm WARN clockmachine-api#1.0.0 No repository field.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! bcrypt#4.0.1 install: `node-pre-gyp install --fallback-to-build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the bcrypt#4.0.1 install script.
npm ERR! This is probably not a problem with npm. There is likely additional log ging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2020-05-26T14_29_34_636Z-debug.log
ERROR: Service 'backend' failed to build: The command '/bin/sh -c npm install' returned a non-zero code: 1
I don't understand this error code, because I have python, python2 and python3. Furthermore, if I type npm install node-pre-gyp it's working but not inside the container. I tried to clean npm cache and use with different nodejs version. the initial one, the 12.16.3 and the 14.x one.
Can you explain to me why this errors occurs ? What dependency should I fullfill and how to get the log inside the container?
If you don't really need Node 13, maybe you can try using Node 8 (either using NVM or choosing the right Node Docker image).
This will skip building bcrypt.
(The reason you're even building bcrypt is because NPM "Pre-built binaries not found for bcrypt#4.0.1 and node#13.1.0")
I installed the pod apollo according to this manual, then at the stage where you have to create a run-time, the build does not work, it returns this error I do not understand why ..
Can't find Apollo CLI. Installing...
npm ERR! Error while executing:
npm ERR! /Applications/Xcode.app/Contents/Developer/usr/bin/git ls-remote -h -t ssh://git#github.com/Project/fitto-ios.git
npm ERR!
npm ERR! git#github.com: Permission denied (publickey).
npm ERR! fatal: Could not read from remote repository.
npm ERR!
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.
npm ERR!
npm ERR! exited with error code: 128
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/mickaelbelhassen/.npm/_logs/2018-08-21T13_43_18_743Z-debug.log
Command /bin/sh failed with exit code 1
And I do not understand why he talks about git ..
Also, the repository ssh://git#github.com/Project/fitto-ios.git is my remote repository, it has nothing to do with Apollo.
Here is my run script is the same as the official documentation:
APOLLO_FRAMEWORK_PATH="$(eval find $FRAMEWORK_SEARCH_PATHS -name "Apollo.framework" -maxdepth 1)"
if [ -z "$APOLLO_FRAMEWORK_PATH" ]; then
echo "error: Couldn't find Apollo.framework in FRAMEWORK_SEARCH_PATHS; make sure to add the framework to your project."
exit 1
fi
cd "${SRCROOT}/${TARGET_NAME}"
$APOLLO_FRAMEWORK_PATH/check-and-run-apollo-cli.sh codegen:generate --queries="$(find . -name '*.graphql')" --schema=schema.json API.swift
You need to install the Apollo CLI from Here Then try building your app again.
Has anyone here got "electron" to work under tails distribution? Or any other download binary for that matter? I tried downloading the x64 binary
from the official site, but it won't execute it:
amnesia#amnesia:~/Desktop/temp$ ./electron --help
bash: ./electron: No such file or directory
I tried putting "bash" in front of it and I get a similar error:
amnesia#amnesia:~/Desktop/temp$ bash ./electron --help
./electron: ./electron: cannot execute binary file
I then installed npm and tried to install it from there and I'm getting the following error:
electron#1.6.6 postinstall /usr/local/lib/node_modules/electron
node install.js
sh: 1: node: Permission denied
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian
npm ERR! electron#1.6.6 postinstall: `node install.js`
npm ERR! Exit status 127
npm ERR!
npm ERR! Failed at the electron#1.6.6 postinstall script.
npm ERR! This is most likely a problem with the electron package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node install.js
npm ERR! You can get their info via:
npm ERR! npm owner ls electron
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 4.8.0-0.bpo.2-amd64
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install" "-g" "electron"
npm ERR! cwd /home/amnesia/Desktop/prog
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.21
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/amnesia/Desktop/prog/npm-debug.log
npm ERR! not ok code 0
amnesia#amnesia:~/Desktop/prog$
Does tails somehow prevent downloaded binaries from executing? Are
there certain directories that don't allow executables? I am confused.
I am using tails 2.11
I was able to get electron to work in tails by downloading the "ia32" version of the binary. For some reason the electron x64 binary does not work, even though I am using the 64-bit version of tails.
Has anyone any clues for setting up aldryn cloud solution on windows 10, using latest docker beta and hyper-v?
When running
docker-compose -f C:\Users\Me\project\docker-compose-windows.yml build
I get these errors:
npm ERR! fetch failed https://registry.npmjs.org/estraverse-fb/-/estraverse-fb-1.3.1.tgz
npm ERR! fetch failed https://registry.npmjs.org/lodash.clonedeep/-/lodash.clonedeep-3.0.2.tgz
npm WARN retry will retry, error on last attempt: Error: getaddrinfo ENOTFOUND registry.npmjs.org
npm ERR! fetch failed https://registry.npmjs.org/user-home/-/user-home-2.0.0.tgz
npm WARN retry will retry, error on last attempt: Error: getaddrinfo ENOTFOUND registry.npmjs.org
npm ERR! fetch failed https://registry.npmjs.org/glob/-/glob-7.0.5.tgz
npm WARN retry will retry, error on last attempt: Error: getaddrinfo ENOTFOUND registry.npmjs.org
npm ERR! fetch failed https://registry.npmjs.org/gaze/-/gaze-1.0.0.tgz
npm WARN retry will retry, error on last attempt: Error: getaddrinfo ENOTFOUND registry.npmjs.org
npm ERR! fetch failed https://registry.npmjs.org/lodash.clonedeep/-/lodash.clonedeep-3.0.2.tgz
npm WARN retry will retry, error on last attempt: Error: getaddrinfo ENOTFOUND registry.npmjs.org
npm ERR! fetch failed https://registry.npmjs.org/user-home/-/user-home-2.0.0.tgz
npm WARN retry will retry, error on last attempt: Error: getaddrinfo ENOTFOUND registry.npmjs.org
npm ERR! fetch failed https://registry.npmjs.org/glob/-/glob-7.0.5.tgz
npm WARN retry will retry, error on last attempt: Error: getaddrinfo ENOTFOUND registry.npmjs.org
npm ERR! fetch failed https://registry.npmjs.org/gaze/-/gaze-1.0.0.tgz
npm WARN retry will retry, error on last attempt: Error: getaddrinfo ENOTFOUND registry.npmjs.org
npm ERR! Linux 4.4.13-moby
npm ERR! argv "node" "/usr/local/bin/npm" "install" "--production"
npm ERR! node v0.12.14
npm ERR! npm v2.15.5
npm ERR! code ENOTFOUND
npm ERR! errno ENOTFOUND
npm ERR! syscall getaddrinfo
npm ERR! network getaddrinfo ENOTFOUND registry.npmjs.org
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Please include the following file with any support request:
npm ERR! /npm-debug.log
ERROR: Service 'web' failed to build: The command '/bin/sh -c (cd / && npm-install-retry -- --production)' returned a non-zero code: 1
I'm not even sure this is the culprit, but I stumbled upon: https://github.com/npm/npm/issues/9863
The solution provided there gives me:
sed: can't read ./lib/utils/rename.js: No such file or directory
ERROR: Service 'web' failed to build: The command '/bin/sh -c cd $(npm root -g)/npm && npm install fs-extra && sed -i -e s/graceful-fs/fs-extra/ -e s/fs.rename/fs.move/ ./lib/utils/rename.js' returned a non-zero code: 2
Am I on the right way? Has anyone succeeded yet and are you willing/able to share?
It looks like your docker VM can't talk to the outside world, or at least it can't talk to its DNS server:
npm ERR! errno ENOTFOUND
npm ERR! syscall getaddrinfo
Please make sure the following command work (in that order) before proceeding:
docker run --rm -it busybox ping 8.8.8.8 # Tests raw TCP traffic
docker run --rm -it busybox ping google.com # Tests DNS connectivity
Aldryn also includes a nice utility to check for all this on your behalf:
aldryn doctor
In most cases, when encountering networking issues, restarting the docker VM helps:
docker-machine restart default
But in the case of Hyper-V it might be because of a missing network configuration as well.