1
MemoryCoin / Re: Linux miner crashing on regular basis
« on: December 20, 2013, 03:16:11 pm »Thanks for the tip! Do you have a MC address for tips?
MLbH5YtCB73CYN375EMMfywN18emFPjDxm
thank you very much!
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
MLbH5YtCB73CYN375EMMfywN18emFPjDxm
thank you very much!
2
MemoryCoin / Re: Linux miner crashing on regular basis
« on: December 19, 2013, 08:20:06 pm »
I'm 99% sure I've found the solution to prevent all the crashes that happen on linux.
For two days the client crashed regularly. After my fix not a single crash or database corruption in 8 hours!!
The crash and database damage happen only if the client is run more than once at the same time.
Now you may ask, why run the client a second time?
A lot of people do it, to read the status from the client, meaning ...
a script starts bitcoind --daemon
but then either another script, cron, or manual command line is used in this way:
watch 'bitcoind getmininginfo & bitcoind listaccounts'
and this watch command calls bitcoind every two seconds, and there is a small chance that the daemon will crash. or it's caused by a memory leak, but not by the deamon, but by the getmininginfo call performed every 2 seconds!
I've disabled my watch script on all 5 linux instances, did no other chances whatsoever (besides a reset to make sure the damage done by watch/getmininginfo is gone), and after 2 days full of crashes, not a single memorycoin daemon crash, in over 8 hours of mining!
I hope this helps.
For two days the client crashed regularly. After my fix not a single crash or database corruption in 8 hours!!
The crash and database damage happen only if the client is run more than once at the same time.
Now you may ask, why run the client a second time?
A lot of people do it, to read the status from the client, meaning ...
a script starts bitcoind --daemon
but then either another script, cron, or manual command line is used in this way:
watch 'bitcoind getmininginfo & bitcoind listaccounts'
and this watch command calls bitcoind every two seconds, and there is a small chance that the daemon will crash. or it's caused by a memory leak, but not by the deamon, but by the getmininginfo call performed every 2 seconds!
I've disabled my watch script on all 5 linux instances, did no other chances whatsoever (besides a reset to make sure the damage done by watch/getmininginfo is gone), and after 2 days full of crashes, not a single memorycoin daemon crash, in over 8 hours of mining!
I hope this helps.
3
MemoryCoin / Re: Linux miner crashing on regular basis
« on: December 18, 2013, 06:10:22 pm »
I get the crashes regularly on Ubuntu 13.10 x64. 32 Cores (Xeon) with 64 GB RAM. Sometimes it's enough to restart daemon, sometimes bitcoind -resync helps, sometimes only a deletion of database.
When the database corruption occurs and I restart with bitcoind -resync I get this:
Do you want to rebuild the block database now?
bitcoind: db/version_set.cc:715: leveldb::VersionSet::~VersionSet(): Assertion `dummy_versions_.next_ == &dummy_versions_' failed.
If I answer with
y
I get
y: command not found
so have to delete the database manually.
---
ubuntu@ip-172-31-18-71:~$ apt-file search libssl.so
libssl-dev: /usr/lib/x86_64-linux-gnu/libssl.so
libssl0.9.8: /lib/x86_64-linux-gnu/libssl.so.0.9.8
libssl0.9.8: /usr/lib/x86_64-linux-gnu/libssl.so.0.9.8
libssl0.9.8-dbg: /usr/lib/debug/lib/x86_64-linux-gnu/libssl.so.0.9.8
libssl1.0.0: /lib/x86_64-linux-gnu/libssl.so.1.0.0
libssl1.0.0-dbg: /usr/lib/debug/lib/x86_64-linux-gnu/libssl.so.1.0.0
--
before compiling installed libssl this way:
apt-get install -y libssl-dev
p.s.
Solving a difficult captcha before posting is extremely annoying! I bet 90% users do not post because of this.
When the database corruption occurs and I restart with bitcoind -resync I get this:
Do you want to rebuild the block database now?
bitcoind: db/version_set.cc:715: leveldb::VersionSet::~VersionSet(): Assertion `dummy_versions_.next_ == &dummy_versions_' failed.
If I answer with
y
I get
y: command not found
so have to delete the database manually.
---
ubuntu@ip-172-31-18-71:~$ apt-file search libssl.so
libssl-dev: /usr/lib/x86_64-linux-gnu/libssl.so
libssl0.9.8: /lib/x86_64-linux-gnu/libssl.so.0.9.8
libssl0.9.8: /usr/lib/x86_64-linux-gnu/libssl.so.0.9.8
libssl0.9.8-dbg: /usr/lib/debug/lib/x86_64-linux-gnu/libssl.so.0.9.8
libssl1.0.0: /lib/x86_64-linux-gnu/libssl.so.1.0.0
libssl1.0.0-dbg: /usr/lib/debug/lib/x86_64-linux-gnu/libssl.so.1.0.0
--
before compiling installed libssl this way:
apt-get install -y libssl-dev
p.s.
Solving a difficult captcha before posting is extremely annoying! I bet 90% users do not post because of this.
4
MemoryCoin / Re: Distribution At Block 32000 - MemoryCoin 2.0
« on: December 14, 2013, 07:50:36 am »
Please don't rush the release. There is already bad talk because of botching MC 1.0. It does not matter if 2.0 is released today or a week later. It's important that the start is well planned.
Pages: [1]
