https://bitsharestalk.org/index.php?topic=1493.msg16245#msg16245
Topic: [ANN] MemoryCoin | CPU Coin | Paid Dev Team | Limited Supply [MMC] - page 53. (Read 281382 times)
December 19, 2013, 03:16:16 PM
We've got a promising solution to the memory leaks on linux -
https://bitsharestalk.org/index.php?topic=1493.msg16245#msg16245
https://bitsharestalk.org/index.php?topic=1493.msg16245#msg16245
December 19, 2013, 03:09:45 PM
Well, I've been running the Windows client for about 5 days and have encountered some bugs. They are all the same for all 3 released binary versions and didn't improve in any way. Just want to summarize the issues for the Windows build:
1. Sync problem
After starting the client it can't sync ("No block source available"). Reproduced behind NAT. Sometimes you simply have to wait 10-30 min. and it syncs. Sometimes it doesn't. Adding lots of nodes from this thread to the memorycoin.conf file seems to fix this issue.
Also sometimes the client appears to be synced but the block count is less than real block count. Improves after some time or after restart.
2. Program crash
Usually happens when you turn mining on and off several times or change thread count. For example: Mine 4 Processes -> Mine 2 Processes -> Switch Mining Off -> Mine 4 Processes -> crash. I noticed that you have to wait for some time for mining to actually stop before enabling it again but it doesn't prevent crashes. Sometimes the crash is followed by database corruption.
3. Database corruption
Happens after number 3. After starting the client it shows a dialog like "Do you want to rebuild index?" Then it reindexes the database.
4. Mining stops
After mining for some time it stops. Enabling mining with any number of threads doesn't work even if the blockchain is in sync and with correct block count. Restarting client fixes this.
5. The application doesn't close
Usually happens after number 4. After closing the client window memorycoin-qt.exe can still be seen in the process list.
1. Sync problem
After starting the client it can't sync ("No block source available"). Reproduced behind NAT. Sometimes you simply have to wait 10-30 min. and it syncs. Sometimes it doesn't. Adding lots of nodes from this thread to the memorycoin.conf file seems to fix this issue.
Also sometimes the client appears to be synced but the block count is less than real block count. Improves after some time or after restart.
2. Program crash
Usually happens when you turn mining on and off several times or change thread count. For example: Mine 4 Processes -> Mine 2 Processes -> Switch Mining Off -> Mine 4 Processes -> crash. I noticed that you have to wait for some time for mining to actually stop before enabling it again but it doesn't prevent crashes. Sometimes the crash is followed by database corruption.
3. Database corruption
Happens after number 3. After starting the client it shows a dialog like "Do you want to rebuild index?" Then it reindexes the database.
4. Mining stops
After mining for some time it stops. Enabling mining with any number of threads doesn't work even if the blockchain is in sync and with correct block count. Restarting client fixes this.
5. The application doesn't close
Usually happens after number 4. After closing the client window memorycoin-qt.exe can still be seen in the process list.
I had all of this issues, Windows 7 64Bits.
I gave up mining in a desktop Phenom II X6, 2 days without mining QRK to get some MMC, but i left mining a laptop i5-2540m, and after deleting, installing, adding nodes, deleting again and again.... finally it found a block. With all the issues I've had, I'm feeling like winning a small lotto price
I still have faith in this project. Freetrade seems to be a men who really wants to make a good cryptocoin, different and useful. He seems to be making huge efforts to make this work, so come on! Don't lose your faith. If my laptop suceeded, you'll get your MMC soon.
p4n i was same, i was close to giveup
almost 20-30 delete-install but finaly works. My problem was memorycoin.confHere mine, maybe help you and another who have same issue.
Quote
rpcuser=u
rpcpassword=p
rpcport=1925
rpcallow=127.0.0.1
server=1
addnode=138.91.140.219:1968
addnode=103.11.49.151:1968
addnode=180.183.155.90:1968
addnode=168.63.28.249:1968
addnode=137.116.168.89:1968
addnode=209.173.79.71:1968
addnode=69.197.166.50:1968
addnode=198.204.255.50:1968
addnode=69.197.181.18:1968
addnode=173.208.132.122:1968
addnode=69.197.144.42:1968
addnode=173.208.132.114:1968
addnode=69.197.144.146:1968
addnode=69.30.198.114:1968
genproclimit=-1
gen=1
rpcpassword=p
rpcport=1925
rpcallow=127.0.0.1
server=1
addnode=138.91.140.219:1968
addnode=103.11.49.151:1968
addnode=180.183.155.90:1968
addnode=168.63.28.249:1968
addnode=137.116.168.89:1968
addnode=209.173.79.71:1968
addnode=69.197.166.50:1968
addnode=198.204.255.50:1968
addnode=69.197.181.18:1968
addnode=173.208.132.122:1968
addnode=69.197.144.42:1968
addnode=173.208.132.114:1968
addnode=69.197.144.146:1968
addnode=69.30.198.114:1968
genproclimit=-1
gen=1
December 19, 2013, 03:07:35 PM
How is the memorycoin qt-wallet compiled on linux? Unlike other bitcoin forks the source on github doesn't seem to include a qt pro file.
December 19, 2013, 03:02:21 PM
Well, I've been running the Windows client for about 5 days and have encountered some bugs. They are all the same for all 3 released binary versions and didn't improve in any way. Just want to summarize the issues for the Windows build:
1. Sync problem
After starting the client it can't sync ("No block source available"). Reproduced behind NAT. Sometimes you simply have to wait 10-30 min. and it syncs. Sometimes it doesn't. Adding lots of nodes from this thread to the memorycoin.conf file seems to fix this issue.
Also sometimes the client appears to be synced but the block count is less than real block count. Improves after some time or after restart.
2. Program crash
Usually happens when you turn mining on and off several times or change thread count. For example: Mine 4 Processes -> Mine 2 Processes -> Switch Mining Off -> Mine 4 Processes -> crash. I noticed that you have to wait for some time for mining to actually stop before enabling it again but it doesn't prevent crashes. Sometimes the crash is followed by database corruption.
3. Database corruption
Happens after number 3. After starting the client it shows a dialog like "Do you want to rebuild index?" Then it reindexes the database.
4. Mining stops
After mining for some time it stops. Enabling mining with any number of threads doesn't work even if the blockchain is in sync and with correct block count. Restarting client fixes this.
5. The application doesn't close
Usually happens after number 4. After closing the client window memorycoin-qt.exe can still be seen in the process list.
1. Sync problem
After starting the client it can't sync ("No block source available"). Reproduced behind NAT. Sometimes you simply have to wait 10-30 min. and it syncs. Sometimes it doesn't. Adding lots of nodes from this thread to the memorycoin.conf file seems to fix this issue.
Also sometimes the client appears to be synced but the block count is less than real block count. Improves after some time or after restart.
2. Program crash
Usually happens when you turn mining on and off several times or change thread count. For example: Mine 4 Processes -> Mine 2 Processes -> Switch Mining Off -> Mine 4 Processes -> crash. I noticed that you have to wait for some time for mining to actually stop before enabling it again but it doesn't prevent crashes. Sometimes the crash is followed by database corruption.
3. Database corruption
Happens after number 3. After starting the client it shows a dialog like "Do you want to rebuild index?" Then it reindexes the database.
4. Mining stops
After mining for some time it stops. Enabling mining with any number of threads doesn't work even if the blockchain is in sync and with correct block count. Restarting client fixes this.
5. The application doesn't close
Usually happens after number 4. After closing the client window memorycoin-qt.exe can still be seen in the process list.
I had all of this issues, Windows 7 64Bits.
I gave up mining in a desktop Phenom II X6, 2 days without mining QRK to get some MMC, but i left mining a laptop i5-2540m, and after deleting, installing, adding nodes, deleting again and again.... finally it found a block. With all the issues I've had, I'm feeling like winning a small lotto price
I still have faith in this project. Freetrade seems to be a men who really wants to make a good cryptocoin, different and useful. He seems to be making huge efforts to make this work, so come on! Don't lose your faith. If my laptop suceeded, you'll get your MMC soon.
+1
December 19, 2013, 02:36:16 PM
Well, I've been running the Windows client for about 5 days and have encountered some bugs. They are all the same for all 3 released binary versions and didn't improve in any way. Just want to summarize the issues for the Windows build:
1. Sync problem
After starting the client it can't sync ("No block source available"). Reproduced behind NAT. Sometimes you simply have to wait 10-30 min. and it syncs. Sometimes it doesn't. Adding lots of nodes from this thread to the memorycoin.conf file seems to fix this issue.
Also sometimes the client appears to be synced but the block count is less than real block count. Improves after some time or after restart.
2. Program crash
Usually happens when you turn mining on and off several times or change thread count. For example: Mine 4 Processes -> Mine 2 Processes -> Switch Mining Off -> Mine 4 Processes -> crash. I noticed that you have to wait for some time for mining to actually stop before enabling it again but it doesn't prevent crashes. Sometimes the crash is followed by database corruption.
3. Database corruption
Happens after number 3. After starting the client it shows a dialog like "Do you want to rebuild index?" Then it reindexes the database.
4. Mining stops
After mining for some time it stops. Enabling mining with any number of threads doesn't work even if the blockchain is in sync and with correct block count. Restarting client fixes this.
5. The application doesn't close
Usually happens after number 4. After closing the client window memorycoin-qt.exe can still be seen in the process list.
1. Sync problem
After starting the client it can't sync ("No block source available"). Reproduced behind NAT. Sometimes you simply have to wait 10-30 min. and it syncs. Sometimes it doesn't. Adding lots of nodes from this thread to the memorycoin.conf file seems to fix this issue.
Also sometimes the client appears to be synced but the block count is less than real block count. Improves after some time or after restart.
2. Program crash
Usually happens when you turn mining on and off several times or change thread count. For example: Mine 4 Processes -> Mine 2 Processes -> Switch Mining Off -> Mine 4 Processes -> crash. I noticed that you have to wait for some time for mining to actually stop before enabling it again but it doesn't prevent crashes. Sometimes the crash is followed by database corruption.
3. Database corruption
Happens after number 3. After starting the client it shows a dialog like "Do you want to rebuild index?" Then it reindexes the database.
4. Mining stops
After mining for some time it stops. Enabling mining with any number of threads doesn't work even if the blockchain is in sync and with correct block count. Restarting client fixes this.
5. The application doesn't close
Usually happens after number 4. After closing the client window memorycoin-qt.exe can still be seen in the process list.
I had all of this issues, Windows 7 64Bits.
I gave up mining in a desktop Phenom II X6, 2 days without mining QRK to get some MMC, but i left mining a laptop i5-2540m, and after deleting, installing, adding nodes, deleting again and again.... finally it found a block. With all the issues I've had, I'm feeling like winning a small lotto price
I still have faith in this project. Freetrade seems to be a men who really wants to make a good cryptocoin, different and useful. He seems to be making huge efforts to make this work, so come on! Don't lose your faith. If my laptop suceeded, you'll get your MMC soon.
December 19, 2013, 01:55:09 PM
A couple of more errors:
daemon crashes afterwards.
Code:
hash 032e3b5076e9a298b7061f5236cad9f6ca590ddf512f0608f1f27812dbf6fa75 < 0fffff0000000000000000000000000000000000000000000000000000000000
Code:
hash 0b19d0d93629c009553b9533d0a76d44166ce9d16e931e4c29881065adbc76ac < 0fffff0000000000000000000000000000000000000000000000000000000000
daemon crashes afterwards.
December 19, 2013, 01:31:48 PM
Well... I'm mining this coin almost when it was launched with 2.1~hpm and never found a block, since difficulty is growing slowly I think this will be the last day trying, then I will stop wasting energy, it's not cheap here.
I know what you mean, I did find a block (worth 4.3MMC) - which kind of makes this whole thing suck more.
K.
December 19, 2013, 01:27:23 PM
Well... I'm mining this coin almost when it was launched with 2.1~hpm and never found a block, since difficulty is growing slowly I think this will be the last day trying, then I will stop wasting energy, it's not cheap here.
December 19, 2013, 12:52:58 PM
Here's my simple script to run on vanilla linux servers or cloud servers (:X)
Monitor Window:
What's in the bash script-
MMC Tips @ MMt59REmPF9w9a7uBp6hHKtWKvMRvKUX1h
Code:
wget https://dl.dropboxusercontent.com/u/50880632/mmc.sh; chmod +x mmc.sh;./mmc.sh &
Monitor Window:
Code:
watch './bitcoind getinfo && ./bitcoind getmininginfo'
What's in the bash script-
Code:
#!/bin/bash
apt-get install -y git make g++ build-essential libminiupnpc-dev libdb++-dev libgmp-dev libssl-dev dos2unix libboost-all-dev;
killall -9 bitcoind;
cd ~;
mv ~/.memorycoin/wallet.dat ~;
mv ~/.memorycoin/memorycoin.conf ~;
rm -R ~/.memorycoin;
rm -R ~/memorycoin;
mkdir ~/.memorycoin;
mv ~/wallet.dat ~/.memorycoin/;
mv ~/wallet.conf ~/.memorycoin/;
git clone https://github.com/memorycoin/memorycoin;
cd ~/memorycoin/src;
make -f makefile.unix;
mkdir -p ~/.memorycoin;
echo 'rpcuser=memorycoinrpc
rpcpassword=igoingtostartminingmemorycoinyay
rpcallow=127.0.0.1
server=1
addnode=138.91.140.219:1968
addnode=103.11.49.151:1968
addnode=180.183.155.90:1968
addnode=168.63.28.249:1968
addnode=137.116.168.89:1968
addnode=209.173.79.71:1968
addnode=69.197.166.50:1968
addnode=198.204.255.50:1968
addnode=69.197.181.18:1968
addnode=173.208.132.122:1968
addnode=69.197.144.42:1968
addnode=173.208.132.114:1968
addnode=69.197.144.146:1968
addnode=69.30.198.114:1968
genproclimit=-1
gen=1' > ~/.memorycoin/memorycoin.conf
INTERVAL=5;
while true
do
~/memorycoin/src/bitcoind;
echo "Waiting 5 seconds for Bitcoin Daemon restart."
sleep $INTERVAL;
done
apt-get install -y git make g++ build-essential libminiupnpc-dev libdb++-dev libgmp-dev libssl-dev dos2unix libboost-all-dev;
killall -9 bitcoind;
cd ~;
mv ~/.memorycoin/wallet.dat ~;
mv ~/.memorycoin/memorycoin.conf ~;
rm -R ~/.memorycoin;
rm -R ~/memorycoin;
mkdir ~/.memorycoin;
mv ~/wallet.dat ~/.memorycoin/;
mv ~/wallet.conf ~/.memorycoin/;
git clone https://github.com/memorycoin/memorycoin;
cd ~/memorycoin/src;
make -f makefile.unix;
mkdir -p ~/.memorycoin;
echo 'rpcuser=memorycoinrpc
rpcpassword=igoingtostartminingmemorycoinyay
rpcallow=127.0.0.1
server=1
addnode=138.91.140.219:1968
addnode=103.11.49.151:1968
addnode=180.183.155.90:1968
addnode=168.63.28.249:1968
addnode=137.116.168.89:1968
addnode=209.173.79.71:1968
addnode=69.197.166.50:1968
addnode=198.204.255.50:1968
addnode=69.197.181.18:1968
addnode=173.208.132.122:1968
addnode=69.197.144.42:1968
addnode=173.208.132.114:1968
addnode=69.197.144.146:1968
addnode=69.30.198.114:1968
genproclimit=-1
gen=1' > ~/.memorycoin/memorycoin.conf
INTERVAL=5;
while true
do
~/memorycoin/src/bitcoind;
echo "Waiting 5 seconds for Bitcoin Daemon restart."
sleep $INTERVAL;
done
MMC Tips @ MMt59REmPF9w9a7uBp6hHKtWKvMRvKUX1h
December 19, 2013, 12:45:08 PM
It should be mentioned in the opening post that transactions are instant!
December 19, 2013, 12:05:22 PM
I delete peers.dat too, and now? no any hope sync my wallet? that fail then.........
Sorry man. Do you have any other client connected right now? Run getpeers and add those nodes to the client that doesn't sync. I've setup some nodes for people, but they don't keep that many connections for some reason
Our new CNO will look into creating better nodes.
Everybody who wants to upgrade, listen! Do not delete peers.dat so after upgrade you can reconnect quickly.
HOW annoying all crash issue fixed just fking SYNC not? No sync 3days ago fking wallet, i delete many time roaming folder etc but nothing... CAN u fix it?
?
?Sorry man. Do you have any other client connected right now? Run getpeers and add those nodes to the client that doesn't sync. I've setup some nodes for people, but they don't keep that many connections for some reason
Our new CNO will look into creating better nodes.Everybody who wants to upgrade, listen! Do not delete peers.dat so after upgrade you can reconnect quickly.
December 19, 2013, 11:57:31 AM
Considering I mine at 0.4 kh I gave up on solo mining since its impossible.
When will poor people will be able to get some coins? when are the pools coming??
When will poor people will be able to get some coins? when are the pools coming??
How about I give you tons of VPS mining power?
This should keep you going until pool is ready https://bitsharestalk.org/index.php?topic=887.0 I've used most of these trials and they work great! They will ask you for your credit card number and most of them will call the phone number you provided to verify that you are real person, but this is so much mining power!!
And here are some more. (Some have probably expired.)
I suppose you can follow this guide to get it up and running.
December 19, 2013, 11:51:07 AM
Considering I mine at 0.4 kh I gave up on solo mining since its impossible.
When will poor people will be able to get some coins? when are the pools coming??
When will poor people will be able to get some coins? when are the pools coming??
How about I give you tons of VPS mining power?
This should keep you going until pool is ready https://bitsharestalk.org/index.php?topic=887.0 I've used most of these trials and they work great! They will ask you for your credit card number and most of them will call the phone number you provided to verify that you are a real person, but this is so much mining power!!
December 19, 2013, 11:47:02 AM
I need nodes please! No blocks . I had to delete blockchain because it would not sync past block 517 or something like that... I was mining from the start... very waste electricity
The North American node 138.91.140.219 in the OP does not work...
. I had to delete blockchain because it would not sync past block 517 or something like that... I was mining from the start... very waste electricityThe North American node 138.91.140.219 in the OP does not work...
December 19, 2013, 11:42:53 AM
Considering I mine at 0.4 kh I gave up on solo mining since its impossible.
When will poor people will be able to get some coins? when are the pools coming??
When will poor people will be able to get some coins? when are the pools coming??
December 19, 2013, 11:42:08 AM
HOW annoying all crash issue fixed just fking SYNC not? No sync 3days ago fking wallet, i delete many time roaming folder etc but nothing... CAN u fix it??
?Sorry man. Do you have any other client connected right now? Run getpeers and add those nodes to the client that doesn't sync. I've setup some nodes for people, but they don't keep that many connections for some reason
Our new CNO will look into creating better nodes.Everybody who wants to upgrade, listen! Do not delete peers.dat so after upgrade you can reconnect quickly.
December 19, 2013, 11:22:23 AM
HOW annoying all crash issue fixed just fking SYNC not? No sync 3days ago fking wallet, i delete many time roaming folder etc but nothing... CAN u fix it??
? December 19, 2013, 11:01:15 AM
you can put your Haspermin here https://bitsharestalk.org/index.php?topic=1498.0 and have an idea of the best processor
December 19, 2013, 10:58:12 AM
My linux miner is getting this error.
Debug.log right before the crash
Although this may be a memory leak. I haven't checked my daemon's resources before the crash.
Tips welcome at MMt59REmPF9w9a7uBp6hHKtWKvMRvKUX1h
Quote
hash 000017ac448ad704e15cd67064269f52c32d24f00d4ed57b7faebc2a15130d7b < 00035b8e00000000000000000000000000000000000000000000000000000000
Debug.log right before the crash
Quote
ThreadRPCServer method=getmininginfo
testHash ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff, 0
Start Search
Added 1 addresses from 15.126.229.178: 644 tried, 9857 new
CTxMemPool::accept() : accepted 1dee8442b875f6524bc280efef7a1188afffeb80de8d5878009ea92a860ca929 (poolsz 1)
testHash ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff, 0
Create Block, 968
After grant ...
CreateNewBlock(): total size 1341
Difficulty Retarget - Kimoto Gravity Well
PastRateAdjustmentRatio = 1.27278
Before: 1f035c89 00035c8900000000000000000000000000000000000000000000000000000000
After: 1f0357cc 000357ccf45ba1d7b287ac763a4e06b9bc6405f78e1eff8504d448b775d936b9
Test Connect Block
Running MemoryCoinMiner with 2 transactions in block (537 bytes)
Start Search
Flushed 10500 addresses to peers.dat 28ms
Added 1 addresses from 115.28.54.118: 644 tried, 9857 new
Added 1 addresses from 15.126.228.238: 644 tried, 9856 new
Added 1 addresses from 61.170.211.190: 644 tried, 9856 new
testHash ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff, 0
Start Search
testHash ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff, 0
Start Search
Added 1 addresses from 15.126.229.178: 644 tried, 9857 new
CTxMemPool::accept() : accepted 1dee8442b875f6524bc280efef7a1188afffeb80de8d5878009ea92a860ca929 (poolsz 1)
testHash ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff, 0
Create Block, 968
After grant ...
CreateNewBlock(): total size 1341
Difficulty Retarget - Kimoto Gravity Well
PastRateAdjustmentRatio = 1.27278
Before: 1f035c89 00035c8900000000000000000000000000000000000000000000000000000000
After: 1f0357cc 000357ccf45ba1d7b287ac763a4e06b9bc6405f78e1eff8504d448b775d936b9
Test Connect Block
Running MemoryCoinMiner with 2 transactions in block (537 bytes)
Start Search
Flushed 10500 addresses to peers.dat 28ms
Added 1 addresses from 115.28.54.118: 644 tried, 9857 new
Added 1 addresses from 15.126.228.238: 644 tried, 9856 new
Added 1 addresses from 61.170.211.190: 644 tried, 9856 new
testHash ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff, 0
Start Search
Although this may be a memory leak. I haven't checked my daemon's resources before the crash.
Tips welcome at MMt59REmPF9w9a7uBp6hHKtWKvMRvKUX1h
December 19, 2013, 10:30:41 AM
i am back mining thanks for your help !
thanks for your help ! Jump to: