I had followed all the steps of configuring the hyperledger business network using this link.
I had configured all the steps but i am stuck at the very last step of starting my business network.I am getting this error
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
6581ef4cc7b6fec6c0b69af693acb62d2690588288e5174d38fa86fcf90fef94:
error starting container: error starting container: Failed to
generate platform-specific docker build: Error returned from build:
1 "npm WARN notice [SECURITY] js-yaml has the following
vulnerabilities: 1 high, 1 moderate. Go here for more details:
https://www.npmjs.com/advisories?search=js-yaml&version=3.10.0-Run
`npm i npm#latest -g` to upgrade your npm version, and then `npm
audit` to get more info.
Please help me to solve this out.
My Enviorment:-
docker:- 18.09.7
docker-compose:-1.21.2
Node:-8.10.0
Npm:-6.9.2
Hyperdledger Fabric:-1.2
Composer:-0.20
Please help me to figure out this issue.
The following are prerequisites for installing the required development tools:
Operating Systems: Ubuntu Linux 14.04 / 16.04 LTS (both 64-bit), or Mac OS 10.12
Docker Engine: Version 17.03 or higher
Docker-Compose: Version 1.8 or higher
Node: 8.9 or higher (note version 9 and higher is not supported)
npm: v5.x
git: 2.9.x or higher
Python: 2.7.x
If you're running on Ubuntu, you can download the prerequisites using the following commands:
curl -O https://hyperledger.github.io/composer/latest/prereqs-ubuntu.sh
chmod u+x prereqs-ubuntu.sh
Related
When I run docker-compose up I'm getting the following error
qemu: uncaught target signal 6 (Aborted) - core dumped
This is happening when docker-compose is running the command bundle install
=> ERROR [5/6] RUN bundle install --jobs 4 --path .bundle/ 4.2s
------
> [5/6] RUN bundle install --jobs 4 --path .bundle/:
#10 4.170 Fetching gem metadata from https://rubygems.org/.[BUG] Segmentation fault at 0x0000418f81e2b0
#10 4.177 ruby 2.3.4p301 (2017-03-30 revision 58214) [x86_64-linux]
#10 4.177
#10 4.177 SEGV received in SEGV handler
#10 4.178 -- Control frame information -----------------------------------------------
#10 4.178 SEGV received in SEGV handler
#10 4.178 SEGV received in SEGV handler
#10 4.178 qemu: uncaught target signal 6 (Aborted) - core dumped
#10 4.192 Aborted
------
executor failed running [/bin/sh -c bundle install --jobs 4 --path .bundle/]: exit code: 134
According to this github issue thread on docker's github – its a qemu related bug:
https://github.com/docker/for-mac/issues/5148#issuecomment-784992663
It mentions that qemu is the upstream component Docker use for running Intel (amd64) containers on M1 (arm64) chips. I checked the qemu repo fora related issues with no luck:
https://gitlab.com/qemu-project/qemu/-/issues?scope=all&utf8=%E2%9C%93&state=opened&search=uncaught+target+signal+6
In my docker-compose file I've passed the following config which helped me fix a couple M1 related issue on docker. But this isn't working for this specific issue.
web:
platform: linux/amd64
...
This issue is happening on the following environment
Macbook Pro M1 2020
Mac OS Big Sur 11.2.3
docker-compose version 1.29.1
docker engine: 20.10.6
docker desktop 3.3.3(64133)
I've also opened an issue on qemu repo as well:
https://gitlab.com/qemu-project/qemu/-/issues/340
Any ideas on how to fix this?
I found a hack. This is a way around that specific issue. I fixed it by adding the following line at the top of my Dockerfile.yml to update the image source which might have been outdated
FROM ruby:2.3.4
If you're experiencing a similar issue with another library I suggest looking for an image on Docker Hub https://hub.docker.com/ and making sure that they have support for the desired architecture: amd64 or arm64, etc...
For more information about the qemu error, you can follow this GitLab issue thread: https://gitlab.com/qemu-project/qemu/-/issues/340
Just thought I'd add a discussion point since this is the first thing that comes up on Google.
We're using Fullstaq Ruby jemalloc as our base image and unfortunately there isn't an ARM build of Fullstaq Ruby. Changing our Dockerfile to use a Dockerhub base image appears to solve the issue.
Switching
FROM quay.io/evl.ms/fullstaq-ruby:2.7.6-jemalloc-buster-slim
to
FROM ruby:2.7.6-slim-bullseye
Seems to do the trick.
After completing full installation of Hyperledger as per their documentation mentioned here, when I execute composer-playground, I get error saying The gRPC binary module was not installed. This may be fixed by running "npm rebuild"
This happens even after I run npm install and npm rebuild.
Full stacktrace is metioned below:
error: [Hyperledger-Composer] :ConnectionProfileManager :getConnectionManagerByTyp Error: Failed to load connector module "composer-connector-hlfv1" for connection type "hlfv1". The gRPC binary module was not installed. This may be fixed by running "npm rebuild"
Original error: Cannot find module '/usr/lib/node_modules/composer-playground/node_modules/grpc/src/node/extension_binary/node-v59-linux-x64-glibc/grpc_node.node'-The gRPC binary module was not installed. This may be fixed by running "npm rebuild"
Original error: Cannot find module '/usr/lib/node_modules/composer-playground/node_modules/grpc/src/node/extension_binary/node-v59-linux-x64-glibc/grpc_node.node'-The gRPC binary module was not installed. This may be fixed by running "npm rebuild"
Original error: Cannot find module '/usr/lib/node_modules/composer-playground/node_modules/grpc/src/node/extension_binary/node-v59-linux-x64-glibc/grpc_node.node'-The gRPC binary module was not installed. This may be fixed by running "npm rebuild"
Original error: Cannot find module '/usr/lib/node_modules/composer-playground/node_modules/grpc/src/node/extension_binary/node-v59-linux-x64-glibc/grpc_node.node'-The gRPC binary module was not installed. This may be fixed by running "npm rebuild"
Original error: Cannot find module '/usr/lib/node_modules/composer-playground/node_modules/grpc/src/node/extension_binary/node-v59-linux-x64-glibc/grpc_node.node'-The gRPC binary module was not installed. This may be fixed by running "npm rebuild"
Original error: Cannot find module '/usr/lib/node_modules/composer-playground/node_modules/grpc/src/node/extension_binary/node-v59-linux-x64-glibc/grpc_node.node'-The gRPC binary module was not installed. This may be fixed by running "npm rebuild"
Original error: Cannot find module '/usr/lib/node_modules/composer-playground/node_modules/grpc/src/node/extension_binary/node-v59-linux-x64-glibc/grpc_node.node'
at Promise.resolve.then (/usr/lib/node_modules/composer-playground/node_modules/composer-common/lib/connectionprofilemanager.js:144:42)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:118:7)
Looks like you are using node V9. Composer only works with Node V8. Suggest you use nvm https://github.com/nvm-sh/nvm to manage your node installations. Use it to install node 8 (nvm install 8). Then you will need to npm install composer again.
I am trying to install opencv using conda on a windows machine. I am running the following command:
conda install --channel https://conda.anaconda.org/menpo opencv
and getting the following error:
Solving environment: done
## Package Plan ##
environment location: C:\ProgramData\Anaconda2
added / updated specs:
- opencv
The following NEW packages will be INSTALLED:
opencv: 2.4.11-py27_1 menpo
Proceed ([y]/n)? y
Preparing transaction: done
Verifying transaction: done
Executing transaction: - WARNING conda.gateways.disk:exp_backoff_fn(49):
Uncaught backoff with errno EEXIST 17
failed
ERROR conda.core.link:_execute(502): An error occurred while installing
package 'None'.
IOError(13, 'Permission denied')
Attempting to roll back.
Rolling back transaction: done
IOError(13, 'Permission denied')
WindowsError(183, 'Cannot create a file when that file already exists')
Other people seem to have similar problems (https://github.com/conda/conda/issues/4393). One of the solutions I found was to downgrade conda. I am currently using conda 4.5.4 and when I try to downgrade using conda install conda=4.2 I get the following error:
The following packages will be DOWNGRADED:
conda: 4.5.4-py27_0 --> 4.2.16-py27_0
conda-build: 3.10.5-py27_0 --> 3.9.2-py27_0
Proceed ([y]/n)? y
Preparing transaction: done
Verifying transaction: done
Executing transaction: failed
ERROR conda.core.link:_execute(502): An error occurred while uninstalling
package 'defaults::conda-build-3.10.5-py27_0'.
WindowsError(5, 'Access is denied')
Attempting to roll back.
Rolling back transaction: done
WindowsError(5, 'Access is denied')
Regarding this issue I found the following similar posts:
conda update conda permission error
Anaconda : Update conda failed because permission error
But the solutions given do not fix my problem.
I also had a problem with installation and usage of the OpenCV library. If you have such а problem, you can try:
uninstall opencv with: conda remove --yes opencv (in case you have an installation but it does not work properly)
install OpenCV through pip: pip install opencv-python
I think this is a problem with opencv that comes from Anaconda channels. I came across this problem four months ago. Тhe problem may be resolved right now.
My guess is that you did not run this command with administrator privileges！
I am using below configuration and trying to make Jenkins build but I am getting errors.
Note, I am able to make build successfully with command line.
My PC environments:
OS: ubuntu 14.04
Gradle version: 2.14.1.
Jenkins version: 2.25
Java version: java-8-openjdk-amd64
JENKINS BUILD ERRORS:
[workspace] $ /bin/sh -xe /tmp/hudson2322559356105735311.sh
+ cd /home/ekambaramv/Jenkins/workspace/CARMODE_STAR_O-OS/MAIN/
+ export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/
+ GRADLE_USER_HOME=/home/ekambaramv/Jenkins/gradle-2.14.1/
+ /home/ekambaramv/Jenkins/gradle-2.14.1/bin/gradle clean build
**FAILURE:** Build failed with an exception.
* What went wrong:
Failed to load native library 'libnative-platform.so' for Linux amd64.
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
Build step 'Execute shell' marked build as failure
Finished: FAILUR
E
I've had similar problems with the JNI libary when using Gradle. It's possible you might be using a version of the JNI library that is incompatible with Gradle.
Try going to the site: https://debian.pkgs.org/9/debian-main-amd64/libnative-platform-jni_0.11-5_amd64.deb.html and downloading the libnative-platform-jni_0.11-5_amd64.deb package onto your machine.
You can either open Nautilus and right click the .deb package and select 'Open with Software Install', or you can navigate the command line to the download directory and run the following:
sudo apt-get install ./libnative-platform-jni_0.11-5_amd64.deb
Next, check to see if Gradle still gives you the same "Failed to load native library..." error message as before by running:
gradle --version
If the problem persists, and you still get the error message, you might want to consider upgrading to a later version of Gradle. I was able to get this working on Gradle 3.2.1, but I know this method isn't always possible.
If you need to back out the changes, just run another sudo apt-get update, and the JNI libraries will be overwritten with the latest version once more.
One More Thing
I mentioned the libraries get overwritten the next time you update your system (apt-get, Software Updater). To prevent this, run the following command:
sudo apt-mark hold libnative-platform-jni
This will force the update software to overlook any later versions of the library. To turn this off, run the opposite command:
sudo apt-mark unhold libnative-platform-jni
I've seen a many problems about this, but I didn't get a solution.
My OS is Yosemite and current OpenCV is 2.4.9
I'm trying to install OpenCV with TBB, but when I do it by sudo port install opencv +debug +python27 +qt4 +tbb (through this SO question):
Rafaels-iMac:y3PQFyQhUG rafaelruizmunoz$ sudo port install opencv
+debug +python27 +qt4 +tbb
Warning: The Xcode Command Line Tools don't appear to be installed; most ports will likely fail to build.
Warning: Install them by running 'xcode-select --install'.
Warning: The Xcode Command Line Tools don't appear to be installed; most ports will likely fail to build.
Warning: Install them by running xcode-select --install'.
---> Computing dependencies for ffmpeg
---> Configuring ffmpeg Error: Failed to configure ffmpeg, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_ffmpeg/ffmpeg/work/ffmpeg-2.6/config.log
Error: org.macports.configure for port ffmpeg returned: configure failure: command execution failed Please see the log file for port ffmpeg for details:
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_ffmpeg/ffmpeg/main.log
Error: Unable to upgrade port: 1
Error: Unable to execute port: upgrade ffmpeg failed
And there are not any logs on those paths.
I've tried (support from SO and MacPorts).
port selfupdate
port upgrade ffmpeg
port clean x264
port upgrade outdated
port -f selfupdate
but nothing happened.
Does anyone have a clue?
Thank you in advance.
EDIT: Doing xcode-select --install doesn't resolve anything.
The code that produces this warning is at http://trac.macports.org/browser/trunk/base/src/port1.0/portutil.tcl?marks=3279-3289#L3266. On 10.10, it checks whether /Library/Developer/CommandLineTools/usr/include exists and /Library/Developer/CommandLineTools/usr/bin/make is executable. Since that's not the case on your system, the Command Line Tools have not been successfully installed.
After running xcode-select --install, a dialog box should pop up that allows you to click "Install" to install the Command Line Tools. See http://osxdaily.com/2014/02/12/install-command-line-tools-mac-os-x/ for screenshots.
Once you installed those, your build should work. If it doesn't, you'll have to upload the contents of the main.log for further diagnosis.