Pages:
Author

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

sr. member
Activity: 292
Merit: 250
I upgraded to v8.55 wallet on my linux pc. Now keep getting this error after about 20mins of mining.

Error Message
------------------
terminate called after throwing an instance of 'boost::exception_detail::clone_impl >'
  what():  boost: mutex lock failed in pthread_mutex_lock: Invalid argument

I haven't had this problem with v8.54. So what's wrong?
Would you please try changing 128 in init.cpp line 541 to 1024, recompiling and running once more? (I am the one to blame for this crash)

Ok so I'm still getting the same error after making the mentioned changes. What now?
sr. member
Activity: 292
Merit: 250
Would you please try changing 128 in init.cpp line 541 to 1024, recompiling and running once more? (I am the one to blame for this crash)

So I changed the code and recompiled and started the daemon (gen=0).

When I run ./bitcoind getinfo I get this: error: {"code":-1,"message":"ReserveKeyFromKeyPool() : read failed"}

When I try running ./bitcoind getinfo again I get this: error: {"code":-1,"message":"CDB() : can't open database file wallet.dat, error -30973"}

Is my wallet.dat now corrupted???
On the bright side, if you had any values there, they can most probably be recovered by pywallet.

Ok, I suppose I'm very lucky. Just transferred all my mmcs to another wallet before all these issues happened. So now new wallet and mining again. Will see if any issues happen again. Thanks reorder.
sr. member
Activity: 462
Merit: 250
Would you please try changing 128 in init.cpp line 541 to 1024, recompiling and running once more? (I am the one to blame for this crash)

So I changed the code and recompiled and started the daemon (gen=0).

When I run ./bitcoind getinfo I get this: error: {"code":-1,"message":"ReserveKeyFromKeyPool() : read failed"}

When I try running ./bitcoind getinfo again I get this: error: {"code":-1,"message":"CDB() : can't open database file wallet.dat, error -30973"}

Is my wallet.dat now corrupted???
On the bright side, if you had any values there, they can most probably be recovered by pywallet.
sr. member
Activity: 462
Merit: 250
Would you please try changing 128 in init.cpp line 541 to 1024, recompiling and running once more? (I am the one to blame for this crash)

So I changed the code and recompiled and started the daemon (gen=0).

When I run ./bitcoind getinfo I get this: error: {"code":-1,"message":"ReserveKeyFromKeyPool() : read failed"}

When I try running ./bitcoind getinfo again I get this: error: {"code":-1,"message":"CDB() : can't open database file wallet.dat, error -30973"}

Is my wallet.dat now corrupted???
Yes, but not exactly due to this reason, any crash hash high chance to corrupt it.
sr. member
Activity: 292
Merit: 250
Would you please try changing 128 in init.cpp line 541 to 1024, recompiling and running once more? (I am the one to blame for this crash)

So I changed the code and recompiled and started the daemon (gen=0).

When I run ./bitcoind getinfo I get this: error: {"code":-1,"message":"ReserveKeyFromKeyPool() : read failed"}

When I try running ./bitcoind getinfo again I get this: error: {"code":-1,"message":"CDB() : can't open database file wallet.dat, error -30973"}

Is my wallet.dat now corrupted???
sr. member
Activity: 462
Merit: 250
I upgraded to v8.55 wallet on my linux pc. Now keep getting this error after about 20mins of mining.

Error Message
------------------
terminate called after throwing an instance of 'boost::exception_detail::clone_impl >'
  what():  boost: mutex lock failed in pthread_mutex_lock: Invalid argument

I haven't had this problem with v8.54. So what's wrong?
Would you please try changing 128 in init.cpp line 541 to 1024, recompiling and running once more? (I am the one to blame for this crash)
sr. member
Activity: 292
Merit: 250
I upgraded to v8.55 wallet on my linux pc. Now keep getting this error after about 20mins of mining.

Error Message
------------------
terminate called after throwing an instance of 'boost::exception_detail::clone_impl >'
  what():  boost: mutex lock failed in pthread_mutex_lock: Invalid argument

I haven't had this problem with v8.54. So what's wrong?
sr. member
Activity: 1274
Merit: 250
PredX - AI-Powered Prediction Market
EC2 cc2.8xlarge

[17:09:31] Found share ...43e17022aa393528: submitting
[17:09:31] Stats: 10.095 hash/min
[17:09:31] PROOF OF WORK RESULT: Accepted
[17:09:34] Found solution - 8427 / 1968 / 2552121027
[17:09:35] Found solution - 2918 / 1968 / 2626787225
[17:09:37] Found share ...e6282adbcfa91429: submitting
[17:09:37] Stats: 10.068 hash/min
[17:09:37] PROOF OF WORK RESULT: Accepted
[17:09:39] Found solution - 620 / 1968 / 4175850305
[17:09:40] Found solution - 4261 / 1968 / 4253120609
[17:09:42] Found solution - 856 / 1968 / 181299850
[17:09:42] Found solution - 14702 / 1968 / 2551600901
[17:09:42] Found solution - 15246 / 1968 / 473877606
[17:09:43] Found solution - 3519 / 1968 / 2346623495
[17:09:43] Found share ...a3f785b287402476: submitting
[17:09:43] Stats: 10.068 hash/min
[17:09:44] PROOF OF WORK RESULT: Accepted


