Pages:
Author

Topic: Darknet DNET Masternode VPS support MP-Hosting now taking DNET as payment. - page 3. (Read 18853 times)

legendary
Activity: 1778
Merit: 1003
NodeMasters
Hi ok next ip Range will be
164.132.143.*

thanks
 Paul

Hi this is now done

Ill keep an eye on the servers  see if that helps



thanks

Paul

i had to fix my nodes with ip's 164.132.143.* again. vps have been restarted 8 hrs ago ->  some chains corrupted and even some wallet.dat's

was able to fix all expect 164.132.143.20.
i can not connect to any server from this node so i can not download a chain if i try to synch from scratch the node gets no connections ...
so this node is dead for now  Embarrassed

edit: it is not only a dns issue, can't connect to any ip either from this node please fix it thanks

HI fixed


thanks
Paul
legendary
Activity: 1148
Merit: 1001
Hi ok next ip Range will be
164.132.143.*

thanks
 Paul

Hi this is now done

Ill keep an eye on the servers  see if that helps



thanks

Paul

i had to fix my nodes with ip's 164.132.143.* again. vps have been restarted 8 hrs ago ->  some chains corrupted and even some wallet.dat's

was able to fix all expect 164.132.143.20.
i can not connect to any server from this node so i can not download a chain if i try to synch from scratch the node gets no connections ...
so this node is dead for now  Embarrassed

edit: it is not only a dns issue, can't connect to any ip either from this node please fix it thanks
legendary
Activity: 1778
Merit: 1003
NodeMasters
Hi ok next ip Range will be
164.132.143.*

thanks
 Paul

Hi this is now done

Ill keep an eye on the servers  see if that helps



thanks

Paul
legendary
Activity: 1778
Merit: 1003
NodeMasters
Hi ok next ip Range will be
164.132.143.*

thanks
 Paul
legendary
Activity: 1778
Merit: 1003
NodeMasters
Hi
ok the ip range 5.39.8.* will be the first to move 

i will get started  on them tonight 


thanks
Paul


ok ok the ip range 5.39.8.*  has now moved to the new server

thanks
Paul
legendary
Activity: 1778
Merit: 1003
NodeMasters
Hi
ok the ip range 5.39.8.* will be the first to move 

i will get started  on them tonight 


thanks
Paul
legendary
Activity: 1778
Merit: 1003
NodeMasters
Hi Guys
ok it looks like Wallets1 server in France rebooted at around 1am this morning
im looking at the logs now

i will start to move 1 IP block off this server  so the load is reduced  and move it on to the new SSD_2 server in France

Ill get this done as fast as i can
Any nodes  that have not been updated to the new version will get an update as well.

thanks
Paul
legendary
Activity: 1638
Merit: 1011
jakiman is back!
Approx 40% of my masternodes were affected but I've got them all back up and running again.

But yeah, that's a big chunk of my daily payments lost. Ah well.
legendary
Activity: 1778
Merit: 1003
NodeMasters
Hi guys
I should be hom in a few hours
I have been I Telford A&e all day

Thanks
Paul
hero member
Activity: 727
Merit: 501
Yeah. This is really not good when approx. 36% of my masternodes gets impacted like this.

As most of them had its blockchain corrupted, I need to resync them from my backup.

But the VPS's are super slow to sync etc as all are probably on the same physical server...
Paul, please, update the blockchain copy you have to accelerate things in this cases. If you download the current copy it results in corrupted blockchain.
Salute
legendary
Activity: 1638
Merit: 1011
jakiman is back!
Yeah. This is really not good when approx. 36% of my masternodes gets impacted like this.

As most of them had its blockchain corrupted, I need to resync them from my backup.

But the VPS's are super slow to sync etc as all are probably on the same physical server...
legendary
Activity: 1148
Merit: 1001
At least 30% of my masternodes went down or stopped syncing also. Sad

sounds familiar. i had to resynch 3 of 10 nodes after the restart.
i guess we have a ~30% chance of a corrupted blockchain if a unexpected vps restart happens  Wink
legendary
Activity: 1638
Merit: 1011
jakiman is back!
At least 30% of my masternodes went down or stopped syncing also. Sad
hero member
Activity: 727
Merit: 501
Both of my MN's in 192.99.217 has finally fallen. First of all as I told in the previous post due to corrupted blockchain, and the other one stucked in block 319325. I have already recovered first of it, and now I'm recovering the second one from scratch.

Just for your info, Paul.

Salute
hero member
Activity: 727
Merit: 501
10 of my vps have been restarted about 2 hrs ago and the nodes where missing
all with ip 164.132.143.xy

seems to work again now but i have to wait 24-48 until for next payouts because i had to start the nodes with controller wallet again

can you please check what happend - thanks

Something similar in my node in 192.99.217.xy. When I have checked it, MN was stopped and blockchain corrupted. I'm resyncing it to see if it starts to work again.

Salute
legendary
Activity: 1148
Merit: 1001
10 of my vps have been restarted about 2 hrs ago and the nodes where missing
all with ip 164.132.143.xy

seems to work again now but i have to wait 24-48 until for next payouts because i had to start the nodes with controller wallet again

can you please check what happend - thanks
hero member
Activity: 728
Merit: 500
legendary
Activity: 1778
Merit: 1003
NodeMasters
Safe to update? Will they need starting with controller again?

Yes you can update as its just a quick update no need to start in the wallet again

thanks
Paul
hero member
Activity: 728
Merit: 500
Safe to update? Will they need starting with controller again?
legendary
Activity: 1778
Merit: 1003
NodeMasters
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 2.0.1.0.2.0.3


This WILL NOT reset the blockchain




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/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]
[/quote]

next type this

Code:
 sh ./darknet-update.sh

you will see

Quote
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

 ./darknet-cli getinfo
{
    "version" : 2010203,
    "protocolversion" : 70701,
    "walletversion" : 61000,
    "balance" : 0.00000000,
    "obfuscation_balance" : 0.00000000,
    "blocks" : 292180,
    "timeoffset" : 0,
    "connections" : 1,
    "proxy" : "",
    "difficulty" : 108933.00935907,
    "testnet" : false,
    "keypoololdest" : 1471968023,
    "keypoolsize" : 1001,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00010000,
    "staking status" : "Staking Not Active",
    "errors" : ""
}


Upodate now Done



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

any problems let me know


thanks
Paul

Pages:
Jump to: