I am setting up a multi-node Hyperledger Sawtooth network using Docker images. I am able to bring up Sawtooth Validator, Settings TP and intkey TP on 3 AWS VMs, however, the Validators are not able to connect each other. I am getting the following error:
Attempted to remove send_message function for connection OutboundConnectionThread-tcp://3.xxx.xxx.xxx:8800, but no send_message function was registered
WARNING dispatch] Attempted to remove send_last_message function for connection OutboundConnectionThread-tcp://3.xxx.xxx.xxx:8800, but no send_last_message function was registered
Any pointers to resolve the issue would be very helpful. Thanks!
Here is the answer I posted in https://chat.hyperledger.org/channel/sawtooth
That looks like a ZMQ error. It was not able to connect, so it had an error when it was disconnecting during cleanup when the task was ending. The real error should be earlier. But I think the root cause is lack of network connectivity. Try these tips and see if they help:
https://sawtooth.hyperledger.org/faq/installation/#i-get-this-error-after-setting-up-a-sawtooth-network-can-t-send-message-ping-response-back-to-because-connection-outboundconnectionthread-tcp-192-168-0-100-8800-not-in-dispatcher
Related
I have a need to run mysql queries within gulp to check certain fields in a table. I currently connect to a development server via ssh tunnel, which is opened via terminal so that my host is set to 'localhost'.
When I execute a connection attempt, the tunnel crashes with:
channel 4: open failed: connect failed: Connection refused
Then the server process crashes with an out of memory error.
We use node-mysql2 and a ssh tunnel to run GraphQL locally for testing, so I can't think of anything in particular in gulp that would cause what is essentially a race condition almost instantaneously from the time that the gulp command is sent.
Gulp Code:
If anyone has any insights I'd be much obliged.
Fix can be found here, thanks to the mysql2 developer for pointing me in the right direction!
More info on fix here:
https://stackoverflow.com/a/30669454/705115
For deploying blockchain in an IBM Cloud Container Service, I am following the steps outlined on https://github.ibm.com/IBM-Blockchain/ibm-container-service/blob/v1.0.0/cs-offerings/free/README.md
while running the script "create_all.sh" I am getting the following error repeatedly:
Unable to connect to the server: dial tcp 127.0.0.1:8080: connectex: No connection could be made because the target machine actively refused it.
Waiting for createchannel container to be Completed
I have already tried starting the procedure from the first step all over again. But no luck so far. Not sure why I keep getting this error.
Any help or hint in this regard will be of great value to me. Thanks!
The environment variable KUBECONFIG should be pointing to the correct "kube config yml" file.
i'm getting some issues connecting to Cloud SQL from Container engine...
I followed https://cloud.google.com/sql/docs/container-engine-connect tutorial and it all seems to work, though I had to tweak a few things with the password/user stuff being sent.
However after several failed attempts of the container trying connect using Cloud SQL Proxy I am now seeing this error ER_HOST_IS_BLOCKED: Host '104.197.135.204' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts'
FLUSH HOSTS; doesn't seem to fix it.
and I'm unable to change the max_connect_errors value since root doesn't have the super privilege & it's not part of the MySQL flags customizable https://cloud.google.com/sql/docs/mysql-flags
any thoughts?
Got some answers through Google Cloud SQL Slack channel. It was actually related to a different database
However, I did learn that the ER_HOST_IS_BLOCKED is reset whenever a successful connection is made so this should never be an issue
I am using AWS Elasticbeanstalk for my project.When I uploading new version app it is giving error
Update environment operation is complete, but with errors. For more information, see troubleshooting documentation
My IAM role has AWSElasticbeanstalkFullAccess
Then why I am getting this error.
Thank in advance
I had the same issue.
I did the following and it worked.
From Elastic Beanstalk environment page, I chose to Rebuild the environment (Actions > Rebuild Environment)
Deployed the new application version.
A number of things can result in this, including issues with .ebextensions files.
Troubleshooting tends to be iterative, since logs are frequently not created or inaccessible.
Things to try:
Roll back to a previous application version and verify any changes to .ebextensions are valid
Rebuild the environment (Actions -> Rebuild Envrionment) in the EB console. This frequently enables EBs log snapshot facility to recover such that you can get further insight into what might be amiss.
You can try digging what the error exactly was by getting the logs of the event in the 'eb-engine.log' file. In my case I got this error and follow one answer to solve it. You can try 'eb logs' command also to get detailed info.
I downloaded and installed the driver setup file, DB2OLEDB.exe, from here:
http://download.microsoft.com/mwg-internal/de5fs23hu73ds/progress?id=HYLbKUfGNl
Using the connection string that worked on another PC, I tried to create a Connection Object in an SSIS package. When I tested the connection I got this error:
Test connection failed because of an error in initializing provider. A TCPIP socket error has occurred (10057): A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied.
Any suggestions on what the cause of this error is and how I might resolve this issue?
By the way, when I use the DB2 Configuration set up utility and test a connection from within that, I am able to successfully connect.
What other info can I provide to help you answer this question?
Thank you
Could this be related to a blocked port?
If you follow all the steps illustrated here: http://www.bidn.com/blogs/PatrickLeBlanc/ssis/700/connecting-to-db2-using-ssis do you still get the same result?
Maybe a silly question, did you restart the computer after the installation?
Are you an admin user on one machine and not on the other?
You could try to verify the port connectivity with a quick telnet command:
telnet your-db-host your-db-listening-port
If it connects, that one is off the list.
Doing some research I've found two possible fixes.
The first link suggests calling BeginReceive after the EndAccept logic is complete. Are you using script code, or just using the GUI without any scripting?
TCP async sockets throwing 10057
The second link points to drivers / software on the PC. It could be that you are missing a windows update or have faulty hardware / drivers.
I think this is less likely the case since you could connect to a different machine with the same connection string(?). Can you verify this is a valid statement?
http://social.msdn.microsoft.com/Forums/en-US/1bc3df95-c86d-4d25-aa20-30f61ed00c63/odd-socket-errors
If you could show the connection strings used for both the working and non working, and give a little more detail about The "Other PC" in comparison to the non-working PC... that would be helpful =]
If neither of the posts I've linked are the solution, this specific Google search has proven to yield some seemingly helpful results
"socket" "10057" "no address was supplied."