https://chainz.cryptoid.info/bbp/
http://explorer.biblepay.org/
Updated explorer to latest version, performed an erasechain, its synced back up now
I think its been pretty reliable, and I think its good to have a backup explorer (from our history)
Id be totally fine with the url being set to the chainz one though
and I will gladly pass on the job of running the 2nd explorer to anyone interested!
(or if there is some other service we could use)
Iquidus explorer is slow, and has higher costs
Chainz explorer is fast, and has more features
Note: Theres a guy working on multithreading (clustering) Iquidus if anyone is interested to help him
https://github.com/iquidus/explorer/pull/257
http://explorer.biblepay.org/
Updated explorer to latest version, performed an erasechain, its synced back up now
I think its been pretty reliable, and I think its good to have a backup explorer (from our history)
Id be totally fine with the url being set to the chainz one though
and I will gladly pass on the job of running the 2nd explorer to anyone interested!
(or if there is some other service we could use)
Iquidus explorer is slow, and has higher costs
Chainz explorer is fast, and has more features
Note: Theres a guy working on multithreading (clustering) Iquidus if anyone is interested to help him
https://github.com/iquidus/explorer/pull/257
This is more related to some prior projects - not iquidis, but its worth a try, could you try this in the config:
rpcthreads=500
litemode=1
And resync?
I was under the impression with Evo we were communicating much faster with Iquidis (I remember you said there is a big difference), but apparently iquidis gets hung occasionally.
So also could you clarify if the node itself is stuck 200 blocks behind, or is it iquidis that ceases to sync? (If its not the node, there is no need to resync the entire chain, if its iquidis we would just resync the iquidis database. But the rpc settings might help if its too dumb to recover). Maybe the daemon is dying, maybe research how to persistenly keep the daemon running also.
The daemon is running fine, its fully synced, checked blockhashes
(Theres a crontab firing every 5 minutes to make sure its running and restart it if it isnt)
I checked mongodb, log file was 5.3GB, not sure if that is slowing things down, deleted it
I edited the mongod.conf file to try to limit the logging [set quiet to enabled]
(easy worst case I can add a crontab to just delete the log file every day)
Running everything again, everything is going, but the website is not updating with latest blocks, weird,
but if you type in a block number it will show/load it
I started looking into the indexing process more, and it fires off and then disappears quick,
I sent the output to a file, theres an error in Iquidus
Code:
/home/explorer/lib/explorer.js:310
if (vout[0].scriptPubKey.type == 'nonstandard') {
^
TypeError: Cannot read property 'scriptPubKey' of undefined
at /home/explorer/lib/explorer.js:310:18
at Object.loop.next (/home/explorer/lib/explorer.js:194:24)
at Object.module.exports.syncLoop (/home/explorer/lib/explorer.js:205:10)
at Object.module.exports.prepare_vout (/home/explorer/lib/explorer.js:284:20)
at /home/explorer/lib/database.js:141:17
at /home/explorer/lib/explorer.js:392:14
at Object.loop.next (/home/explorer/lib/explorer.js:194:24)
at Object.module.exports.syncLoop (/home/explorer/lib/explorer.js:205:10)
at Object.module.exports.prepare_vin (/home/explorer/lib/explorer.js:369:20)
at /home/explorer/lib/database.js:140:15
at Request._callback (/home/explorer/lib/explorer.js:107:14)
at Request.self.callback (/home/explorer/node_modules/request/request.js:187:22)
at emitTwo (events.js:87:13)
at Request.emit (events.js:172:7)
at Request.(/home/explorer/node_modules/request/request.js:1044:10)
at emitOne (events.js:77:13)
Looks like its happening in the 3rd parameter, an anonymous function, getting passed into syncLoop()
prepare_vout():
https://github.com/iquidus/explorer/blob/master/lib/explorer.js#L310
syncLoop():
https://github.com/iquidus/explorer/blob/c8ac131aed4f065b4f327ec379eaef2a006e5f50/lib/explorer.js#L169
Looks like this guy ran into similar issue
https://github.com/iquidus/explorer/issues/60
and posted this solution: https://github.com/cryptorex/bitcoinz-explorer/commit/267a0dfd8015bc90488b2b53ae9c49be2da83bff
Ill try adding it and report back
===
Iquidus Block Explorer Guide
https://www.reddit.com/r/BiblePay/comments/7elm7r/iquidus_block_explorer_guide/
===
Options:
1. Try to pinpoint the bug
2. Reset the mongo database to last backup and sync from there
3. Reset the mongo database entirely and sync from the beginning
4. Retire the explorer
5. Change URL to point to Chainz
6. Find and setup 2nd explorer service
