v0.10.17.x Testing

yidakee · Nov 28, 2014

~~Someone sent me 96 tDRK about an hour ago, but did not hit the blockchain~~

Ended up going through...

Status: 0/unconfirmed
Date: 11/28/14 12:08
From: unknown
To: myy68698XcBQsnZjCV9Wh6Ax3vvfPzHafw (own address, label: Testenet 1)
Credit: 96.00 DRK
Net amount: +96.00 DRK
Transaction ID: 124db50e154d099c59b50ce7d63ff3f77d37113de6424de27d70028ecd2d62db

coingun · Nov 28, 2014

Lukas_Jackson said:
coingun's p2pool doesn't work atm. Will be up soon

It's back sorry had some issues with the wallets.

http://test.p2pool.masternode.io:18998/static/

Propulsion · Nov 28, 2014

Having segmentation faults with 10.17.01. on two separate occasions now. Running it through GDB but of course it's not doing it now.

Edit: Got it.

debug.log said:
2014-11-28 20:59:02 InstantX:rocessConsensusVote - Transaction Lock Is Complelete, broadcasting!
2014-11-28 20:59:02 ProcessMessageInstantX::txlreq - Transaction Lock Request: 104.33.210.231:19999 /Satoshi:0.10.17.1/ : rejected 33218beb66233f9065a4fea94b0db546ccfe1da3b54de5b32cfe3c886035d693
2014-11-28 20:59:13 Flushed 1249 addresses to peers.dat 13ms
2014-11-28 20:59:14 Removing old transaction lock 33218beb66233f9065a4fea94b0db546ccfe1da3b54de5b32cfe3c886035d693

Code:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffd37fe700 (LWP 4191)]
0x00007ffff46e8c56 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0  0x00007ffff46e8c56 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007ffff75fe783 in SHA256_Update ()
   from /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
#2  0x000000000047045e in uint256 SerializeHash<CTransaction>(CTransaction const&, int, int) ()
#3  0x00000000005065d1 in CleanTransactionLocksList() ()
#4  0x00000000004fc166 in ThreadCheckDarkSendPool() ()
#5  0x00007ffff693fa4a in ?? ()
   from /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.54.0
#6  0x00007ffff671e182 in start_thread ()
   from /lib/x86_64-linux-gnu/libpthread.so.0
#7  0x00007ffff474afbd in clone () from /lib/x86_64-linux-gnu/libc.so.6

flare · Nov 28, 2014

Propulsion said:

Having segmentation faults with 10.17.01. on two separate occasions now. Running it through GDB but of course it's not doing it now.

Edit: Got it.

Code:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffd37fe700 (LWP 4191)]
0x00007ffff46e8c56 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0  0x00007ffff46e8c56 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007ffff75fe783 in SHA256_Update ()
   from /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
#2  0x000000000047045e in uint256 SerializeHash<CTransaction>(CTransaction const&, int, int) ()
#3  0x00000000005065d1 in CleanTransactionLocksList() ()
#4  0x00000000004fc166 in ThreadCheckDarkSendPool() ()
#5  0x00007ffff693fa4a in ?? ()
   from /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.54.0
#6  0x00007ffff671e182 in start_thread ()
   from /lib/x86_64-linux-gnu/libpthread.so.0
#7  0x00007ffff474afbd in clone () from /lib/x86_64-linux-gnu/libc.so.6

Got a crash on buffer overflow here

Code:

*** buffer overflow detected ***: darkcoind terminated
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x73e0f)[0x7fbacddfbe0f]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x5c)darkcoind: /home/ubuntu/install/include/boost/thread/pthread/recursive_mutex.hpp:101: boost::recursive_mutex::~recursive_mutex(): Assertion `!pthread_mutex_destroy(&m)' failed.

BrainShutdown · Nov 28, 2014

Propulsion said:

Having segmentation faults with 10.17.01. on two separate occasions now. Running it through GDB but of course it's not doing it now.

Edit: Got it.

Code:

2014-11-28 20:59:02 InstantX::ProcessConsensusVote - Transaction Lock Is Complelete, broadcasting!
2014-11-28 20:59:02 ProcessMessageInstantX::txlreq - Transaction Lock Request: 104.33.210.231:19999 /Satoshi:0.10.17.1/ : rejected 33218beb66233f9065a4fea94b0db546ccfe1da3b54de5b32cfe3c886035d693
2014-11-28 20:59:13 Flushed 1249 addresses to peers.dat  13ms
2014-11-28 20:59:14 Removing old transaction lock 33218beb66233f9065a4fea94b0db546ccfe1da3b54de5b32cfe3c886035d693

Code:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffd37fe700 (LWP 4191)]
0x00007ffff46e8c56 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0  0x00007ffff46e8c56 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007ffff75fe783 in SHA256_Update ()
   from /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
#2  0x000000000047045e in uint256 SerializeHash<CTransaction>(CTransaction const&, int, int) ()
#3  0x00000000005065d1 in CleanTransactionLocksList() ()
#4  0x00000000004fc166 in ThreadCheckDarkSendPool() ()
#5  0x00007ffff693fa4a in ?? ()
   from /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.54.0
#6  0x00007ffff671e182 in start_thread ()
   from /lib/x86_64-linux-gnu/libpthread.so.0
#7  0x00007ffff474afbd in clone () from /lib/x86_64-linux-gnu/libc.so.6

same here seg fault after

Code:

2014-11-28 21:00:15 Removing old transaction lock c36f5dad03ed0f72bc1b10facee65ad05744a6a141d3636482b09895e197c392

thelonecrouton · Nov 28, 2014

Getting: 'Status: 0/unconfirmed, has not been successfully broadcast yet' when sending with IX box checked.

Also couldn't DS 10DRK despite having 162 showing as available, with or without manually selecting the inputs.

coingun · Nov 28, 2014

Segfault here as well on the wallet running p2pool and block explorer.

edit: And again...

qwizzie · Nov 28, 2014

got my first succesfull InstantX : 30b7a6c5a40a711d5554e80d7a245d69b810b1a4c2c84c02139e50f5a950d64a

received at target wallet mmTszWeVKUpPaB7Jd6DwifdKphmgC3DG8e instantly .. status however still shows 0 / unconfirmed.. should have
shown 1 as it succeeded at arriving at target wallet.

My previous InstantX got through 3 Masternodes and arrived also at target wallet (a bit late .. but still).

edit : on second thought... it keeps on 0 / unconfirmed untill POW (pools) validates it.. so that makes sense.
what does not make sense is the warning ''has not been successfully transmitted'' while the InstantX did arrive at the target wallet and is therefore successfull in my eyes.
we need some confirmation towards users that InstantX was successfull ? somewhere in the transaction details ? Or maybe current Masternodes InstantX confirmations dont
work as intended? blocking InstantX to get added to Total Balance untill POW confirms it ?

thelonecrouton · Nov 28, 2014

Local QT segfaulted for me too.

stdout:

Code:

stu@stu-laptop:~/.darkcoin$ ./darkcoin-qt --instantxdepth=6
init message: Verifying wallet...
init message: Loading block index...
init message: Verifying blocks...
init message: Loading wallet...
init message: Loading addresses...
init message: Done loading
!!!! USING INSTANTX2
!!!! USING INSTANTX2
QMetaObject::invokeMethod: No such method WalletModel::updateConfirmations()
QMetaObject::invokeMethod: No such method WalletModel::updateConfirmations()
!!!! USING INSTANTX2
QMetaObject::invokeMethod: No such method WalletModel::updateConfirmations()
QMetaObject::invokeMethod: No such method WalletModel::updateConfirmations()
Segmentation fault (core dumped)

last few secs of debug.log:

Code:

2014-11-28 21:12:39 received block 00000002512656dee5a8d52a36e2e141e4e3b5ac888e82a8d0d8b902f955fb26 peer=20
2014-11-28 21:12:39 CheckBlock() : Couldn't find masternode payment(0|1392857138) or payee(0|n2QgqDT8LP1zBMZdfN2uwubpSURG5wSGJz) nHeight 71197.
2014-11-28 21:12:39 CheckBlock() : Couldn't find masternode payment(0|1392857138) or payee(0|n2QgqDT8LP1zBMZdfN2uwubpSURG5wSGJz) nHeight 71197.
2014-11-28 21:12:40 Committing 2 changed transactions to coin database...
2014-11-28 21:12:40 SetBestChain: new best=00000002512656dee5a8d52a36e2e141e4e3b5ac888e82a8d0d8b902f955fb26  height=71197  log2_work=45.905418  tx=157187  date=2014-11-28 21:12:23 progress=1.000000
2014-11-28 21:12:40 received getdata for: block 00000001b9a0c2a0767bd2b303fbba40a3edd2846825924b495547f6b3d02014 peer=3
2014-11-28 21:12:40 received getdata for: block 00000002512656dee5a8d52a36e2e141e4e3b5ac888e82a8d0d8b902f955fb26 peer=3
2014-11-28 21:12:41 received getdata for: block 00000002512656dee5a8d52a36e2e141e4e3b5ac888e82a8d0d8b902f955fb26 peer=19
2014-11-28 21:12:41 ProcessMessageInstantX::txlreq
2014-11-28 21:12:41 ProcessMessageInstantX::txlreq - Already Have Transaction Lock Request: 86.20.185.139:19999 /Satoshi:0.10.17.1/ : accepted 9788ccc18017b5a97dff5e3f5cb3b5e13e3d9dab4450f47b56597228fcdf4c93
2014-11-28 21:12:42 send last getblocks for 00000001b9a0c2a0767bd2b303fbba40a3edd2846825924b495547f6b3d02014 peer=18
2014-11-28 21:12:42 send last getblocks for 00000002512656dee5a8d52a36e2e141e4e3b5ac888e82a8d0d8b902f955fb26 peer=18
2014-11-28 21:12:43 getblocks 71197 to 0 limit 500 peer=18
2014-11-28 21:12:43 getblocks -1 to 0 limit 500 peer=18
2014-11-28 21:12:44 dstx: Got Masternode transaction 5b5e3245070fc6ad82ac9cdfd5cd91a6f67a06a856a1a228113be1e0cc004483

DS was hustling along at top speed though.

edit: MN just crashed too. Last line in debug.log:

Code:

2014-11-28 21:00:18 Removing old transaction lock c36f5dad03ed0f72bc1b10facee65ad05744a6a141d3636482b09895e197c392

coingun · Nov 28, 2014

Ok well I'm completely perplexed by this block explorer. I have reset it three times. I have updated the required address_version in abe.conf and i've dropped the database and rebuild numerous times. Still refuses to display testnet addresses??? WTF??? Flare any thoughts?

Lukas_Jackson · Nov 28, 2014

With instantx I still need to wait for 1 confirmation not 6 but it is not instant yet :wink:

qwizzie · Nov 28, 2014

okay, InstantX transactions do seem to work but something is wrong with the confirmation aspect and it isnt added instantly to the Total Balance of the target wallet, it keeps
waiting for POW to confirm it while InstantX should have confirmed it already through its Masternodes ?

edit : running wallet with commandline -instantxdepth=6 didnt help either .....

flare · Nov 28, 2014

coingun said:
Ok well I'm completely perplexed by this block explorer. I have reset it three times. I have updated the required address_version in abe.conf and i've dropped the database and rebuild numerous times. Still refuses to display testnet addresses??? WTF??? Flare any thoughts?

Edit the "chain" table in the DB directly

Code:

update chain set chain_address_version=unhex('6F') where chain_name='Darkcoin';

and rescan the blockchain again.

Code:

python -m Abe.abe --config abe-my.conf --rescan

coingun · Nov 28, 2014

flare said:
Edit the "chain" table in the DB directly

Code:

update chain set chain_address_version=unhex('6F') where chain_name='Darkcoin';

and rescan the blockchain again.

mysql> select * from chain;
+----------+----------+-----------+------------+-------------+-----------------------+---------------------+
| chain_id | magic_id | policy_id | chain_name | chain_code3 | chain_address_version | chain_last_block_id |
+----------+----------+-----------+------------+-------------+-----------------------+---------------------+
| 1 | 1 | 1 | Darkcoin | DRK | L | 71216 |
+----------+----------+-----------+------------+-------------+-----------------------+---------------------+
1 row in set (0.01 sec)

mysql> update chain set chain_address_version=unhex('6F') where chain_name='Darkcoin';
Query OK, 1 row affected (0.02 sec)
Rows matched: 1 Changed: 1 Warnings: 0

mysql> select * from chain;
+----------+----------+-----------+------------+-------------+-----------------------+---------------------+
| chain_id | magic_id | policy_id | chain_name | chain_code3 | chain_address_version | chain_last_block_id |
+----------+----------+-----------+------------+-------------+-----------------------+---------------------+
| 1 | 1 | 1 | Darkcoin | DRK | o | 71216 |
+----------+----------+-----------+------------+-------------+-----------------------+---------------------+
1 row in set (0.00 sec)

BAM!!! God you are good.

Edit: Didn't seem like a rescan was needed.

coingun · Nov 28, 2014

This wallet and p2pool pretty much hate each other. Basically seg faults the wallet within 10mins of running any bit of load. 10mh/s and under even.

qwizzie · Nov 28, 2014

weird, i just did another InstantX with commandline -instantxdepth=6 and that one was added to target wallet's Total Balance immediately
and transaction details showed 6 confirmations ... so that one worked as intended

Propulsion · Nov 28, 2014

Segmentation Fault whenever the daemon "Removes old transaction lock".

debug.log said:
2014-11-28 21:54:22 Removing old transaction lock 975d119097c2cfdb0b9afee391182febccf5749d51574a40f85b23d8eedabfbc

Code:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffca5b1700 (LWP 4671)]
0x00007ffff46e8a70 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0  0x00007ffff46e8a70 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007ffff75fe6ff in SHA256_Update ()
   from /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
#2  0x00000000004703ec in uint256 SerializeHash<CTransaction>(CTransaction const&, int, int) ()
#3  0x00000000005065d1 in CleanTransactionLocksList() ()
#4  0x00000000004fc166 in ThreadCheckDarkSendPool() ()
#5  0x00007ffff693fa4a in ?? ()
   from /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.54.0
#6  0x00007ffff671e182 in start_thread ()
   from /lib/x86_64-linux-gnu/libpthread.so.0
#7  0x00007ffff474afbd in clone () from /lib/x86_64-linux-gnu/libc.so.6

yidakee · Nov 28, 2014

How many MNs are up? I'm under a VM and acting funny, not letting me "masternode start" no matter what I do. But I've had this before, I cant remember which wifi settings on the VM side...

MrMime · Nov 28, 2014

new tMN up.

Lukas_Jackson · Nov 28, 2014

40 tMN

v0.10.17.x Testing

Well-known member

Well-known member

The buck stops here.

Well-known member

Active member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Active member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

The buck stops here.

Well-known member

Active member

Active member