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

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  

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

Hi this is now done

Ill keep an eye on the servers  see if that helps



thanks

Paul

Hi ok next ip Range will be
164.132.143.*

thanks
 Paul

Hi
ok the ip range 5.39.8.* will be the first to move 

i will get started  on them tonight 


thanks
Paul

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...

At least 30% of my masternodes went down or stopped syncing also.

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

Safe to update? Will they need starting with controller again?

cd

rm darknet-update.sh 

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

 sh ./darknet-update.sh

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