v12.2 Testing

Status
Not open for further replies.

Geert

Member
Aug 26, 2015
46
21
48
This issue is limited to the wallet code I am assuming. Can we address this little wart in a minor release after 12.2?

I just remember how i'm dealing with this issue on Mainnet. I normally mix the amount i want to privatesend with a reasonable high number of rounds (lets say 6).
I then create a privatesend transaction to myself, just to see if i can get the privatesend transaction through (i cancel it at the end).

If it can not get through because wallet says "not enough denominated funds available", then i set the number of rounds to mix one round lower (in this case to round 5)
and try a new privatesend transaction to see if it gets through.

Its a little workaround to get some of my masternode payments to an exchange through privatesend, when there is a deadline on when that transaction needs to be
known on the blockchain (some exchanges give you a limited time window to sent your Dash to their specific address).

I agree there should be a better solution for this....
 

demo

Well-known Member
Apr 23, 2016
3,114
263
153
Dash Address
XnpT2YQaYpyh7F9twM6EtDMn1TCDCEEgNX
Compilation in my 32bit old machine passed succesfully.
Lets vote the numbers now.
 

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,861
1,854
1,283
Hum, I had the wrong index number in my MN config. I don't see how I could have started the one MN successfully with the wrong index number though? Well, anyway, when I have enough confirmations, I'm pretty sure I'll be able to start the second MN. Also, now everything looks good.

Unlock wallet no longer has the option "for mixing only"? Is that because there is no other use for unlocking the wallet unless you're sending funds, so now it's the only option?

I'm sorry, I don't understaned why my wallet says disabled for all PS function on the overview tab when I enabled everything in the settings - options tabs. I've even restarted the wallet.

I've unlocked the wallet, still I can't select anything under "private send" and the two left buttons say Disabled as well as the main button there.

Do I need a special line in the dash.conf file?

Also, I have "watchdog expired" which just popped up. Not sure if it's something to be concerned about? I still have "masternode started successfully" ?

My other MN, has 51 confirmations but the remote server does not show the MN started. However the local wallet does show "started 1 MN successfully"

Gotta go to bed, getting ill, LOL :D Good night ya'all :)
 
Last edited:

qwizzie

Well-known Member
Aug 6, 2014
1,558
729
183
Dash wallet will actually stop further mixing untill that Privatesend Collateral Payment transaction gets confirmed, is it really necessary to wait on that POW confirmation of these Privatesend Collateral Payments and thereby putting the mixing on hold ?
To @UdjinM6

Still hoping for a reply.

Edit : adjusted the quotation for clarity about what i'm asking
 
Last edited:

GNULinuxGuy

