Hyperledger fabric2.5 peer lifecycle chaincode approveformyorg Error: timed out waiting for txid on all peers - etimedout

I am running HyperledgerFabric 2.5 and I would like to deploy a 3 organizations network with multi peers when I commitChaincodeDefinition i faced an "Error: timed out waiting for txid on all peers"
i already tried to fix it after doing research and saw that it DNS error people solved it by adding an extra host but i couldn't fix it.
Any suggestion will be appreciated

Related

Unable to instantiate the chaincode in muticloud setup

I am trying to achieve the multicloud architecture. My network has 2 peers, 1 orderer and a webclient. This network is in Azure. I am trying to add a peer from Google Cloud Platform to the channel of Azure. For this, I created a crypto-config for 3rd peer from Azure webclient. But in the crypto-config, I made the changes like peers in Azure have their own certificates while for the 3rd peer, I placed the newly created certificates. Now I can install, instantiate, invoke and do queries in the peers(1 and 2). And I can install the chaincodes in 3rd peer. But I am unable to instantiate the chaincodes.
Getting the following error: Error: could not assemble transaction, err proposal response was not successful, error code 500, msg error starting container: error starting container: Post http://unix.sock/containers/create?name=dev-(CORE_PEER_ID)-documentCC-1: dial unix /var/run/docker.sock: connect: permission denied
Can anyone guide me on this.
Note: All the peers, orderer, webclient are running in different vm(s)
#soundarya
It doesn’t matter how many places your solution is deployed
The problem is you are running docker by using sudo command try to add docker to sudo group
Below block will help you out
https://www.digitalocean.com/community/questions/how-to-fix-docker-got-permission-denied-while-trying-to-connect-to-the-docker-daemon-socket
To learn more concept about docker.sock
You can refer to my answer in another Can anyone explain docker.sock

Need help in fixing this error "Connection reset by peer - SSL_connect"

Need help in fixing this error
Faraday::ConnectionFailed (Connection reset by peer - SSL_connect):
this is logfile from /var/log/gitlab/gitlab-rails/production.log
i got this error when i'm trying to google auth to our gitlab-ce.
this is my environment:
- CentOS 7
- Gitlab 12.5
any help is appreciated :) Thanks
You had a similar error reported in gitlab-org/gitlab-foss issue 1924:
I had the exact same thing happen last night and it turned out that the /etc/resolv.conf within the Docker container was unreadable by the "git" user for the container.
This prevents it from resolving the host you're calling back to.
The ball started rolling after reading this issue: docker-gitlab issue 627.
In your case, you might not use a GitLab within Docker, in which case, check your proxy.

Impossible to install python package with anaconda on corporate laptop

I have anaconda install on my corporate laptop. I want to install 2 python packages( Potply & Fuzzywuzzy) but each time I try I have the same error message
Solving environment: failed
CondaHTTPError: HTTP 000 CONNECTION FAILED for url
<https://repo.anaconda.com/pk
gs/r/win-64/repodata.json.bz2>
Elapsed: -
An HTTP error occurred when trying to retrieve this URL.
HTTP errors are often intermittent, and a simple retry will get you on
your way.
If your current network has https://www.anaconda.com blocked, please file
a support request with your network engineering team.
ConnectTimeout(MaxRetryError("HTTPSConnectionPool
(host='repo.anaconda.com',pot
=443): Max retries exceeded with url: /pkgs/r/win-64/repodata.json.bz2
(Caused by ConnectTimeoutError(<urllib3.connection.VerifiedHTTPSConnection
object at 0x00000000054D45F8>, 'Connection to repo.anaconda.com timed out.
(connect timeout=9.
15)'))"))
I have tried to use use the command :
conda config --set ssl_verify no
or
conda config --set ssl_verify false
but none of them are working for me. Also because it's my company laptop I am not admin so I am not able to change the firewall and connection properties and I am not able to contact the service desk to help me on that.
So I 'll be more than happy to hear your solution(s).

GitHub Desktop / Git Shell: SSL read: error:00000000:lib(0):func(0):reason(0), errno 10054

Since this morning, when I try to sync from GitHub Desktop after creating a commit, I sometimes get the message:
When I try to push the commit in Git Shell, I get:
SSL read: error:00000000:lib(0):func(0):reason(0), errno 10054
What could be the issue?
It takes around one or two minute between the time I try to push and the time I get the error message (in GitHub Desktop or Git Shell), so I suspect some connection issues on GitHub side (I have checked the robustness of the connection on my side), but I find the message sibylline.
I use GitHub Desktop with Windows 7 SP1 x64 Ultimate.
Change URL from https to http, for me it worked. There must be problem with ssl tunnel. But currently you can start it by switching to http.
I got here because I was looking for a solution, too. I have got an SSL read: error.... (identical to yours) returned as well when I was trying to push a commit. The reason might have been some big files in the commit that you were trying to push to github.
For me, I followed steps https://git-lfs.github.com provides and it seems to solve my problem.

Openshift git push error

I recently installed an openshift instance with 2 brokers 2 nodes and 3 mongodb/active mq nodes.
I used the openshift origin puppet module and it is mostly working ok.
I can create, move & deploy normal and scalable applications but when I push changes to my gear (using git) I get the following error message:
Failed to report deployment to broker. This will be corrected on the next git push. Message: Connection reset by peer - SSL_connect
The push itself is successful:
remote: Git Post-Receive Result: success
remote: Activation status: success
remote: Deployment completed with status: success
But I always get this error message when I push.
I checked the node and broker logs I tried to tcpdump the servers and use wireshark to check the communication between node and broker and I tried to google the error and came up with mostly nothing.
I also went over the deployment guide and checked the installation and everything seems to be in order.
When I:
curl https://MyBroker/broker/rest/api
I get an api response and not an SSL error:
{"api_version":1.7,"data":{"API": {"href":"https://MyBroker/broker/rest/api","method":"GET","optional_params":[] ..
Any help will be appreciated.
Thank you
Keren