v0.10.9.x Help test RC2 forking issues

chaeplin · Jun 19, 2014

MykelSIlver said:
Thanks for your input!
I have tried the hot only config (without the masternodeaddr)
But when I start my masternode I got the message:

inbound port is not open. Please open it and try again. (19999 for testnet and 9999 for mainnet)

I am sure my port is open.

My .darkcoin.conf looks like this:

addnode=23.23.186.131
masternode=1
maxconnections=200

masternodeprivkey=7sDNcghj9gfgrE9ghgKbxtFp1ezLM2tiwYsDa977sejEX

listen=1

Is it really possible to appear in the masternode list with a hot only setup????

I haven't test hot only setup.

MykelSIlver · Jun 19, 2014

chaeplin said:
I haven't test hot only setup.

NP. Again my thanks for looking into this. All the best!

Propulsion · Jun 19, 2014

The error I had above was serious. The wallet was originally made on a linux system, and then swapped into a windows system. It seems like that could of caused an issue somehow.

I was able to transfer the full balance into a freshly created windows wallet. Shortly after the transaction was broadcast, the error wallet crashed. Now it will not reopen. Thankfully, there are zero funds in it at this time. The windows wallet seems to function 100%. If anyone wants to look at the error wallet, I'll upload it.

chaeplin · Jun 19, 2014

Propulsion said:
The error I had above was serious. The wallet was originally made on a linux system, and then swapped into a windows system. It seems like that could of caused an issue somehow.

I was able to transfer the full balance into a freshly created windows wallet. Shortly after the transaction was broadcast, the error wallet crashed. Now it will not reopen. Thankfully, there are zero funds in it at this time. The windows wallet seems to function 100%. If anyone wants to look at the error wallet, I'll upload it.

Hmm, what was the version of libdb ?

I saw a warnning on binary wallet compatibility.

https://github.com/darkcoinproject/darkcoin/blob/master/doc/build-unix.md

Code:

Ubuntu precise has packages for libdb5.1-dev and libdb5.1++-dev,
but using these will break binary wallet compatibility, and is not recommended.

copy the error occured wallet to linux, check if darkcoind can open it.

Propulsion · Jun 20, 2014

chaeplin said:
Hmm, what was the version of libdb ?

I saw a warnning on binary wallet compatibility.

https://github.com/darkcoinproject/darkcoin/blob/master/doc/build-unix.md

Code:

Ubuntu precise has packages for libdb5.1-dev and libdb5.1++-dev, but using these will break binary wallet compatibility, and is not recommended.

copy the error occured wallet to linux, check if darkcoind can open it.