Member
Jul 22, 2014
112
68
78
Dash Address
XjkXfrYTSvdYe4738DtNVX5XfUz7qU9HnY
Dedicated tMN updated to v0.12.2.0-4ecbedb. Appears to be functioning pretty well and receiving payments. Shut it down, removed debug.log and restarted. Seeing quite a few of the errors below during MASTERNODE_SYNC_MNW.
Code:
2017-10-21 17:17:43 ERROR: CMasternodePaymentVote::CheckSignature -- Got bad Masternode payment signature, masternode=014a5a4145e228e2f92a38bd5e37cb1393e6185fc9a2b1ba99d689d974bae2a8-1, error: Keys don't match: pubkey=5d8d4b607f1dcc67025d8b82a2f19da9037dbf4b, pubkeyFromSig=21b12fd8f79a818979415c3f4c8f7e580ed617be, hash=3f0c217042461351a1078a6663c993d696014585c52edbecaf6c6172625f9b98, vchSig=G1IeGAs1aoZw2KCawmghA4U7c8H5Cl2Srzo9Y6EYRRM0TKq1RjVCNH7nZiIkQFm5udatY+C1wThX4/GB9KSVAkE=
2017-10-21 17:17:43 ERROR: CMasternodePaymentVote::CheckSignature -- Got bad Masternode payment signature, masternode=014a5a4145e228e2f92a38bd5e37cb1393e6185fc9a2b1ba99d689d974bae2a8-1, error: Keys don't match: pubkey=5d8d4b607f1dcc67025d8b82a2f19da9037dbf4b, pubkeyFromSig=21b12fd8f79a818979415c3f4c8f7e580ed617be, hash=815d843873cb3560963434d570ad9b18c91dc4267d61923d9a17f62b6bbe6f1b, vchSig=G254yUlcomsk+Q2TNuO0cpOZkxXY+b4xED0uflTPZHGmSr4b5YMdO5c+iN35AbVk4aiFptiKJHGRhGg9KoD0vUA=
2017-10-21 17:17:43 ERROR: CMasternodePaymentVote::CheckSignature -- Got bad Masternode payment signature, masternode=014a5a4145e228e2f92a38bd5e37cb1393e6185fc9a2b1ba99d689d974bae2a8-1, error: Keys don't match: pubkey=5d8d4b607f1dcc67025d8b82a2f19da9037dbf4b, pubkeyFromSig=21b12fd8f79a818979415c3f4c8f7e580ed617be, hash=bf9a675f24299273273ed2431abdf0f8bee3cad6dc68c8bcf307b9a73d83c5ae, vchSig=HBuQjzABInI/BCcJyi71vooGgCmWdXQ1hKq/woVGX2dHLWGpGV0ZSTsgW0lNTjRRJBLiH8g64sBM6GLrkpDjGVM=
I wonder if those are being caused by older nodes on the network? Will continue adding nodes/testing today and tomorrow. :)
 

UdjinM6

Official Dash Dev
Dash Core Team
Moderator
May 20, 2014
3,638
3,538
1,183
Hum, I had the wrong index number in my MN config. I don't see how I could have started the one MN successfully with the wrong index number though? Well, anyway, when I have enough confirmations, I'm pretty sure I'll be able to start the second MN. Also, now everything looks good.

Unlock wallet no longer has the option "for mixing only"? Is that because there is no other use for unlocking the wallet unless you're sending funds, so now it's the only option?

I'm sorry, I don't understaned why my wallet says disabled for all PS function on the overview tab when I enabled everything in the settings - options tabs. I've even restarted the wallet.

I've unlocked the wallet, still I can't select anything under "private send" and the two left buttons say Disabled as well as the main button there.

Do I need a special line in the dash.conf file?

Also, I have "watchdog expired" which just popped up. Not sure if it's something to be concerned about? I still have "masternode started successfully" ?

My other MN, has 51 confirmations but the remote server does not show the MN started. However the local wallet does show "started 1 MN successfully"

Gotta go to bed, getting ill, LOL :D Good night ya'all :)
Remove "masternode=1" from local wallet dash.conf and use only masternode.conf and remote dash.conf, mixing is not supported on masternodes.

To @UdjinM6

Still hoping for a reply.

Edit : adjusted the quotation for clarity about what i'm asking
Good point, we could probably search for collateral id in mempool too. This shouldn't slow down mixing that much though, it should be a pretty rare event anyway. Also, having more irregularity probably even makes mixing process slightly better ;)
 

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,861
1,854
1,283
Thank you Udjin. You say mixing is not supported on masternodes, you mean on the 1000 single deposit, right? Because I'm mixing right now on the other coins that have in the same wallet, seemingly fine?

BTW, did you guys already fix all the bugs, making this a boring test for us all? LOL ;)

OK, maybe you are correct and I can't do PS with MNs in the wallet. I'm getting the error:

"Private Send request incomplete: collateral not valid, will retry"

Oh, OK, upon reading other comments, it looks like this is actually an issue with waiting for collateral payment to clear before being allowed to start mixing. Why was that necessary? Is that part of the bug that was found? Thanks for insight :)
 
Last edited:

UdjinM6

