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

[pjcltd]

I noticed that whole heap of my VPS seemed to have crashed sometime today.
All of them ended up with corrupted blockchains. Syncing them back now.
I better create a backup of the blockchain so I can get them syncing faster...

can you let me know the ip's please

[1714953131]

1714953131

[B1tUnl0ck3r]

Hey! I just discovered this post. It sound really great. How much does it cost in DNET? I didn't find it in the OP. thanks in advance.

Hi
I'm not at home to give you the exact amount but what ever $ rate is in DNET


thanks
Paul

Okay nice. What's your reference price for Dnet in $, please?

[pjcltd]

Hey! I just discovered this post. It sound really great. How much does it cost in DNET? I didn't find it in the OP. thanks in advance.

Hi
I'm not at home to give you the exact amount but what ever $ rate is in DNET


thanks
Paul

Okay nice. What's your reference price for Dnet in $, please?

Hi ok
if you want to pay for my hosting charges  in DNET this is how you do it

First ALL payments  MUST be sent to this address  and no other address DEawqqHYU4U27KKppGjNygSTRkQrdnHctM

this is how you work out what to send in DNET

i use http://coinmill.com/BTC_USD.html to get the USD / BTC price 


Goto BITTREX
https://bittrex.com/Market/Index?MarketName=BTC-DNET


get the ASK price  = 0.00000697
Get the BID price  = 0.00000661
take the BID price from the ASK price 

0.00000697 - 0.00000661 = 0.00000036 / 2 = 0.00000018
0.00000661 + 0.00000018 = 0.00000679

if your invoice is for $10.00 then that .02 BTC 

so .02 / 0.00000679 = 2945.50810015 DNET to send to the above address

you then send the DNET TXid with the invoice No. you are paying to me in a support ticket or a PM on here  and ill do the rest

IF YOU MAKE A MISTAKE IN SENDING THE COINS TO A DIFFERENT ADDRESS  THATS YOUR FAULT AND YOU WILL STILL HAVE TO PAY AGAIN.


Hope that all clear. If not ask away


these prices  are correct at time of this post 



Thanks
Paul

[jakiman]

can you let me know the ip's please

I forgot to keep a list but some of the subnets were:

164.132.238.xxx
37.59.209.xxx
164.132.237.xxx
164.132.189.xxx

[pjcltd]

can you let me know the ip's please

I forgot to keep a list but some of the subnets were:

164.132.238.xxx
37.59.209.xxx
164.132.237.xxx
164.132.189.xxx

so are they all up now ?

[berron]

Please, include a darknet-update-blockchain.sh in your scrypt list to avoid us to sync the complete blockchain everytime that this kind of shit happens. Your server are horrible slow updating, and I can't stay half an hour waiting for the sync. These problems make me lost money and a lot of time.

[pjcltd]

Please, include a darknet-update-blockchain.sh in your scrypt list to avoid us to sync the complete blockchain everytime that this kind of shit happens. Your server are horrible slow updating, and I can't stay half an hour waiting for the sync. These problems make me lost money and a lot of time.

HI
ok what script are you talking about ?
when the coin was having issues we was ALL advised  to sync from the start 
if we did not do that  we would have problems

If you have an issue with any of my servers  open a support ticket with the ip range you are having issues  with and i will have a a look at the server

Im going through an upgrade process on ALL my servers  they are all going to SSD


thanks
Paul

[DRPD]

Please, include a darknet-update-blockchain.sh in your scrypt list to avoid us to sync the complete blockchain everytime that this kind of shit happens. Your server are horrible slow updating, and I can't stay half an hour waiting for the sync. These problems make me lost money and a lot of time.

HI
ok what script are you talking about ?
when the coin was having issues we was ALL advised  to sync from the start  
if we did not do that  we would have problems

If you have an issue with any of my servers  open a support ticket with the ip range you are having issues  with and i will have a a look at the server

Im going through an upgrade process on ALL my servers  they are all going to SSD


thanks
Paul

the problem is everytime the vps's are restarted (yesterday almost all of my mn's were restarted) we have to resync from scratch because the chain is corrupted.
i guess berron expects a script so everytime our vps's are restarted out of the blue like yesterday the corrupted chain will automatically be replaced.

I have to admit some servers are realy slow sometimes. i hope it will be better with ssd, but i guess we have to resync again after that  

[pjcltd]

Please, include a darknet-update-blockchain.sh in your scrypt list to avoid us to sync the complete blockchain everytime that this kind of shit happens. Your server are horrible slow updating, and I can't stay half an hour waiting for the sync. These problems make me lost money and a lot of time.

HI
ok what script are you talking about ?
when the coin was having issues we was ALL advised  to sync from the start  
if we did not do that  we would have problems

If you have an issue with any of my servers  open a support ticket with the ip range you are having issues  with and i will have a a look at the server

Im going through an upgrade process on ALL my servers  they are all going to SSD


thanks
Paul

the problem is everytime the vps's are restarted (yesterday almost all of my mn's were restarted) we have to resync from scratch because the chain is corrupted.
i guess berron expects a script so everytime our vps's are restarted out of the blue like yesterday the corrupted chain will automatically be replaced.

I have to admit some servers are realy slow sometimes. i hope it will be better with ssd, but i guess we have to resync again after that  

HI
ok well there was no work been done on any of my servers yeaterday and no Downtime emails from anyone

as for a scrypt that replaces the block chain

I can build that no problem at all infact ill do it today.


thanks
Paul

[DRPD]

Please, include a darknet-update-blockchain.sh in your scrypt list to avoid us to sync the complete blockchain everytime that this kind of shit happens. Your server are horrible slow updating, and I can't stay half an hour waiting for the sync. These problems make me lost money and a lot of time.

HI
ok what script are you talking about ?
when the coin was having issues we was ALL advised  to sync from the start  
if we did not do that  we would have problems

If you have an issue with any of my servers  open a support ticket with the ip range you are having issues  with and i will have a a look at the server

Im going through an upgrade process on ALL my servers  they are all going to SSD


thanks
Paul

the problem is everytime the vps's are restarted (yesterday almost all of my mn's were restarted) we have to resync from scratch because the chain is corrupted.
i guess berron expects a script so everytime our vps's are restarted out of the blue like yesterday the corrupted chain will automatically be replaced.

I have to admit some servers are realy slow sometimes. i hope it will be better with ssd, but i guess we have to resync again after that  

HI
ok well there was no work been done on any of my servers yeaterday and no Downtime emails from anyone

as for a scrypt that replaces the block chain

I can build that no problem at all infact ill do it today.


thanks
Paul

well there must be something happend yesterday most of my vps's  were restarted (ip range 164.132.238.xy for example), i'm 100% sure jakiman and others can confirm this

[DRPD]

btw, vps's are restarting again only some: 37.59.209.xy, 164.132.189.xy  164.132.238.xy (20 minutes ago)
i guess mor will follow ...

blockchain corrupted and i have to resync again, please fix this problem with restarts!

[jakiman]

Tons of my masternodes/VPSs died again today. (mostly same ones that died yesterday + few more I think)
I can't connect to some and those I can ended up with a corrupt blockchain once again. Is it due to upgrade?

164.132.237.xxx
164.132.238.xxx
37.59.209.xxx
164.132.189.xxx
151.80.2.xxx

I've created a ticket...

[DRPD]

chain backup here:
https://drive.google.com/open?id=0B_Egj11irGZyOFYydk03aGVJaXc

Block 287845 (1-2 hrs ago)

[DRPD]

ok alot of my nodes on mp hosting are now dying all 1 - 2 hrs or falling out of sync
no point to resync atm i guess ....

let us know if the problems are fixed

[borris123]

Tons of my masternodes/VPSs died again today. (mostly same ones that died yesterday + few more I think)
I can't connect to some and those I can ended up with a corrupt blockchain once again. Is it due to upgrade?

164.132.237.xxx
164.132.238.xxx
37.59.209.xxx
164.132.189.xxx
151.80.2.xxx

I've created a ticket...

alot of mine same ip range are doing the same. either restarted/corrupt/not running

[jakiman]

All of the unconnectable VPS's were rebooted and now can login. I've started resyncing all of them again now.

[pjcltd]

All of the unconnectable VPS's were rebooted and now can login. I've started resyncing all of them again now.

Hi i have put up a clean block chain zip
http://149.56.154.83/
this file gets updated every 3 hours 

im looking into the server logs as it seemd to have rebooted this morrning but it was not reported


I think this serveris for the chop (next one to get the SSD upgrade)


thanks
Paul

[borris123]

Tons of my masternodes/VPSs died again today. (mostly same ones that died yesterday + few more I think)
I can't connect to some and those I can ended up with a corrupt blockchain once again. Is it due to upgrade?

164.132.237.xxx
164.132.238.xxx
37.59.209.xxx
164.132.189.xxx
151.80.2.xxx

I've created a ticket...

alot of mine same ip range are doing the same. either restarted/corrupt/not running

its done it again.

[pjcltd]

Tons of my masternodes/VPSs died again today. (mostly same ones that died yesterday + few more I think)
I can't connect to some and those I can ended up with a corrupt blockchain once again. Is it due to upgrade?

164.132.237.xxx
164.132.238.xxx
37.59.209.xxx
164.132.189.xxx
151.80.2.xxx

I've created a ticket...

alot of mine same ip range are doing the same. either restarted/corrupt/not running

its done it again.

the servers not rebooting
its under attack

i need to get this filtered  

[berron]

Please, include a darknet-update-blockchain.sh in your scrypt list to avoid us to sync the complete blockchain everytime that this kind of shit happens. Your server are horrible slow updating, and I can't stay half an hour waiting for the sync. These problems make me lost money and a lot of time.

HI
ok what script are you talking about ?
when the coin was having issues we was ALL advised  to sync from the start  
if we did not do that  we would have problems

If you have an issue with any of my servers  open a support ticket with the ip range you are having issues  with and i will have a a look at the server

Im going through an upgrade process on ALL my servers  they are all going to SSD


thanks
Paul

the problem is everytime the vps's are restarted (yesterday almost all of my mn's were restarted) we have to resync from scratch because the chain is corrupted.
i guess berron expects a script so everytime our vps's are restarted out of the blue like yesterday the corrupted chain will automatically be replaced.

I have to admit some servers are realy slow sometimes. i hope it will be better with ssd, but i guess we have to resync again after that  

Exactly, you told it much better than me.

Paul, I restarted the MN's when the update happened. If I remember correctly I did it about ten times before the devs were finally able to fix everything. I helped trying to install the new version of the wallet everytime it was changed as soon as I could and informing about the results. And of course, that was not your responsibility at all, and I think no one told anything in this thread during those days. But there has been in these months a lot of server restarting, due changes in configuration, external attacks and so on. And avoid that is your responsibility as to have a strong pass to my servers is mine.

Sorry, Paul, but if things don't start to change, I will migrate all my MN's to vultr once the contracted time expires. I have one there during two months, and yes, I had to do all the config work and in that moment it was really expensive compared to yours. But the MN's didn't fail a day in those two months. It's frustrating to have to redo all once and once again. As I told you, I'm losing time and money everytime this happens. Don't take this as any kind of personal attack, simply the quality of the contracted service is less than expected lately. Hope you being able to sort all the things out, but in other case, I will have to abandone your servers. In only some days reward is going to decrease and we will have lost a good amount of DNET in this period. And I only have half docen of MN's. People with a lot of them has the right to be really upset wtih this.

Ah, I will not create a ticket again for this, I have problems in nodes in the same ip ranges than others, so put another ticket in the queue would not help to any of us.

Salute