Bitshares RPC Issues

[roadscape]

the command i use for the rpc has not changed,

cli_wallet -H 0.0.0.0:8092

in fact nothing in our set up has changed whatsoever.... really confused what could cause the rpc to stop responding like this,

can you @xeroc confirm you have no issues currently with your own rpc?

@roadscape can you?


i wouldnt be posting here if i hadnt exaused all my other attempts to resolve this for 8+ hours so im sorry for dragging you all in

all i get when i try my rpc is:

curl: (56) Recv failure: Connection reset by peer

No issues on my end.. not sure what would cause this.. fwiw, I always start it with something like

Code: [Select]

./programs/cli_wallet/cli_wallet --rpc-http-endpoint="127.0.0.1:8081" -s ws://127.0.0.1:8082

[xeroc]

a) you should never ever have your wallet listen to 0.0.0.0 .. no matter your firewall setting
b) make sure your wallet is not already running and maybe stuck
c) make sure it is indeed listening to the port using "netstat -tulpen"

[kuro112]

the command i use for the rpc has not changed,

cli_wallet -H 0.0.0.0:8092

in fact nothing in our set up has changed whatsoever.... really confused what could cause the rpc to stop responding like this,

can you @xeroc confirm you have no issues currently with your own rpc?

@roadscape can you?


i wouldnt be posting here if i hadnt exaused all my other attempts to resolve this for 8+ hours so im sorry for dragging you all in

all i get when i try my rpc is:

curl: (56) Recv failure: Connection reset by peer

[pc]

I wanted to write the same thing as xeroc - for me accessing the wallet RPC API via curl works just fine.

I did have the same problem that you seem to have, when I first tried that a couple of months ago, exactly because I wasn't using the --rpc-http-endpoint option but the --rpc-endpoint.

[xeroc]

The RPC has not changed. Ivassume something is strange in your setup.
Make sure to have the -H flag for opening the rpc port at the cli-wallet. Do not use the -r (unless of course you do not want HTTP wrapped JSON)

[kuro112]

hey guys, were trying to get sharebits and our rpc back online, but were facing a weird issue with the new fork, hopefully some one like @xeroc will have some idea,

so we updated to the new fork, local wallet commands work fine;

Code: [Select]

unlocked >>> "get_committee_member" ebit
"get_committee_member" ebit
{
  "id": "1.5.23",
  "committee_member_account": "1.2.159",
  "vote_id": "0:112",
  "total_votes": 0,
  "url": "ebitrose.com"
}

however when we try to curl both locally and remotely, we get no response at all:

Code: [Select]

curl --data-binary '{\"jsonrpc\":\"2.0\",\"method\":\"call\",\"params\":[0,\"is_locked\",[]],\"id\":1337}'  http://127.0.0.1:8092/rpc
nothing has changed on our setup in terms of firewall, build method, etc - i use automated scripts to perform everything...

the only thing we can think of is that this may be a bug as a result of the most recent fork.... any insight anyone?