Official Dash Dev
Dash Core Team
Moderator
May 20, 2014
3,638
3,538
1,183
Thank you Udjin. You say mixing is not supported on masternodes, you mean on the 1000 single deposit, right? Because I'm mixing right now on the other coins that have in the same wallet, seemingly fine?
...
No, I assumed that you started your wallet as a local masternode (i.e. you have "masternode=1" in local dash.conf) - that's when wallet turns all PS buttons into "Disabled". Another case is when wallet just tried to create a new automatic backup and it failed to do so for some reason. But I never saw this actually being the reason for anyone before, so I assumed that (most likely) it's the former.

...
BTW, did you guys already fix all the bugs, making this a boring test for us all? LOL ;)
...
Yep, everything seems to be working properly atm :)
 

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,861
1,854
1,283
I like the warning that there are very few number of keys left and that the wallet is about to make a backup for you, but you should make another separate backup. It's a nice reminder! Thanks on behalf of us old and senile :D

I'm sorry @UdjinM6 , I haven't had to touch my masternodes beyond restarting about 2-3 times total in all this time since 12.1 came out. Hence I totally forgot everything, and I don't follow directions very well. Not because I don't want to, but more due to ADD reasons, LOL. I figure I may be a pain in the butt but maybe I'm valuable in that I might do things so stupid you never would have thought to test such a thing, LOL.

Anyway, I have a watchdog expired issue. I downloaded the sentinel folder, all other dependencies were previously installed, so I didn't redo any of that. should I have?

And finally, additional: My mixing, only 3 rounds, is stuck at 93% and the message is "submitted to Masternode, waiting in que" but it never progresses, just sticks there.

Really?????????????? How do I constantly miss these things!

NOTE: Make sure you pulled Sentinel from `core-v0.12.2.x` branch and changed network to `testnet` in `sentinel.conf`.

OK, lets see if I can get the MNs to work now, LOL

Is the protocol 70208 correct? How can I tell if I screwed up Sentinel? Or that I have the correct version? Still not getting over "watchdog expired despite changing the conf file. Is there a command to restart sentinel? Thanks :)
 
Last edited:

qwizzie

Well-known Member
Aug 6, 2014
1,558
729
183
to @UdjinM6

With regards to PrivateSend and the message "Not enough denominated funds available", maybe we could extend it to this :

"Not enough denominated funds available, pls set the number of rounds to mix lower or higher. Note that lower rounds will be less secure
and higher rounds will need additional mixing time"

With regards to number of rounds to mix, this is currently maxed out at 8 rounds. I'm wondering if we could set it to 10 rounds. This means if PrivateSend transactions can not go through at 8 rounds because certain input amounts have too low number of rounds mixed, we still have two extra rounds to play with to get that PrivateSend transaction send with the strongest anonymity.
 
Last edited:

t0dd

Active Member
Mar 21, 2016
150
132
103
keybase.io
Dash Address
XyxQq4qgp9B53QWQgSqSxJb4xddhzk5Zhh
12.2 RPMs built for Fedora 25, 26 and EL7 -- sources here and instruction for installing the binaries for all the various configurations:
https://github.com/taw00/dashcore-rpm

For the binaries, they are in my testing repo. The dashcore-fedora.repo and dashcore-centos.repo yum/dnf files have been updated pointing at the right repositories (by default they enable stable, of course and you will have to switch to the testing repository for 12.2).

I'm making the assumption that if you are doing testing and are fedora-savvy, you likely know what I am talking about here (or simply read the docs at the site listed above -- it really isn't that complicated). If you are confused and want some help, poke me on discord (t0dd there as well).

....

And hello again to everyone. I took 5+ months off and am only slowly re-inserting myself back into the tech-scene. :)
Happy Dashing!
 

strophy

