-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Indexing Problem - Problem with block? #56
Comments
very strange, looking at the raw block and tx data, everything looks normal. Nothing comes to mind right now, i will need to investigate further. |
Thanks, I'd really appreciate any pointers you can give me. Everybody is fresh out of ideas! |
just to confirm, you have txindex enabled? (although if you didnt, it would error out much sooner than that block) |
Hi. Yes, I have txindex=1 in crowncoin.conf. |
looking at the last blocks reward tx, they are identical (ignoring hashes of course). it should process it fine. Doesnt look like a code issue (either in explorer or daemon), potentially an environmental issue, what is the load on the server like? Are you launching explorer with forever or something similar (using bin/instance) or npm start? Also maybe try adding or increasing rpctimeout in crowncoin.conf. tbh, this has be fairly stumped also. random question. you're not running out of hdd space? |
Hi. Glad its not just us! Load is low on the server. Plenty of disk space. I have tried with forever and npm start. Will try rpctimeout change now. You'd be very welcome to log on and take a look if you are interested! I could always change the credentials afterwards. |
Increasing RPC timeout didn't work. I'll keep on thinking and trying things, will post here if I crack it. |
It's always the exact same block? |
Yes, the the last indexed block is 600804 every single time I try a reindex or update. I even rebuilt the server today and reinstalled from scratch to try to eliminate some environmental factors with no luck. |
https://github.com/iquidus/explorer/blob/master/routes/index.js#L52 try changing rtx.vout in that line, to JSON.parse(rtx.vout) will most likely not fix it, but just in case, give it a go. |
That doesn't work, sorry! I appreciate you spending time on this! |
cool, didnt think it would. I will need to set up my own instance of this to debug properly. Can you link me to the github? |
https://github.com/Crowndev/crowncoin.git master This is a script I use to compile a CRW node from source on Ubuntu 16.04 just in case you needed a pointer for dependencies.
|
tx id : d031164873b08c3e7f906aac62aad28ef2968502c6a9af356b525d8caba6ea17 1LgxCV2ETBCgP6zg8U4EupxdmaMCK4dBK sends 50 000, but only sends 49750 to 1GyCGSiCLEszrYMguz2uz4ywpQ36SgjAyV and the rest go to fees |
Good spot! @iquidus Does this explain what the problem is? Seems more than coincidental that the problem block has 250CRW unaccounted for in it. Crowncoin has the ability to create named CRW addresses, the fee for doing so is 250 CRW which is burned. There will be more blocks like this. I noticed that chainz.cryptoid.info can't sync past the same block either. Is there any way we can modify iquidus explorer to process this block and any others with the 250 CRW burn transaction in? |
Sorry to hassle @iquidus , any ideas on how we can get Iquidus to cope with burn transactions? I'm very keen to use your explorer. |
Kurrent has exactly the same issue. When coins being destroyed, the block explorer no longer works. This happened when in Kurrent the coins are minted into zerocoins. That's where the exceptions seen. Dev any way to get around it? |
Hi. Just a quick update. Iquidus is the best open source explorer out there. I'm willing to pay a decent bounty to anybody who can fix the issue so that it works with blockchains that destroy coins. Any help would be appreciated. |
@Stone-Hedge i dont know if still on time, but i fixed that on https://github.com/leoreinaux/explorer |
for solve this problem at the first time you launch the site, and testing you have to start your explorer node application and inmediately next go to another console instance and |
added a fix for insta-destroyed change that caused crashes in sync.js fix made by rbtgit: their words from iquidus#56 "I've had this issue and fixed it by changing the following line in explorer.js: if (vout[i].scriptPubKey.type != 'nonstandard' && vout[i].scriptPubKey.type != 'nulldata') { to if (vout[i].scriptPubKey.type != 'nonstandard' && vout[i].scriptPubKey.type != 'nulldata' && vout[i].scriptPubKey.hasOwnProperty("addresses")) { "
anyone using zerocoin will have this issue as well @rbtgit fix above will resolve the issue though |
tried the above fix and it was able to pass the block it was getting stuck on but moving blocks after implanting new code caused the whole explorer to mess up and not display blocks and connections counts etc.. |
For anyone coming here from google, try the suggestions here: https://github.com/go140point6/pvpcoin-explorer#fix-for-length-undefined This will eventually be resolved by modular commands for indexing altcoins with non-standard transactions. |
iquidus/explorer#56 Resolves this ^^^^
what @rbtgit wrote solved my problem (indexing of BTAD coin) ... thank you so much |
Hi,
I am attempting to set up Iquidus for Crowncoin. Indexing always fails at block #600805. #600804 is the last successfully indexed block. The dev team are not aware of anything unusual about this block. There are no hard forks associated with it, it looks pretty normal.
The error message is as follows:
This is an explorer link to the block that is causing a problem https://www.blockexperts.com/crw/height/600805
Coin daemon is latest version and I have tried re-indexing. Daemon is running with appropriate flags.
Can anybody advise?
Many thanks,
Dan
The text was updated successfully, but these errors were encountered: