I am trying to deploy a smart contract on the sawtooth network. While creating account with the command : It is getting a timeout.
seth account create --nonce=0 --wait myalias
Error: Problem submitting account creation transaction: Transaction was submitted, but client timed out before it was committed.
Can we increase the timeout or what can be the possible solution for the error?
This usually happens if you did not have --wait on the command line, so the client to wait for the commit response.
Another thing you can do is check that all the client services are running (listed in the docker-compose.yaml file if you are using Docker).
Related
I have a running instance of VerneMQ (cluster of 2 nodes) on Google kubernets and using MySQL (CloudSQL) for Auth. Server accepts connections over TLS
It works fine, but after a few days i start seeing this message on the log:
can't authenticate client {[],<<"Client-id">>} from X.X.X.X:16609 due to plugin_chain_exhausted
The client app (paho) complains that the server refused the connection for being "not authorized (code=5 in paho error)"
after a few retry it finally connects. but every time it get's harder and harder until it just won't connect anymore
If i restart VerneMQ everything get's back to normal
I have only 3 clients currently connected at most, at the same time.
clients already connected have no issues in pub/sub.
In my configuration i have (among other things):
log.console.level=debug
plugins.vmq_diversity=on
vmq_diversity.mysql.* = all of them set
allow_anonymous=off
vmq_diversity.auth_mysql.enabled=on
it's like the server degrades over time. the status webpage reports no problem
My verne server was build from the git repository about a month ago and runs on a docker container
what could be the cause?
what else could i check to find posibles causes? maybe a diversity missconfiguration?
Tks
To quickly explain the plugin_chain_exhausted log: with Verne you can run multiple authentication/authorization plugins, and they will be checked in a chain. If one plugin allows the client, it will be in. If no plugin allows the client, you'll see the log above.
This does not explain the behaviour you describe, though. I don't think I have seen that.
In any case, the first thing to check is whether you actually run multiple plugins. For instance: have you disabled the vmq.passwd and the vmq.acl plugins?
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
Sometimes Mysql57 service while restarting after config changes remains in starting state. most times after a while it comes back in Started. But some times its get stuck in Starting.
Even If I kill process and retry it, does not work.
What is the solution.
check the service account you are using to run Mysql57 service (you are logged in from that account, & Never use Network service account, Use an Admin account which has LOGON as service access, which comes when you just put the creds in for service account properties dialgue.)
Check the temp file which mysql is access does not have locks on it.
restart the machine and try again
I am following the etherpad tutorial.
I created a container on ubuntu and ran it locally. The push to bluemix worked. However when I try to run the container on bluemix I get the following error:
Sorry, an error occurred on our side: Unable to create the network. No
tenant network is available for allocation. [Incident ID
e1d83d17ff51f0ae]
Is this temporary failure or my fault?
I ran the following command
$ sudo ice run -p 9080 --name ethernotes registry-ice.ng.bluemix.net/alicesbox/notes:latest
This is a temporary failure. The response says "an error occurred on our side". When an IBM Container is created it is given a private IP address reachable only by other containers sharing the account. The system was unable to give your instance that address.
Try again.
After your instance has been created you can make it public-facing by giving it a public IP address.
I'm trying to execute the command in the Windows console:
C:\SphinxSearch\bin\indexer --all --config C:\SphinxSearch\sphinx.conf
But I get an error:
ERROR: index 'indexname': sql_connect: Can't create TCP/IP socket
(10093) (DSN=mysql://root:*#localhost:3306/test).
A data source is mysql. Before the server restart everyone works fine.
How can I fix it?
I'm having the same error 10093. It's a windows error code by the way. In my case it occurs when trying to run the indexer through the system account via a scheduled task. If I'm running it directly as administrator, there's not a problem.
According to the site above:
Either your application hasn't called WSAStartup(), or WSAStartup() failed, or--possibly--you are accessing a socket which the current active task does not own (i.e. you're trying to share a socket between tasks).
In my case I'm thinking it might be the last one, some security problem due to user SYSTEM being used in my scheduled task. I was able to solve it by using my admin user instead: in the scheduled task, I set to use my local admin account with the option to "Run when user is logged on or not" and "Do not store password". I've also checked "Run with highest privileges". This seems to have done the trick as now my indexes are rotating on schedule.