Bitcoin Forum
April 10, 2024, 09:23:35 PM *
News: Latest Bitcoin Core release: 26.0 [Torrent]
 
   Home   Help Search Login Register More  
Poll
Question: .
.
.

Pages: « 1 ... 167 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 ... 541 »
  Print  
Author Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN  (Read 782149 times)
jakiman
Legendary
*
Offline Offline

Activity: 1638
Merit: 1011


jakiman is back!


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

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)

"If you don't want people to know you're a scumbag then don't be a scumbag." -- margaritahuyan
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
borris123
Hero Member
*****
Offline Offline

Activity: 728
Merit: 500


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

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?
4x13 (OP)
Legendary
*
Offline Offline

Activity: 1078
Merit: 1011


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

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

Activity: 728
Merit: 500


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

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
Merit: 100


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

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

berron
Hero Member
*****
Offline Offline

Activity: 727
Merit: 501



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

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

Have you tried a real DEX??? But a real DEX like this!!!
mikegi
Full Member
***
Offline Offline

Activity: 165
Merit: 100


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

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
Merit: 500


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

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: 165
Merit: 100


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

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
Merit: 500


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

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??
mikegi
Full Member
***
Offline Offline

Activity: 165
Merit: 100


View Profile
September 14, 2016, 10:07:41 PM
 #4331

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

It's hard to say for sure. SSD can fail too, just in different ways. I haven't seen a failed SSD yet though.

I did find a simple command line test for Windows using WMIC.

from the command prompt, run
"wmic"
and then
"diskdrive get status"

I noticed that  https://www.smartmontools.org/ is available for windows too.

If you decide to start any of the SMART tests, I'd suggest backing up important stuff before. I did have a hard disk that failed during an "extended test". I have seen enough disks fail and don't trust storing anything important on just 1 disk.
jakiman
Legendary
*
Offline Offline

Activity: 1638
Merit: 1011


jakiman is back!


View Profile
September 15, 2016, 01:52:24 AM
 #4332

It's ssd one only runs me wallets and windows and had it at christmas. Is on constant but can't be nakered already??

I highly doubt it's the SSD although there's always a chance.

I've recently had heaps of corrupt blockchain for DNET. Way more often than any other coin I've ever dealt with.
It was pretty much always due to to the hang that sometimes happens while starting up the remote masternode.

Once the downloaded blockchain goes bad, even though sometimes the wallet launches and works, it ends up crashing later down the track.

Haunebu81
Hero Member
*****
Offline Offline

Activity: 525
Merit: 500


View Profile
September 15, 2016, 12:12:45 PM
 #4333

I'm having hell of a time trying to get my MN's to stay in ENABLED status.

It seems as if even one instance out of the five locks up on my VPS, then all 5 MN's go into MISSING status.

On 8 of my 22 VPS's, between 1 to 4 instances of the darknetd constantly lock up on me. I have to delete the blockchian files, stop the instances, then restart them again, only to have it happen all over again.

When I run the getinfo command on the locked up instances, it says something like "Error loading block database", and occasionally "Cannot connect to server".

Anyone guess why this keeps happening? I'm using mxnsch's script, btw, which automatically uses the latest version of darknetd. My control wallet is also on the latest version. I'm on the $5 VULTR VPS's.


borris123
Hero Member
*****
Offline Offline

Activity: 728
Merit: 500


View Profile
September 15, 2016, 12:38:18 PM
 #4334

I'm having hell of a time trying to get my MN's to stay in ENABLED status.

It seems as if even one instance out of the five locks up on my VPS, then all 5 MN's go into MISSING status.

On 8 of my 22 VPS's, between 1 to 4 instances of the darknetd constantly lock up on me. I have to delete the blockchian files, stop the instances, then restart them again, only to have it happen all over again.

When I run the getinfo command on the locked up instances, it says something like "Error loading block database", and occasionally "Cannot connect to server".

Anyone guess why this keeps happening? I'm using mxnsch's script, btw, which automatically uses the latest version of darknetd. My control wallet is also on the latest version. I'm on the $5 VULTR VPS's.




i was having same problems when testing the vultr script. gave up in the end and stuck with mphosting. it may save a little money per node but how much is your time worth? how many hours have you spent already trying do it all yourself? remember maintenance as well. something will happen not if at some point. do you have the knowledge to fix it yourself? would it just be easier to pay someone to do all that for you?

paul/mp hosting spot on. Plus you can pay in DNET.

just send him msg like this after you sent it to DEawqqHYU4U27KKppGjNygSTRkQrdnHctM

PAID
invoice 1193
11.20 US Dollar equals
0.0185 Bitcoin
0.0185/0.00000701 = 2639.08701854
sent 2640

the 701 is middle value of the high and low on bittex.
Haunebu81
Hero Member
*****
Offline Offline

Activity: 525
Merit: 500


