THAT'S IT!!! mninfo you are the MAN! You just saved this coin and definitely deserver a bounty from the dev team!
The trick is to delete all files in the data directory. Resync the wallet from scratch. It shows ENABLED!
Topic: ✅|ANN| 🌍DESIRE |NeoScrypt| |🔨MasterNodes🔨| - COIN OF YOUR DREAMS! - page 97. (Read 167500 times)
November 14, 2017, 08:37:49 PM
November 14, 2017, 08:37:03 PM
No luck with sentinel, followed peoples instructions. No coins for last 2 days. Frustrating, especially since I paid for the masternode hosting service, it looks like its just an ip address and you have to manage and do everything yourself.
https://cdn.shopify.com/s/files/1/0598/6757/files/capture38.jpg?6552870429517263903
https://cdn.shopify.com/s/files/1/0598/6757/files/capture38.jpg?6552870429517263903
You need to start the masternode as usually first! On the debug console: masternode start
Details here: https://github.com/lazyboozer/Desire_files/blob/master/Setup%20Desire%20MasterNodes.pdf
Once the masternode is running, then you might run sentinel (or simply leave it open as is now, but make sure to start the masternode!)
Oh, didn't know that, on linux you must manually start it each time.
November 14, 2017, 08:34:29 PM
No luck with sentinel, followed peoples instructions. No coins for last 2 days. Frustrating, especially since I paid for the masternode hosting service, it looks like its just an ip address and you have to manage and do everything yourself.
You need to start the masternode as usually first! On the debug console: masternode start
Details here: https://github.com/lazyboozer/Desire_files/blob/master/Setup%20Desire%20MasterNodes.pdf
Once the masternode is running, then you might run sentinel (or simply leave it open as is now, but make sure to start the masternode!)
November 14, 2017, 08:27:19 PM
No luck with sentinel, followed peoples instructions. No coins for last 2 days. Frustrating, especially since I paid for the masternode hosting service, it looks like its just an ip address and you have to manage and do everything yourself.
https://cdn.shopify.com/s/files/1/0598/6757/files/capture38.jpg?6552870429517263903
https://cdn.shopify.com/s/files/1/0598/6757/files/capture38.jpg?6552870429517263903
You need to start the masternode as usually first! On the debug console: masternode start
Details here: https://github.com/lazyboozer/Desire_files/blob/master/Setup%20Desire%20MasterNodes.pdf
Make sure "masternode status" says it is enabled (from the debug console) and "mnsync status" returns MASTERNODE_SYNC_WAITING or MASTERNODE_SYNC_FINISHED
Once the masternode is running, then you might run sentinel (or simply leave it open as is now, but make sure to start the masternode!)
November 14, 2017, 08:25:10 PM
No errors this time. MN status still shows WATCHDOG_EXPIRED though in the controlling wallet. Maybe I should wait a little. While I am waiting... What should I do if I have a masternode for another coin, i.e. VIVO on the same VPS that is having the same issue. How would I start the Sentinel for that coin too? Noone is replying in VIVO topic about this.
That's some progress
It's weird though that it doesn't show PRE_ENABLED :/ Have you ran through all the "masternode start" process? If so, let's wait for a few minutes and check if it changes (I might be sleeping by that time, if so I'll check in 7-9h)For VIVO, copy sentinel-win64.exe to another place and create a new sentinel.conf in that new place, this time make "desire_conf" point to the VIVO config file (still, name it desire_conf=xxx, as that is what it's expecting).
Once this is done, modify vivo.conf (or whatever it is called) to also contain all that data, but make sure to change "rpcport" to something else, whatever as long as it is greater than 1024, I'll use 9928 here
rpcuser=someuser
rpcpassword=somepass
server=1
rpcport=9928
rpcconnect=127.0.0.1
someuser and somepass need not be the same as before, you can/want to change them
I was reading through the dash code and it seems like before there was some governance message for the vote order of masternodes for it to update the watchdog. Now thas has changed to sentinel.
What block are you at right now?? Just to make sure it is not stuck (and thus not receving updates)
Could you upload a copy of your "debug.log" (inside desirecore) to somewhere? I believe it doesn't contain sensitive information, but if you want to be sure, simply check for lines with "CMasternode::Check" or "MNPING -- Masternode" or "CActiveMasternode::SendMasternodePing" and upload those.
OK, we got something!!!! I have several MNs and was applying your changed to all of them and one of them just changed ENABLED. For that particular MN I deleted all files in data dir exept for wallet and .conf files and started from scratch. Let me do the same for another MN and see if it is exactly the thing that fixed it.
November 14, 2017, 08:15:37 PM
No luck with sentinel, followed peoples instructions. No coins for last 2 days. Was running perfectly before. Frustrating, especially since I paid for the masternode hosting service which isnt what I thought it was.
I see only 1/4 or less of the other masternodes in the list say enabled, the rest are all watchdog or start again. No coins yet with it in watchdog, and then it goes to new start every couple hours.
I see only 1/4 or less of the other masternodes in the list say enabled, the rest are all watchdog or start again. No coins yet with it in watchdog, and then it goes to new start every couple hours.
November 14, 2017, 08:10:01 PM
No errors this time. MN status still shows WATCHDOG_EXPIRED though in the controlling wallet. Maybe I should wait a little. While I am waiting... What should I do if I have a masternode for another coin, i.e. VIVO on the same VPS that is having the same issue. How would I start the Sentinel for that coin too? Noone is replying in VIVO topic about this.
That's some progress
It's weird though that it doesn't show PRE_ENABLED :/ Have you ran through all the "masternode start" process? If so, let's wait for a few minutes and check if it changes (I might be sleeping by that time, if so I'll check in 7-9h)For VIVO, copy sentinel-win64.exe to another place and create a new sentinel.conf in that new place, this time make "desire_conf" point to the VIVO config file (still, name it desire_conf=xxx, as that is what it's expecting).
Once this is done, modify vivo.conf (or whatever it is called) to also contain all that data, but make sure to change "rpcport" to something else, whatever as long as it is greater than 1024, I'll use 9928 here
rpcuser=someuser
rpcpassword=somepass
server=1
rpcport=9928
rpcconnect=127.0.0.1
someuser and somepass need not be the same as before, you can/want to change them
I was reading through the dash code and it seems like before there was some governance message for the vote order of masternodes for it to update the watchdog. Now thas has changed to sentinel.
What block are you at right now?? Just to make sure it is not stuck (and thus not receving updates)
Could you upload a copy of your "debug.log" (inside desirecore) to somewhere? I believe it doesn't contain sensitive information, but if you want to be sure, simply check for lines with "CMasternode::Check" or "MNPING -- Masternode" or "CActiveMasternode::SendMasternodePing" and upload those.
November 14, 2017, 07:50:26 PM
No errors this time. MN status still shows WATCHDOG_EXPIRED though in the controlling wallet. Maybe I should wait a little. While I am waiting... What should I do if I have a masternode for another coin, i.e. VIVO on the same VPS that is having the same issue. How would I start the Sentinel for that coin too? Noone is replying in VIVO topic about this.
That's some progress
It's weird though that it doesn't show PRE_ENABLED :/ Have you ran through all the "masternode start" process? If so, let's wait for a few minutes and check if it changes (I might be sleeping by that time, if so I'll check in 7-9h)For VIVO, copy sentinel-win64.exe to another place and create a new sentinel.conf in that new place, this time make "desire_conf" point to the VIVO config file (still, name it desire_conf=xxx, as that is what it's expecting).
Once this is done, modify vivo.conf (or whatever it is called) to also contain all that data, but make sure to change "rpcport" to something else, whatever as long as it is greater than 1024, I'll use 9928 here
rpcuser=someuser
rpcpassword=somepass
server=1
rpcport=9928
rpcconnect=127.0.0.1
someuser and somepass need not be the same as before, you can/want to change them
November 14, 2017, 07:38:15 PM
No errors this time. MN status still shows WATCHDOG_EXPIRED though in the controlling wallet. Maybe I should wait a little. While I am waiting... What should I do if I have a masternode for another coin, i.e. VIVO on the same VPS that is having the same issue. How would I start the Sentinel for that coin too? Noone is replying in VIVO topic about this.
That's some progress
It's weird though that it doesn't show PRE_ENABLED :/ Have you ran through all the "masternode start" process? If so, let's wait for a few minutes and check if it changes (I might be sleeping by that time, if so I'll check in 7-9h)For VIVO, copy sentinel-win64.exe to another place and create a new sentinel.conf in that new place, this time make "desire_conf" point to the VIVO config file (still, name it desire_conf=xxx, as that is what it's expecting).
Once this is done, modify vivo.conf (or whatever it is called) to also contain all that data, but make sure to change "rpcport" to something else, whatever as long as it is greater than 1024, I'll use 9928 here
rpcuser=someuser
rpcpassword=somepass
server=1
rpcport=9928
rpcconnect=127.0.0.1
someuser and somepass need not be the same as before, you can/want to change them
November 14, 2017, 07:30:36 PM
Windows standalone Sentinel
So I have finally build it, please test it and consider it to be a beta, something might fail (I don't have desire in Windows).
Download: https://github.com/ZonnCash/sentinel/releases/tag/v1.1.0-win64
Virustotal (3/67): https://www.virustotal.com/es/file/3a65c0df1fb89607531d8c02bb2a3070f1c39f555944d118c67d8ee616be5b18/analysis/1510697796/
Use at your own risk, it has been compiled exactly as the Github repo says
How to
To make it point to your desire.conf, you have three options:
A) Create a file sentinel.conf in the same folder as the EXE with the following content:
desire_conf=C:\path\to\desire.conf
Start sentinel-win64.exe
B) From a console, execute the EXE by passing arguments
sentinel-win64.exe --config=C:\path\to\desire.conf
C) By creating a shortcut
1) Right click the sentinel-win64.exe, "Create Shortcut".
2) Right click the shortcut, Properties
3) Edit Target and, at the end, add a SPACE and then "--config=C:\path\to\desire.conf" INCLUDING the quotes "
Double click the shortcut to start sentinel.
Feedback
Either if it works or not for you, please get back to me in this post and tell us!
Using desire.conf: C:\Users\Administrator\AppData\Roaming\DesireCore\desire.confSo I have finally build it, please test it and consider it to be a beta, something might fail (I don't have desire in Windows).
Download: https://github.com/ZonnCash/sentinel/releases/tag/v1.1.0-win64
Virustotal (3/67): https://www.virustotal.com/es/file/3a65c0df1fb89607531d8c02bb2a3070f1c39f555944d118c67d8ee616be5b18/analysis/1510697796/
Use at your own risk, it has been compiled exactly as the Github repo says
How to
To make it point to your desire.conf, you have three options:
A) Create a file sentinel.conf in the same folder as the EXE with the following content:
desire_conf=C:\path\to\desire.conf
Start sentinel-win64.exe
B) From a console, execute the EXE by passing arguments
sentinel-win64.exe --config=C:\path\to\desire.conf
C) By creating a shortcut
1) Right click the sentinel-win64.exe, "Create Shortcut".
2) Right click the shortcut, Properties
3) Edit Target and, at the end, add a SPACE and then "--config=C:\path\to\desire.conf" INCLUDING the quotes "
Double click the shortcut to start sentinel.
Feedback
Either if it works or not for you, please get back to me in this post and tell us!
2017-11-15 01:50 Running sentinel
[Errno 10061] No connection could be made because the target machine actively re
fused it
Cannot connect to desired. Please ensure desired is running and the JSONRPC port
is open to Sentinel.
Is your rpcport the default one? Try running with the argument "--rcp-port=999", where 999 is your port.
Other than that, is sentinel and desired running on the same machine?
That error is telling that nothing is listening on that ip:port, so either desired is running on a different machine, port or not running at all
Does your desire.conf has any rpcuser and rpcpassword set? That might be it, simply write them, ie.
rpcuser=someuser
rpcpassword=somepassword
EDIT: Also, restart wallet after doing so! Otherwise they won't get loaded
Try to make them somewhat more difficult to guess. Other than that, before running sentinel-win64.exe make sure the wallet is runing
Please make sure the wallet is running 0.12.2.1. Can you try restarting the VPS? So we'll be sure everything is loaded and running as expected.
I'll try to setup a minimal wallet on windows and check if it works for me
Oookay! I've just setup a wallet on my Windows machine, you desire.conf should contain (at least):
rpcuser=someuser
rpcpassword=somepass
server=1
rpcport=9918
rpcconnect=127.0.0.1
After this, it will work
(I'll just repost the whole new thing, just in case someone sees the quotes, which are outdated)
November 14, 2017, 07:20:47 PM
Windows standalone Sentinel
So I have finally build it, please test it and consider it to be a beta, something might fail (I don't have desire in Windows).
Download: https://github.com/ZonnCash/sentinel/releases/tag/v1.1.0-win64
Virustotal (3/67): https://www.virustotal.com/es/file/3a65c0df1fb89607531d8c02bb2a3070f1c39f555944d118c67d8ee616be5b18/analysis/1510697796/
Use at your own risk, it has been compiled exactly as the Github repo says
How to
To make it point to your desire.conf, you have three options:
A) Create a file sentinel.conf in the same folder as the EXE with the following content:
desire_conf=C:\path\to\desire.conf
Start sentinel-win64.exe
B) From a console, execute the EXE by passing arguments
sentinel-win64.exe --config=C:\path\to\desire.conf
C) By creating a shortcut
1) Right click the sentinel-win64.exe, "Create Shortcut".
2) Right click the shortcut, Properties
3) Edit Target and, at the end, add a SPACE and then "--config=C:\path\to\desire.conf" INCLUDING the quotes "
Double click the shortcut to start sentinel.
Feedback
Either if it works or not for you, please get back to me in this post and tell us!
Using desire.conf: C:\Users\Administrator\AppData\Roaming\DesireCore\desire.confSo I have finally build it, please test it and consider it to be a beta, something might fail (I don't have desire in Windows).
Download: https://github.com/ZonnCash/sentinel/releases/tag/v1.1.0-win64
Virustotal (3/67): https://www.virustotal.com/es/file/3a65c0df1fb89607531d8c02bb2a3070f1c39f555944d118c67d8ee616be5b18/analysis/1510697796/
Use at your own risk, it has been compiled exactly as the Github repo says
How to
To make it point to your desire.conf, you have three options:
A) Create a file sentinel.conf in the same folder as the EXE with the following content:
desire_conf=C:\path\to\desire.conf
Start sentinel-win64.exe
B) From a console, execute the EXE by passing arguments
sentinel-win64.exe --config=C:\path\to\desire.conf
C) By creating a shortcut
1) Right click the sentinel-win64.exe, "Create Shortcut".
2) Right click the shortcut, Properties
3) Edit Target and, at the end, add a SPACE and then "--config=C:\path\to\desire.conf" INCLUDING the quotes "
Double click the shortcut to start sentinel.
Feedback
Either if it works or not for you, please get back to me in this post and tell us!
2017-11-15 01:50 Running sentinel
[Errno 10061] No connection could be made because the target machine actively re
fused it
Cannot connect to desired. Please ensure desired is running and the JSONRPC port
is open to Sentinel.
Is your rpcport the default one? Try running with the argument "--rcp-port=999", where 999 is your port.
Other than that, is sentinel and desired running on the same machine?
That error is telling that nothing is listening on that ip:port, so either desired is running on a different machine, port or not running at all
Does your desire.conf has any rpcuser and rpcpassword set? That might be it, simply write them, ie.
rpcuser=someuser
rpcpassword=somepassword
EDIT: Also, restart wallet after doing so! Otherwise they won't get loaded
Try to make them somewhat more difficult to guess. Other than that, before running sentinel-win64.exe make sure the wallet is runing
Please make sure the wallet is running 0.12.2.1. Can you try restarting the VPS? So we'll be sure everything is loaded and running as expected.
I'll try to setup a minimal wallet on windows and check if it works for me
Oookay! I've just setup a wallet on my Windows machine, you desire.conf should contain (at least):
rpcuser=someuser
rpcpassword=somepass
server=1
rpcport=9918
rpcconnect=127.0.0.1
After this, it will work
(I'll just repost the whole new thing, just in case someone sees the quotes, which are outdated)
November 14, 2017, 07:14:04 PM
First time coming across this thread. I'm interested because I want to try out mining, with CPU, to learn more about it. Has anyone checked out the source code, make sure it doesn't have any secret code?
November 14, 2017, 07:06:54 PM
Windows standalone Sentinel
So I have finally build it, please test it and consider it to be a beta, something might fail (I don't have desire in Windows).
Download: https://github.com/ZonnCash/sentinel/releases/tag/v1.1.0-win64
Virustotal (3/67): https://www.virustotal.com/es/file/3a65c0df1fb89607531d8c02bb2a3070f1c39f555944d118c67d8ee616be5b18/analysis/1510697796/
Use at your own risk, it has been compiled exactly as the Github repo says
How to
To make it point to your desire.conf, you have three options:
A) Create a file sentinel.conf in the same folder as the EXE with the following content:
desire_conf=C:\path\to\desire.conf
Start sentinel-win64.exe
B) From a console, execute the EXE by passing arguments
sentinel-win64.exe --config=C:\path\to\desire.conf
C) By creating a shortcut
1) Right click the sentinel-win64.exe, "Create Shortcut".
2) Right click the shortcut, Properties
3) Edit Target and, at the end, add a SPACE and then "--config=C:\path\to\desire.conf" INCLUDING the quotes "
Double click the shortcut to start sentinel.
Feedback
Either if it works or not for you, please get back to me in this post and tell us!
Using desire.conf: C:\Users\Administrator\AppData\Roaming\DesireCore\desire.confSo I have finally build it, please test it and consider it to be a beta, something might fail (I don't have desire in Windows).
Download: https://github.com/ZonnCash/sentinel/releases/tag/v1.1.0-win64
Virustotal (3/67): https://www.virustotal.com/es/file/3a65c0df1fb89607531d8c02bb2a3070f1c39f555944d118c67d8ee616be5b18/analysis/1510697796/
Use at your own risk, it has been compiled exactly as the Github repo says
How to
To make it point to your desire.conf, you have three options:
A) Create a file sentinel.conf in the same folder as the EXE with the following content:
desire_conf=C:\path\to\desire.conf
Start sentinel-win64.exe
B) From a console, execute the EXE by passing arguments
sentinel-win64.exe --config=C:\path\to\desire.conf
C) By creating a shortcut
1) Right click the sentinel-win64.exe, "Create Shortcut".
2) Right click the shortcut, Properties
3) Edit Target and, at the end, add a SPACE and then "--config=C:\path\to\desire.conf" INCLUDING the quotes "
Double click the shortcut to start sentinel.
Feedback
Either if it works or not for you, please get back to me in this post and tell us!
2017-11-15 01:50 Running sentinel
[Errno 10061] No connection could be made because the target machine actively re
fused it
Cannot connect to desired. Please ensure desired is running and the JSONRPC port
is open to Sentinel.
Is your rpcport the default one? Try running with the argument "--rcp-port=999", where 999 is your port.
Other than that, is sentinel and desired running on the same machine?
That error is telling that nothing is listening on that ip:port, so either desired is running on a different machine, port or not running at all
Does your desire.conf has any rpcuser and rpcpassword set? That might be it, simply write them, ie.
rpcuser=someuser
rpcpassword=somepassword
EDIT: Also, restart wallet after doing so! Otherwise they won't get loaded
Try to make them somewhat more difficult to guess. Other than that, before running sentinel-win64.exe make sure the wallet is runing
Please make sure the wallet is running 0.12.2.1. Can you try restarting the VPS? So we'll be sure everything is loaded and running as expected.
I'll try to setup a minimal wallet on windows and check if it works for me
November 14, 2017, 07:04:39 PM
Windows standalone Sentinel
So I have finally build it, please test it and consider it to be a beta, something might fail (I don't have desire in Windows).
Download: https://github.com/ZonnCash/sentinel/releases/tag/v1.1.0-win64
Virustotal (3/67): https://www.virustotal.com/es/file/3a65c0df1fb89607531d8c02bb2a3070f1c39f555944d118c67d8ee616be5b18/analysis/1510697796/
Use at your own risk, it has been compiled exactly as the Github repo says
How to
To make it point to your desire.conf, you have three options:
A) Create a file sentinel.conf in the same folder as the EXE with the following content:
desire_conf=C:\path\to\desire.conf
Start sentinel-win64.exe
B) From a console, execute the EXE by passing arguments
sentinel-win64.exe --config=C:\path\to\desire.conf
C) By creating a shortcut
1) Right click the sentinel-win64.exe, "Create Shortcut".
2) Right click the shortcut, Properties
3) Edit Target and, at the end, add a SPACE and then "--config=C:\path\to\desire.conf" INCLUDING the quotes "
Double click the shortcut to start sentinel.
Feedback
Either if it works or not for you, please get back to me in this post and tell us!
Using desire.conf: C:\Users\Administrator\AppData\Roaming\DesireCore\desire.confSo I have finally build it, please test it and consider it to be a beta, something might fail (I don't have desire in Windows).
Download: https://github.com/ZonnCash/sentinel/releases/tag/v1.1.0-win64
Virustotal (3/67): https://www.virustotal.com/es/file/3a65c0df1fb89607531d8c02bb2a3070f1c39f555944d118c67d8ee616be5b18/analysis/1510697796/
Use at your own risk, it has been compiled exactly as the Github repo says
How to
To make it point to your desire.conf, you have three options:
A) Create a file sentinel.conf in the same folder as the EXE with the following content:
desire_conf=C:\path\to\desire.conf
Start sentinel-win64.exe
B) From a console, execute the EXE by passing arguments
sentinel-win64.exe --config=C:\path\to\desire.conf
C) By creating a shortcut
1) Right click the sentinel-win64.exe, "Create Shortcut".
2) Right click the shortcut, Properties
3) Edit Target and, at the end, add a SPACE and then "--config=C:\path\to\desire.conf" INCLUDING the quotes "
Double click the shortcut to start sentinel.
Feedback
Either if it works or not for you, please get back to me in this post and tell us!
2017-11-15 01:50 Running sentinel
[Errno 10061] No connection could be made because the target machine actively re
fused it
Cannot connect to desired. Please ensure desired is running and the JSONRPC port
is open to Sentinel.
Is your rpcport the default one? Try running with the argument "--rcp-port=999", where 999 is your port.
Other than that, is sentinel and desired running on the same machine?
That error is telling that nothing is listening on that ip:port, so either desired is running on a different machine, port or not running at all
Does your desire.conf has any rpcuser and rpcpassword set? That might be it, simply write them, ie.
rpcuser=someuser
rpcpassword=somepassword
EDIT: Also, restart wallet after doing so! Otherwise they won't get loaded
Try to make them somewhat more difficult to guess. Other than that, before running sentinel-win64.exe make sure the wallet is runing
Please make sure the wallet is running 0.12.2.1. Can you try restarting the VPS? So we'll be sure everything is loaded and running as expected.
I'll try to setup a minimal wallet on windows and check if it works for me
November 14, 2017, 06:57:49 PM
Windows standalone Sentinel
So I have finally build it, please test it and consider it to be a beta, something might fail (I don't have desire in Windows).
Download: https://github.com/ZonnCash/sentinel/releases/tag/v1.1.0-win64
Virustotal (3/67): https://www.virustotal.com/es/file/3a65c0df1fb89607531d8c02bb2a3070f1c39f555944d118c67d8ee616be5b18/analysis/1510697796/
Use at your own risk, it has been compiled exactly as the Github repo says
How to
To make it point to your desire.conf, you have three options:
A) Create a file sentinel.conf in the same folder as the EXE with the following content:
desire_conf=C:\path\to\desire.conf
Start sentinel-win64.exe
B) From a console, execute the EXE by passing arguments
sentinel-win64.exe --config=C:\path\to\desire.conf
C) By creating a shortcut
1) Right click the sentinel-win64.exe, "Create Shortcut".
2) Right click the shortcut, Properties
3) Edit Target and, at the end, add a SPACE and then "--config=C:\path\to\desire.conf" INCLUDING the quotes "
Double click the shortcut to start sentinel.
Feedback
Either if it works or not for you, please get back to me in this post and tell us!
Using desire.conf: C:\Users\Administrator\AppData\Roaming\DesireCore\desire.confSo I have finally build it, please test it and consider it to be a beta, something might fail (I don't have desire in Windows).
Download: https://github.com/ZonnCash/sentinel/releases/tag/v1.1.0-win64
Virustotal (3/67): https://www.virustotal.com/es/file/3a65c0df1fb89607531d8c02bb2a3070f1c39f555944d118c67d8ee616be5b18/analysis/1510697796/
Use at your own risk, it has been compiled exactly as the Github repo says
How to
To make it point to your desire.conf, you have three options:
A) Create a file sentinel.conf in the same folder as the EXE with the following content:
desire_conf=C:\path\to\desire.conf
Start sentinel-win64.exe
B) From a console, execute the EXE by passing arguments
sentinel-win64.exe --config=C:\path\to\desire.conf
C) By creating a shortcut
1) Right click the sentinel-win64.exe, "Create Shortcut".
2) Right click the shortcut, Properties
3) Edit Target and, at the end, add a SPACE and then "--config=C:\path\to\desire.conf" INCLUDING the quotes "
Double click the shortcut to start sentinel.
Feedback
Either if it works or not for you, please get back to me in this post and tell us!
2017-11-15 01:50 Running sentinel
[Errno 10061] No connection could be made because the target machine actively re
fused it
Cannot connect to desired. Please ensure desired is running and the JSONRPC port
is open to Sentinel.
Is your rpcport the default one? Try running with the argument "--rcp-port=999", where 999 is your port.
Other than that, is sentinel and desired running on the same machine?
That error is telling that nothing is listening on that ip:port, so either desired is running on a different machine, port or not running at all
Does your desire.conf has any rpcuser and rpcpassword set? That might be it, simply write them, ie.
rpcuser=someuser
rpcpassword=somepassword
EDIT: Also, restart wallet after doing so! Otherwise they won't get loaded
Try to make them somewhat more difficult to guess. Other than that, before running sentinel-win64.exe make sure the wallet is runing
November 14, 2017, 06:12:19 PM
Windows standalone Sentinel
So I have finally build it, please test it and consider it to be a beta, something might fail (I don't have desire in Windows).
Download: https://github.com/ZonnCash/sentinel/releases/tag/v1.1.0-win64
Virustotal (3/67): https://www.virustotal.com/es/file/3a65c0df1fb89607531d8c02bb2a3070f1c39f555944d118c67d8ee616be5b18/analysis/1510697796/
Use at your own risk, it has been compiled exactly as the Github repo says
How to
To make it point to your desire.conf, you have three options:
A) Create a file sentinel.conf in the same folder as the EXE with the following content:
desire_conf=C:\path\to\desire.conf
Start sentinel-win64.exe
B) From a console, execute the EXE by passing arguments
sentinel-win64.exe --config=C:\path\to\desire.conf
C) By creating a shortcut
1) Right click the sentinel-win64.exe, "Create Shortcut".
2) Right click the shortcut, Properties
3) Edit Target and, at the end, add a SPACE and then "--config=C:\path\to\desire.conf" INCLUDING the quotes "
Double click the shortcut to start sentinel.
Feedback
Either if it works or not for you, please get back to me in this post and tell us!
Using desire.conf: C:\Users\Administrator\AppData\Roaming\DesireCore\desire.confSo I have finally build it, please test it and consider it to be a beta, something might fail (I don't have desire in Windows).
Download: https://github.com/ZonnCash/sentinel/releases/tag/v1.1.0-win64
Virustotal (3/67): https://www.virustotal.com/es/file/3a65c0df1fb89607531d8c02bb2a3070f1c39f555944d118c67d8ee616be5b18/analysis/1510697796/
Use at your own risk, it has been compiled exactly as the Github repo says
How to
To make it point to your desire.conf, you have three options:
A) Create a file sentinel.conf in the same folder as the EXE with the following content:
desire_conf=C:\path\to\desire.conf
Start sentinel-win64.exe
B) From a console, execute the EXE by passing arguments
sentinel-win64.exe --config=C:\path\to\desire.conf
C) By creating a shortcut
1) Right click the sentinel-win64.exe, "Create Shortcut".
2) Right click the shortcut, Properties
3) Edit Target and, at the end, add a SPACE and then "--config=C:\path\to\desire.conf" INCLUDING the quotes "
Double click the shortcut to start sentinel.
Feedback
Either if it works or not for you, please get back to me in this post and tell us!
2017-11-15 01:50 Running sentinel
[Errno 10061] No connection could be made because the target machine actively re
fused it
Cannot connect to desired. Please ensure desired is running and the JSONRPC port
is open to Sentinel.
Is your rpcport the default one? Try running with the argument "--rcp-port=999", where 999 is your port.
Other than that, is sentinel and desired running on the same machine?
That error is telling that nothing is listening on that ip:port, so either desired is running on a different machine, port or not running at all
Does your desire.conf has any rpcuser and rpcpassword set? That might be it, simply write them, ie.
rpcuser=someuser
rpcpassword=somepassword
EDIT: Also, restart wallet after doing so! Otherwise they won't get loaded
Try to make them somewhat more difficult to guess. Other than that, before running sentinel-win64.exe make sure the wallet is runing
November 14, 2017, 06:06:19 PM
Could someone test this on linux? (x64)
https://github.com/ZonnCash/sentinel/releases/tag/linux
Pass an argument --config=/path/to/desire.conf
Let's see if this works! I'll compile Windows at home
https://github.com/ZonnCash/sentinel/releases/tag/linux
Pass an argument --config=/path/to/desire.conf
Let's see if this works! I'll compile Windows at home
I'm not good at linux but somehow I tried. Result as follows.
root@VPS:~/sentinel# ./linux-main --config=/root/.desirecore/desire.conf
Traceback (most recent call last):
File "main.py", line 2, in
ImportError: cannot import name config
[4198] Failed to execute script main
Maybe I missed important things. I just downloaded file and set permission and run.
Nope, that was absolutely my fault. There were some errors that I fixed on the windows build but missed to update the linux one.
Please test the build here:
https://github.com/ZonnCash/sentinel/releases/tag/v1.1.0-win64
November 14, 2017, 06:04:38 PM
Windows standalone Sentinel
So I have finally build it, please test it and consider it to be a beta, something might fail (I don't have desire in Windows).
Download: https://github.com/ZonnCash/sentinel/releases/tag/v1.1.0-win64
Virustotal (3/67): https://www.virustotal.com/es/file/3a65c0df1fb89607531d8c02bb2a3070f1c39f555944d118c67d8ee616be5b18/analysis/1510697796/
Use at your own risk, it has been compiled exactly as the Github repo says
How to
To make it point to your desire.conf, you have three options:
A) Create a file sentinel.conf in the same folder as the EXE with the following content:
desire_conf=C:\path\to\desire.conf
Start sentinel-win64.exe
B) From a console, execute the EXE by passing arguments
sentinel-win64.exe --config=C:\path\to\desire.conf
C) By creating a shortcut
1) Right click the sentinel-win64.exe, "Create Shortcut".
2) Right click the shortcut, Properties
3) Edit Target and, at the end, add a SPACE and then "--config=C:\path\to\desire.conf" INCLUDING the quotes "
Double click the shortcut to start sentinel.
Feedback
Either if it works or not for you, please get back to me in this post and tell us!
Using desire.conf: C:\Users\Administrator\AppData\Roaming\DesireCore\desire.confSo I have finally build it, please test it and consider it to be a beta, something might fail (I don't have desire in Windows).
Download: https://github.com/ZonnCash/sentinel/releases/tag/v1.1.0-win64
Virustotal (3/67): https://www.virustotal.com/es/file/3a65c0df1fb89607531d8c02bb2a3070f1c39f555944d118c67d8ee616be5b18/analysis/1510697796/
Use at your own risk, it has been compiled exactly as the Github repo says
How to
To make it point to your desire.conf, you have three options:
A) Create a file sentinel.conf in the same folder as the EXE with the following content:
desire_conf=C:\path\to\desire.conf
Start sentinel-win64.exe
B) From a console, execute the EXE by passing arguments
sentinel-win64.exe --config=C:\path\to\desire.conf
C) By creating a shortcut
1) Right click the sentinel-win64.exe, "Create Shortcut".
2) Right click the shortcut, Properties
3) Edit Target and, at the end, add a SPACE and then "--config=C:\path\to\desire.conf" INCLUDING the quotes "
Double click the shortcut to start sentinel.
Feedback
Either if it works or not for you, please get back to me in this post and tell us!
2017-11-15 01:50 Running sentinel
[Errno 10061] No connection could be made because the target machine actively re
fused it
Cannot connect to desired. Please ensure desired is running and the JSONRPC port
is open to Sentinel.
Is your rpcport the default one? Try running with the argument "--rcp-port=999", where 999 is your port.
Other than that, is sentinel and desired running on the same machine?
That error is telling that nothing is listening on that ip:port, so either desired is running on a different machine, port or not running at all
November 14, 2017, 05:58:50 PM
Windows standalone Sentinel
So I have finally build it, please test it and consider it to be a beta, something might fail (I don't have desire in Windows).
Download: https://github.com/ZonnCash/sentinel/releases/tag/v1.1.0-win64
Virustotal (3/67): https://www.virustotal.com/es/file/3a65c0df1fb89607531d8c02bb2a3070f1c39f555944d118c67d8ee616be5b18/analysis/1510697796/
Use at your own risk, it has been compiled exactly as the Github repo says
How to
To make it point to your desire.conf, you have three options:
A) Create a file sentinel.conf in the same folder as the EXE with the following content:
desire_conf=C:\path\to\desire.conf
Start sentinel-win64.exe
B) From a console, execute the EXE by passing arguments
sentinel-win64.exe --config=C:\path\to\desire.conf
C) By creating a shortcut
1) Right click the sentinel-win64.exe, "Create Shortcut".
2) Right click the shortcut, Properties
3) Edit Target and, at the end, add a SPACE and then "--config=C:\path\to\desire.conf" INCLUDING the quotes "
Double click the shortcut to start sentinel.
Feedback
Either if it works or not for you, please get back to me in this post and tell us!
Using desire.conf: C:\Users\Administrator\AppData\Roaming\DesireCore\desire.confSo I have finally build it, please test it and consider it to be a beta, something might fail (I don't have desire in Windows).
Download: https://github.com/ZonnCash/sentinel/releases/tag/v1.1.0-win64
Virustotal (3/67): https://www.virustotal.com/es/file/3a65c0df1fb89607531d8c02bb2a3070f1c39f555944d118c67d8ee616be5b18/analysis/1510697796/
Use at your own risk, it has been compiled exactly as the Github repo says
How to
To make it point to your desire.conf, you have three options:
A) Create a file sentinel.conf in the same folder as the EXE with the following content:
desire_conf=C:\path\to\desire.conf
Start sentinel-win64.exe
B) From a console, execute the EXE by passing arguments
sentinel-win64.exe --config=C:\path\to\desire.conf
C) By creating a shortcut
1) Right click the sentinel-win64.exe, "Create Shortcut".
2) Right click the shortcut, Properties
3) Edit Target and, at the end, add a SPACE and then "--config=C:\path\to\desire.conf" INCLUDING the quotes "
Double click the shortcut to start sentinel.
Feedback
Either if it works or not for you, please get back to me in this post and tell us!
2017-11-15 01:50 Running sentinel
[Errno 10061] No connection could be made because the target machine actively re
fused it
Cannot connect to desired. Please ensure desired is running and the JSONRPC port
is open to Sentinel.
Is your rpcport the default one? Try running with the argument "--rcp-port=999", where 999 is your port.
Other than that, is sentinel and desired running on the same machine?
That error is telling that nothing is listening on that ip:port, so either desired is running on a different machine, port or not running at all
November 14, 2017, 05:57:20 PM
Could someone test this on linux? (x64)
https://github.com/ZonnCash/sentinel/releases/tag/linux
Pass an argument --config=/path/to/desire.conf
Let's see if this works! I'll compile Windows at home
https://github.com/ZonnCash/sentinel/releases/tag/linux
Pass an argument --config=/path/to/desire.conf
Let's see if this works! I'll compile Windows at home
I'm not good at linux but somehow I tried. Result as follows.
root@VPS:~/sentinel# ./linux-main --config=/root/.desirecore/desire.conf
Traceback (most recent call last):
File "main.py", line 2, in
ImportError: cannot import name config
[4198] Failed to execute script main
Maybe I missed important things. I just downloaded file and set permission and run.
Jump to: