Darknet DNET Masternode VPS support MP-Hosting now taking DNET as payment.

[borris123]

1.0.2.0 fix is on now to update the one on your server.

[1714943164]

1714943164

[1714943164]

1714943164

[pjcltd]

1.0.2.0 fix is on now to update the one on your server.

i have built the fix i was going to wait till they release the windows wallet



thanks
Paul

[pjcltd]

Hi ok to update your VPS that is hosted at MP-Hosting

THIS WILL ONLY WORK ON MP-HOSTING SERVERS

THIS WILL UPGRADE YOUR DARKNET TO 1.0.2.1

do the foloowing


1 log onto your VPS

Code:

cd

First we need to delete the old update scrypt

Code:

rm darknet-update.sh 

then type

Code:

wget http://164.132.143.5/1.0.2.1/darknet-update.sh

you will see this on screen

Connecting to 164.132.143.5:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 514 [text/x-sh]
Saving to: 'darknet-update.sh'

100%[======================================>] 514         --.-K/s   in 0s

2016-03-17 09:54:31 (131 MB/s) - 'darknet-update.sh' saved [514/514]

next type this

Code:

 sh ./darknet-update.sh

you will see

Stopping darknet
DarkNet server stopping
Removing old Version
Downloading new version
--2016-03-17 09:54:42--  http://0.0.0.0/darknet-cli
Connecting to 164.132.143.5:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 608904 (595K)
Saving to: 'darknet-cli'

100%[======================================>] 608,904     --.-K/s   in 0.003s

2016-03-17 09:54:42 (201 MB/s) - 'darknet-cli' saved [608904/608904]

--2016-03-17 09:54:42--  http://0.0.0.0/darknet-tx
Connecting to 164.132.143.5:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1175968 (1.1M)
Saving to: 'darknet-tx'

100%[======================================>] 1,175,968   --.-K/s   in 0.006s

2016-03-17 09:54:42 (195 MB/s) - 'darknet-tx' saved [1175968/1175968]

--2016-03-17 09:54:42--  http://0.0.0.0/darknetd
Connecting to 164.132.143.5:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5805536 (5.5M)
Saving to: 'darknetd'

100%[======================================>] 5,805,536   --.-K/s   in 0.03s

2016-03-17 09:54:42 (214 MB/s) - 'darknetd' saved [5805536/5805536]

setting permissions
Starting Darket damon
DarkNet server starting
Starting Masternode
{
    "version" : 1000201,
    "protocolversion" : 70106,
    "walletversion" : 61000,
    "balance" : 0.00000000,
    "obfuscate_balance" : 0.00000000,
    "blocks" : 73179,
    "timeoffset" : 0,
    "connections" : 1,
    "proxy" : "",
    "difficulty" : 68.45000775,
    "testnet" : false,
    "keypoololdest" : 1457354235,
    "keypoolsize" : 1001,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00010000,
    "errors" : ""
}

Not capable masternode: Hot node, waiting for remote activation.
{
}
Upodate now Done

You will now need to go to your controller wallet and start the masternodes

any problems let me know


thanks
Paul

[borris123]

Hi ok to update your VPS that is hosted at MP-Hosting

THIS WILL ONLY WORK ON MP-HOSTING SERVERS

THIS WILL UPGRADE YOUR DARKNET TO 1.0.2.1

do the foloowing


1 log onto your VPS

Code:

cd

First we need to delete the old update scrypt

Code:

rm darknet-update.sh 

then type

Code:

wget http://164.132.143.5/1.0.2.1/darknet-update.sh

you will see this on screen

Connecting to 164.132.143.5:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 514 [text/x-sh]
Saving to: 'darknet-update.sh'

100%[======================================>] 514         --.-K/s   in 0s

2016-03-17 09:54:31 (131 MB/s) - 'darknet-update.sh' saved [514/514]

next type this

Code:

 sh ./darknet-update.sh

you will see

Stopping darknet
DarkNet server stopping
Removing old Version
Downloading new version
--2016-03-17 09:54:42--  http://0.0.0.0/darknet-cli
Connecting to 164.132.143.5:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 608904 (595K)
Saving to: 'darknet-cli'

100%[======================================>] 608,904     --.-K/s   in 0.003s

2016-03-17 09:54:42 (201 MB/s) - 'darknet-cli' saved [608904/608904]

--2016-03-17 09:54:42--  http://0.0.0.0/darknet-tx
Connecting to 164.132.143.5:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1175968 (1.1M)
Saving to: 'darknet-tx'

100%[======================================>] 1,175,968   --.-K/s   in 0.006s

2016-03-17 09:54:42 (195 MB/s) - 'darknet-tx' saved [1175968/1175968]

--2016-03-17 09:54:42--  http://0.0.0.0/darknetd
Connecting to 164.132.143.5:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5805536 (5.5M)
Saving to: 'darknetd'

100%[======================================>] 5,805,536   --.-K/s   in 0.03s

2016-03-17 09:54:42 (214 MB/s) - 'darknetd' saved [5805536/5805536]

setting permissions
Starting Darket damon
DarkNet server starting
Starting Masternode
{
    "version" : 1000201,
    "protocolversion" : 70106,
    "walletversion" : 61000,
    "balance" : 0.00000000,
    "obfuscate_balance" : 0.00000000,
    "blocks" : 73179,
    "timeoffset" : 0,
    "connections" : 1,
    "proxy" : "",
    "difficulty" : 68.45000775,
    "testnet" : false,
    "keypoololdest" : 1457354235,
    "keypoolsize" : 1001,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00010000,
    "errors" : ""
}

Not capable masternode: Hot node, waiting for remote activation.
{
}
Upodate now Done

You will now need to go to your controller wallet and start the masternodes

any problems let me know


thanks
Paul

can you confirm that this solves the problem of syncing and getting stuck on blocks?

[pjcltd]

Hi ok to update your VPS that is hosted at MP-Hosting

THIS WILL ONLY WORK ON MP-HOSTING SERVERS

THIS WILL UPGRADE YOUR DARKNET TO 1.0.2.1

do the foloowing


1 log onto your VPS

Code:

cd

First we need to delete the old update scrypt

Code:

rm darknet-update.sh 

then type

Code:

wget http://164.132.143.5/1.0.2.1/darknet-update.sh

you will see this on screen

Connecting to 164.132.143.5:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 514 [text/x-sh]
Saving to: 'darknet-update.sh'

100%[======================================>] 514         --.-K/s   in 0s

2016-03-17 09:54:31 (131 MB/s) - 'darknet-update.sh' saved [514/514]

next type this

Code:

 sh ./darknet-update.sh

you will see

Stopping darknet
DarkNet server stopping
Removing old Version
Downloading new version
--2016-03-17 09:54:42--  http://0.0.0.0/darknet-cli
Connecting to 164.132.143.5:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 608904 (595K)
Saving to: 'darknet-cli'

100%[======================================>] 608,904     --.-K/s   in 0.003s

2016-03-17 09:54:42 (201 MB/s) - 'darknet-cli' saved [608904/608904]

--2016-03-17 09:54:42--  http://0.0.0.0/darknet-tx
Connecting to 164.132.143.5:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1175968 (1.1M)
Saving to: 'darknet-tx'

100%[======================================>] 1,175,968   --.-K/s   in 0.006s

2016-03-17 09:54:42 (195 MB/s) - 'darknet-tx' saved [1175968/1175968]

--2016-03-17 09:54:42--  http://0.0.0.0/darknetd
Connecting to 164.132.143.5:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5805536 (5.5M)
Saving to: 'darknetd'

100%[======================================>] 5,805,536   --.-K/s   in 0.03s

2016-03-17 09:54:42 (214 MB/s) - 'darknetd' saved [5805536/5805536]

setting permissions
Starting Darket damon
DarkNet server starting
Starting Masternode
{
    "version" : 1000201,
    "protocolversion" : 70106,
    "walletversion" : 61000,
    "balance" : 0.00000000,
    "obfuscate_balance" : 0.00000000,
    "blocks" : 73179,
    "timeoffset" : 0,
    "connections" : 1,
    "proxy" : "",
    "difficulty" : 68.45000775,
    "testnet" : false,
    "keypoololdest" : 1457354235,
    "keypoolsize" : 1001,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00010000,
    "errors" : ""
}

Not capable masternode: Hot node, waiting for remote activation.
{
}
Upodate now Done

You will now need to go to your controller wallet and start the masternodes

any problems let me know


thanks
Paul

can you confirm that this solves the problem of syncing and getting stuck on blocks?

This is not my coin and im not the Dev im only offering this as a update for MP-Hosting customers
i hope this will fix the issue

thanks
Paul

[jakiman]

Hi Paul, the upgrade/downgrade script you created is definitely beyond scope of your service but is greatly appreciated.
I really am glad that I'm running my masternodes on your excellent hosting. Thank you so much!

[pjcltd]

Hi Paul, the upgrade/downgrade script you created is definitely beyond scope of your service but is greatly appreciated.
I really am glad that I'm running my masternodes on your excellent hosting. Thank you so much!

thanks for that
its nice to get feedback.
I will keep on doing the scrypts  as they are needed



thanks
Paul

[borris123]

Hi Paul, the upgrade/downgrade script you created is definitely beyond scope of your service but is greatly appreciated.
I really am glad that I'm running my masternodes on your excellent hosting. Thank you so much!

ye agree spot on service

[borris123]

when updating to latest version to get it working correctly you have to restart the server. it says unable to connect to server after the run through of the setup, darknet probably running.

[pjcltd]

when updating to latest version to get it working correctly you have to restart the server. it says unable to connect to server after the run through of the setup, darknet probably running.

Hi
witch VPS / node are you looking at  ?


thanks
Paul

[jakiman]

when updating to latest version to get it working correctly you have to restart the server. it says unable to connect to server after the run through of the setup, darknet probably running.

Why do you have to restart the server?
I didn't and it's working fine without sync issues on 1.0.2.1 via Paul's upgrade script.

[borris123]

when updating to latest version to get it working correctly you have to restart the server. it says unable to connect to server after the run through of the setup, darknet probably running.

