Latest update: It's been five weeks since I sent my Moneroj from Poloniex to my GUI wallet. The "Blocks Remaining" has counted down four times, each time for less than twenty minutes. The other fifty-plus times I have opened my GUI wallet, the "Blocks Remaining" has risen from what it read the last time that I opened it. I have changed the block size from the default 200 to 20 and I have changed the daemon address to node.moneroworld.com, leaving the port at 18081. But I cannot tie any of these changes directly to any occasion of the blocks counting down. And not one fraction of my Moneroj has shown up in my GUI wallet. About half-way through all of this, the daemon started to work from the GUI wallet and I have not had to run monerod.exe manually. What do I need to do to get all the blocks?
Monero has yet to arrive in my wallet.
It's been several days since I sent Monero from Poloniex to the Monero wallet shown.
These are two separate programs that I have assumed need to run simultaneously.
The command line box goes this far and though the cursor blinks, I cannot input anything.
Do I just need to wait or is there something that I'm not doing right?
The number of blocks remaining has changed once while I have made several attempts at restarting both of these programs.
Assume that I am a total newbie when you answer because I haven't hardly got a notion as to what is going on.
http://ensignlineargenerator.tripod.com/webonmediacontents/Monero Wallet 12.jpg http://ensignlineargenerator.tripod.com/webonmediacontents/Monero Wallet 12a.jpg
I have observed that when my daemon displays as in the above picture, it was actively counting-down the "Blocks Remaining" on my GUI Wallet.
Now it still displays as shown with the "Blocks Remaining" standing still, yet still "Synchronizing".
What can I do to get my "Blocks Remaining" to count-down?
![Screen Shot](http://ensignlineargenerator.tripod.com/webonmediacontents/Monero Wallet 11.jpg "Screen Shot") The GUI wallet now says that it is connected but not synchronizing and still 0.00 balance. I got the line-command wallet to load 94717 blocks. But it seems to have stopped doing anything. I attempted to refresh it to no avail. I'm going to restart everything to see what happens.
Once again, my "Blocks Remaining" has come to a standstill, even though the Wallet GUI says it's synchronizing. And here is the latest from the daemon:
←[0m 2017-07-25 16:44:16.798 [P2P6] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:293 [126.96.36.199:18080 OUT] Sync data returned a new top block candidate: 202154 → 1362286 [Your node is 1160132 blocks <1049 days> behind]
2017-07-25 16:44:47.123 [P2P6] ERROR blockchain
src/cryptonote_core/blockchain.cpp:3383 Error adding block with hash: <6f0dca866420b58864282e662d39cd298543103d6f6e7013f8996befa8da647e> to blockchain, what = Error adding spent key image to db transaction: MDB_CORRUPTED: Located page was wrong type
2017-07-25 16:44:02.491 [P2P6] WARN blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:71 Failed to query m_blocks: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
2017-07-25 16:45:02.491 [P2P6] WARN blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:71 DB error attempting to fetch block index from hashMDB_BAD_TXN: Transaction must abort, has a child, or is invalid
2017-07-25 16:45:08.156 [P2P6] WARN blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:71 DB error attempting to fetch block index from hashMDB_BAD_TXN: Transaction must abort, has a child, or is invalid
2017-07-25 16:45:16.188 [P2P6] WARN blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:71 Failed to query m_blocks: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
Error messages similar to the above kept coming while my "Blocks Remaining" were counting down as in my last report.
I can only assume that these are not fatal errors, but just temporary.
I have tried restarting the daemon several times and also just left it alone for hours on end.
I would really appreciate a response from someone in-the-know.
Good news! I just kept saving and exiting the daemon a few times. Then I happened to check the Wallet GUI and it was not only synchronizing (which it has claiming to do for quite some time), but the "Blocks Remaining" were counting down at a rather fearsome pace. Meanwhile, the daemon keeps repeating at times: Transaction must abort, has a child, or is invalid. I don't dare touch either the daemon or the Wallet. It looks as though I am on my way to receiving my Moneroj... which is a very good thing as the amount is rather sizable. Now I need to look into a cold wallet to get my Moneroj completely off-line. That'll entail another transfer and a fee, which doesn't matter.
The basic facts as I see them:
I sent Monero from Poloniex to my GUI wallet address.
In order for the wallet to function, the daemon needs to be running as it does the work of relaying information from the Internet. However, I do not know whether the daemon is stuck or is working. Its last line states: 'Failed to query m_blocks: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid'.
[See later comment directly above.]
The command line wallet is supposed to work but I am unable to get it to switch to my created wallet as it will not accept the command (./monero-wallet-cli --restore-deterministic-wallet); it says that it is an unknown command.
All I want to do is verify that my Monero is in my wallet and then I will transfer it to Poloniex for storage that will not be as troublesome.
Additional Note: Re: Item #3 (See below). Apparently, the newer GUI (monero-gui-win-x64-v0.10.3.1) does work. So I have that up and running. Well, "running" is relative as nothing ever changes on it. Only when I start it, does the "Blocks Remaining" show a different (and higher) number.
Moneromooo said, "If the GUI is stuck, check the messages (in the settings page IIRC for any errors)...exit the GUI, edit the config file (I think it's somewhere in ~/.config/monero-core or thereabouts), and switch the testnet setting to 0, restart GUI." This is from a week ago, so I can only assume that it is valid for the GUI that I have. However, I do not know how to do a single thing in this quote.
I have found from Steve1943: Add --data-dir "path/to/blockchain" to the launch command. Here is an example for Windows: monerod.exe --data-dir "D:\My Documents\bitmonero"
This addresses the problem of the daemon downloading the blockchain onto the C:\ drive and allows one to download the data elsewhere.
My problem is that I do not know how to access the launch command. Apparently this is something very basic; but I still have no idea as to where to begin.
Today's first entry: Now when I try to run monero-wallet-cli, I get as far as choosing a language when a line in red pops up and the window closes before I can read the line.
So I am stuck with just the daemon operating, which reads:
The daemon will start synchronizing with the network. It may take up to several hours.
<-[0m 2017-07-19 12:23:47.811 [P2P7] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:293 [188.8.131.52:18080 OUT] Sync data returned a n ew top block candidate:202154 → 1357828 [Your node is 1155674 blocks <1043 day s>behind]
2017-07-19 12:24:15.570 [P2P7] ERROR blockchain src/cryptonote_core/bloc kchain.cpp:3383 Error adding block with hash: <6f0dca866420b58864282e662d39cd298 543103d6f6e7013f8996befa8da647e> to blockchain, what = Error adding spent key im age to db transaction: MDB_CORRUPTED: Located page was wrong type
2017-07-19 12:24:15.570 [P2P7] WARN blockchain.db.lmdb src/blockshain_d b/lmdb/db.cpp:71 Failed to query m_blocks: MDB_BAD_TKN: Transaction must abort, has a child, or is invalid
2017-07-19 12:24:44.624 [P2P7] WARN blockchain.db.lmdb src/blockchain_d b/lmdb/db_lmdb.cpp:71 Failed to query m_blocks: MDB_BAD_TKN: Transaction must abort, has a child, or is invalid
My latest task was to disable my private internet access program. Now I am getting a lot more activity on the daemon but it does seem to be just repeating the last two paragraphs.
Today, I deleted all things Monero from my system and then followed a tutorial from monero.how (https://www.monero.how/tutorial-how-to-create-a-command-line-monero-wallet).
I ended up with two command line windows with some activity going on.
I then followed another tutorial (https://www.monero.how/tutorial-how-to-use-the-monero-gui-wallet), and was able to retrieve my original wallet. This was the second time that my "Blocks remaining" changed.
So now I have three windows open: the daemon (monerod.exe), the command line wallet (monero-wallet-cli), and the Monero Wallet GUI. I have yet to ascertain whether anything is happening or if things are hung up.
The monero-wallet-cli is showing the new command line wallet that I made today. I inputted "refresh" to see if that might change things. It seems not. There appears to not be a way that I can change which wallet that the daemon is working for. For all I know, the daemon may be working on both wallets.
I am going to do some more research online.
So, again I deleted all Monero files from my computer. I ran CCleaner on the registry to clear up anything wrong there. Used CCleaner to truly empty my Recycle Bin.
Then I reinstalled the line command wallet and daemon. The above page link above showed that I needed to input a command that can only be accessed by creating a wallet. I wanted to avoid doing that, but in the end, had no choice.
I finally got to the point where I could put in the command: ./monero-wallet-cli --restore-deterministic-wallet. But it stated that it didn't recognize the command. Does anyone know what error there is in the command that I input? I'm making some progress but it would certainly be nice to have someone knowledgeable respond.
moneromooo posted 1 week ago Weight: 480
"The old .net GUI is way obsolete, yes. Don't use. You won't be able to sync with it."
So I am just wasting my time trying to get the GUI to work. That just takes me back to attempting to restore my wallet on the command line wallet; with it not recognizing the command: ./monero-wallet-cli --restore-deterministic-wallet.
From (https://www.monero.how/tutorial-restore-monero-command-line-wallet-from-seed), the following is what I am supposed to encounter when I input the command:
[wallet 47CL7F]: ./monero-wallet-cli --restore-deterministic-wallet Creating the logger system Monero 'Wolfram Warptangent' (v0.10.0.0-release) Logging at log level 0 to /Users/dre/Downloads/monero.mac.x64.v0-10-0-0/./monero-wallet-cli.log Specify wallet file name (e.g., MyWallet). If the wallet doesn't exist, it will be created. Wallet file name: mywallet The wallet doesn't exist, generating new one password: **** password: **** Specify Electrum seed: locker welders womanly lodge gumball selfish altitude dewdrop terminal nagged exit acquire hookup ashtray wobbly nineteen duration duties javelin patio baffles ambush bamboo bite nineteen Restore from specific blockchain height (optional, default 0): 0 Generated new wallet: 47CL7FiNtW417VjzWt9Zse8Z8URhaHaA2L9jJq6rrLtDhiYK9PfbCavhhMKws9xEdKHBeGcQtJmPt4uEMivooNztC5UkHLD View key: 005c98c3db115140289bd0dfad97f910e6eeb5e8e12d02fdd4ab2373fbe9110a
Your wallet has been generated!
The problem here is apparently that this maneuver generates a new wallet with a new password; then it allows you to enter the 25-word seed... which should bring up the existing/to-be-restored wallet. Yet it goes on to state that it generates a new wallet... with a new address. Then to further confuse me, it states that "your wallet has been generated"... which could mean restored.
But all of my ranting is useless as the line command wallet does not recognize the first command.
Maybe I have just shot myself in the foot by erasing all traces of all Monero files from my system, in order to start over. But I do have the 25-word mnemonic; so, at some point in the future, I should be able to retrieve my funds. And right now, that's all I ask.