FreeTrade (OP)
Legendary
Offline
Activity: 1428
Merit: 1030
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 19, 2013, 12:15:19 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.
Thanks! It's very helpful to get detailed bug reports like these. Do you have an address for tips?
|
Membercoin - Layer 1 Coin used for the member.cash decentralized social network. 10% Interest On All Balances. Browser and Solo Mining. 100% Distributed to Users and Developers.
|
|
|
Riseman
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 19, 2013, 12:20:22 PM |
|
Thanks! It's very helpful to get detailed bug reports like these. Do you have an address for tips?
MMC: MUWGuy3eWwnDWw3bUMK2DcW2cESvwv72r9 Thanks!
|
|
|
|
reaxion
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 66
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 19, 2013, 12:46:03 PM |
|
i left my miner running yesterday after the update to 0.8.54 when i returned today the miner had stopped being responsive to commands and it had lost sync with the network at somepoint yesterday. upon closing and restarting it said i needed to recompile so i deleted all in the appdata folder and tried to resync i tried reloading but no connections found in about 5 mins so i restarted a couple more times then just left it open ... after about 20 mins of no connections and it being 3 days behind i have just seen it change i have 2 connection and its resyncing slowly in case anyone has had same problem you just need to be patient it will resync slowly Hopefully i will be back on soon hunting for my first reward ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
|
reaxion
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 66
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 19, 2013, 12:47:52 PM |
|
I need to add i also had manually to cancel the process of the MemorycoinQt in task manager to restart it
|
|
|
|
Delinquency
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 19, 2013, 01:33:14 PM Last edit: December 19, 2013, 01:45:00 PM by Delinquency |
|
Glitch when restarting after crash. Happened twice. had to clean the block chain and chainstate folders and rebuild to fix. 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...
|
|
|
|
reaxion
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 66
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 19, 2013, 01:48:06 PM |
|
mine keep stalling at 2 days to go - no block source also when my memorycoinqt starts its already mining with 8 processes so i have to stop it.
it was all working great till the updates other than major difficulty jumps
anyone know of a solution ?
|
|
|
|
nomullet
Newbie
Offline
Activity: 22
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 19, 2013, 01:50:01 PM |
|
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.
|
|
|
|
Delinquency
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 19, 2013, 02:03:21 PM |
|
please post your debug logs so that the devs can fix asap. 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.
|
|
|
|
RejectKid
Newbie
Offline
Activity: 10
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 19, 2013, 02:06:27 PM |
|
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.
|
|
|
|
CleverCraftsman
Newbie
Offline
Activity: 14
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 19, 2013, 02:10:05 PM |
|
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.
|
|
|
|
Delinquency
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 19, 2013, 02:12:53 PM |
|
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.
These are some of the pains when adopting a new coin, early bugs.
|
|
|
|
CleverCraftsman
Newbie
Offline
Activity: 14
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 19, 2013, 02:58:04 PM |
|
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.
These are some of the pains when adopting a new coin, early bugs. I know, I know. I just can't keep running my friends' computers (with their permission) at full blast only to find out it's gotten out of sync with the blockchain or that a new fork has been released immediately. I don't have the time for it. I think I'm still going to keep working on making a working Mac client that I can release for those who would be interested. I wish I knew more about miner development so I can help out with that.
|
|
|
|
automake
Newbie
Offline
Activity: 22
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 19, 2013, 03:08:00 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.
i can confirm all of these issues, too
|
|
|
|
belltown
Sr. Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 301
Merit: 250
still can't change my profile pic
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 19, 2013, 03:08:40 PM |
|
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.
Yes, this is the right solution. Already on www.MemoryCoin.info, see "does't sync after update?" Everybody, please follow these instructions.
|
|
|
|
reaxion
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 66
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 19, 2013, 03:30:41 PM |
|
i am back mining ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) thanks for your help !
|
|
|
|
Delinquency
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 19, 2013, 03:58:12 PM |
|
My linux miner is getting this error. hash 000017ac448ad704e15cd67064269f52c32d24f00d4ed57b7faebc2a15130d7b < 00035b8e00000000000000000000000000000000000000000000000000000000 Debug.log right before the crash 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 Although this may be a memory leak. I haven't checked my daemon's resources before the crash. Tips welcome at MMt59REmPF9w9a7uBp6hHKtWKvMRvKUX1h
|
|
|
|
|
iDoge
Newbie
Offline
Activity: 40
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 19, 2013, 04:22:23 PM |
|
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? ![Huh](https://bitcointalk.org/Smileys/default/huh.gif) ?
|
|
|
|
belltown
Sr. Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 301
Merit: 250
still can't change my profile pic
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 19, 2013, 04:42:08 PM |
|
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? ![Huh](https://bitcointalk.org/Smileys/default/huh.gif) ? 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 ![Sad](https://bitcointalk.org/Smileys/default/sad.gif) 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.
|
|
|
|
giveBTCpls
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 19, 2013, 04:42:53 PM |
|
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??
|
|
|
|
|