BitShares Forum
Main => Technical Support => Topic started by: madforstrength on June 16, 2016, 04:44:35 am
-
Hi @xeroc ,
I am having an issue that after running for sometime wallet starts showing this message:
10 assert_exception: Assert Exception\n!ec: websocket send failed: invalid state\n {"msg":"invalid state"}\n th_a websocket.cpp:164 send_message
Than I have to restart wallet to make it work again.
Can you help me out in sorting this issue as my applications stop working and requires manual restart of wallet.
-
I noticed that error also from time to time ... no clue how to fix this ..
@dannotestein, do you have an explanation for this?
-
I noticed that error also from time to time ... no clue how to fix this ..
@dannotestein, do you have an explanation for this?
It looks like that error means the wallet is sending data at an inappropriate time for the server to process it. Do either of you have a test case that can reliably reproduce the error so that we can investigate it? Also, are you both using python libraries to communicate with the wallet?
-
I noticed that error also from time to time ... no clue how to fix this ..
@dannotestein, do you have an explanation for this?
It looks like that error means the wallet is sending data at an inappropriate time for the server to process it. Do either of you have a test case that can reliably reproduce the error so that we can investigate it? Also, are you both using python libraries to communicate with the wallet?
That error happens even in the cli-wallet itself .. not python interaction at all .. (at least this happend to me with the steem cli-wallet .. not using the bts cli-wallet much)
-
I noticed that error also from time to time ... no clue how to fix this ..
@dannotestein, do you have an explanation for this?
It looks like that error means the wallet is sending data at an inappropriate time for the server to process it. Do either of you have a test case that can reliably reproduce the error so that we can investigate it? Also, are you both using python libraries to communicate with the wallet?
That error happens even in the cli-wallet itself .. not python interaction at all .. (at least this happend to me with the steem cli-wallet .. not using the bts cli-wallet much)
ok, we're not experiencing this here, and we use the cli-wallet pretty heavily, of course, so it must be something different about the usage (or the way it's being compiled). Are you guys using pre-built binaries? Also, do you either of you have a somewhat repeatable test case?
-
not re-producable here unfortunatelly .. but it happens quite often on my steem cli-wallet ..
the usualy behavior is something like this
> unlock xxxxx
> list_my_accounts
> transfer x y "z STEEM" "" true
or
> transfer_to_vesting ..
If I keep the cli-wallet open for a few minutes doing nothing with it .. then the call after it will return the error message above
-
not re-producable here unfortunatelly .. but it happens quite often on my steem cli-wallet ..
the usualy behavior is something like this
> unlock xxxxx
> list_my_accounts
> transfer x y "z STEEM" "" true
or
> transfer_to_vesting ..
If I keep the cli-wallet open for a few minutes doing nothing with it .. then the call after it will return the error message above
I use my steem cli-wallet in very similar ways reasonably often, but I haven't ever seen this error (although I suppose it's possible that console spam has scrolled it off the screen). I'm starting to wonder if it's not some difference in how our wallets or witnesses are compiled.
-
Perhaps there were networking issues between your cli and a remote node?
Dan may be running local nodes, so didn't see such issue.
-
Perhaps there were networking issues between your cli and a remote node?
Dan may be running local nodes, so didn't see such issue.
probably .. will try to work on localhost more often and see if it happens again
-
Perhaps there were networking issues between your cli and a remote node?
Dan may be running local nodes, so didn't see such issue.
My steem witness is on a local node and I was assuming xeroc did as well :-)