I am getting the below error while deploying the business network using multi org env.
Error : Error trying install business network. Error: No valid responses from any peers.
Responses from attempted peer comms was an error : Error : 14 UNAVAILABLE : Connect Failed.
Quick background of my env:
I have a local ubuntu machine with Composer installed.
I have Multi Org setup installed with Hyperledger Fabric which includes 3 Orgs with 9 peers in 9 physical machines.
The connection profile has been used here to deploy the business network application from my local ubuntu machine.
Cards have been created sucessfully with the given Connection Profile and also imported successfully. Created 3 connection profiles for the 3 organizations. Also used TLS certs in the connection profiles.
Please guide me to resolve the issue.
This error is usually seen when the CLI cannot connect to the Fabric using the addresses specified in the connection.json file. Either the Fabric containers are not started or they are not accessible to the CLI via the addresses specified.
Perhaps the addresses are wrong? If you are using 9 physical machines are the addresses resolving? are there firewall issues?
Related
I am trying to run this project on Ubuntu 18.04 server. I am running both server and client on this machine. Then from windows 10 with port 9000 I am getting access to client in my chrome browser at http://localhost:8000/#/
The browser loads the project but the problem is I can't log into the website with trusted account and some other data do not get loaded . When I see browser console I see an error message saying:
Failed to load resource: net::ERR_CONNECTION_REFUSED
This is the server setting:
This is the client setting and putty setting to connect to client.
VPN has been used to connect to server via PuTTY.
The error message in browser:
Could anyone shed some light on this issue? Is it related to windows 10 or VPN or some other issues? I followed some steps from here https://www.ionos.com/digitalguide/hosting/technical-matters/err-connection-reset/
By default, the Flask development environment uses 127.0.0.1 (localhost), which restricts access to processes on the same host (except for VMs/containers, which aren't a factor here).
To access Flask from outside of localhost (e.g., from your Windows 10 machine), use the IP address 0.0.0.0. (You can pass it to run(), or via a command line option of the flask command.
However, do note the warnings about (not) using the development environment for production use.
I am getting a connection refused error while trying to deploy a new business network on the Hyperledger Composer playground which is running locally on the environment. The environment is behind the corporate proxy and I have setup both the proxies (http and https) in the system.
The exact error is mentioned below:
{"error":
{"code":"ECONNREFUSED","errno":"ECONNREFUSED","syscall":"connect","address":"151.101.0.162","port":443}}
I have followed the links given below to setup the Hyperledger Fabric and the corresponding docker containers.
https://hyperledger.github.io/composer/installing/development-tools.html
https://hyperledger.github.io/composer/tutorials/developer-guide.html
At the end of the setup, I notice that there are five docker containers running in the system -
composer, peer0.org1.example.com, orderer.example.com, ca.org1.example.com and couchdb
When I follow the developer guide and try deploying the new business network on the Online BlueMix Composer Playground platform, it works. I was able to see the transactions, commodities and etc for the sample example application.
However, I notice the above error when I tried deploying the new business network on the local composer playground.
The development environment on which the Composer and the fabric is hosted are Ubuntu 14.04, python 2.7, node v6.11.0, npm5.0.4, docker-compose v1.13.0.
Can somebody kindly suggest a workaround / direct me to certain links to resolve this problem?
I am trying to learn basics of blockchain by trying the multichain platform, I have been following multichain guide to make a private blockchain, I am using two instances of EC2, I managed to create a blockchain using my first instance :
>multichaind secondChain -daemon
MultiChain Core Daemon build 1.0 alpha 27 protocol 10007
MultiChain server starting
Looking for genesis block...
Genesis block found
Other nodes can connect to this node using:
multichaind secondChain#XXX.XX.X.XX:XXXX
Node started
However, when I try to connect to the blockchain using a second instance of EC2, I am getting rejected :
>multichaind secondChain#XXX.XX.X.XX:XXXX
MultiChain Core Daemon build 1.0 alpha 27 protocol 10007
Retrieving blockchain parameters from the seed node XXX.XX.X.XX:XXXX ...
Error: Couldn't connect to the seed node XXX.XX.X.XX on port XXXX - please check multichaind is running at that address and that your firewall settings allow incoming connections.
Which is kind of expected, as I need to grant connect rights to that machine. However, It should return me a wallet address so I can grant the connection rights.
I think this is related to EC2 settings that are probably not allowing me to connect. I have few knowledge of EC2 and networks in general. I can't figure this out.
Have you checked if the access to the port is granted on the instance you're trying to connect?
If multichaind says "please check multichaind is running at that address and that your firewall settings allow incoming connection"
It is usually one or the other. Port and Running already.
Since you havent yet granted, its probably port.
I'm trying to install oracle on AWS redhat instance. Follow the steps given on this url: http://www.davidghedini.com/pg/entry/install_oracle_11g_xe_on And when I run config command as follows
/etc/init.d/oracle-xe configure
It gives following error.
Database Configuration failed. Look into
/u01/app/oracle/product/11.2.0/xe/config/log for details
When I check the log files it shows following errors.
ORA-01034: ORACLE not available Process ID: 0 Session ID: 0 Serial
number: 0
It seems specific issue on AWS cloud instance.
Is it because of swap memory?
Or is it because of port issue?
I'm using micro instance on it.
How can I get through?
this might be an EC2 security group issue and outbound access to the network on some port being used by the installer (license check, maybe?).
if your EC2 instance is very tightly locked down, you could test if it's a security group issue by adding a new Outbound security group rule to allow all TCP traffic out to anywhere on the internet (0.0.0.0/0)
for example, the install might be trying to hit a remote licensing server endpoint via HTTP or HTTPS but your security group doesn't allow that traffic out.
perhaps there's a 'verbose' flag that you can run the installer with that can give you more info about what it's failing on? HTH
Why would a Visual Studio Web Deploy have a failure of "unexpected error occurred on a send" when publishing to an intranet site that resolves as an IPv6 address? I am assuming IPv6 had something to do with it because adding the IPv4 address to the hosts file resolves the issue and the web deploy succeeds.
Details:
Initially the build error came from a TeamCity build agent, but the same issue occurs when attempting to publish (or just validate the connection in the publish profile) from Visual Studio.
A ping (successful) to the target machine resolves to an IPv6 address which is identical to the address found from running "ipconfig" on the target machine itself, except for a different Scope ID on the tail end.
Windows UNC share paths to the target machines work fine
The target machine is actually the host of the VM on which the build agent runs.
Below is the error from validating connection on publish profile.
And detail from the original build/deploy attempt.
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(4276, 5): Web deployment task failed. (Could not complete the request to remote agent URL 'https://tapserver:8172/msdeploy.axd?site=MealPlannerCIAPI'.)
This error indicates that you cannot connect to the server. Make sure the service URL is correct, firewall and network settings on this computer and on the server computer are configured properly, and the appropriate services have been started on the server.
Error details:
Could not complete the request to remote agent URL 'https://tapserver:8172/msdeploy.axd?site=MealPlannerCIAPI'.
The underlying connection was closed: An unexpected error occurred on a send.
Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
An existing connection was forcibly closed by the remote host
Again I've fixed the issue, but it is a very baffling fix to me. What would break any of the msdeploy calls that is fixed by adding the IPv4 address to the hosts file when it is clearly already reaching that host using v6?
Have you checked the Option IP Address Restrictions in the Management Service-Configuration (IIS)?
Please be aware that you're always connecting with your local IPv6 address if you try to access an IPv6 target. If you have configured any restrictions, they won't apply for your IPv6 address as the restriction configuration is not compatible with IPv6. So your connection attempt will be declined automatically if you set Access for unspecified clients to Deny.