View Profile
September 15, 2016, 12:41:27 PM
 #4335

I'm having hell of a time trying to get my MN's to stay in ENABLED status.

It seems as if even one instance out of the five locks up on my VPS, then all 5 MN's go into MISSING status.

On 8 of my 22 VPS's, between 1 to 4 instances of the darknetd constantly lock up on me. I have to delete the blockchian files, stop the instances, then restart them again, only to have it happen all over again.

When I run the getinfo command on the locked up instances, it says something like "Error loading block database", and occasionally "Cannot connect to server".

Anyone guess why this keeps happening? I'm using mxnsch's script, btw, which automatically uses the latest version of darknetd. My control wallet is also on the latest version. I'm on the $5 VULTR VPS's.




i was having same problems when testing the vultr script. gave up in the end and stuck with mphosting. it may save a little money per node but how much is your time worth? how many hours have you spent already trying do it all yourself? remember maintenance as well. something will happen not if at some point. do you have the knowledge to fix it yourself? would it just be easier to pay someone to do all that for you?

paul/mp hosting spot on. Plus you can pay in DNET.

just send him msg like this after you sent it to DEawqqHYU4U27KKppGjNygSTRkQrdnHctM

PAID
invoice 1193
11.20 US Dollar equals
0.0185 Bitcoin
0.0185/0.00000701 = 2639.08701854
sent 2640

the 701 is middle value of the high and low on bittex.

$1.50 per month per MN and $1.00 set up fee per MN?
Rumhurius
Legendary
*
Offline Offline

Activity: 1672
Merit: 1046


Here we go again


View Profile
September 15, 2016, 12:48:22 PM
Last edit: September 15, 2016, 01:17:51 PM by Rumhurius
 #4336

seems like the latest wallet release is broken again somehow.
My Wallet crashed and now its stuck after restart.
Forked again ?

This Shit really needs a testnet.

One older Version even corrupted my wallet before.
So make sure you have a nice n clean wallet.dat backup before you update guys.

borris123
Hero Member
*****
Offline Offline

Activity: 728
Merit: 500


View Profile
September 15, 2016, 01:30:25 PM
 #4337

I'm having hell of a time trying to get my MN's to stay in ENABLED status.

It seems as if even one instance out of the five locks up on my VPS, then all 5 MN's go into MISSING status.

On 8 of my 22 VPS's, between 1 to 4 instances of the darknetd constantly lock up on me. I have to delete the blockchian files, stop the instances, then restart them again, only to have it happen all over again.

When I run the getinfo command on the locked up instances, it says something like "Error loading block database", and occasionally "Cannot connect to server".

Anyone guess why this keeps happening? I'm using mxnsch's script, btw, which automatically uses the latest version of darknetd. My control wallet is also on the latest version. I'm on the $5 VULTR VPS's.




i was having same problems when testing the vultr script. gave up in the end and stuck with mphosting. it may save a little money per node but how much is your time worth? how many hours have you spent already trying do it all yourself? remember maintenance as well. something will happen not if at some point. do you have the knowledge to fix it yourself? would it just be easier to pay someone to do all that for you?

paul/mp hosting spot on. Plus you can pay in DNET.

just send him msg like this after you sent it to DEawqqHYU4U27KKppGjNygSTRkQrdnHctM

PAID
invoice 1193
11.20 US Dollar equals
0.0185 Bitcoin
0.0185/0.00000701 = 2639.08701854
sent 2640

the 701 is middle value of the high and low on bittex.

$1.50 per month per MN and $1.00 set up fee per MN?

ye. you do get late fees as well so if your due on a certain day pay the day before.
berron
Hero Member
*****
Offline Offline

Activity: 727
Merit: 501



View Profile
September 15, 2016, 04:22:22 PM
 #4338

seems like the latest wallet release is broken again somehow.
My Wallet crashed and now its stuck after restart.
Forked again ?

This Shit really needs a testnet.

One older Version even corrupted my wallet before.
So make sure you have a nice n clean wallet.dat backup before you update guys.
I have also forked this afternoon, after about a week of no problematic behaviour. I'm now syncing again, will post later the result. darknet.conf has only coin-server.com has node and except for the obfuscation problems I post before all was running smooth till this afternoon (16:30 aprox GMT+1). If you want the log file, post an email and I will send you.

Salute

Have you tried a real DEX??? But a real DEX like this!!!
4x13 (OP)
Legendary
*
Offline Offline

Activity: 1078
Merit: 1011


View Profile
September 15, 2016, 09:12:09 PM
 #4339

What wallet version were you using?
jakiman
Legendary
*
Offline Offline

Activity: 1638
Merit: 1011


jakiman is back!


View Profile
September 15, 2016, 10:55:13 PM
 #4340

Just confirming that I'm not having issues with both my Windows & Linux wallets and masternodes on 2.1.2.3. Cool

Pages: « 1 ... 167 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 ... 541 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!