Administrator
Dash Core Team
Moderator
Dash Support Group
Feb 13, 2016
710
408
133
Anyway, I have a watchdog expired issue. I downloaded the sentinel folder, all other dependencies were previously installed, so I didn't redo any of that. should I have?
Hey, so I recently went through the steps of setting up a 12.2 masternode on testnet. It's pretty straightforward but you need to get sentinel from the 12.2.x branch and not master, as long as it is still pre-release. Follow my notes here: https://dashpay.atlassian.net/wiki/spaces/DOC/pages/118162190/Masternodes+under+testnet
 

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,861
1,854
1,283
Thank you @strophy I will follow :) I've installed this version after deleting existing sentinel directory. I will wait to see if it works, and I think it will :) Tests passed :) In the mean time, could your link be added to the OP so others can get in on this game? Thanks :)

All working now :D Yaaay!
 
Last edited:

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,861
1,854
1,283
Syncing takes a really long time. I have 8 connections, and it just seems really slothy. Is that just due to not having enough MNs or other wallets on the network?
 

qwizzie

Well-known Member
Aug 6, 2014
1,558
729
183
Syncing takes a really long time. I have 8 connections, and it just seems really slothy. Is that just due to not having enough MNs or other wallets on the network?
What are the results when you remove the blockchain, the peers.dat file and the banlist.dat file and let it sync from scratch ?

Edit : are we talking about blockchain syncing or the additional syncing ?
 

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,861
1,854
1,283
I deleted everything except wallet.dat and config files. I opened the wallet and it syncs up super fast until it gets to the last week or so, then it slows to a crawl. in fact it seems I'm stuck at 5 days

No, not quite stuck, it seems to be doing something, but very slowly

Wow, and it's laggy too. If I click on it in the task bar, it doesn't want to open up on the desktop (on top of chrome)

Well, anyways, I made a copy of the debug log if anyone wants to see it. It might just be slow? I seem to have connections (8) so not sure why it gets so laggy and slow (about 15 minutes for last 5 days)

BTW I do like the automatic unlocking for mixing only window that comes up when you say to mix. I'd usually wonder why after so many hours nothing happened, only to realize I forgot to unlock :p
 
Last edited:

qwizzie

Well-known Member
Aug 6, 2014
1,558
729
183
I deleted everything except wallet.dat and config files. I opened the wallet and it syncs up super fast until it gets to the last week or so, then it slows to a crawl. in fact it seems I'm stuck at 5 days

No, not quite stuck, it seems to be doing something, but very slowly

Wow, and it's laggy too. If I click on it in the task bar, it doesn't want to open up on the desktop (on top of chrome)

Well, anyways, I made a copy of the debug log if anyone wants to see it. It might just be slow? I seem to have connections (8) so not sure why it gets so laggy and slow (about 15 minutes for last 5 days)

BTW I do like the automatic unlocking for mixing only window that comes up when you say to mix. I'd usually wonder why after so many hours nothing happened, only to realize I forgot to unlock :p
Are you operating with a new wallet or are you operating with a pre-fork testnet wallet ?
 

codablock

Active Member
Core Developer
Mar 29, 2017
100
154
93
36
I deleted everything except wallet.dat and config files. I opened the wallet and it syncs up super fast until it gets to the last week or so, then it slows to a crawl. in fact it seems I'm stuck at 5 days

No, not quite stuck, it seems to be doing something, but very slowly

Wow, and it's laggy too. If I click on it in the task bar, it doesn't want to open up on the desktop (on top of chrome)
The behavior you see is most likely due to an optimization that was recently added and the large blocks that appear on testnet. The optimization (assumed valid block) skips some verification for all blocks which are the ancestors of a known valid block. The feature was backported from Bitcoin and the original announcement can be found here: https://bitcoincore.org/en/2017/03/08/release-0.14.0/#assumed-valid-blocks
This means, after this block you get "normal" processing times, the same you would have for all blocks without this feature. So it actually got overall faster, but feels slower close to syncing up :D

Then there are the large blocks you currently find in testnet. The point were it gets really slow is very likely the point were some big block testing was performed, so you're downloading and verifying >1mb blocks at this point in time.

Regarding the laggyness of the UI...that shouldn't happen of course. Gonna check this tomorrow.
 

AjM

