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

I have lot of problems after editing the darknet.conf with the

:wq (pushed simultaneously, one after another, first : then wq???) I have tried some combinations but due the server lag, or my imcopetency or another thing I has been unable to record my changes.

Then I have tried to stop the scrypt execution when the config file is opened. I have corrected it manually with nano darknet.conf in the .darknet directory and checked changes have been saved. All seems to be ok, ./darknetd, server started, then ./darknet-cli, but when the blockchain finish to load, i have this:

Version seems to be correct but blocks seems to be stucked in 259200. Is this normal or the way I have updated the server doesn't work??

Thanks

{
    "version" : 2000100,
    "protocolversion" : 70300,
    "walletversion" : 61000,
    "balance" : 0.00000000,
    "obfuscation_balance" : 0.00000000,
    "blocks" : 259200,
    "timeoffset" : 0,
    "connections" : 10,
    "proxy" : "",
    "difficulty" : 48.59999131,
    "testnet" : false,
    "keypoololdest" : 1463951312,
    "keypoolsize" : 1001,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00010000,
    "staking status" : "Staking Not Active",
    "errors" : ""}

cd

rm darknet-update.sh 

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

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]

 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

*************************************************************************************

Ok this is where it changes a bit
To make sure that you are on the correct chain you will need to edit your .darknet/darknet.conf
so this update scrypt will open it up for you at the right time

When its opened up you need to delete the addnode lines and add the following

to delete the lines move the curder down to the addmode line and press


that line will be removed keep pressing till they have all gone
DONT go crasy take your time

when they are all gone you can insert the new addnodes bellow by pressing


now can type into the new lines



now you need to press the Eskape key

next press



It will then carry on starting the nodes




Starting Darket damon
DarkNet server starting
Starting Masternode
{
    "version" : 2000100,
    "protocolversion" : 70300,
    "walletversion" : 61000,
    "balance" : 0.00000000,
    "obfuscation_balance" : 0.00000000,
    "blocks" : 454,
    "timeoffset" : 0,
    "connections" : 7,
    "proxy" : "",
    "difficulty" : 37.09591186,
    "testnet" : false,
    "keypoololdest" : 1457354235,
    "keypoolsize" : 1001,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00010000,
    "staking status" : "Staking Not Active",
    "errors" : ""
}


Upodate now Done

What are the instructions to update our vps? Thanks Paul.

Ok, I know that it has no relation with the hosting, with the wallet itself instead. But I was wondering if maybe could be something we could do.

Thanks

HI
its not our systems thats the issue it the coin
they guys are working on a solution and im sure they will update it soon


thanks
Paul

hey can you look at ticket #990726 again.

cheers

Hi Paul,

I know there is some problems with the POS transition. Two of my MN seems to be stucked at block 259200 but shows no errors, but the third one show this message

Is there something we can do to solve this? Reinstall the update or something?

Thanks

   "version" : 2000000,
    "protocolversion" : 70200,
    "walletversion" : 61000,
    "balance" : 0.00000000,
    "obfuscation_balance" : 0.00000000,
    "blocks" : 259200,
    "timeoffset" : 6,
    "connections" : 40,
    "proxy" : "",
    "difficulty" : 48.59999131,
    "testnet" : false,
    "keypoololdest" : 1460397145,
    "keypoolsize" : 1001,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00010000,
    "staking status" : "Staking Not Active",
    "errors" : "Warning: We do not appear to fully agree with our peers! You may need to upgrade, or other nodes may need to upgrade."

just building you 2 more to replace them now

thanks
Paul

still struggling with Ticket #990726

Hi Guys
sorry if your having issues  getting on to my site
we are under an attack its not DDOS  as yet  but they are attacking our server




thanks
Paul

cd

rm darknet-update.sh 

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

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]

 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
{
    "version" : 2000000,
    "protocolversion" : 70200,
    "walletversion" : 61000,
    "balance" : 0.00000000,
    "obfuscation_balance" : 0.00000000,
    "blocks" : 0,
    "timeoffset" : 0,
    "connections" : 0,
    "proxy" : "",
    "difficulty" : 0.00024414,
    "testnet" : false,
    "keypoololdest" : 1457354235,
    "keypoolsize" : 1001,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00010000,
    "staking status" : "Staking Not Active",
    "errors" : ""
}

Upodate now Done