Author Topic: October 5 Test Network  (Read 84482 times)

0 Members and 1 Guest are viewing this topic.

Offline puppies

  • Hero Member
  • *****
  • Posts: 1659
    • View Profile
  • BitShares: puppies
I assume the issue is where I define -s "<ip-of-full/witness-node:port>"  from the directions:
programs/cli_wallet/cli_wallet --rpc-http-endpoint="127.0.0.1:8092" -s "<ip-of-full/witness-node:port>"

but I can't find anything that makes it happy here.

I use this
Code: [Select]
./cli_wallet -w oct5_w0 --chain-id 60e21871125ea9995fe498b7f68a87a85c6583725ea5448f6fd969c59a37df83 -s ws://127.0.0.1:8090 -H 127.0.0.1:8092

That did it.  Thank you Spectral.

Why are you guys launching cli_wallet with the -s flag?  I just launch with
Code: [Select]
./cli_wallet  --chain-id 60e21871125ea9995fe498b7f68a87a85c6583725ea5448f6fd969c59a37df83 -H 127.0.0.1:8092does the -s flag give you access to the other apis?
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Xeldal

  • Guest
I assume the issue is where I define -s "<ip-of-full/witness-node:port>"  from the directions:
programs/cli_wallet/cli_wallet --rpc-http-endpoint="127.0.0.1:8092" -s "<ip-of-full/witness-node:port>"

but I can't find anything that makes it happy here.

I use this
Code: [Select]
./cli_wallet -w oct5_w0 --chain-id 60e21871125ea9995fe498b7f68a87a85c6583725ea5448f6fd969c59a37df83 -s ws://127.0.0.1:8090 -H 127.0.0.1:8092

That did it.  Thank you Spectral.

Offline Spectral

I assume the issue is where I define -s "<ip-of-full/witness-node:port>"  from the directions:
programs/cli_wallet/cli_wallet --rpc-http-endpoint="127.0.0.1:8092" -s "<ip-of-full/witness-node:port>"

but I can't find anything that makes it happy here.

I use this
Code: [Select]
./cli_wallet -w oct5_w0 --chain-id 60e21871125ea9995fe498b7f68a87a85c6583725ea5448f6fd969c59a37df83 -s ws://127.0.0.1:8090 -H 127.0.0.1:8092
Vote for BTS-2 witness: spectral (1.6.30)
0.9 DVS delegate: dvs1.bitspace
Stay tuned for bitspace-clains worker!

Offline puppies

  • Hero Member
  • *****
  • Posts: 1659
    • View Profile
  • BitShares: puppies
I updated my failover script.  It is posted here https://bitsharestalk.org/index.php/topic,18875.new.html#new to keep this thread less crowded.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Xeldal

  • Guest
Having trouble getting feeds going.  Using https://python-graphenelib.readthedocs.org/en/latest/pricefeed.html

In launching the wallet I get the following error:
Code: [Select]
:~/graphene/programs/cli_wallet# ./cli_wallet -w test_wallet --chain-id 60e21871125ea9995fe498b7f68a87a85c6583725ea5448f6fd969c59a37df83 -H 127.0.0.1:8092 -s "127.0.0.1:8090"   
Logging RPC to file: logs/rpc/rpc.log
638120ms th_a       main.cpp:114                  main                 ] key_to_wif( committee_private_key ): 5...W
638121ms th_a       main.cpp:118                  main                 ] nathan_pub_key: GPH...V
638121ms th_a       main.cpp:119                  main                 ] key_to_wif( nathan_private_key ): 5...3
638122ms th_a       main.cpp:166                  main                 ] wdata.ws_server: 127.0.0.1:8090
10 assert_exception: Assert Exception
uri.substr(0,3) == "ws:":
    {}
    th_a  websocket.cpp:600 connect

    {"uri":"127.0.0.1:8090"}
    th_a  websocket.cpp:621 connect

I have witness running with this command:
Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090"  --genesis-json oct5-genesis.json -d oct5 -s "104.236.51.238:2005" -s "104.236.144.84:1776" --witness-id '"1.6.24"' --private-key '["GPH...t","5...5"]'