Well-known Member
Foundation Member
Jun 23, 2014
1,335
571
283
Finland
Regarding the laggyness of the UI...that shouldn't happen of course. Gonna check this tomorrow.
I can confirm laggy GUI, it was unusable about 2-3 mins, when i last time tried it.
Never experienced so totally laggy ui.
Win7 x64.
 

demo

Well-known Member
Apr 23, 2016
3,114
263
153
Dash Address
XnpT2YQaYpyh7F9twM6EtDMn1TCDCEEgNX
Regarding the laggyness of the UI...that shouldn't happen of course. Gonna check this tomorrow.
Maybe the laggyness is due to the trafficgraphdatatests.cpp issue? TrafficGraphData returns a float, while QCOMPARE (before the fix) doesnt expect a float. So in qt older than 5 it does not compile at all, and in qt greater than 5 it takes long time to transliterate. Bandwidth graphs are often found to be laggy, so they have to be coded carefully.

More news. I just applied @UdjinM6 's fix, I compiled the code, and I entered the testnet. The gui is too laggy indeed. I will disable totally the bandwidth graph funtionality, recompile, and see if the laggyness is solved. Timeo Danaos et dona ferentes.
 
Last edited:
  • Like
Reactions: qwizzie

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,861
1,854
1,283
I still think over 15 minutes for 5 days is a bit long...? Mine is also on windows 10 64bit GUI version

Also, I just read in the thread made to get current MN owners to update sentinel due to crazy Europeans using commas (JK) and it said there that Flare said v12.2 won't have "watchdog expired" anymore. This is weird because I can't get my tMNs to stay on because they say "watchdog expired"

I dropped the ball last night and didn't change the conf file in sentinel last time I updated, so hopefully it will work in a few........ but still, it has "watchdog expired, so why would flare say there was no watchdog in 12.2?
 
Last edited:

t0dd

Active Member
Mar 21, 2016
150
132
103
keybase.io
Dash Address
XyxQq4qgp9B53QWQgSqSxJb4xddhzk5Zhh
I think Sentinel has independent version numbers... It was at start 1.0.0 and currently is at 1.0.1
so i suspect if Sentinel version change, it will change to 1.0.2

But please correct me if i'm wrong here...
Turns out you are wrong. Somewhat. Yes, Sentinel has independent versions, but there is no guidance as what the version scheme should be for master versus next branches. The sentinel in support of v12.2 is unversioned. It will not be 1.0.2. We know this only because 1.0.1 was just updated today with a hotfix to fix an issue and the version became 1.0.2. So... 1.0.2 is a supporting version of sentinel for 12.1.

I think I will just call it 1.1.0 and if it ends up being a continuation of the 1.0.x series... well... we'll have some communicating to do. :)
 
  • Like
Reactions: qwizzie

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,861
1,854
1,283
Are you operating with a new wallet or are you operating with a pre-fork testnet wallet ?
New wallet, all updated when this thread was opened. no old wallet.dat, nothing. brand new testnet3 folder

If there is no watchdog in 12.2 why do I have watchdog expired? I can't seem to get my MNs running for some reason???

3 rounds of mixing went smoothly to 100%

I have since upped it to 8 rounds and it's slow and sitting at idle a lot. Maybe I'm the only one mixing since last night?
 
Last edited:

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,861
1,854
1,283
I restarted desktop wallet and mixing began again

Also, MNs finally say enabled. Not sure what was wrong but it fixed itself??

Nope, my desktop wallet says watchdog expired again. And my server side wallets don't show any errors. not sure that they ever would have though?? Plus, I don't get any payouts.
 
Last edited:

demo

Well-known Member
Apr 23, 2016
3,114
263
153
Dash Address
XnpT2YQaYpyh7F9twM6EtDMn1TCDCEEgNX
I restarted desktop wallet and mixing began again

Also, MNs finally say enabled. Not sure what was wrong but it fixed itself??
You have some peers that are banned. Watch them in your qt wallet. Maybe the problem was fixed because of the ban of those peers.

