Bitcoin Forum
December 10, 2016, 05:10:26 AM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: [SOLVED] Bitcoin taking up 100% CPU constantly!  (Read 1181 times)
Luke-Jr
Legendary
*
Offline Offline

Activity: 2100



View Profile
July 01, 2012, 10:52:36 PM
 #1

This is the Linux leapsecond bug. To fix it, either reboot or run (with proper permissions):
Code:
date -s "`date`"

1481346626
Hero Member
*
Offline Offline

Posts: 1481346626

View Profile Personal Message (Offline)

Ignore
1481346626
Reply with quote  #2

1481346626
Report to moderator
1481346626
Hero Member
*
Offline Offline

Posts: 1481346626

View Profile Personal Message (Offline)

Ignore
1481346626
Reply with quote  #2

1481346626
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
Xenland
Legendary
*
Offline Offline

Activity: 980


I'm not just any shaman, I'm a Sha256man


View Profile
July 02, 2012, 01:17:33 AM
 #2

Good thing my kernel is the newest version!
Luke-Jr
Legendary
*
Offline Offline

Activity: 2100



View Profile
July 02, 2012, 01:20:30 AM
 #3

Good thing my kernel is the newest version!
AFAIK this bug affects all versions of Linux presently...

justusranvier
Legendary
*
Offline Offline

Activity: 1400



View Profile WWW
July 02, 2012, 01:28:35 AM
 #4

Good thing my kernel is the newest version!
AFAIK this bug affects all versions of Linux presently...
https://it.slashdot.org/story/12/06/30/2123248/the-leap-second-is-here-are-your-systems-ready

That article claims it's only versions prior to 2.6.39.
Luke-Jr
Legendary
*
Offline Offline

Activity: 2100



View Profile
July 02, 2012, 02:00:24 AM
 #5

Good thing my kernel is the newest version!
AFAIK this bug affects all versions of Linux presently...
https://it.slashdot.org/story/12/06/30/2123248/the-leap-second-is-here-are-your-systems-ready

That article claims it's only versions prior to 2.6.39.
No, it says the last time was prior to 2.6.29.

gmaxwell
Staff
Legendary
*
Offline Offline

Activity: 2030



View Profile
July 02, 2012, 02:47:20 AM
 #6

That article claims it's only versions prior to 2.6.39.

I observed it on 3.3.7-1.fc16.x86_64 and 3.4.2-4.fc17.x86_64.  Not all vulnerable systems hit it, it depended on the system load at the time of the leapsecond.
Xenland
Legendary
*
Offline Offline

Activity: 980


I'm not just any shaman, I'm a Sha256man


View Profile
July 02, 2012, 02:51:01 AM
 #7

Good thing my kernel is the newest version!
AFAIK this bug affects all versions of Linux presently...
https://it.slashdot.org/story/12/06/30/2123248/the-leap-second-is-here-are-your-systems-ready

That article claims it's only versions prior to 2.6.39.
No, it says the last time was prior to 2.6.29.

I'll admit I read it the other way.



That article claims it's only versions prior to 2.6.39.

I observed it on 3.3.7-1.fc16.x86_64 and 3.4.2-4.fc17.x86_64.  Not all vulnerable systems hit it, it depended on the system load at the time of the leapsecond.

and assumed it was that because I never experienced any problems but really was probably similar to this observation^
fuzzster
Newbie
*
Offline Offline

Activity: 19


View Profile
May 29, 2013, 06:34:55 AM
 #8

My Bitcoin daemon has started taking up 100% CPU as mentioned here (a restart of the daemon fixes it for half a day, but the same keeps happening).

I'm not sure how this does anything when the date on my system is correct (when running 'date')?

Could this still be a possible solution? And does it affect the current block I am mining? As I am 80% through and don't want anything to reset!

Thanks.
Blowfeld
Jr. Member
*
Offline Offline

Activity: 53



View Profile
May 30, 2013, 06:39:55 AM
 #9

My Bitcoin daemon has started taking up 100% CPU as mentioned here

No leapseconds recently, so this thread is probably not your problem.  [Maybe fuzzter's query should be a separate thread?]

My Bitcoin 0.7.2 client began spending its time at 100% CPU busy a couple of weeks ago.  I was forced to shutdown my client.  Whatever is causing this is effectively a form of DOS, in my opinion.

My client has contained the vanity address for "correct horse battery staple" for many months.  [It's been interesting to watch tiny deposits appear and disappear from the account.]  I suspect the problem is related to the recent block-chain spam involving this vanity address.  Unfortunately, if the standard client provides a method of completely and totally expunging an address from the wallet, I haven't found it.  (I'm aware of a third-party tool to do the job.)  This seems like a pretty serious limitation (and DOS vulnerability) of the reference-standard client.

Coincidentally, at about the same time, my client has been displaying a "nag" message saying "Action required: see http://bitcoin.org/may15.html for more information".  I've already taken the other mitigation steps, but my client continues to be nag me.]

It's probably the block-chain spam causing the 100% CPU?  Maybe it's the nag message causing the 100% CPU?  Or maybe it's some combination of these factors.

BTW, after having had my wallet offline for a little over a week, my client consumed 318 minutes of a modern i7's CPU time over the last ~5.5 hours.  The wallet is now synchronized, but every time I blink, it goes back to 100% CPU busy for minutes at a time.  I can't imagine what the client might be doing that could *possibly* take 318 minutes of a modern CPU's time!

1BLowmewTGDsLYEAbvenZCcEnLJzwuFssX
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!