Topic: bitcoin daemon becomes completely unresponsive (Read 507 times)

All,

Very recently I have run into an issue with my bitcoin daemon.  I am wondering if it might have to do with the pool software I'm running on top of it, and will likely ask this same question if I can find a forum thread for the pool .  Here's what I notice:

1) I start up the bitcoin daemon process and all is happy.
2) After about 24 hours, the process becomes completely unresponsive.  Typing:
Or any other command just hangs without returning.
3) This causes all kinds of havoc on my pool.  Website runs exceptionally slow.  I get bombarded with mail from the cron jobs saying they're already running.  Things like that.  When I look at my debug.log, all I see is it trying to create new blocks:
The fact that it's trying to create a new block every 6 seconds seems a bit odd, but looking at the log shows that is pretty consistently happening, even when things are running smoothly.

My only recourse is to kill the process and restart it.  Doing so makes everything run smoothly once again.  Once restarted, I can see typically "normal" things in the log:

By the way, I'm running 0.11.2 compiled and built from source on Ubuntu 15.10.  Pool is running MPOS/NOMP.  Processes are running on a 4 core box with 8G RAM.  Looking at CPU usage, bitcoind is about 150% or more when it is unresponsive.  Typically it ranges anywhere from 30% to 80%.

I'm wondering if having a max block size of 1M is causing problems.  If you look at the two log snippets I included above, when it was completely unresponsive, all it was doing was trying to create new blocks of max size (or very close to it).  When things are running smoothly, the blocks its trying to create are considerably smaller.

Thanks in advance for any suggestions.