By the way, when I click at the IP address of my peers I receive information about them. But no information appears for my banned peers, just their IP address. I would like to know more about my banned peers. And the reason why you have banned them. One omen is best, to defend your country.
 
Last edited:

demo

Well-known Member
Apr 23, 2016
3,114
263
153
Dash Address
XnpT2YQaYpyh7F9twM6EtDMn1TCDCEEgNX
Maybe the laggyness is due to the trafficgraphdatatests.cpp issue? TrafficGraphData returns a float, while QCOMPARE (before the fix) doesnt expect a float. So in qt older than 5 it does not compile at all, and in qt greater than 5 it takes long time to transliterate. Bandwidth graphs are often found to be laggy, so they have to be coded carefully.

More news. I just applied @UdjinM6 's fix, I compiled the code, and I entered the testnet. The gui is too laggy indeed. I will disable totally the bandwidth graph funtionality, recompile, and see if the laggyness is solved. Timeo Danaos et dona ferentes.
After the changes I made (disabling totally the bandwidth graph) my gui is not laggy any more.
I recommend everyone (@TanteStefana , @AjM, @codablock e.t.c) to do the same.
Who needs this damned bandwidth graph anyway?
 
Last edited:

demo

Well-known Member
Apr 23, 2016
3,114
263
153
Dash Address
XnpT2YQaYpyh7F9twM6EtDMn1TCDCEEgNX
After the changes I made (disabling totally the bandwidth graph) my gui is not laggy any more.
I recommend everyone (@TanteStefana , @AjM, @codablock e.t.c) to do the same.
Who needs this damned bandwidth graph anyway?
I cleared the .dashcore directory, and tried a fresh install of my wallet. The gui lags again. So disabling the bandwidth graph the way I did it, is neither the only reason, nor the main reason for the initial lag.

You can follow the discussion here, to see what I did in order to turn my gui superfast (by disabling a lot of gui notifications)

TO THE DEVELOPERS: ALL uiInterface NOTIFICATIONS SHOULD BE CHECKED THOUGHTFULLY, BECAUSE THEY MAY CAUSE GUI LAGS
You may also fix ./qt/clientmodel.cpp and ./ui_interface.h in order to prevent gui notifications in case the notification rate is huge. Do something similar to this and tune this, when appropriate. If I am about to name ONE responsible for the lag, I would say: CMasternodeSync::processTick

You may give me some tip for helping discovering the GUI-lag bug in:
Dash:XnpT2YQaYpyh7F9twM6EtDMn1TCDCEEgNX
Disclaimer: Whatever tip is given to me will be used in favor of the Dash community and against the greedy Dash generation of 2014-2016 (and the greedy masternode owners in general). Possible uses of the tips you are giving to me: Budget proposals to reduce the greed, coding things to reduce the greed (vote the numbers, universal dividend e.t.c), financing proof of individuality meetings, maybe also financing a Dash hard fork in case the greed remains.

I reported the issue here, and waiting for response.
 
Last edited:

demo

Well-known Member
Apr 23, 2016
3,114
263
153
Dash Address
XnpT2YQaYpyh7F9twM6EtDMn1TCDCEEgNX
I tried to run sentinel and I get the following message:

~/.dashcore/sentinel$ ps -efl|grep dashd
1 S src 2587 1 3 80 0 - 63753 hrtime 17:39 ? 00:00:41 ./dashd
0 S src 3904 1407 0 80 0 - 1286 pipe_w 17:57 pts/1 00:00:00 grep --color=auto dashd

~/.dashcore/sentinel$ venv/bin/python bin/sentinel.py
-342: non-JSON HTTP response with '401 Unauthorized' from server
Cannot connect to dashd. Please ensure dashd is running and the JSONRPC port is open to Sentinel.


What am I doing wrong? As long as dashd is obviously running, how do I open a JSONRPC port to sentinel?
 
Last edited:

demo

