c0in_junkie
|
|
March 23, 2017, 07:42:42 AM |
|
Where can i find instructions about installing and securing pivx wallet?
|
|
|
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
jazen777
Newbie
Offline
Activity: 4
Merit: 0
|
|
March 23, 2017, 08:39:00 AM |
|
Where can i find instructions about installing and securing pivx wallet?
Quickest response time - pivx.slack.com Other -https://forum.pivx.org/c/pivx-guides Goodluck! :-) -jazen
|
|
|
|
|
mxnsch
|
|
March 23, 2017, 09:32:56 AM |
|
devs you need for hard work to fix some shits erorrs in pivx daemon after its once killed (why?) and after manual restart the blockchain is corrupted: [root@xxxx ~]# : Corrupted block database detected. Do you want to rebuild the block database now?
2017-03-23 07:08:46 ERROR: ProcessNewBlock : AcceptBlock FAILED 2017-03-23 07:08:46 block time=1490233275 adjusted time=1490252926 is proof of stake=1 2017-03-23 07:08:46 ERROR: GetTransaction : Deserialize or I/O error - ReadCompactSize() : size too large 2017-03-23 07:08:46 ERROR: CheckProofOfStake() : INFO: read txPrev failed 2017-03-23 07:08:46 WARNING: ProcessBlock(): check proof-of-stake failed for block 32077a6f993ca48d2869fcba5839f0633f2dda3c66a2c817323b3343beba1f8d 2017-03-23 07:08:46 ERROR: ProcessNewBlock : AcceptBlock FAILED 2017-03-23 07:08:47 block time=1490233275 adjusted time=1490252927 is proof of stake=1 2017-03-23 07:08:47 ERROR: GetTransaction : Deserialize or I/O error - ReadCompactSize() : size too large 2017-03-23 07:08:47 ERROR: CheckProofOfStake() : INFO: read txPrev failed 2017-03-23 07:08:47 WARNING: ProcessBlock(): check proof-of-stake failed for block 32077a6f993ca48d2869fcba5839f0633f2dda3c66a2c817323b3343beba1f8d 2017-03-23 07:08:47 ERROR: ProcessNewBlock : AcceptBlock FAILED 2017-03-23 07:09:00 block time=1490233275 adjusted time=1490252940 is proof of stake=1 2017-03-23 07:09:00 ERROR: GetTransaction : Deserialize or I/O error - ReadCompactSize() : size too large 2017-03-23 07:09:00 ERROR: CheckProofOfStake() : INFO: read txPrev failed 2017-03-23 07:09:00 WARNING: ProcessBlock(): check proof-of-stake failed for block 32077a6f993ca48d2869fcba5839f0633f2dda3c66a2c817323b3343beba1f8d
Never had that issue. Why did you kill the process? How did you install PIVX and what version? Feel free to hit #support in slack. Ps.: It's obviously a known issue when you try _really_ hard to kill the process multiple times and only happening to installations on a SSD ;-) Fix in the works here: https://github.com/PIVX-Project/PIVX/issues/69 Stay calm, coins are safe.
|
██ ███ nope ██ ███
|
|
|
linux_master
Newbie
Offline
Activity: 5
Merit: 0
|
|
March 23, 2017, 09:50:06 AM |
|
devs you need for hard work to fix some shits erorrs in pivx daemon after its once killed (why?) and after manual restart the blockchain is corrupted: [root@xxxx ~]# : Corrupted block database detected. Do you want to rebuild the block database now?
2017-03-23 07:08:46 ERROR: ProcessNewBlock : AcceptBlock FAILED 2017-03-23 07:08:46 block time=1490233275 adjusted time=1490252926 is proof of stake=1 2017-03-23 07:08:46 ERROR: GetTransaction : Deserialize or I/O error - ReadCompactSize() : size too large 2017-03-23 07:08:46 ERROR: CheckProofOfStake() : INFO: read txPrev failed 2017-03-23 07:08:46 WARNING: ProcessBlock(): check proof-of-stake failed for block 32077a6f993ca48d2869fcba5839f0633f2dda3c66a2c817323b3343beba1f8d 2017-03-23 07:08:46 ERROR: ProcessNewBlock : AcceptBlock FAILED 2017-03-23 07:08:47 block time=1490233275 adjusted time=1490252927 is proof of stake=1 2017-03-23 07:08:47 ERROR: GetTransaction : Deserialize or I/O error - ReadCompactSize() : size too large 2017-03-23 07:08:47 ERROR: CheckProofOfStake() : INFO: read txPrev failed 2017-03-23 07:08:47 WARNING: ProcessBlock(): check proof-of-stake failed for block 32077a6f993ca48d2869fcba5839f0633f2dda3c66a2c817323b3343beba1f8d 2017-03-23 07:08:47 ERROR: ProcessNewBlock : AcceptBlock FAILED 2017-03-23 07:09:00 block time=1490233275 adjusted time=1490252940 is proof of stake=1 2017-03-23 07:09:00 ERROR: GetTransaction : Deserialize or I/O error - ReadCompactSize() : size too large 2017-03-23 07:09:00 ERROR: CheckProofOfStake() : INFO: read txPrev failed 2017-03-23 07:09:00 WARNING: ProcessBlock(): check proof-of-stake failed for block 32077a6f993ca48d2869fcba5839f0633f2dda3c66a2c817323b3343beba1f8d
Never had that issue. Why did you kill the process? How did you install PIVX and what version? Feel free to hit #support in slack. Ps.: It's obviously a known issue when you try _really_ hard to kill the process multiple times and only happening to installations on a SSD ;-) Fix in the works here: https://github.com/PIVX-Project/PIVX/issues/69 Stay calm, coins are safe. Its killed not by me, it was crash, now I am experementing with maxconnection parameter, looks like decreasing this paramater more stable for daemon But it is a fact that some daemon crashing corrupts local blockchain and it is a bug need for fix it and yes it is SSD VPS, thanks for link
|
|
|
|
mxnsch
|
|
March 23, 2017, 09:51:49 AM |
|
devs you need for hard work to fix some shits erorrs in pivx daemon after its once killed (why?) and after manual restart the blockchain is corrupted: [root@xxxx ~]# : Corrupted block database detected. Do you want to rebuild the block database now?
2017-03-23 07:08:46 ERROR: ProcessNewBlock : AcceptBlock FAILED 2017-03-23 07:08:46 block time=1490233275 adjusted time=1490252926 is proof of stake=1 2017-03-23 07:08:46 ERROR: GetTransaction : Deserialize or I/O error - ReadCompactSize() : size too large 2017-03-23 07:08:46 ERROR: CheckProofOfStake() : INFO: read txPrev failed 2017-03-23 07:08:46 WARNING: ProcessBlock(): check proof-of-stake failed for block 32077a6f993ca48d2869fcba5839f0633f2dda3c66a2c817323b3343beba1f8d 2017-03-23 07:08:46 ERROR: ProcessNewBlock : AcceptBlock FAILED 2017-03-23 07:08:47 block time=1490233275 adjusted time=1490252927 is proof of stake=1 2017-03-23 07:08:47 ERROR: GetTransaction : Deserialize or I/O error - ReadCompactSize() : size too large 2017-03-23 07:08:47 ERROR: CheckProofOfStake() : INFO: read txPrev failed 2017-03-23 07:08:47 WARNING: ProcessBlock(): check proof-of-stake failed for block 32077a6f993ca48d2869fcba5839f0633f2dda3c66a2c817323b3343beba1f8d 2017-03-23 07:08:47 ERROR: ProcessNewBlock : AcceptBlock FAILED 2017-03-23 07:09:00 block time=1490233275 adjusted time=1490252940 is proof of stake=1 2017-03-23 07:09:00 ERROR: GetTransaction : Deserialize or I/O error - ReadCompactSize() : size too large 2017-03-23 07:09:00 ERROR: CheckProofOfStake() : INFO: read txPrev failed 2017-03-23 07:09:00 WARNING: ProcessBlock(): check proof-of-stake failed for block 32077a6f993ca48d2869fcba5839f0633f2dda3c66a2c817323b3343beba1f8d
Never had that issue. Why did you kill the process? How did you install PIVX and what version? Feel free to hit #support in slack. Ps.: It's obviously a known issue when you try _really_ hard to kill the process multiple times and only happening to installations on a SSD ;-) Fix in the works here: https://github.com/PIVX-Project/PIVX/issues/69 Stay calm, coins are safe. Its killed not by me, it was crash, now I am experementing with maxconnection parameter, looks like decreasing this paramater more stable for daemon on VPS But it is a fact that some daemon crashing corrupts local blockchain and it is a bug need for fix it and yes it is SSD VPS, thanks for link Be assured it's being worked on. Is your ram limited by any chance? When you don't have enough, the process get's killed by the linux kernel. Never had that issue myself, but i can replicate it by killing as stated in the github issue.
|
██ ███ nope ██ ███
|
|
|
bitmaster1x
Legendary
Offline
Activity: 1274
Merit: 1000
CRYPTO-CITY.COM 🌟 Communities
|
|
March 23, 2017, 10:08:16 AM |
|
Not even heard about this until a few days ago and this was around since 2015. Interesting.
|
|
|
|
ciro1
Sr. Member
Offline
Activity: 463
Merit: 252
Bitcore (BTX) - Your Payment Coin
|
|
March 23, 2017, 10:20:53 AM |
|
Alot of people are gonna hear about pivx after it hit $2. I can't believe I didn't buy in when it was 0.18 few days ago
|
|
|
|
linux_master
Newbie
Offline
Activity: 5
Merit: 0
|
|
March 23, 2017, 10:29:06 AM |
|
When you don't have enough, the process get's killed by the linux kernel.
of course I know it Is your ram limited by any chance?
of course, 512 Mb now, but how to determine which of config parameteres influences to the ram? pivx daemon like dash may be and bitcoin I think very gluttonous for ram but dash daemon more and more stable now, a lot of work has been done there and ok this discussion can be moved to pivx forum
|
|
|
|
lordzc
|
|
March 23, 2017, 10:47:26 AM |
|
How long will this ascension continue?
|
|
|
|
bitmaster1x
Legendary
Offline
Activity: 1274
Merit: 1000
CRYPTO-CITY.COM 🌟 Communities
|
|
March 23, 2017, 10:49:35 AM |
|
I just realized that this is just a re-branding of DNET. LoL
|
|
|
|
misterbones
Full Member
Offline
Activity: 182
Merit: 100
Trader*Investor
|
|
March 23, 2017, 10:52:21 AM |
|
DUMP INCOMING SOON
|
|
|
|
coinwider
Full Member
Offline
Activity: 184
Merit: 101
Put the fun back into banking!
|
|
March 23, 2017, 10:58:49 AM |
|
How long will this ascension continue? a Mars journey takes 6 months
|
Put the fun back into banking! Use cryptocurrencies. --- PivX --- TenX --- Lisk --- Factom --- Siacoin ---
|
|
|
ooom
Full Member
Offline
Activity: 165
Merit: 100
Learning is the beginning of wealth.
|
|
March 23, 2017, 11:15:53 AM |
|
Where can you use PIVX? Circulating supply: 7,181,585 DASH 52,537,624 PIVX Supply is a way to huge to reach an amazing price. I think anything above 5 dollar mark per PIVX will be highly over payed. Looking at today status of the project it's still needs a ton of development in various directions.
|
Disclaimer: My material is for informational purposes only. It should not be considered legal or financial advice. I do not make any guarantee or other promise as to any results that may be obtained from using my content.
|
|
|
LemonAndFriesOne
Legendary
Offline
Activity: 1050
Merit: 1000
|
|
March 23, 2017, 11:26:11 AM |
|
Can't wait until the next part of PIVx is released. Should be good
|
|
|
|
BitcoinFX
Legendary
Offline
Activity: 2646
Merit: 1720
https://youtu.be/DsAVx0u9Cw4 ... Dr. WHO < KLF
|
|
March 23, 2017, 11:41:29 AM |
|
When you don't have enough, the process get's killed by the linux kernel.
of course I know it Is your ram limited by any chance?
of course, 512 Mb now, but how to determine which of config parameteres influences to the ram? pivx daemon like dash may be and bitcoin I think very gluttonous for ram but dash daemon more and more stable now, a lot of work has been done there and ok this discussion can be moved to pivx forum 512 MB is low RAM. Check if you have a paging file (SWAP) set-up (if the following command returns blank then you don't have one)... Create a 1GB SWAP file (double the amount of physical RAM is the recommendation up to 2 GB physical RAM) sudo dd if=/dev/zero of=/swapfile bs=64M count=16 N.B. count=16 = 1GB SWAP (count=32 would create a 2GB SWAP etc.) You then need to make the paging file persistent on re-boot by adding the following line to the base of /etc/fstab. Open fstab ... /swapfile none swap sw 0 0 crtl + x (to save) Also adding the following lines to sysctl.conf will make the SWAP file more efficient on a server. Open sysctl.conf ... sudo nano /etc/sysctl.conf vm.swappiness = 60 vm.vfs_cache_pressure = 50 Again, crtl + x (to save) Now restart the wallet daemon. Hope it helps.
|
|
|
|
linux_master
Newbie
Offline
Activity: 5
Merit: 0
|
|
March 23, 2017, 11:49:44 AM |
|
When you don't have enough, the process get's killed by the linux kernel.
of course I know it Is your ram limited by any chance?
of course, 512 Mb now, but how to determine which of config parameteres influences to the ram? pivx daemon like dash may be and bitcoin I think very gluttonous for ram but dash daemon more and more stable now, a lot of work has been done there and ok this discussion can be moved to pivx forum 512 MB is low RAM. Check if you have a paging file (SWAP) set-up (if the following command returns blank then you don't have one)... Create a 1GB SWAP file (double the amount of physical RAM is the recommendation up to 2 GB physical RAM) sudo dd if=/dev/zero of=/swapfile bs=64M count=16 N.B. count=16 = 1GB SWAP (count=32 would create a 2GB SWAP etc.) You then need to make the paging file persistent on re-boot by adding the following line to the base of /etc/fstab. Open fstab ... /swapfile none swap sw 0 0 crtl + x (to save) Also adding the following lines to sysctl.conf will make the SWAP file more efficient on a server. Open sysctl.conf ... sudo nano /etc/sysctl.conf vm.swappiness = 60 vm.vfs_cache_pressure = 50 Again, crtl + x (to save) Now restart the wallet daemon. Hope it helps. yes its blank many thanks bro
|
|
|
|
iosemite
Newbie
Offline
Activity: 7
Merit: 0
|
|
March 23, 2017, 11:57:26 AM |
|
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! COMING PUMP !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
btc-e.com poloniex.com /88888888888888888888888888\ |88888888888888888888888888/ |~~____~~~~~~~~~"""""""""| / \_________/"""""""""""""\ / | \ \ / | 88 88 \ \ / | 88 88 \ \ / / \ | / | ________ \ | \ | \______/ / | /"\ \ \____________ / | | |__________\_ | | / / /""""\ \_------' '-------/ -- \____/,___________\ -------/ ------* | \ || | \ || | ^ \ || | | \ \ || | | \ \ || | | \ \ \| / /"""\/ / ------------- | | / |\--_ \____/___/ | |\-_ | | | \_ | | | \ | | | \_ | | | ----___ | | | \----------| / | | ----------""\ /"\--"--_| | | \ |_______/ \______________/ ) \___/
|
|
|
|
Arvydas77
|
|
March 23, 2017, 12:19:18 PM |
|
OMG, how I've missed such a great opportunity with PIVX.
|
|
|
|
Redni
|
|
March 23, 2017, 12:26:33 PM |
|
OMG, how I've missed such a great opportunity with PIVX.
It is never too late
|
|
|
|
|