GUI tool for running Masternode with Trezor

Bertrand256

Active Member
Feb 13, 2017
244
291
123
Dash Address
XwZzf7yqYoUBnDFqE7r3zuNmpwKo1CYLMC
Doesn't start, but when I run it a second time, no gui appears but I can see two processes and then they disappear.
What is your Linux distribution/version?
Check if there is anything in the logfile (/home/<username>/DashMasternodeTool/logs/dmt.log)

I'm acting a little blindly because this error doesn't want to show up on my Ubuntu 16.04.
 

GrandMasterDash

Grizzled Member
Masternode Owner/Operator
Jul 12, 2015
2,909
1,110
1,183
What is your Linux distribution/version?
Check if there is anything in the logfile (/home/<username>/DashMasternodeTool/logs/dmt.log)

I'm acting a little blindly because this error doesn't want to show up on my Ubuntu 16.04.
It's not writing to the log file.

If I start it from a command line it says, "Failed to write all bytes for PyQt5.Qt.so".

Dist is manjaro / xfce (arch derivative)
 

Bertrand256

Active Member
Feb 13, 2017
244
291
123
Dash Address
XwZzf7yqYoUBnDFqE7r3zuNmpwKo1CYLMC
Dist is manjaro / xfce (arch derivative)
I have installed Manjaro (v17.0.6) but unfortunately the problem does not occur. It remains for me to force python upgrade to v3.6 and then compile binaries. We'll see.
 

GrandMasterDash

Grizzled Member
Masternode Owner/Operator
Jul 12, 2015
2,909
1,110
1,183
I have installed Manjaro (v17.0.6) but unfortunately the problem does not occur. It remains for me to force python upgrade to v3.6 and then compile binaries. We'll see.
The manjaro version number doesn't mean very much because it's a rolling a release; latest software with no need for re-installing OS. Did you update your system? Python on manjaro is version 3.6.2-1
 

Bertrand256

Active Member
Feb 13, 2017
244
291
123
Dash Address
XwZzf7yqYoUBnDFqE7r3zuNmpwKo1CYLMC
The manjaro version number doesn't mean very much because it's a rolling a release; latest software with no need for re-installing OS. Did you update your system? Python on manjaro is version 3.6.2-1
Yes, I've updated system - DMT works fine on it. Btw, it's a pretty cool distribution - I did not know it before.
If upgrading a python version on my development machine will not help, I will use Manjaro to compile binaries for you. As you wrote, it already has python 3.6, so it will not be a big deal.
 

Bertrand256

Active Member
Feb 13, 2017
244
291
123
Dash Address
XwZzf7yqYoUBnDFqE7r3zuNmpwKo1CYLMC
I assume that are two false postives, right?
Yes, those "generic" alarms are very misleading. I've checked the files with Norton Internet Security and they are ok.
 

Bertrand256

Active Member
Feb 13, 2017
244
291
123
Dash Address
XwZzf7yqYoUBnDFqE7r3zuNmpwKo1CYLMC
The manjaro version number doesn't mean very much because it's a rolling a release; latest software with no need for re-installing OS. Did you update your system? Python on manjaro is version 3.6.2-1
To my Keybase share I have uploaded binaries compiled on two systems: Ubuntu and Manjaro. Both are based on the newest Python - v3.6. Please, give me a feedback whether those files run with or without problems.
URL: https://keybase.pub/bertrand256/dash-masternode-tool/testing/DMT 0.9.12-linux/
 

GrandMasterDash

Grizzled Member
Masternode Owner/Operator
Jul 12, 2015
2,909
1,110
1,183

Bertrand256

Active Member
Feb 13, 2017
244
291
123
Dash Address
XwZzf7yqYoUBnDFqE7r3zuNmpwKo1CYLMC
Yep, works flawlessly.
Btw, the previous problem when it wasn't starting, I think it might of been because my tmpfs was full. Anyway, it's working now.
Ok, great that you located the cause. Thanks for the feedback.
 

GrandMasterDash

Grizzled Member
Masternode Owner/Operator
Jul 12, 2015
2,909
1,110
1,183
Just launched the Proposals window and got the error, "Problems encountered while processing some of the proposals data. Look into the log file for details."

The log file wasn't updated, it's still got an old entry "INFO | __init__ | App started"
 

Bertrand256

Active Member
Feb 13, 2017
244
291
123
Dash Address
XwZzf7yqYoUBnDFqE7r3zuNmpwKo1CYLMC
Just launched the Proposals window and got the error, "Problems encountered while processing some of the proposals data. Look into the log file for details."

The log file wasn't updated, it's still got an old entry "INFO | __init__ | App started"
When you close the application, the log should be flushed to disk (it's cached at runtime). I probably know what is the error: there is a new proposal with one of the fields with a different data type than expected. I have fixed this already and will release in a day or two along with other changes I'm working on.
 

GrandMasterDash

Grizzled Member
Masternode Owner/Operator
Jul 12, 2015
2,909
1,110
1,183
When you close the application, the log should be flushed to disk (it's cached at runtime). I probably know what is the error: there is a new proposal with one of the fields with a different data type than expected. I have fixed this already and will release in a day or two along with other changes I'm working on.
After closing the log file was unchanged.
 

GrandMasterDash

Grizzled Member
Masternode Owner/Operator
Jul 12, 2015
2,909
1,110
1,183
Suggestion: When fetching the status of a masternode, I was wondering if it would be nicer to display the queue position as a progress bar.
 

UdjinM6

Official Dash Dev
Dash Core Team
Moderator
May 20, 2014
3,639
3,537
1,183
@Bertrand256 pls update default DMT RPC nodes (alice and luna) to Dash Core 12.2 to allow DMT to start 12.2 masternodes. Thanks! :)
 

Bertrand256

Active Member
Feb 13, 2017
244
291
123
Dash Address
XwZzf7yqYoUBnDFqE7r3zuNmpwKo1CYLMC
@Bertrand256 pls update default DMT RPC nodes (alice and luna) to Dash Core 12.2 to allow DMT to start 12.2 masternodes. Thanks! :)
Hi, one of the RPC nodes upgraded, the second left as verion 12.1 for those who for some reason have to send "start masternode" message for their old (v12.1) masternodes.
That v12.1 RPC node has its TCP port changed, so DMT with default configuration will skip it while connecting.
 

