Bitcoin Forum
July 23, 2017, 02:52:57 AM *
News: Due to BIP91, it would starting now be prudent to require 5x more confirmations than usual before trusting transactions.
 
   Home   Help Search Donate Login Register  
Poll
Question: I will be posting the DNET Price on the twitter at a set interval. Please vote for the frequency I will post it, I Want to lessen the complains of over activity.. Smiley
every 15 min - 37 (13.1%)
every 30 min - 12 (4.2%)
every hour - 58 (20.5%)
every 2 hours - 22 (7.8%)
every 4 hours - 154 (54.4%)
Total Voters: 283

Pages: « 1 ... 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 [218] 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 ... 428 »
  Print  
Author Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - POS 2.0 - ZEROCOIN PROTOCOL  (Read 545979 times)
jakiman
Legendary
*
Offline Offline

Activity: 1022



View Profile
September 13, 2016, 12:10:27 PM
 #4341

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

Follow me on Twitter for latest PIVX updates @ https://twitter.com/jakimanboy
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1500778377
Hero Member
*
Offline Offline

Posts: 1500778377

View Profile Personal Message (Offline)

Ignore
1500778377
Reply with quote  #2

1500778377
Report to moderator
1500778377
Hero Member
*
Offline Offline

Posts: 1500778377

View Profile Personal Message (Offline)

Ignore
1500778377
Reply with quote  #2

1500778377
Report to moderator
1500778377
Hero Member
*
Offline Offline

Posts: 1500778377

View Profile Personal Message (Offline)

Ignore
1500778377
Reply with quote  #2

1500778377
Report to moderator
Haunebu81
Hero Member
*****
Offline Offline

Activity: 515


View Profile
September 13, 2016, 12:19:17 PM
 #4342

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
*
Offline Offline

Activity: 1022



View Profile
September 13, 2016, 12:22:50 PM
 #4343

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

Follow me on Twitter for latest PIVX updates @ https://twitter.com/jakimanboy
Haunebu81
Hero Member
*****
Offline Offline

Activity: 515


View Profile
September 13, 2016, 12:53:38 PM
 #4344

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
*
Offline Offline

Activity: 1022



View Profile
September 13, 2016, 01:13:01 PM
 #4345

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.

Follow me on Twitter for latest PIVX updates @ https://twitter.com/jakimanboy
DRPD
Hero Member
*****
Offline Offline

Activity: 742


View Profile
September 13, 2016, 01:41:11 PM
 #4346

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
Haunebu81
Hero Member
*****
Offline Offline

Activity: 515


View Profile
September 13, 2016, 02:12:00 PM
 #4347

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?
s3v3nh4cks
Legendary
*
Offline Offline

Activity: 1050


View Profile WWW
September 13, 2016, 04:54:43 PM
 #4348

As of Sept 15th, 1:00 pm EST The Masternode Enforcement will be re-enabled, anyone still on Source v2.1.2.1 or older will stall, and no longer receive any rewards. Please make sure you are updated before then.

PIVX: DPQabewFmgSFxAtZPKszNKb2E6eHqPfJt5
borris123
Hero Member
*****
Offline Offline

Activity: 728


View Profile
September 13, 2016, 05:37:34 PM
 #4349

As of Sept 15th, 1:00 pm EST The Masternode Enforcement will be re-enabled, anyone still on Source v2.1.2.1 or older will stall, and no longer receive any rewards. Please make sure you are updated before then.

Will the nodes go missing if they are on the wrong version?
s3v3nh4cks
Legendary
*
Offline Offline

Activity: 1050


View Profile WWW
September 13, 2016, 07:37:24 PM
 #4350

As of Sept 15th, 1:00 pm EST The Masternode Enforcement will be re-enabled, anyone still on Source v2.1.2.1 or older will stall, and no longer receive any rewards. Please make sure you are updated before then.

Will the nodes go missing if they are on the wrong version?
Yes, You must be on the correct protocol version, which is source v2.1.2.2 and v2.1.2.3 atm

PIVX: DPQabewFmgSFxAtZPKszNKb2E6eHqPfJt5
jakiman
Legendary
*
Offline Offline

Activity: 1022



View Profile
September 13, 2016, 09:10:16 PM
 #4351

As of Sept 15th, 1:00 pm EST The Masternode Enforcement will be re-enabled, anyone still on Source v2.1.2.1 or older will stall, and no longer receive any rewards. Please make sure you are updated before then.

Dev Wallet Update

New v2.1.2.3 wallet update has been released on github by Stakebox. It is only mandatory if you are currently on v2.1.2.1 or below.