I assume the issue is where I define -s "<ip-of-full/witness-node:port>"  from the directions:
programs/cli_wallet/cli_wallet --rpc-http-endpoint="127.0.0.1:8092" -s "<ip-of-full/witness-node:port>"

but I can't find anything that makes it happy here.

Offline roadscape

I swapped the base/quote as in the patch in the last commit .. would someone tell me if that is all you need for now?

That's all :)
http://cryptofresh.com  |  witness: roadscape

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
I swapped the base/quote as in the patch in the last commit .. would someone tell me if that is all you need for now?

Offline puppies

  • Hero Member
  • *****
  • Posts: 1659
    • View Profile
  • BitShares: puppies
So.  Am I the only one that gets a left margin when I copy from pastebin?  It messes up the python whitespace.  Is there a way to copy without it?

Did you try downloading the raw file?

Nope.  That worked.  Thanks.  I'm very new to pastebin.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline cube

  • Hero Member
  • *****
  • Posts: 1404
  • Bit by bit, we will get there!
    • View Profile
  • BitShares: bitcube
So.  Am I the only one that gets a left margin when I copy from pastebin?  It messes up the python whitespace.  Is there a way to copy without it?

Did you try downloading the raw file?
ID: bitcube
bitcube is a dedicated witness and committe member. Please vote for bitcube.

Offline spartako

  • Sr. Member
  • ****
  • Posts: 401
    • View Profile
I update my observer node to the latest master I was not able to publish the feed for SILVER.
I got a strange error that you can find here:

https://github.com/cryptonomex/graphene/issues/371

Thanks to bitcube that helped me on telegram (thanks a lot!!!) I switched to a previous commit e68e99ed3ae11ddac607e983e7549e8278fdecc4 and I was able to broadcast the tx but my witness producer started to missing blocks.

So I suspect that if some witness producer update to latest master risk going into a fork.
wallet_account_set_approval spartako

Offline puppies

  • Hero Member
  • *****
  • Posts: 1659
    • View Profile
  • BitShares: puppies
So.  Am I the only one that gets a left margin when I copy from pastebin?  It messes up the python whitespace.  Is there a way to copy without it?

Also I will be missing blocks as I will be testing an updated failover script.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline Spectral

Edit: The latest script is cool!   It has a page of nice stats.  Great work, xeroc!  :)

I apply the same workaround changes to the script and here it is:

http://pastebin.com/vhhXYqjJ

The modified script has the prompt removed.  I need to run it 'automated'. :P

That did the trick, the feed published now. Thank you!

And also +5% to xeroc!
Vote for BTS-2 witness: spectral (1.6.30)
0.9 DVS delegate: dvs1.bitspace
Stay tuned for bitspace-clains worker!

Offline lafona

  • Sr. Member
  • ****
  • Posts: 231
    • View Profile
  • BitShares: lafona
running some tests of the failover script. sorry about the missed blocks
BTS Witnesses: delegate-1.lafona     Witness Thread: https://bitsharestalk.org/index.php/topic,21569.msg280911/topicseen.html#msg280911
MUSE Witness: lafona

Offline puppies

  • Hero Member
  • *****
  • Posts: 1659
    • View Profile
  • BitShares: puppies
Code: [Select]
rm -Rf witness_node_data_dir/blockchain                       # this is what resync does

that means when we do :
Code: [Select]
--resync-blockchain

we loose also our initial config.ini file with our custom settings and it's replaced with the default config.ini   ???

No.  --resync-blockchain does not remove your config.ini
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline rnglab

  • Full Member
  • ***
  • Posts: 171
    • View Profile
  • BitShares: rnglab

just removed InBTC and works great : )

Wonderful!

Regarding the yunbi error, have you tried contacting them to request for an unban of your ip?  Their contact - https://yunbi.com/documents/contact

I will do that, and also ask for their api call limits so we are all aware. Thank you for the advise.
« Last Edit: October 10, 2015, 11:27:59 am by rnglab »