To your second question, I guess that is problem with the database and the resync after the fork, in fact, I feel there is no database saving the old blocks, because beside the 100 blocks being show there is no record of past transaction
I'l be over this in the night.
I have see your comments, at least in this treath, and you seem to know a lot. A little advise for were to begin to fix this issues would be much appreciated
i checked old and new blocks, ANY /block/ url gives me empty page.
so i guess it's not the second question, there are no records for block hashes at all.
i don't know how explorer obtains hashes but when i program rpc calls,
in getblock output tx data are at least one level deeper in json than mint and blockhash,
no chance to get it wrong
Not quite get it (noob), but I'll look for a solution, I bet in the way I'll understand your answer
thanks for the feedback
OK guys I really need some help here
Sintoms
- I take a random ID transaction from my wallet and put on the search bar of the explorer, and it show me the details of that transaction, perfect BUT sometimes it shows
"Error! : Search found no results for:xxxxxxxxxxxxxx".
Now I select a random hash from the screen click it, got to address bar and paste my transaction ID after "
http://198.50.229.39:3001/tx/PASTE_YOUR _ID_HERE"
It actually show the the details of the transaction
Now the weir thing is that if now I come back to block-explorer homepage and put my transaction ID in the search bar it also show me the details the the transaction and no more errors.
Really I don't know how to fix this, I was planning to wipe out the database of the explorer and erase the .loco folder (except the wallet and conf file) and build again from scratch but if any of you have any idea about this issue, I'll be much greatfull (I'm not asking a magic solution, just put me in the right way)
I would personally delete the user database on mongo then delete the index & cluster files in "explorer/temp" and the loco blockchain, I would then Add a user to the mongo db again then make sure all settings are correct in the settings.json then run mongo and select to use "use explorerdb" once done run the explorer first then the wallet after, If it was me I would use the -txindex -reindex -listen -server -daemon options when running the daemon for a block ex, Also have you setup a cronjob for the block ex to update every minute, minute n half ?
Clear as water, now i see the problem, after the fork, I deleted the blockchain, compiled the new daemon, run it and then
node scripts/sync.js index reindex then node scripts/sync.js index update
But I totally forgot to "use explorerdb" and delete the cluster file on "explorer/temp" before running the daemon.
The only option missing (from the ones you mention) in loco.conf is -reindex, and the cronjob is set to update every 1 minute.
Thanks Nightz I'll be working on this now.
I had the faucet with 1000 coins but after the fork 800 disappear (yes the last ones I send) when I'm done with the explorer, I will double the faucet reward, reduce the waiting time,
and fill it up with 1000 LOC.
BTW: Please someone come up with a better text for the home page