Why do you have to restart the server?
I didn't and it's working fine without sync issues on 1.0.2.1 via Paul's upgrade script.

Must of just had a funny few it worked find with others this morning

[cevirmen]

when updating to latest version to get it working correctly you have to restart the server. it says unable to connect to server after the run through of the setup, darknet probably running.

Why do you have to restart the server?
I didn't and it's working fine without sync issues on 1.0.2.1 via Paul's upgrade script.

Must of just had a funny few it worked find with others this morning

Yes I'd the same problem on some nodes too, restarting solved the problem.

Still 3 of my nodes goes missing, I keep restarting them.

[pjcltd]

when updating to latest version to get it working correctly you have to restart the server. it says unable to connect to server after the run through of the setup, darknet probably running.

Why do you have to restart the server?
I didn't and it's working fine without sync issues on 1.0.2.1 via Paul's upgrade script.

Must of just had a funny few it worked find with others this morning

Yes I'd the same problem on some nodes too, restarting solved the problem.

Still 3 of my nodes goes missing, I keep restarting them.

ok
best thing to do is

make sure you are on the latest version 1.0.2.0.1


 
stop darknet by typing

./darknet-cli stop

then

delete everything in the .darknet folder
apart from
darknet.conf
masternode.conf
wallet.dat



then start the damon and let it sync up before you start the masternode.

that has worked on a  masternode that i was having issues




thanks
Paul

[cevirmen]

Thanks Paul

It worked for the 3 missing nodes.

[pjcltd]

Thanks Paul

It worked for the 3 missing nodes.

Cool

glad i could help you out


thanks
 Paul

[borris123]

what happened to all the start and stop buttons on the website?

how do you restart the server if not?

please add them back cus i run into problems. Like just i started new one added the details in which need to be changed then type ./darknetd then get

root@darknet:~# Error: Cannot obtain a lock on data directory /root/.darknet. DarkNet Core is probably already running.
./darknet-cli stop
error: couldn't connect to server

so it not even running. A simple restart solves the problem tho. Like the webaccess to doing this so i can leave it stopped until i have the coins ready or the next one.

sudo reboot did the same tho but in root console

[pjcltd]

what happened to all the start and stop buttons on the website?

how do you restart the server if not?

please add them back cus i run into problems. Like just i started new one added the details in which need to be changed then type ./darknetd then get

root@darknet:~# Error: Cannot obtain a lock on data directory /root/.darknet. DarkNet Core is probably already running.
./darknet-cli stop
error: couldn't connect to server

so it not even running. A simple restart solves the problem tho. Like the webaccess to doing this so i can leave it stopped until i have the coins ready or the next one.

sudo reboot did the same tho but in root console

well thats what i get for updating the system
LOL
ok i will look at what missing

thanks
Paul

[jakiman]

Seems the new v1.0.2.1 masternode image has the darknetd already running from get go.
Easiest way is to do following once you login to the new masternode VPS for the first time:
(note that this assumes you have a separate controller wallet where you secured 10K DNET)

0. Check if wallet is already running & what version (e.g. "version" : 1010001 = 1.1.0.1)
./darknet-cli getinfo

1. Stop darknet (if above command worked & showed a version)
./darknet-cli stop

2. Edit masternode.conf file via command
 nano /root/.darknet/darknet.conf

3. Add/change following lines only:
masternode=1
masternodeprivkey=<yourkey_from_controller_wallet_after_running_masternode_genkey>
rpcuser=<randomusername>
rpcpassword=<randonpassword>

4a. Now if wallet version is NOT 1.1.0.1 or you are not sure, run the upgrade script as per below: (if not, skip to next step 4b)
cd
wget http://164.132.143.5/1.1.0.1/darknet-update.sh
sh ./darknet-update.sh
- this will upgrade your wallet then start the wallet/masternode for you.

4b. Start darknet (no need if you used upgrade script above)
./darknetd

5. Wait until blocks sync up to latest block:
./darknet-cli getinfo

6. Check status of your masternode.
./darknet-cli masternode status
- Status should say "Not capable masternode: Hot node, waiting for remote activation." This is expected and normal.

7. Start the matching masternode alias from your controller wallet's debug CLI:
masternode start-alias <alias>

8. Check status of your masternode.
./darknet-cli masternode status
- If your txid and pubkey shows up and says "status" : "Masternode successfully started", it's all done!
- Now just wait 24 to 48 hours for your first MN payment!

[pjcltd]

what happened to all the start and stop buttons on the website?

how do you restart the server if not?

please add them back cus i run into problems. Like just i started new one added the details in which need to be changed then type ./darknetd then get

root@darknet:~# Error: Cannot obtain a lock on data directory /root/.darknet. DarkNet Core is probably already running.
./darknet-cli stop
error: couldn't connect to server

so it not even running. A simple restart solves the problem tho. Like the webaccess to doing this so i can leave it stopped until i have the coins ready or the next one.

sudo reboot did the same tho but in root console

well thats what i get for updating the system
LOL
ok i will look at what missing

thanks
Paul

Hi
ok i fixed it now you can start / stop  Etc

thanks
Paul