Well-known Member
Apr 23, 2016
3,114
263
153
Dash Address
XnpT2YQaYpyh7F9twM6EtDMn1TCDCEEgNX
Also, I have "watchdog expired" which just popped up. Not sure if it's something to be concerned about?
Thank you @strophy I will follow :) I've installed this version after deleting existing sentinel directory. I will wait to see if it works, and I think it will :) Tests passed :) In the mean time, could your link be added to the OP so others can get in on this game? Thanks :)

All working now :D Yaaay!
I also have the same "WATCHDOG_EXPIRE" issue in my tmasternode.
Could you please explain me, step by step, how you solved this?

here is what I did:

Code:
[email protected]:~/.dashcore$ ./dash-cli getinfo | grep version
  "version": 120200,
  "protocolversion": 70208,
  "walletversion": 61000,
[email protected]:~/.dashcore$ git clone -b core-v0.12.2.x https://github.com/dashpay/sentinel.git
Cloning into 'sentinel'...
remote: Counting objects: 3321, done.
remote: Compressing objects: 100% (13/13), done.
Receiving objects: 100% (3321/3321), 1.18 MiB | 345.00 KiB/s, done.
remote: Total 3321 (delta 9), reused 7 (delta 3), pack-reused 3305
Resolving deltas: 100% (2203/2203), done.
[email protected]:~/.dashcore$ cd sentinel
[email protected]:~/.dashcore/sentinel$ virtualenv ./venv
Using base prefix '/usr'
New python executable in /home/src/.dashcore/sentinel/venv/bin/python3
Also creating executable in /home/src/.dashcore/sentinel/venv/bin/python
Installing setuptools, pip, wheel...done.
[email protected]:~/.dashcore/sentinel$ cat requirements.txt
inflection==0.3.1
peewee==2.8.3
py==1.4.31
pycodestyle==2.2.0
pytest==3.0.1
python-bitcoinrpc==1.0
simplejson==3.8.2
[email protected]:~/.dashcore/sentinel$ ./venv/bin/pip install -r requirements.txt
Collecting inflection==0.3.1 (from -r requirements.txt (line 1))
Collecting peewee==2.8.3 (from -r requirements.txt (line 2))
Collecting py==1.4.31 (from -r requirements.txt (line 3))
  Using cached py-1.4.31-py2.py3-none-any.whl
Collecting pycodestyle==2.2.0 (from -r requirements.txt (line 4))
  Using cached pycodestyle-2.2.0-py2.py3-none-any.whl
Collecting pytest==3.0.1 (from -r requirements.txt (line 5))
  Using cached pytest-3.0.1-py2.py3-none-any.whl
Collecting python-bitcoinrpc==1.0 (from -r requirements.txt (line 6))
Collecting simplejson==3.8.2 (from -r requirements.txt (line 7))
Installing collected packages: inflection, peewee, py, pycodestyle, pytest, python-bitcoinrpc, simplejson
Successfully installed inflection-0.3.1 peewee-2.8.3 py-1.4.31 pycodestyle-2.2.0 pytest-3.0.1 python-bitcoinrpc-1.0 simplejson-3.8.2
[email protected]:~/.dashcore/sentinel$ crontab -l
# Edit this file to introduce tasks to be run by cron.
# Each task to run has to be defined through a single line
# indicating with different fields when the task will be run
# and what command to run for the task
# To define the time you can provide concrete values for
# minute (m), hour (h), day of month (dom), month (mon),
# and day of week (dow) or use '*' in these fields (for 'any').#
# Notice that tasks will be started based on the cron's system
# daemon's notion of time and timezones.
# Output of the crontab jobs (including errors) is sent through
# email to the user the crontab file belongs to (unless redirected).
# For example, you can run a backup of all your user accounts
# at 5 a.m every week with:
# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
# For more information see the manual pages of crontab(5) and cron(8)
# m h  dom mon dow   command

* * * * * cd /home/src/.dashcore/sentinel && ./venv/bin/python bin/sentinel.py >/dev/null 2>&1