Smiley

3 in a row within one minute? That sounds odd.

I am not solo mining.
full member
Activity: 140
Merit: 100
EC2 cc2.8xlarge

[17:09:31] Found share ...43e17022aa393528: submitting
[17:09:31] Stats: 10.095 hash/min
[17:09:31] PROOF OF WORK RESULT: Accepted
[17:09:34] Found solution - 8427 / 1968 / 2552121027
[17:09:35] Found solution - 2918 / 1968 / 2626787225
[17:09:37] Found share ...e6282adbcfa91429: submitting
[17:09:37] Stats: 10.068 hash/min
[17:09:37] PROOF OF WORK RESULT: Accepted
[17:09:39] Found solution - 620 / 1968 / 4175850305
[17:09:40] Found solution - 4261 / 1968 / 4253120609
[17:09:42] Found solution - 856 / 1968 / 181299850
[17:09:42] Found solution - 14702 / 1968 / 2551600901
[17:09:42] Found solution - 15246 / 1968 / 473877606
[17:09:43] Found solution - 3519 / 1968 / 2346623495
[17:09:43] Found share ...a3f785b287402476: submitting
[17:09:43] Stats: 10.068 hash/min
[17:09:44] PROOF OF WORK RESULT: Accepted


Smiley

3 in a row within one minute? That sounds odd.
full member
Activity: 238
Merit: 100
Superressistant who longed for MMC, beholds with pain
The tempting clusters were too high to gain;
Grieved in his heart he forced a careless smile,
And cried ,‘The specs are to high and hardly worth my while.’
sr. member
Activity: 1274
Merit: 250
PredX - AI-Powered Prediction Market
EC2 cc2.8xlarge

[17:09:31] Found share ...43e17022aa393528: submitting
[17:09:31] Stats: 10.095 hash/min
[17:09:31] PROOF OF WORK RESULT: Accepted
[17:09:34] Found solution - 8427 / 1968 / 2552121027
[17:09:35] Found solution - 2918 / 1968 / 2626787225
[17:09:37] Found share ...e6282adbcfa91429: submitting
[17:09:37] Stats: 10.068 hash/min
[17:09:37] PROOF OF WORK RESULT: Accepted
[17:09:39] Found solution - 620 / 1968 / 4175850305
[17:09:40] Found solution - 4261 / 1968 / 4253120609
[17:09:42] Found solution - 856 / 1968 / 181299850
[17:09:42] Found solution - 14702 / 1968 / 2551600901
[17:09:42] Found solution - 15246 / 1968 / 473877606
[17:09:43] Found solution - 3519 / 1968 / 2346623495
[17:09:43] Found share ...a3f785b287402476: submitting
[17:09:43] Stats: 10.068 hash/min
[17:09:44] PROOF OF WORK RESULT: Accepted


Smiley
member
Activity: 98
Merit: 10
it sounds good because of its differentce

there are so many script coins
sr. member
Activity: 1274
Merit: 250
PredX - AI-Powered Prediction Market
Amazon paid Spot instance, cc2.8 Large.


As a cautionary note to anyone who may even think about abusing the free $200 AWS credit using fake/temp CC numbers, don't even bother.  

Amazon considers that "deliberate" theft of service and has been sending law enforcement to peoples' doors.  


Also, 1.286k CAT coins for sale.

Just requested same Spot.....lets see Cheesy
member
Activity: 93
Merit: 10
Impossible to solo mine with current difficulty, but the only polo is so buggy that almost never works. Better just mine another coin and stop wasting time.
legendary
Activity: 2156
Merit: 1131
Anyone having problem on mmcpool.com ?
All shares are refused for hours.
How to fix it ?
legendary
Activity: 854
Merit: 1000
Amazon paid Spot instance, cc2.8 Large.


As a cautionary note to anyone who may even think about abusing the free $200 AWS credit using fake/temp CC numbers, don't even bother.  

Amazon considers that "deliberate" theft of service and has been sending law enforcement to peoples' doors.  


Also, 1.286k CAT coins for sale.
sr. member
Activity: 1274
Merit: 250
PredX - AI-Powered Prediction Market
And the Amazon ec2 cc2.8 Large

[13:45:43] Stats: 10.095 hash/min
[13:45:46] PROOF OF WORK RESULT: Accepted

Not bad.

$2.400 per Hour???

Naw, @ .456/h

Which Instance Type? I am seeing $2.400 per Hour for On-Demand Instances.
legendary
Activity: 854
Merit: 1000
And the Amazon ec2 cc2.8 Large

[13:45:43] Stats: 10.095 hash/min
[13:45:46] PROOF OF WORK RESULT: Accepted

Not bad.

$2.400 per Hour???

Naw, @ .456/h
sr. member
Activity: 1274
Merit: 250
PredX - AI-Powered Prediction Market
And the Amazon ec2 cc2.8 Large

[13:45:43] Stats: 10.095 hash/min
[13:45:46] PROOF OF WORK RESULT: Accepted

Not bad.

$2.400 per Hour???
legendary
Activity: 854
Merit: 1000
wow, HT makes that much of a difference?  Shocked
Pages:
Jump to: