Are you syncing to an SSD? A resync from scratch may be worthwhile to ensure best performance going forward. Also, are you using the CLI or the GUI?
Yes, I am. I used the link above and redid the chain and now it's fine. I was using the GUI, but I had a bug in the wallet that I could not understand and so I went back to the CLI. I would try and explain it but I probably couldn't. In any event, I'm back up and running, thanks for all the help everyone!! Mooonero ftw!!  Perhaps you should give GUI v0.13.0.4 a try? Lots of bugs were fixed in this version. |
|
|
|
1. Have you tried restarting the daemon?
2. Do you have sufficient free disk space?
3. Are there any errors in bitmonero.log?
1 Yes many times 2. Yes 90GB 3. Not that I can really see. Let me tail it for a while and I'll post back. It's odd because it appears to be eating a lot of bandwith, and the percent has moved to 95 but it still says i'm on that same block... Thanks for your help as always - back shortly.... Are you syncing to an SSD? A resync from scratch may be worthwhile to ensure best performance going forward. Also, are you using the CLI or the GUI? |
|
|
|
Any idea why I can't sync my node past block 1528559? 2018-11-12 18:25:42.824 [P2P4] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:310 [xxx.183.x.x:1388 INC] Sync data returned a new top block candidate: 1528559 -> 1703594 [Your node is 175035 blocks (243 days) behind] It's been stuck here for like a whole day now... sync_info Height: 1528559, target: 1703594 (89.7255%) Downloading at 2604 kB/s 5 peers status Height: 1528559/1703594 (89.7%) on mainnet, not mining, net hash 946.19 MH/s, v6, up to date, 5(out)+2(in) connections, uptime 0d 0h 4m 3s it doesn't seem to be connecting to many peers. Is there a way to add nodes?  Thanks! Edit - Yes, i have an SSD  1. Have you tried restarting the daemon? 2. Do you have sufficient free disk space? 3. Are there any errors in bitmonero.log? |
|
|
|
I have question. Will Monero not connect if the GUI is an old version? I am running old version and it isn't working. I see "waiting for daemon to sync. Thanks for any answer.
Correct. You ought to run the most recent version (GUI v0.13.0.4), which can be found here: https://reddit.com/r/Monero/comments/9ti2on/gui_v01304_beryllium_bullet_released/Please take notice of the following: This version, if using your own (local) node, requires a database conversion, which may take a few hours and the GUI may show that it's Disconnected (or unable to connect) from the daemon (monerod). I'd advise to simply let it run and after the database conversion has completed the GUI will connect back to the daemon (monerod). |
|
|
|
Guys what do you think about new exchange https://www.tokens.net?What about payment ids - they are not used at all. Once your deposit XMR address is generated, it is used without payment id. It seems a bit danger to me, because as I know I has no "official" ways to prove I made a transaction to that address. Are they providing an integrated address (106 characters) for deposits? Because those still allow one to verify that his transaction correctly arrived. Basically you can use this guide with either a plain address, a plain address + a long (old), unencrypted payment ID, plain address + short (new), encrypted payment ID, an integrated address, or a subaddress. https://monero.stackexchange.com/questions/6134/how-do-i-as-a-sender-verify-that-my-transaction-actually-arrived |
|
|
|
When I try to make a transaction with GUI v0.13.0.4 and the Ledger Nano S on Windows 10 I have this error message:
unexpected error: Unable to send hidapi command. Error 64: L
Edit: after several try I managed to make a transaction. I guess I should be happy.
Note that it could be that your USB cable is slightly damaged and therefore inhibits the GUI from functioning properly. |
|
|
|
In the absence of a black swan event - and ten years after the white paper it doesn't look like we will see one - there is only one conclusion you can make.
By this criterion, we can expect Bitcoin to survive about 10 years. Taleb mentions, if I recall correctly, the term "at least" / "minimum" for non-perishable stuff. Thus, following the Lindy effect, a non-perishable good that has existed for 10 years is expected to at least exist another 10 years. Now, I suppose Bitcoin is technically an implementation of something non-perishable, which somewhat weakens the Lindy effect. |
|
|
|
Anybody use monerujo? what is the "public sub address"?is that a one-time stealth address? untrackable? No it's simply a public address that is unlinkable to your main public address (the one that starts with a 4). More information can be found here: https://monero.stackexchange.com/questions/3673/what-is-a-sub-addressAnd next question. I created a new wallet from nano s however syncing is taking some time. Do i need to leave nano s connected during syncing?
No. The Ledger device has to remain connected during the syncing progress, otherwise the progress won't be saved. |
|
|
|
Hi I'm having some issues connecting to Daemon with the new wallet, I updated from 12.2.0 to 13.0.03 I can login and see my balance but In the Daemon log I get
"Error: couldn't connect to Daemon 127.0.0.1:18081"
"Error: problem fetching info-- rpc_request:"
I tried monerod.exe and I get something like..
Global SRC Daemon/rpc.h:69 core rpc ok on port 18081
Global SRC Daemon/rpc.h:86 intitializing core...
SRC/cryptonote_core/cryptonote_core.cpp447
INFO global SRC/Blockchain_db/1mdb.cpp:4213[1;33mMigrating Blockchain from DB version 2 to 3 - this may take awhile
ERROR Blockchain.db.1mdb SRC/Blockchain_db/1mdb/db_1mdb.cpp:4232 output found
WARN Blockchain.db.1mdbSRC/Blockchain_db/1mdb/db_1mdb.cpp:75
Failed to build RCT output distribution
ERROR cn SRC/cryptonote_core/cryptonote_core.cpp548 error opening database: failed to build rct Output distribution
INFO global SRC/Daemon/rpc.h:96 deinitializing core rpc Server..
INFO global SRC/Daemon/rpc.h:90 deinitializing P2P...
Then it shuts down. Please advise
Regards PN
Did you shut down the GUI whilst the daemon (monerod) was performing the database conversion? |
|
|
|
To answer your question. The problem is I didn't know how to stop new wallet from downloading blockchain to my C driver ProgramData\bitmonero and my C drive is SSD on which I don't have enough space for blockchain.
I couldn't find instructions either.
Ok, so in wallet Settings > Node > I chose directory of old blockchain but I see it is not connecting to that but downloading again from start.
What is the proper directory setup to connect, do I need to choose some file? Instructions are not clear about that.
Can you tell (or PM) me the exact directory the correct blockchain file (data.mdb) is located? Then I can provide specific instructions. D:\Monero\lmdb\data.mdb The Blockchain Location on the Settings page has to be set to D:\Monero then. Hopefully this helps. |
|
|
|
To answer your question. The problem is I didn't know how to stop new wallet from downloading blockchain to my C driver ProgramData\bitmonero and my C drive is SSD on which I don't have enough space for blockchain. I couldn't find instructions either. Ok, so in wallet Settings > Node > I chose directory of old blockchain but I see it is not connecting to that but downloading again from start. What is the proper directory setup to connect, do I need to choose some file? Instructions are not clear about that. Can you tell (or PM) me the exact directory the correct blockchain file (data.mdb) is located? Then I can provide specific instructions. |
|
|
|
I deleted old wallet and want to upgrade to new one. I have seeds, wallet pass and blockchain files, how do I connect new wallet with blockchain files so it doesn't download everything?
I tried just using new wallet but it started synch to different driver to my C: where is small SSD drive and I don't have space there for that.
Need to connect new wallet to where is blockchain on my D hdd drive.
You can set the blockchain location to the proper directory on the settings page. May I ask why you deleted everything though? You should've simply followed the instructions on how to upgrade here: https://www.reddit.com/r/Monero/comments/9ol2ic/gui_v01303_beryllium_bullet_released/ |
|
|
|
Ok, if those blockexplorers are ok than my transaction is fine. So the fault is on cryptopias site I guess .. I'll just wait for their support team to check  Their support team should be able to resolve your issue. |
|
|
|
Thanks for help ! Now all ok !! Good to hear and you're welcome. |
|
|
|
|
Show Posts
: 