[email protected]:~/.dashcore/sentinel$ cat sentinel.conf
# specify path to dash.conf or leave blank
# default is the same as DashCore
dash_conf=/home/src/.dashcore/dash.conf

# valid options are mainnet, testnet (default=mainnet)
# network=mainnet

network=testnet
rpcuser=demo
rpcpassword=aaaa
rpcallowip=127.0.0.1
rpcport=9998


# database connection details
db_name=database/sentinel.db
db_driver=sqlite

[email protected]:~/.dashcore/sentinel$ ./venv/bin/py.test ./test
==================================================================== test session starts ====================================================================
platform linux -- Python 3.5.3, pytest-3.0.1, py-1.4.31, pluggy-0.3.1
rootdir: /home/src/.dashcore/sentinel, inifile:
collected 22 items

test/integration/test_jsonrpc.py F
test/unit/test_dash_config.py .
test/unit/test_dashd_data_shims.py ..
test/unit/test_dashy_things.py ......
test/unit/test_models.py ..
test/unit/test_submit_command.py .
test/unit/models/test_proposals.py ....
test/unit/models/test_superblocks.py .....

========================================================================= FAILURES ==========================================================================
________________________________________________________________________ test_dashd _________________________________________________________________________

    def test_dashd():
        config_text = DashConfig.slurp_config_file(config.dash_conf)
        network = 'mainnet'
        is_testnet = False
        genesis_hash = u'00000ffd590b1485b3caadc19b22e6379c733355108f107a430458cdf3407ab6'
        for line in config_text.split("\n"):
            if line.startswith('testnet=1'):
                network = 'testnet'
                is_testnet = True
                genesis_hash = u'00000bafbc94add76cb75e2ec92894837288a481e5c005f6563d91623bf8bc2c'
 
        creds = DashConfig.get_rpc_creds(config_text, network)
        dashd = DashDaemon(**creds)
        assert dashd.rpc_command is not None
 
        assert hasattr(dashd, 'rpc_connection')
 
        # Dash testnet block 0 hash == 00000bafbc94add76cb75e2ec92894837288a481e5c005f6563d91623bf8bc2c
        # test commands without arguments
>       info = dashd.rpc_command('getinfo')

test/integration/test_jsonrpc.py:34:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
lib/dashd.py:42: in rpc_command
    return self.rpc_connection.__getattr__(params[0])(*params[1:])
venv/lib/python3.5/site-packages/bitcoinrpc/authproxy.py:139: in __call__
    response = self._get_response()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = <bitcoinrpc.authproxy.AuthServiceProxy object at 0xb67011ec>

    def _get_response(self):
        http_response = self.__conn.getresponse()
        if http_response is None:
            raise JSONRPCException({
                'code': -342, 'message': 'missing HTTP response from server'})
 
        content_type = http_response.getheader('Content-Type')
        if content_type != 'application/json':
            raise JSONRPCException({
>               'code': -342, 'message': 'non-JSON HTTP response with \'%i %s\' from server' % (http_response.status, http_response.reason)})
E           bitcoinrpc.authproxy.JSONRPCException: -342: non-JSON HTTP response with '401 Unauthorized' from server

venv/lib/python3.5/site-packages/bitcoinrpc/authproxy.py:187: JSONRPCException
============================================================ 1 failed, 21 passed in 4.74 seconds ============================================================
[email protected]:~/.dashcore$ ./dash-cli getinfo
{
  "version": 120200,
  "protocolversion": 70208,
  "walletversion": 61000,
  "balance": 6269.74098202,
  "privatesend_balance": 0.00000000,
  "blocks": 17922,
  "timeoffset": 0,
  "connections": 10,
  "proxy": "",
  "difficulty": 1.332960439336927,
  "testnet": true,
  "keypoololdest": 1509273923,
  "keypoolsize": 999,
  "paytxfee": 0.00000000,
  "relayfee": 0.00001000,
  "errors": ""
}
 
Last edited:
Status
Not open for further replies.