[ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN - page 326.

Haunebu81

hero member

Activity: 525

Merit: 500

Quote from: DRPD on September 13, 2016, 08:41:11 AM

Quote from: Haunebu81 on September 13, 2016, 07:53:38 AM

Quote from: jakiman on September 13, 2016, 07:22:50 AM

Quote from: Haunebu81 on September 13, 2016, 07:19:17 AM

I just set up 22 VPS's this weekend and reinstalled 9 of the malfunctioning ones yesterday, and they're still having issues. I'll try reinstalling them one last time before I resort to mp-hosting or something.

BTW, how would I stop the daemons if I'm using mxnsch's script?

Oh that's weird if so. Hopefully another reinstall (or simple restart of the daemon) will fix it. hmm.

To stop, just run the following command with the MN number you want to stop:
/usr/local/bin/darknet-cli -conf=/etc/masternodes/darknet_n1.conf stop

Then restart it using:
systemctl restart darknet_n1

Okay and the script won't try to automatically restart it? I remember I found a way to kill the darknetd process by using the PID number, but the daemons kept being automatically restarted.

yes the instance will be restarted autom.

close it like this: systemctl stop darknet_n1, systemctl stop darknet_n2 ...

and it will stay down until you restart the service with: systemctl restart darknet_n1, systemctl restart darknet_n2 ...

Cheers

Yes, thanks! =D

Now when I've got "top" open, and I see my 5 darknetd's in there. Is there any way I can tell which one belongs to which directory (darknet_n1, _n2 etc) based on the PID or something?

DRPD

legendary

Activity: 1148

Merit: 1001

Quote from: Haunebu81 on September 13, 2016, 07:53:38 AM

Quote from: jakiman on September 13, 2016, 07:22:50 AM

Quote from: Haunebu81 on September 13, 2016, 07:19:17 AM

I just set up 22 VPS's this weekend and reinstalled 9 of the malfunctioning ones yesterday, and they're still having issues. I'll try reinstalling them one last time before I resort to mp-hosting or something.

BTW, how would I stop the daemons if I'm using mxnsch's script?

Oh that's weird if so. Hopefully another reinstall (or simple restart of the daemon) will fix it. hmm.

To stop, just run the following command with the MN number you want to stop:
/usr/local/bin/darknet-cli -conf=/etc/masternodes/darknet_n1.conf stop

Then restart it using:
systemctl restart darknet_n1

Okay and the script won't try to automatically restart it? I remember I found a way to kill the darknetd process by using the PID number, but the daemons kept being automatically restarted.

yes the instance will be restarted autom.

close it like this: systemctl stop darknet_n1, systemctl stop darknet_n2 ...

and it will stay down until you restart the service with: systemctl restart darknet_n1, systemctl restart darknet_n2 ...

Cheers

jakiman

legendary

Activity: 1638

Merit: 1011

jakiman is back!

Quote from: Haunebu81 on September 13, 2016, 07:53:38 AM

Okay and the script won't try to automatically restart it? I remember I found a way to kill the darknetd process by using the PID number, but the daemons kept being automatically restarted.

Nope. Script doesn't auto-start anything. It's only an install script.

Haunebu81

hero member

Activity: 525

Merit: 500

Quote from: jakiman on September 13, 2016, 07:22:50 AM

Quote from: Haunebu81 on September 13, 2016, 07:19:17 AM

I just set up 22 VPS's this weekend and reinstalled 9 of the malfunctioning ones yesterday, and they're still having issues. I'll try reinstalling them one last time before I resort to mp-hosting or something.

BTW, how would I stop the daemons if I'm using mxnsch's script?

Oh that's weird if so. Hopefully another reinstall (or simple restart of the daemon) will fix it. hmm.

To stop, just run the following command with the MN number you want to stop:
/usr/local/bin/darknet-cli -conf=/etc/masternodes/darknet_n1.conf stop

Then restart it using:
systemctl restart darknet_n1

Okay and the script won't try to automatically restart it? I remember I found a way to kill the darknetd process by using the PID number, but the daemons kept being automatically restarted.

jakiman

legendary

Activity: 1638

Merit: 1011

jakiman is back!

Quote from: Haunebu81 on September 13, 2016, 07:19:17 AM

I just set up 22 VPS's this weekend and reinstalled 9 of the malfunctioning ones yesterday, and they're still having issues. I'll try reinstalling them one last time before I resort to mp-hosting or something.

BTW, how would I stop the daemons if I'm using mxnsch's script?

Oh that's weird if so. Hopefully another reinstall (or simple restart of the daemon) will fix it. hmm.

To stop, just run the following command with the MN number you want to stop:
/usr/local/bin/darknet-cli -conf=/etc/masternodes/darknet_n1.conf stop

Then restart it using:
systemctl restart darknet_n1

Haunebu81

hero member

Activity: 525

Merit: 500

Quote from: jakiman on September 13, 2016, 07:10:27 AM

Quote from: Haunebu81 on September 13, 2016, 07:06:31 AM

The single-core $5 vultr VPS's with 5mn on each, and I have several of them.

The ones with high cpu usage are the same ones that keep going missing. More than half of my VPS's do not have this high cpu usage issue and they stay in enabled status.

Have they been working well before but not now? or was it like this from day 1?
If it was from day 1, I would just reinstall that server from the beginning again.

Here's the top output from one of my Vultr's top output while having 5 active masternodes running 2.1.2.3:

Code:

top - 12:10:34 up 11 days, 23:20, 1 user, load average: 0.11, 0.08, 0.06
Tasks: 124 total, 1 running, 123 sleeping, 0 stopped, 0 zombie
%Cpu(s): 2.3 us, 1.0 sy, 5.7 ni, 90.9 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem : 758164 total, 56784 free, 547736 used, 153644 buff/cache
KiB Swap: 3071996 total, 2407500 free, 664496 used. 82496 avail Mem

  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
32729 mastern+ 20 0 907192 83924 7216 S 2.0 11.1 36:31.76 darknetd
  308 mastern+ 20 0 917084 151376 4964 S 1.7 20.0 36:22.56 darknetd
  335 mastern+ 20 0 914492 102372 3928 S 1.7 13.5 36:34.83 darknetd
  322 mastern+ 20 0 921992 93256 4448 S 1.3 12.3 36:08.66 darknetd
  349 mastern+ 20 0 905464 95700 2720 S 1.3 12.6 35:53.29 darknetd
   1 root 20 0 185172 3720 2312 S 0.0 0.5 0:19.21 systemd
   2 root 20 0 0 0 0 S 0.0 0.0 0:00.20 kthreadd

I just set up 22 VPS's this weekend and reinstalled 9 of the malfunctioning ones yesterday, and they're still having issues. I'll try reinstalling them one last time before I resort to mp-hosting or something.

BTW, how would I stop the daemons if I'm using mxnsch's script?

jakiman

legendary

Activity: 1638

Merit: 1011

jakiman is back!

Quote from: Haunebu81 on September 13, 2016, 07:06:31 AM

The single-core $5 vultr VPS's with 5mn on each, and I have several of them.

The ones with high cpu usage are the same ones that keep going missing. More than half of my VPS's do not have this high cpu usage issue and they stay in enabled status.

Have they been working well before but not now? or was it like this from day 1?
If it was from day 1, I would just reinstall that server from the beginning again.

Here's the top output from one of my Vultr's top output while having 5 active masternodes running 2.1.2.3:

Code:

top - 12:10:34 up 11 days, 23:20, 1 user, load average: 0.11, 0.08, 0.06
Tasks: 124 total, 1 running, 123 sleeping, 0 stopped, 0 zombie
%Cpu(s): 2.3 us, 1.0 sy, 5.7 ni, 90.9 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem : 758164 total, 56784 free, 547736 used, 153644 buff/cache
KiB Swap: 3071996 total, 2407500 free, 664496 used. 82496 avail Mem

  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
32729 mastern+ 20 0 907192 83924 7216 S 2.0 11.1 36:31.76 darknetd
  308 mastern+ 20 0 917084 151376 4964 S 1.7 20.0 36:22.56 darknetd
  335 mastern+ 20 0 914492 102372 3928 S 1.7 13.5 36:34.83 darknetd
  322 mastern+ 20 0 921992 93256 4448 S 1.3 12.3 36:08.66 darknetd
  349 mastern+ 20 0 905464 95700 2720 S 1.3 12.6 35:53.29 darknetd
   1 root 20 0 185172 3720 2312 S 0.0 0.5 0:19.21 systemd
   2 root 20 0 0 0 0 S 0.0 0.0 0:00.20 kthreadd

jakiman

legendary

Activity: 1638

Merit: 1011

jakiman is back!

I have now upgraded ALL my wallets & masternodes to 2.1.2.3. (Both Windows & Linux)
I've done them in batches over the last few days and can confirm all are working well. Grin

Haunebu81

hero member

Activity: 525

Merit: 500

Quote from: pjcltd on September 13, 2016, 06:06:29 AM

Quote from: Haunebu81 on September 13, 2016, 05:58:17 AM

What would cause the darknetd CPU usage to stay so high all the time on my VPS boxes? It's been 24 hours already and the daemons are using 100%....

whats the spec of your VPS ?
and how many MN's are you running on it ?

thanks
Paul

The single-core $5 vultr VPS's with 5mn on each, and I have several of them.

The ones with high cpu usage are the same ones that keep going missing. More than half of my VPS's do not have this high cpu usage issue and they stay in enabled status.

kokokoin

hero member

Activity: 638

Merit: 500

I have the same problem with few missing masternodes.
Masternode status results in: 'Not capable masternode: Hot node, waiting for remote activation.'
But i run them with controller wallet after update.
All my MN's are on MP-hosting.

pjcltd

legendary

Activity: 1778

Merit: 1003

NodeMasters

Quote from: Haunebu81 on September 13, 2016, 05:58:17 AM

What would cause the darknetd CPU usage to stay so high all the time on my VPS boxes? It's been 24 hours already and the daemons are using 100%....

whats the spec of your VPS ?
and how many MN's are you running on it ?

thanks
Paul

Haunebu81

hero member

Activity: 525

Merit: 500

What would cause the darknetd CPU usage to stay so high all the time on my VPS boxes? It's been 24 hours already and the daemons are using 100%....

boy2k

full member

Activity: 168

Merit: 100

Quote from: kokokoin on September 13, 2016, 03:32:43 AM

Replacing wallet.dat with old backup fixed the problem with these two errors. Wallet now staking.

will try now mate.
reindexing....

Confirmed, this fixed my staking. Now to work out why nodes keep going missing... :/

kokokoin

hero member

Activity: 638

Merit: 500

Replacing wallet.dat with old backup fixed the problem with these two errors. Wallet now staking.

kokokoin

hero member

Activity: 638

Merit: 500

Quote from: boy2k on September 13, 2016, 03:01:40 AM

anyone else having issues with staking not activating in the new windows wallet?
Also masternodes are now going missing more, still no rewards from them but rebuilt them yesterday so hopefully today (for the ones that managed to stay enabled anyway..)

Yes, after update my wallet is not staking. And every time i close it there is an error:

*** System error while flushing: CDB : Error -30974, can't open database
CDBEnv::EnvShutdown : Error -30974 shutting down database environment: DB_RUNRECOVERY: Fatal error, run database recovery

Resyncing doesn't help.

boy2k

full member

Activity: 168

Merit: 100

anyone else having issues with staking not activating in the new windows wallet?
Also masternodes are now going missing more, still no rewards from them but rebuilt them yesterday so hopefully today (for the ones that managed to stay enabled anyway..)

kokokoin

hero member

Activity: 638

Merit: 500

Quote from: borris123 on September 12, 2016, 10:26:23 AM

Quote from: Haunebu81 on September 12, 2016, 10:22:32 AM

Quote from: kokokoin on September 12, 2016, 10:10:11 AM

After update of all my MN's they became 'MISSING'. Tried 'masternode start-many' on my controller wallet but it stopped to respond.

It's a known issue. You have to start hem one by one using:

masternode start-alias (Masternode Label) (Password)

aka

masternode start-alias Masternode01 Sd$%w!nn8X

Also, wait several seconds between each attempt and make sure the wallet it sully sync'd. It still freezes up on me, but a little less often with that method.

do this method instead as you will still get crashes doing that.

- console command: walletpassphrase 12000 [HIT ENTER]
- console command: masternode start-alias [HIT ENTER]
- arrow up key to re enter passphrase
- arrow up key twice change the name

When i write 'walletpassphrase 1200' there is error: 'CDB : Error -30974, can't open database (code -1)'. But the wallet unlocks. Is it ok?

4x13

legendary

Activity: 1078

Merit: 1011

Ok, as i agreed, I matched the votes on CoinPayments from 9-9-15 thru 9-11-16, only 11 votes from that time frame.

CPAI4KVAKJFNUBN0FXG7ECDBWJ

11 Votes (No I am not counting these votes toward the giveaway) Lets keep it going Everyone, long way to go still. We need 1000 Votes and we are now at 422..

NotMyFarm

full member

Activity: 236

Merit: 100

Quote from: .cryptic. on September 13, 2016, 12:20:00 AM

Quote from: .cryptic. on September 11, 2016, 11:31:16 AM

Quote from: tombtc on September 11, 2016, 06:09:57 AM

Unlock your wallets and it will start staking.

Been running an unlocked wallet for the last 48 hours on Windows 7.
Still nothing. Huh

NO staking.

bump Any ideas?

is the staking arrow green ?

4x13

legendary

Activity: 1078

Merit: 1011

Quote from: .cryptic. on September 13, 2016, 12:20:00 AM

Quote from: .cryptic. on September 11, 2016, 11:31:16 AM

Quote from: tombtc on September 11, 2016, 06:09:57 AM

Unlock your wallets and it will start staking.

Been running an unlocked wallet for the last 48 hours on Windows 7.
Still nothing. Huh

NO staking.

bump Any ideas?

what are your block sizes?? is the wallet truly unlocked? have you restarted the wallet for shits and giggles? The wallet won't stake if it is not fully synced.

Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN - page 326. (Read 782375 times)