Pages:
Author

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

newbie
Activity: 51
Merit: 0
Okay. Flash Fork at 607 - github updated. Binaries available shortly.


Binaries available. The Kimoto Gravity Well has us now.

To be sure i have the right one. Its version 0.8.53.0 unk?
legendary
Activity: 1470
Merit: 1030
Okay. Flash Fork at 607 - github updated. Binaries available shortly.


Binaries available. The Kimoto Gravity Well has us now.
hero member
Activity: 724
Merit: 500
I've also updated to the new build. The old worked, but with crashes. New build does not work at all. Ubuntu 13.10.

Code:
************************
EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_6system12system_errorEEEEE
context: unable to load ssl2 md5 routines
memorycoin in AppInit()
legendary
Activity: 1470
Merit: 1030
Okay. Flash Fork at 607 - github updated. Binaries available shortly.
full member
Activity: 212
Merit: 100
Is there a way to improve the mining increasing the use of ram? could improve performance?
currently always use 1G regardless of the number of threads.
thanks
hero member
Activity: 724
Merit: 500
Quote
tterminate called after throwing an instance of 'boost::exception_detail::clone_impl >'
what():  boost::thread_resource_error: Resource temporarily unavailable


does anyone getting this error in the deamon?

You're probably running out of memory; do you have more than 512 MiB per thread you're attempting to run (if you're mining -- not sure what might cause that if you're just running the wallet.)

You get this error also on 64GB systems after 1-2 hours.
sr. member
Activity: 420
Merit: 250
about 3 hours for #607 block
sr. member
Activity: 420
Merit: 250
+1

2 hours out of sync on block 606, and not syncing up, no matter which version.

same here.

We're at a high difficulty block that is taking a long time to solve. This is what the fork is designed to fix, but we're still 150 blocks out. It is not a particular problem though - if the blockchain slows down too much, we'll bring the fork forward.

150 blocks might be few days at this speed.
bring it forward:)
hero member
Activity: 658
Merit: 502
+1, the rcpthreads or port setting is only used when you remotely access the server. Not when mining.


It's not. Your built-in miner talk with client with rcp protocol



FaSan
legendary
Activity: 1470
Merit: 1030
+1

2 hours out of sync on block 606, and not syncing up, no matter which version.

same here.

We're at a high difficulty block that is taking a long time to solve. This is what the fork is designed to fix, but we're still 150 blocks out. It is not a particular problem though - if the blockchain slows down too much, we'll bring the fork forward.
hero member
Activity: 499
Merit: 500
Some of my miners out of sync on block 606 which according to the miners still synced is the correct block. I tryed downloadinf the new client but its the same, on the correct block but wont sync. If it just stuck because of such a long block time or do i need to do something?
+1

Same here.
hero member
Activity: 658
Merit: 502
Quote
tterminate called after throwing an instance of 'boost::exception_detail::clone_impl >'
what():  boost::thread_resource_error: Resource temporarily unavailable


does anyone getting this error in the deamon?

me too ,10 servers ,same error,and other errors

My miner is not working anymore with newest code. I get:

Code:
EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_6system12system_errorEEEEE       
context: unable to load ssl2 md5 routines       
memorycoin in AppInit()


What OS ?

Looking some openssl bug. Try to update openssl and openssl-dev packages



FaSan
hero member
Activity: 854
Merit: 539
Some of my miners out of sync on block 606 which according to the miners still synced is the correct block. I tryed downloadinf the new client but its the same, on the correct block but wont sync. If it just stuck because of such a long block time or do i need to do something?
+1
hero member
Activity: 724
Merit: 500
Delete the "rpcthreads" setting and use only the "genproclimit". It's the onlyone solution for now

This does not fix the problem. stop telling people this fixes the problem. you are filling this thread with FUD!

+1, the rcpthreads or port setting is only used when you remotely access the server. Not when mining.
sr. member
Activity: 420
Merit: 250
+1

2 hours out of sync on block 606, and not syncing up, no matter which version.

same here.
newbie
Activity: 23
Merit: 0

My miner is not working anymore with newest code. I get:

Code:
EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_6system12system_errorEEEEE       
context: unable to load ssl2 md5 routines       
memorycoin in AppInit()

Anyone else seeing this?

Are you getting this error when you start the wallet, or only when you start mining?

I added some more memory cleanup code a short time ago - might be related.
This is happening when starting ./bitcoind. I might be an exception here since I am on Manjaro/Arch Linux. The previous version worked though (at least it started).
legendary
Activity: 1470
Merit: 1030

My miner is not working anymore with newest code. I get:

Code:
EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_6system12system_errorEEEEE       
context: unable to load ssl2 md5 routines       
memorycoin in AppInit()

Anyone else seeing this?

Are you getting this error when you start the wallet, or only when you start mining?

I added some more memory cleanup code a short time ago - might be related.

Yes. I also see this

Can you try rolling back the last commit to see if that helps?
sr. member
Activity: 363
Merit: 250

My miner is not working anymore with newest code. I get:

Code:
EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_6system12system_errorEEEEE       
context: unable to load ssl2 md5 routines       
memorycoin in AppInit()

Anyone else seeing this?

Are you getting this error when you start the wallet, or only when you start mining?

I added some more memory cleanup code a short time ago - might be related.

Yes. I also see this
Pages:
Jump to: