Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - jtme

Pages: 1 [2] 3
16
Muse/SoundDAC / Re: MUSE Witnesses
« on: October 15, 2015, 08:17:09 pm »
I'm  interested, especially if you are looking for those who are not running bts at the same time,
yet they have already experience running the witness.
I was part of the latest graphene test net, missed least blocks.
I have skipped attempting being bts witness, but I would like to be a muse witness.

17
General Discussion / Re: October 5 Test Network
« on: October 11, 2015, 08:02:45 pm »
Could be it's using the built in genesis which only has 10 or so accounts in it.

 Did you triplecheck the genesis file is in the right location? ;) and are you using a seed node in config.ini?

Yes on all counts. I posted the full config.ini below (above).

my strace shows

Code: [Select]
open("genesis.json", O_RDONLY) = 3

if you do not have it in the output, it is not opened then.

18
General Discussion / Re: October 5 Test Network
« on: October 11, 2015, 06:49:42 pm »
I've been launching the witness_node the same way for several months and never ran into issues like you had, both building locally and copying to a VPS. One thing that did bug me a few times was an incorrect genesis path, that error message really is unclear...

Yeah that one bit me in the ass so hard I still can't sit without pain :)

It was changed from a relative path that processed ~ for example to an absolute one.

sometimes it is helpful to see what files are opened or atempted to open  using strace

Code: [Select]
strace -f ./witness_node_startup_script   2>&1 | grep open

19
General Discussion / Re: October 5 Test Network
« on: October 09, 2015, 11:45:32 am »
Many delegates went in a big minor fork (~35% partecipations) and also spartako and spartako_bot

I removed the blockchain and resynced with the main chain using this seed node:
188.165.233.53:1777

This is the error then I found:
Code: [Select]
3080000 unlinkable_block_exception: unlinkable block
block does not link to known chain
    {}
    th_a  fork_database.cpp:78 _push_block

    {"new_block":{"previous":"00018aeac52ac578eead894ddaefb832bab051d0","timestamp":"2015-10-09T10:10:21","witness":"1.6.19","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f6a191cc3c9f8ea6d06f1e3546931a35873961b0b0defe5689a35de504c448ddc3818793a52abbe65da08faa70b5700df2c13088629dd9c1c43a13a2f3ac9fc8c","transactions":[]}}
    th_a  db_block.cpp:197 _push_block
901261ms th_a       fork_database.cpp:57          push_block           ] Pushing block to fork database that failed to link: 00018aec0d81d4f086eaffcecc9a028749483c49, 101100
901262ms th_a       fork_database.cpp:58          push_block           ] Head: 101115, 00018afb2ccf99a7986cf678b67613061ba56d0f
901262ms th_a       application.cpp:429           handle_block         ] Error when pushing block:
3080000 unlinkable_block_exception: unlinkable block
block does not link to known chain
    {}


syncing from 104.236.51.238:2005 with latest master witout any problem
it requires a bit patience until it stops writing
Code: [Select]
1831000ms th_a       witness.cpp:179               block_production_loo ] Not producing block because production is disabled until we receive a
 recent block (see: --enable-stale-production)
1832000ms th_a       witness.cpp:179               block_production_loo ] Not producing block because production is disabled until we receive a
 recent block (see: --enable-stale-production)

and starts syncing.

20
General Discussion / Re: October 5 Test Network
« on: October 09, 2015, 07:25:04 am »
After upgrading, I'm unable to download blocks - I deleted all data dirs etc to be sure, used --resync-blockchain etc too.

It's stuck at
482000ms th_a       witness.cpp:179               block_production_loo ] Not producing block because production is disabled until we receive a recent block (see: --enable-stale-production)

Is the seednode not sending blocks? Is there another seed node I can try?

seednode is fine, just synced from it quite quickly. But I'm not yet on latest master.

21
General Discussion / Re: October 5 Test Network
« on: October 07, 2015, 07:54:03 pm »
BM, I think there are now 3 witnesses waiting to be voted in:

bitshares-argentina
triox-delegate
pmc

Voted.   Any others?

yep, I think I got voted out by this (had only my votes) 1.6.31

22
General Discussion / Re: October 5 Test Network
« on: October 07, 2015, 06:13:01 pm »
I am getting this sometimes

Code: [Select]
3033114ms th_a       db_block.cpp:191              _push_block          ] Failed to push new block:
10 assert_exception: Assert Exception
next_block.witness == scheduled_witness: Witness produced block at wrong time
    {"block witness":"1.6.37","scheduled":"1.6.24","slot_num":1}
    th_a  db_block.cpp:646 validate_block_header

    {"next_block.block_num()":58718}
    th_a  db_block.cpp:511 _apply_block