Bertrand256

Active Member
Feb 13, 2017
244
291
123
Dash Address
XwZzf7yqYoUBnDFqE7r3zuNmpwKo1CYLMC
As you probably know, migration to v12.2 has already begun.
DMT is prepared for it, but there is a small nuance: "start masternode" message format requires passing the masternode's current protocol version into it. In the current DMT version (0.9.12) this value is taken from the RPC node DMT is connected to, not from the masternode. So, if you are going to send the "start masternode" message, you have to connect to a RPC node based on the same version as your masternode.

If you are going to start your v12.2 masternode with DMT you don't need to do anything unless you changed the default configuration, which should look as below:
upload_2017-11-8_9-54-51.png
Note: node "alice" will be skipped while connecting from DMT, as it currently runs v12.1 (it has public RPC port changed to invalidate that particular connection).


Those of you, who for some reason want to start old (v12.1) masternode with DMT+public RPC cfg, have to change the configuration to look like this:
upload_2017-11-8_9-55-47.png
In short: disable "luna" and "test" nodes and change "alice's" RPC port to 8081

Next DMT version (which I plan to release today) reads protocol version from the user's masternode, not from RPC node.
 
Last edited:
  • Like
Reactions: UdjinM6

Bertrand256

Active Member
Feb 13, 2017
244
291
123
Dash Address
XwZzf7yqYoUBnDFqE7r3zuNmpwKo1CYLMC
DashMasternodeTool v0.9.13 released
  • Full support for Ledger Nano S hardware wallets (including earnings transfer)
  • Consider the masternode protocol version when sending the 'start masternode' message
  • Fix: 'invalid password' message for RPC over SSH connection before even asking the user for a password
  • Fix of #2: reconnect froblem for RPC over SSH connection type
  • Fix of #3: AttributeError: 'int' object has no attribute 'replace'
Binaries: https://github.com/Bertrand256/dash-masternode-tool/releases/tag/v0.9.13
 

Cofresí

Member
Core Developer
Aug 22, 2014
86
82
58
121
Carribean
Hi Bertrand! I cannot open the new version v0.9.13 on macOS Sierra. The old version works.

Thank you!
 

Bertrand256

Active Member
Feb 13, 2017
244
291
123
Dash Address
XwZzf7yqYoUBnDFqE7r3zuNmpwKo1CYLMC
  • Like
Reactions: Cofresí

Vedran Yoweri

Active Member
Apr 29, 2015
334
152
113
Hi Bertrand,
issue starting 12.2 mn.
DMT 0.9.13 linux_x64 reports mn as protocol 70206, should be 70208.
tried via connected to local dash-qt 2.12 and alice on 8081, same result : watchdog_expired v.70206

any thoughts? thanks.
 

GrandMasterDash

Grizzled Member
Masternode Owner/Operator
Jul 12, 2015
2,909
1,110
1,183
Oh, dashninja says my protocol is 70206 (not 70208) even though I updated and enabled to 12.2.

DMT status doesn't seem to show me the protocol number (or I've missed it)
 

Bertrand256

Active Member
Feb 13, 2017
244
291
123
Dash Address
XwZzf7yqYoUBnDFqE7r3zuNmpwKo1CYLMC
Hi Bertrand,
issue starting 12.2 mn.
DMT 0.9.13 linux_x64 reports mn as protocol 70206, should be 70208.
tried via connected to local dash-qt 2.12 and alice on 8081, same result : watchdog_expired v.70206

any thoughts? thanks.
I would like to inform you and others about potential problems you may have with starting masternode using DMT 0.9.13. As I mentioned earlier, v0.9.13 reads the protocol version of your masternode from the Dash network.

The problem is that it reads this value from the RPC node to which it is connected, so if you try to start your mn just after its upgrade, that RPC node may still keep the old version of your mn, because of non-zero propagation time in the Dash network.

Therefore, to start masternode after its upgrade to v12.2 I recommend using DMT 0.9.12, that sets the protocol version to 70208 (if using the "standard" RPC configuration).
Sorry for the confusion, but I did not foresee this.
 
  • Like
Reactions: splawik21

Bertrand256

Active Member
Feb 13, 2017
244
291
123
Dash Address
XwZzf7yqYoUBnDFqE7r3zuNmpwKo1CYLMC
The problem is that it reads this value from the RPC node to which it is connected, so if you try to start your mn just after its upgrade, that RPC node may still keep the old version of your mn, because of non-zero propagation time in the Dash network.
Problem is temporary and will be resolved after propagation of the information on the Dash network, but I have to consider more reliable method of determining the version of the masternode protocol before next "big update" :)
 

GrandMasterDash

Grizzled Member
Masternode Owner/Operator
Jul 12, 2015
2,909
1,110
1,183
On the server, dash-cli getinfo says my version is 120105 and protocolversion is 70206, why? I had done the updates and started the masternode 16 hours ago.