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

[jakiman]

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

[1714945327]

1714945327

[1714945327]

1714945327

[1714945327]

1714945327

[berron]

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

[pjcltd]

Hi guys
I should be hom in a few hours
I have been I Telford A&e all day

Thanks
Paul

[jakiman]

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.

[pjcltd]

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

[pjcltd]

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

i will get started  on them tonight 


thanks
Paul

[pjcltd]

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

[pjcltd]

Hi ok next ip Range will be
164.132.143.*

thanks
 Paul

[pjcltd]

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

[DRPD]

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  

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

[pjcltd]

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  

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

[jakiman]

Thanks Paul. Got all of them up and running now.

[DRPD]

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  

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

thanks but 5 nodes more went missing with this ip range 5 minutes ago
164.132.143.19 not able to connect anywhere now too, was able to fix the rest

i hope you fixed the source of the problem  

[pjcltd]

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  

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

thanks but 5 nodes more went missing with this ip range 5 minutes ago
164.132.143.19 not able to connect anywhere now too, was able to fix the rest

i hope you fixed the source of the problem  

yep give me 20 mins
I'll get them fixed

[pjcltd]

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  

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

thanks but 5 nodes more went missing with this ip range 5 minutes ago
164.132.143.19 not able to connect anywhere now too, was able to fix the rest

i hope you fixed the source of the problem  

yep give me 20 mins
I'll get them fixed

done

[pjcltd]

Hi

ok last lot of ip Moves to this new server  is

164.132.189.*


thanks
Paul

[pjcltd]

Hi It looks like there been an issue with one of our servers  in France 

Dear Customer,

Our monitoring system has just detected a fault on our rack 46C04
The fault was noticed on 2016-10-02 22:54:08

Our team of technicians on site (operational 24/7), has been informed
of the fault and will intervene on your machine.

Please be aware that other interventions may currently be in progress and
an intervention lasts on average 30 minutes per machine.

We are therefore not able to give you more details on the starting time
of the intervention.

You can see a general display of the machines currently in fault and
in intervention across our network at the following address:

Your server is in rack 46C04

You will receive an email as soon as a technician takes charge of your
server. Meanwhile, you have can reboot it via your manager.


ill keep you all informed

thanks
Paul

[pjcltd]

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

THIS WILL ONLY WORK ON MP-HOSTING SERVERS
DO NOT USE ANY OTHER PRECOMPILED FILES
this will update you to 2.3.1 with a new blockchain from (03/10/2016 10:10am)

do the following


1 log onto your VPS

Code:

cd

Code:

 rm darknet-update.sh

Code:

wget http://164.132.143.5/darknet-update-clean.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-clean.sh'

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

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

next type this

Code:

 sh ./darknet-update-clean.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


./darknet-cli getinfo
{
    "version" : 2010300,
    "protocolversion" : 70705,
    "walletversion" : 61000,
    "balance" : 0.00000000,
    "obfuscation_balance" : 0.00000000,
    "blocks" : 324195,
    "timeoffset" : 0,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 152575.85193232,
    "testnet" : false,
    "keypoololdest" : 1475484108,
    "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

[kokokoin]

Thanks for update!

[jakiman]

Hi Paul, I'm getting Access Denied when going to http://my.mp-hosting.co.uk/clientarea.php