|
Title: Insight become unresponsive after few minutes/hours Post by: mmitech on November 11, 2015, 02:10:55 PM I forked Insight for another coin and got it to sync properly, but I am having stability issues, the problem appears few minutes after starting the server, one instance(CPU core) goes to 100% and as a result insight become unresponsive, the only way to solve it is to kill it.
I am wondering if anyone of you has experienced the same issues with insight and how did you solve it ? https://i.imgur.com/Amo3WMX.png Title: Re: Insight become unresponsive after few minutes/hours Post by: fbueller on November 11, 2015, 02:28:07 PM IIRC, there is a bug in bitcoind which results in 100% CPU usage when no peers are available. It never happens on the Bitcoin network, but it's noticeable with altcoins.
https://github.com/bitcoin/bitcoin/issues/6903 Title: Re: Insight become unresponsive after few minutes/hours Post by: mmitech on November 11, 2015, 04:48:44 PM IIRC, there is a bug in bitcoind which results in 100% CPU usage when no peers are available. It never happens on the Bitcoin network, but it's noticeable with altcoins. https://github.com/bitcoin/bitcoin/issues/6903 interesting! but do you think that Insight-bitcore-api has the same issue ? if so, what would be a proper solution for that?... really strange, I am wondering how all the insight forks are doing just fine ? Is there a good guide/wiki on how to import insight for another coin ? maybe I am missing something here, because I tried to do this with two coins and got the same issue with both of them !!! , I tried installing forever, but that doesn't really help, forever would be great only if insight would crash instantly after having the issue. Title: Re: Insight become unresponsive after few minutes/hours Post by: chrisvl on November 11, 2015, 05:10:05 PM IIRC, there is a bug in bitcoind which results in 100% CPU usage when no peers are available. It never happens on the Bitcoin network, but it's noticeable with altcoins. https://github.com/bitcoin/bitcoin/issues/6903 interesting! but do you think that Insight-bitcore-api has the same issue ? if so, what would be a proper solution for that?... really strange, I am wondering how all the insight forks are doing just fine ? Is there a good guide/wiki on how to import insight for another coin ? maybe I am missing something here, because I tried to do this with two coins and got the same issue with both of them !!! , I tried installing forever, but that doesn't really help, forever would be great only if insight would crash instantly after having the issue. are you sure that the problem stems from Insight-bitcore-api ? Title: Re: Insight become unresponsive after few minutes/hours Post by: mmitech on November 11, 2015, 05:28:43 PM IIRC, there is a bug in bitcoind which results in 100% CPU usage when no peers are available. It never happens on the Bitcoin network, but it's noticeable with altcoins. https://github.com/bitcoin/bitcoin/issues/6903 interesting! but do you think that Insight-bitcore-api has the same issue ? if so, what would be a proper solution for that?... really strange, I am wondering how all the insight forks are doing just fine ? Is there a good guide/wiki on how to import insight for another coin ? maybe I am missing something here, because I tried to do this with two coins and got the same issue with both of them !!! , I tried installing forever, but that doesn't really help, forever would be great only if insight would crash instantly after having the issue. are you sure that the problem stems from Insight-bitcore-api ? that was my reference guide, and at this point I am not sure of anything anymore, I tried a complete clean linux setup, I upgraded the VM then installed nodejs, forever, git, build-essential, htop, nginx, libboost-all-dev, libdb++-dev, libminiupnpc-dev, libcurl4-openssl-dev .... that is it, and edited the config, networks.js and RpcClient.js, Peersync.js, and Blockextractor.js to suite my coin. Insight launch without any issues works like a charm for few minutes to a couple of hours then one instance goes to 100% and it becomes unresponsive. see the process that become unresponsive in the picture below. I raised this issue on GitHub, but Bitpay don't answer/close any issues anymore. https://i.imgur.com/bAo1RFN.jpg |