3033116ms th_a       application.cpp:425           handle_block         ] Error when pushing block:
10 assert_exception: Assert Exception
next_block.witness == scheduled_witness: Witness produced block at wrong time
    {"block witness":"1.6.37","scheduled":"1.6.24","slot_num":1}
    th_a  db_block.cpp:646 validate_block_header

    {"next_block.block_num()":58718}
    th_a  db_block.cpp:511 _apply_block

    {"new_block":{"previous":"0000e55de39c07283d1779c89018c18206bfa9f2","timestamp":"2015-10-07T17:50:33","witness":"1.6.37","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f19b73fc82aa7519e28f34b1f8e10f63da27365c8e5699fd9f77c0ee1f4c4b02841560af821e3ec8e71f72264934140c7fb2cdd78e0f91920edc7b8cba9c33cfb","transactions":[]}}
    th_a  db_block.cpp:197 _push_block

I see the same. Perhaps something wrong wrong 1.6.37.

updated to latest master again (jtm1).

23
General Discussion / Re: October 5 Test Network
« on: October 07, 2015, 02:59:34 pm »
jtm1 updated

24
General Discussion / Re: October 5 Test Network
« on: October 06, 2015, 05:26:24 pm »
I would appreciate votes too, proxy set

  jtm1
{
  "id": "1.6.31",
  "witness_account": "1.2.91556"

25
General Discussion / Re: October 5 Test Network
« on: October 05, 2015, 10:14:10 pm »
get_witness jtm1
{
  "id": "1.6.31",
  "witness_account": "1.2.91556",

ready. The vps is
2core 2GB RAM, 1Gbit network

I will move within some hours to
4core 4GB RAM, 1Gbit network vps

so it will meet the min. specs.

26
General Discussion / Re: October 5 Test Network
« on: October 05, 2015, 10:00:09 pm »
Code: [Select]
(gdb) file path_and_file_name_of_your_witness_node_file
(gdb) set args your_starting_parameters
(gdb) run


Thank you :D

Sorry to keep asking stupid questions...but, I was trying to edit xeroc scrypt for feed, and vim seems stuck. There is --INSERT --recording at the end, but I cannot write or even quit... Hint?
Try press ESC ESC ESC, then ':q!'?

I would humbly suggest using
Code: [Select]
ulimit -c unlimited

this will enable core dumps for witness_node
and hence no need to run it in gdb.
Backtrace can be generated from coredump.

I hope I'm not missing something, I'm not an expert on debugging bin. apps.

27
General Discussion / Re: October 2nd Test Network
« on: October 04, 2015, 07:06:42 am »
would be nice if those stress tests would be preanounced.
so we could observe the nodes behaviour (cpu/io load etc) and
bytemaster could set up new testnet if things go wrong
and the network dies.

Before the last stress test (when the network was mostly idle), I have noticed my witness was constantly consuming
10-15% cpu which was strange, also mising some blocks. So I switched
to backup witness. The new witness was under 1% cpu and reported
extra 20 missed blocks, althought the switchower was immediate using update_witness
without any block loss. So it seems the original witness lost track
of lost blocks somehow too.

Also would it not be better to run stress tests without debug mode on
to get better performance ?

28
General Discussion / Re: October 2nd Test Network
« on: October 03, 2015, 07:11:56 pm »
spartako, thank you again for sending CORE! I managed to upgrade my account now :)

Unfortunately, I'm still short 5000 CORE to actually create a witness. Could someone please send another 5000 to account:
'bitspace-testaccount1'?

In case anyone wonders, the total CORE amount needed to register a witness is 15000 CORE. 10k for the account upgrade + 5K for creating the witness (unless I'm missing something)

sent

29
General Discussion / Re: October 2nd Test Network
« on: October 02, 2015, 11:17:06 pm »
"Normal" price feeding activated.

Can you provide "step-by-step" instruction for us?
I'm running with a modified version of xeroc's price feeding script, nothing else special.
Xeroc's: https://github.com/xeroc/python-graphenelib
Mine: https://github.com/abitmore/python-graphenelib

I had made some efforts to get it running, but don't have time to re-do it. I'll try to remember and post.
* Env: Ubuntu 14.04 LTS x86_64, python3 is pre-installed
* sudo apt-get install python3-numpy python3-prettytable python3-setuptools
* Install AutobahnPython
** git clone https://github.com/tavendo/AutobahnPython.git
** cd AutobahnPython
** git checkout v0.9.6
** cd autobahn
** python3 setup.py install
* git clone https://github.com/abitmore/python-graphenelib.git
** cd python-graphenelib
** python3 setup.py install
** cd scripts
** cp config-example.py config.py
** Edit config.py
** python3 pricefeeds.py

it is possible to install autobahn by
Code: [Select]
apt-get install python3-pip
pip3 install autobahn

pricefeeds.py was crashing by division by zero some hours ago, but now it is working fine.
publishing pricefeeds now

30
General Discussion / Re: October 2nd Test Network
« on: October 02, 2015, 09:30:58 pm »
jtm1 updated but missing votes

Pages: 1 [2] 3