https://github.com/Darknet-Crypto/Darknet/releases/tag/v2.1.2.3

Change Log
- Syncing chain from scratch not working in 2.1.2.2 has been fixed
- Main page's balance showing incorrectly in 2.1.2.2 has been fixed
- Compiling issues in certain Linus systems in 2.1.2.2 has been fixed

Notes
- If you are running 2.1.2.1 or below, it is mandatory to update to 2.1.2.2 or higher as it corrects budget & reward payments.
- If you are already running 2.1.2.2 without issues, it is not mandatory to update to 2.1.2.3 unless you would like fixes listed above.
- Upgrading from 2.1.2.2 or below to 2.1.2.3 does not require a full resync. Just stop, replace binaries then restart wallet.
- As with any wallet upgrades, please backup first if it's an important wallet. (especially your staking or controller wallet etc)

Follow me on Twitter for latest PIVX updates @ https://twitter.com/jakimanboy
borris123
Hero Member
*****
Offline Offline

Activity: 728


View Profile
September 13, 2016, 09:17:46 PM
 #4352

As of Sept 15th, 1:00 pm EST The Masternode Enforcement will be re-enabled, anyone still on Source v2.1.2.1 or older will stall, and no longer receive any rewards. Please make sure you are updated before then.

Will the nodes go missing if they are on the wrong version?
Yes, You must be on the correct protocol version, which is source v2.1.2.2 and v2.1.2.3 atm

cheers. you said new website was almost done last week? any update?
s3v3nh4cks
Legendary
*
Offline Offline

Activity: 1050


View Profile WWW
September 13, 2016, 10:46:43 PM
 #4353

As of Sept 15th, 1:00 pm EST The Masternode Enforcement will be re-enabled, anyone still on Source v2.1.2.1 or older will stall, and no longer receive any rewards. Please make sure you are updated before then.

Will the nodes go missing if they are on the wrong version?
Yes, You must be on the correct protocol version, which is source v2.1.2.2 and v2.1.2.3 atm

cheers. you said new website was almost done last week? any update?

Still being worked on, It will roll out in phases. Initially there will be a users area with analytics, then we will have some voting to see what will be added next to the website.

PIVX: DPQabewFmgSFxAtZPKszNKb2E6eHqPfJt5
borris123
Hero Member
*****
Offline Offline

Activity: 728


View Profile
September 14, 2016, 12:41:33 PM
 #4354

getting this crash windows 10 64bit

2016-09-14 12:40:15 *** Failed to read block
2016-09-14 12:40:18 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2016-09-14 12:40:18 *** Failed to read block
2016-09-14 12:40:18 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2016-09-14 12:40:18 *** Failed to read block
2016-09-14 12:40:18 opencon thread interrupt
2016-09-14 12:40:18 dumpaddr thread stop
2016-09-14 12:40:18 addcon thread interrupt
2016-09-14 12:40:18 net thread interrupt
2016-09-14 12:40:19 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2016-09-14 12:40:19 *** Failed to read block
NotMyFarm
Full Member
***
Offline Offline

Activity: 236


View Profile
September 14, 2016, 12:49:14 PM
 #4355

fired up a bunch of MNs
2nd day up - all paied 1st time
 Grin

berron
Hero Member
*****
Offline Offline

Activity: 541



View Profile
September 14, 2016, 08:05:58 PM
 #4356

I have a completion of obfuscation of 93% and continuous messages of Non compatible MN found since three days ago. Is this the expected behaviour?
Salute
mikegi
Full Member
***
Offline Offline

Activity: 164


View Profile
September 14, 2016, 08:37:17 PM
 #4357

getting this crash windows 10 64bit

2016-09-14 12:40:15 *** Failed to read block
2016-09-14 12:40:18 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2016-09-14 12:40:18 *** Failed to read block
2016-09-14 12:40:18 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2016-09-14 12:40:18 *** Failed to read block
2016-09-14 12:40:18 opencon thread interrupt
2016-09-14 12:40:18 dumpaddr thread stop
2016-09-14 12:40:18 addcon thread interrupt
2016-09-14 12:40:18 net thread interrupt
2016-09-14 12:40:19 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2016-09-14 12:40:19 *** Failed to read block

A quick look a google this... https://github.com/bitcoin/bitcoin/issues/5668

A long read but my guess would be that block file is corrupted.

Reload the blockchain from scratch... or copy it from a wallet or node that doesn't have this problem.
(keep/backup your wallet and configuration).
If you copy the blockchain from another node, make sure it is stopped when you make the copy.
borris123
Hero Member
*****
Offline Offline

Activity: 728


