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

Ok, Paul, will do. Sorry.

Hi Barron
I have been working on the servers
But
Please don't use compiled files from any one but the ones I provide
I have posted in the past about this
I build them for the masternodes on a masternode
And they should be the only ones you use on my servers.

Thanks for the scripts though


Thanks
Paul

Jakiman has just announced that new version to correct some problems syncing from scrach and other minor changes has been launched as I was writing my post. To use new version instead v2.1.2.2 simply change these two code lines:


for these


Notice that the version number has changed.

Salute

Hi Paul,

All the MN's seems to be working right now quite well, I don't know if you have done any king of changes but they seem to work, thanks.

If anyone is interested on updating their MN's to v2.1.2.2 version and while Paul prepare the scrypt here goes the instruction list. If your MN is working fine and you only want to update it use this command list:


and if you have a corrupted, stucked or similar blockchain use this:


Some people has found problems restarting the MN's from the controller wallet, controller wallet shows the MN's as ENABLED but when you enter in the MN and type


you found the message "Hot masternode waiting for remote activation". Jakiman found the solution stopping and starting again the daemon. And I find that it you make it very fast it doesn't work. So in that case you have to do:


And restart the MN's from the controller wallet. I have found some problems also using start-all instead of start-alias to restart them, but I think this is not a general problem.

If anyone find any kind of mistake, please tell.

Hope this helps.

Edited for typos and small corrections in code.

Nice thank you very much for your answer. I will think about it and keep you informed. Thanks for providing this awesome service to the darknet community.

New server is built
im just lookng at the ip ranges to move over first

whens server update? dont want to be changing masternodes over and enabling them to find have to do it all again. the enabling takes the piss.

really hope masternode start-missing is fixed in this new wallet update.

I've got all the masternodes that got affected back up and running now.

To be totally honest
I'm not sure
The attack is still going on
Someone is targeting the main server ip
By me replacing the server that will stop
Also I will update the blockchain on all the vps's as they transfer

Thanks
Paul

Are you migrating all those ip ranges that keep crashin/corrupting/restarting whatever it's doing?

Is it just a dodgy server or is something malicious going on?

Ok new server ordered  with ssd drives  and more ram
Build will start in the morning
I will let you know when I'll start transferring vps's

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

the servers not rebooting
its under attack

i need to get this filtered  

its done it again.

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

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

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

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

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

Block 287845 (1-2 hrs ago)

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