Almost certain i used 5.1. (Don't have access to that machine until tomorrow)

I can do one better though for future reference. Here is the db.log file.
http://pastebin.com/QxZUmQs5

Edit: But then again, my original wallet from way back when has no issues whatsoever. Once again, almost positive that wallet was made with 5.1 as well. *Shrug*

chaeplin · Jun 20, 2014

Propulsion said:
Almost certain i used 5.1. (Don't have access to that machine until tomorrow)

I can do one better though for future reference. Here is the db.log file.
http://pastebin.com/QxZUmQs5

Edit: But then again, my original wallet from way back when has no issues whatsoever. Once again, almost positive that wallet was made with 5.1 as well. *Shrug*

Pretty sure, libdb version.

Code:

file wallet.dat has LSN 1/17743, past end of log at 1/333
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
DB_ENV->log_flush: LSN of 1/17743 past current end-of-log of 1/333
Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
wallet.dat: unable to flush page: 11

Propulsion · Jun 20, 2014

I'll check tomorrow and post my findings.

MykelSIlver · Jun 20, 2014

MykelSIlver said:
NP. Again my thanks for looking into this. All the best!

Its working now!
http://drk.poolhash.org/darksend.html reports my ip, but has "No" in the second column

is flag 1 and is in darkcoin.io: NO
Is this a problem?

chaeplin · Jun 20, 2014

MykelSIlver said:
Its working now!
http://drk.poolhash.org/darksend.html reports my ip, but has "No" in the second column

is flag 1 and is in darkcoin.io: NO
Is this a problem?

Update in "is flag 1 and is in darkcoin.io" field is slitely late. max 5 ~ 10 min.

MykelSIlver · Jun 20, 2014

chaeplin said:
Update in "is flag 1 and is in darkcoin.io" field is slitely late. max 5 ~ 10 min.

Thanks. Is now for more than an hour still "No"
Hope it will disappear and go to "yes" ....

EDIT: If it stays on "No", does the payout still occur in that case?

chaeplin · Jun 20, 2014

MykelSIlver said:
Thanks. Is now for more than an hour still "No"
Hope it will disappear and go to "yes" ....

EDIT: If it stays on "No", does the payout still occur in that case?

Check https://elbzo.net/masternodes.html
Awesome tool ;D

MykelSIlver · Jun 20, 2014

chaeplin said:
Check https://elbzo.net/masternodes.html
Awesome tool ;D

Thanks! Only this first column is (Status darkcoin.io) is still status: "unlisted" for me at this moment :-( all other columns are active. Hope nothing is wrong?

Is there anything I can do about this? Thanks in advance

MykelSIlver · Jun 20, 2014

After shut down the cold wallet and start again a masternode list does not list my ip (of hot wallet anymore). In my debug.log of my hot wallet the message appeared that it was safe to shut down the cold wallet. My hot and cold wallet share the same wallet (one on my local pc, one at Digital Ocean vps). Is that the cause of my problem?

flare · Jun 20, 2014

MykelSIlver said:
Thanks! Only this first column is (Status darkcoin.io) is still status: "unlisted" for me at this moment :-( all other columns are active. Hope nothing is wrong?

Is there anything I can do about this? Thanks in advance

It seems darkcoin.io is a bit laggy - i don't think you have a problem, just give it some time. As long as your IP is listed in the majority of miners/pools clients, your node will get votes and payments.

MykelSIlver · Jun 20, 2014

How up to date is the masternode list in the console of the client(command "masternode list" in console) ? Is there also a lag. Because at that list my ip address is not listed anymore (after a restart of my cold wallet)

MykelSIlver · Jun 20, 2014

When I do a restart of my masternode the following error appear in my debug.log:
ResendWalletTransactions()
2014-06-20 11:08:30 Got bad masternode address signature
????

chaeplin · Jun 20, 2014

MykelSIlver said:
When I do a restart of my masternode the following error appear in my debug.log:
ResendWalletTransactions()
2014-06-20 11:08:30 Got bad masternode address signature
????

If appeared ip is yours, Stop both darkcoind.
Not yours ? No problem.

If appeared ip is yours,
Read this https://www.darkcointalk.org/threads/help-test-rc2-forking-issues.1009/page-44#post-8910

* Moving 1k tDRK to New address and changing masternodeprivkey solves the problem.
And ip of NM is possibly banned by others. So changing of ip of NM is needed.

MykelSIlver · Jun 20, 2014

chaeplin said:
If appeared ip is yours, Stop both darkcoind.
Not yours ? No problem.

If appeared ip is yours,
Read this https://www.darkcointalk.org/threads/help-test-rc2-forking-issues.1009/page-44#post-8910

* Moving 1k tDRK to New address and changing masternodeprivkey solves the problem.
And ip of NM is possibly banned by others. So changing of ip of NM is needed.

***You are Grand Master***

This was my problem man!

AlexGR · Jun 21, 2014

Since RC3 is delayed and we'll have more time to check things, please perform some examination and hardening on time-related attack vectors. As far as I'm aware this area could use some checking and could also present a problem if such vectors are found.

You* might want to try hacked clients with malicious mods to any time-related / time-dependent function that could bring up anomalies and then harden the code for time-related attack vectors. All time-related or sequential functions that build on prior events should be potential candidates. A flow chart might be needed to highlight possible logic vectors on paper. The code can also be reviewed to check for specific lines.

* I'm not active on testing testnet, so I can't do it - someone else has to check it.

vertoe · Jun 21, 2014

Will prepare a new testnet masternode. Are we going to start a new thread for "RC3 forking issues" ?

jimbit · Jun 22, 2014

vertoe said:
Will prepare a new testnet masternode. Are we going to start a new thread for "RC3 forking issues" ?

adding some hashrate: 8Mh solo
I started my testnet MN . this is the current list:

"184.73.179.187:19999" : 1,
"5.45.102.169:19999" : 1,
"104.33.210.231:19999" : 1,
"188.226.243.116:19999" : 1,
"54.178.176.195:19999" : 1,
"92.222.10.179:19999" : 1,
"198.50.148.87:19999" : 1,
"92.222.19.36:19999" : 1,
"184.73.179.196:19999" : 1,
"54.76.220.114:19999" : 1,
"54.189.217.227:19999" : 1,
"188.226.133.22:19999" : 1,
"188.226.248.36:19999" : 1

TanteStefana · Jun 22, 2014

I've still got a testnet masternode going, but it's on 10.10.1. I guess I'll update it? Or? Actually, shouldn't Evan start another thread for RC3.1?

Lariondos · Jun 22, 2014

Started 3 MN 10.10.2 on testnet yesterday. One of them gets double the payments as each of the others. All of them are just 1k MN and were online all the time. May we have an issue here or is this just (good and bad) luck?
"92.222.10.179:19999" - normal, location: France
"92.222.19.36:19999" - normal, location: France
"198.50.148.87:19999" - x2, location: Canada
Please don't tell me the location would have an impact on payments.

vertoe · Jun 22, 2014

Lariondos said:
Started 3 MN 10.10.2 on testnet yesterday. One of them gets double the payments as each of the others. All of them are just 1k MN and were online all the time. May we have an issue here or is this just (good and bad) luck?
"92.222.10.179:19999" - normal, location: France
"92.222.19.36:19999" - normal, location: France
"198.50.148.87:19999" - x2, location: Canada
Please don't tell me the location would have an impact on payments.

define x2?
and link accounts or transactions please http://23.23.186.131:1234/chain/DarkCoin

Lariondos · Jun 22, 2014

vertoe said:
define x2?
and link accounts or transactions please http://23.23.186.131:1234/chain/DarkCoin

Very sorry - I think i have mixed up some internal transactions to the same wallet. Still have to learn much more to read the blockchain. :sad:

Lariondos · Jun 22, 2014

Having recovered partially from my confusion - sorry again - I still have this question, hopefully doing it right this time.
If you look at account mtLYCQ6it9eDjqGurjqBmtFSzebK8ttyaL, you find 55 MN payments for about 1 day. For the same day, you find just 25 MN payments for account mnX22j3tEyovhif1GeecQ8YCAYzWHuXEv3. Both masternodes started yesterday, one at about 11:30 and the other about 12:00 GMT and still running since. (Just ignore the internal transactions, this just started me to wonder.)
Is this variance to be expected, is the time intervall not sufficient, or would one see this as suspicious?

Hope my questions don't bother anyone, otherwise simply ignore me.

yidakee · Jun 22, 2014

Lariondos said:
Having recovered partially from my confusion - sorry again - I still have this question, hopefully doing it right this time.
If you look at account mtLYCQ6it9eDjqGurjqBmtFSzebK8ttyaL, you find 55 MN payments for about 1 day. For the same day, you find just 25 MN payments for account mnX22j3tEyovhif1GeecQ8YCAYzWHuXEv3. Both masternodes started yesterday, one at about 11:30 and the other about 12:00 GMT and still running since. (Just ignore the internal transactions, this just started me to wonder.)
Is this variance to be expected, is the time intervall not sufficient, or would one see this as suspicious?

Hope my questions don't bother anyone, otherwise simply ignore me.

That happened to me too, one node got double of the other within a 24h period. I also experienced 44h without first payout on another node, and a 30 minutes (first payout) from another. Testnet is very small in comparison, so variance is a simple plausible answer.

Awaiting orders from Captain Eddufield. Will bring 15mh/s to testnet too. Just need to know where to point to!

flare · Jun 22, 2014

Lariondos said:
Having recovered partially from my confusion - sorry again - I still have this question, hopefully doing it right this time.
If you look at account mtLYCQ6it9eDjqGurjqBmtFSzebK8ttyaL, you find 55 MN payments for about 1 day. For the same day, you find just 25 MN payments for account mnX22j3tEyovhif1GeecQ8YCAYzWHuXEv3. Both masternodes started yesterday, one at about 11:30 and the other about 12:00 GMT and still running since. (Just ignore the internal transactions, this just started me to wonder.)
Is this variance to be expected, is the time intervall not sufficient, or would one see this as suspicious?

Hope my questions don't bother anyone, otherwise simply ignore me.

For me its normal variance - have a look at http://tdrk.poolhash.org/blocks/masterpay.txt to get a impression how the payouts are distributed.

Code:

[...]
last 90 blocks
     18 mpgNHgxhtGHhYX98wam8X9DWzpNMNaNuEA
      9 n36fd8g9ad9bph8zcmVbLPXYbkqr5H59zF
      9 muj9oHwCtoWLcrALSfV7yQS2yh1KLpbXo6
      8 mpmb1TWTTAvZNiwU91GAX1numoZeLusN8N
      7 mtLYCQ6it9eDjqGurjqBmtFSzebK8ttyaL
      7 mkLN57jC9sYqMkp8RBcJF2H9hvhz6vabwQ
      5 mzCKvrXb42KekMJcFGhneNVnJRcuRPc5Mt
      5 mxv11kABs5n2aLWHytKgFQvESd2f9vwywL
      4 muNRbrwBSgTCdHTYL5R2Eokvj9H1q21ytC
      4 mpd9So5Ryybp5zgxssDxArS8k8z4ie2i26
      4 mfpSMCgkVjrtkSVhfswSWUsdbRUxU6gFFm
      2 msBm7XEsX4x5DSkLcC44tayXS3hYyN8wBR
      2 ms9JqmHQ6QrLbeFFyAp22cofqnR5PNuHkK
      2 mpKNkHEdgtxQAjTCkGB4ZwHAED74qwjDvj
      2 mnX22j3tEyovhif1GeecQ8YCAYzWHuXEv3
      1 mw23256bSTqEkP6ThTRrY3KNicB9cfwzLR
      1 -

Lets say there were 576 blocks paid in the last 24 hours, and 15 active masternodes, then the expected median for one node is 38.4 payouts - which matches the average payouts for your two nodes quite nicely: (55 + 25) / 2 = 40

So yes: It's variance and the timeframe of 1 day is to small to judge wether there is a significant deviation. The distribution algorithm is using (random) tx hashes for each node, to spoof it you will have to find a way to manipulate the tx-hashes .

Lariondos · Jun 22, 2014

yidakee said:
That happened to me too, one node got double of the other within a 24h period. I also experienced 44h without first payout on another node, and a 30 minutes (first payout) from another. Testnet is very small in comparison, so variance is a simple plausible answer.

Awaiting orders from Captain Eddufield. Will bring 15mh/s to testnet too. Just need to know where to point to!

Ok, so let's watch it for some weeks. My testnet nodes will run til next mainnet fork.

I could bring my 12mh/s to testnet, but we need lots and lots more.

yidakee · Jun 22, 2014

We need both lots of hash power and LOTS of clients, p2pool, NOMP, MPOS, and of course... MN's. I will await for instructions and not touch my nodes. I may embark in trying to make a p2pool during this RC3.1.

I hope Evan took the weekend of with family & friends to chill and relax his brain. Today is the only day I am "against" Evan.

World Cup game, Portugal vs USA !!

v0.10.9.x Help test RC2 forking issues

Active Member

New Member

The buck stops here.

Active Member

The buck stops here.

Active Member

The buck stops here.

New Member

Active Member

New Member

Active Member

New Member

New Member

Administrator

New Member

New Member

Active Member

New Member

New Member

Three of Nine

Well-known Member

Grizzled Member

Well-known Member

Three of Nine

Well-known Member

Well-known Member

Well-known Member

Administrator

Well-known Member

Well-known Member