View Profile
September 14, 2016, 08:43:23 PM
 #4358

getting this crash windows 10 64bit

2016-09-14 12:40:15 *** Failed to read block
2016-09-14 12:40:18 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2016-09-14 12:40:18 *** Failed to read block
2016-09-14 12:40:18 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2016-09-14 12:40:18 *** Failed to read block
2016-09-14 12:40:18 opencon thread interrupt
2016-09-14 12:40:18 dumpaddr thread stop
2016-09-14 12:40:18 addcon thread interrupt
2016-09-14 12:40:18 net thread interrupt
2016-09-14 12:40:19 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2016-09-14 12:40:19 *** Failed to read block

A quick look a google this... https://github.com/bitcoin/bitcoin/issues/5668

A long read but my guess would be that block file is corrupted.

Reload the blockchain from scratch... or copy it from a wallet or node that doesn't have this problem.
(keep/backup your wallet and configuration).
If you copy the blockchain from another node, make sure it is stopped when you make the copy.

i always keep a backup of the main folder as it does seem to corrupt alot.
mikegi
Full Member
***
Offline Offline

Activity: 164


View Profile
September 14, 2016, 09:15:41 PM
 #4359

getting this crash windows 10 64bit

2016-09-14 12:40:15 *** Failed to read block
2016-09-14 12:40:18 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2016-09-14 12:40:18 *** Failed to read block
2016-09-14 12:40:18 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2016-09-14 12:40:18 *** Failed to read block
2016-09-14 12:40:18 opencon thread interrupt
2016-09-14 12:40:18 dumpaddr thread stop
2016-09-14 12:40:18 addcon thread interrupt
2016-09-14 12:40:18 net thread interrupt
2016-09-14 12:40:19 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2016-09-14 12:40:19 *** Failed to read block

A quick look a google this... https://github.com/bitcoin/bitcoin/issues/5668

A long read but my guess would be that block file is corrupted.

Reload the blockchain from scratch... or copy it from a wallet or node that doesn't have this problem.
(keep/backup your wallet and configuration).
If you copy the blockchain from another node, make sure it is stopped when you make the copy.

i always keep a backup of the main folder as it does seem to corrupt alot.

Not sure about how to do this with Windows... but it is worth using a tool to check the S.M.A.R.T. data for your hard disk.

A few years ago, a family member had a Windows Vista laptop that was really slow... It was nice that Vista had some kind of tool to resize disk partitions so I could install Linux. Windows didn't indicate any problem... but running dmesg under Linux showed something was up, looking at the S.M.A.R.T. data  with smartctl showed that there were lots of seek errors.

Not sure if windows is any better now about telling the user their disk is dangerously close to being useless. Maybe someone else can recommend a good windows utility to check this?

Good to have backups!
 
borris123
Hero Member
*****
Offline Offline

Activity: 728


View Profile
September 14, 2016, 09:30:28 PM
 #4360

getting this crash windows 10 64bit

2016-09-14 12:40:15 *** Failed to read block
2016-09-14 12:40:18 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2016-09-14 12:40:18 *** Failed to read block
2016-09-14 12:40:18 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2016-09-14 12:40:18 *** Failed to read block
2016-09-14 12:40:18 opencon thread interrupt
2016-09-14 12:40:18 dumpaddr thread stop
2016-09-14 12:40:18 addcon thread interrupt
2016-09-14 12:40:18 net thread interrupt
2016-09-14 12:40:19 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2016-09-14 12:40:19 *** Failed to read block

A quick look a google this... https://github.com/bitcoin/bitcoin/issues/5668

A long read but my guess would be that block file is corrupted.

Reload the blockchain from scratch... or copy it from a wallet or node that doesn't have this problem.
(keep/backup your wallet and configuration).
If you copy the blockchain from another node, make sure it is stopped when you make the copy.

i always keep a backup of the main folder as it does seem to corrupt alot.

Not sure about how to do this with Windows... but it is worth using a tool to check the S.M.A.R.T. data for your hard disk.

A few years ago, a family member had a Windows Vista laptop that was really slow... It was nice that Vista had some kind of tool to resize disk partitions so I could install Linux. Windows didn't indicate any problem... but running dmesg under Linux showed something was up, looking at the S.M.A.R.T. data  with smartctl showed that there were lots of seek errors.

Not sure if windows is any better now about telling the user their disk is dangerously close to being useless. Maybe someone else can recommend a good windows utility to check this?

Good to have backups!
 

It's ssd one only runs me wallets and windows and had it at christmas. Is on constant but can't be nakered already??
Pages: « 1 ... 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 [218] 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 ... 428 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!