Topic: [ANN] MemoryCoin | CPU Coin | Paid Dev Team | Limited Supply [MMC] - page 54. (Read 281387 times)

Seems like people are still having this issue of getting stuck.  Here's my solution hope it works for you.

1) make sure you have latest build v0.8.54.0-unk-beta
2) if you're getting stuck per se, go to the the path where the appdata is contained.  in my case it's C:\Users\abuchanan\AppData\Roaming\MemoryCoin so yours will most likely be C:\Users\[WINDOWS_USERNAME]\AppData\Roaming\MemoryCoin
3) Go and delete everything in there except wallet.dat and peers.dat
4) start up the memorycoin.exe again and let it sync back up from day 0 to now.
5) should be fine after this, if not addnodes...add more nodes...oh an keep adding nodes wait a bit and you should be okay.

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.

These are some of the pains when adopting a new coin, early bugs.

So I had download the update for a fork at 7xx(can't remember what it was) and thought everything was fine. Didn't notice that you had decided to emergency fork it at 607.

Came home yesterday and was excited to have finally found a block. It wasn't real, though.

How was I supposed to know that you would decide to fork it 100 blocks earlier......

I'm really disappointed in this coin. I've been mining since the release and I'm done.

Same here- deleted the old block chain and takes forever to load the block and crashes... exact same operation on the linux box and it was up and running in a few minutes.

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.

ThreadRPCServer method=getmininginfo
testHash ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff, 0
Start Search
ThreadRPCServer method=getinfo
keypool reserve 3
keypool return 3
ThreadRPCServer method=getmininginfo
ThreadRPCServer method=getinfo
keypool reserve 3
keypool return 3
ThreadRPCServer method=getmininginfo
ThreadRPCServer method=getinfo
keypool reserve 3
keypool return 3
ThreadRPCServer method=getmininginfo
found solution - 814 / 1968 / 239863267
ThreadRPCServer method=getinfo
keypool reserve 3
keypool return 3
ThreadRPCServer method=getmininginfo
ThreadRPCServer method=getinfo
keypool reserve 3
keypool return 3
ThreadRPCServer method=getmininginfo
testHash 8483376418dfb5403da6e6eff6d4f11215dbb1cc1eb6e16028d276a5494597b8, 1
Start Search
ThreadRPCServer method=getinfo
keypool reserve 3
keypool return 3
ThreadRPCServer method=getmininginfo



MemoryCoin version v0.8.5-59-g2806f95-beta (2013-12-18 17:42:32 +0700)
Using OpenSSL version OpenSSL 1.0.1e 11 Feb 2013
Startup time: 2013-12-19 13:29:28
Default data directory /root/.memorycoin
Using data directory /root/.memorycoin
Using at most 125 connections (1024 file descriptors available)
Using 16 threads for script verification
init message: Verifying wallet...
dbenv.open LogDir=/root/.memorycoin/database ErrorFile=/root/.memorycoin/db.log
Bound to [::]:1968
Bound to 0.0.0.0:1968
init message: Loading block index...
Opening LevelDB in /root/.memorycoin/blocks/index
Opened LevelDB successfully
Opening LevelDB in /root/.memorycoin/chainstate
Opened LevelDB successfully
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: LoadBlockIndex() : CheckIndex failed: CBlockIndex(pprev=0x7f2d88810960, pnext=(nil), nHeight=860, merkle=5673807da71bc8de6f7f9d5e618e3dd05bbf901b088742cd2383596eb7a8332f, hashBlock=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff)
: Error loading block database.
Do you want to rebuild the block database now?
Flush(false)
DBFlush(false) ended               0ms
StopNode()
Flushed 0 addresses to peers.dat  2ms
Committing 0 changed transactions to coin database...

Thanks! It's very helpful to get detailed bug reports like these. Do you have an address for tips?

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.

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.

I need to set 3 cores of 4.

test  pls

then you're using hole capacity i guess

How to use 3 CPU cores?

"setgenerate true 3" doesn't set cores to 3