search

monero-project / monero-gui

Monero: the secure, private, untraceable cryptocurrency
Other
1.73k stars 767 forks source link

"Daemon failed to start" #890

Closed gitmehubscotty closed 5 years ago

gitmehubscotty commented 7 years ago

Hi guys, Monero keeps giving me this message when I try to setup localhost:18081 "Daemon failed to start. Please check your wallet and daemon log for errors. You can also try to start monerod.exe manually." unbenannt unbenannt2

Sincerely

leonklingele commented 6 years ago

@emminer what's the output of lsof -i | grep 18081 (while the daemon is running)? Do you start the daemon manually (via CLI?) or automatically via GUI?

cc45 commented 6 years ago

Well I left it on since I posted and it still does not work. Have we tried uninstalling and reinstalling the wallet? Can we mine directly to a wallet for Monero? I really wanted to be part of this but I have to be honest in that if the wallet is this much of an issue I am going to move on. Or can I mine to my light wallet? (Yes I know its not recommended however we are not talking about a mining farm either).

emminer commented 6 years ago

lsof -i | grep 18081 outputs nothing. I started daemon automatically via GUI, I clicked the start daemon button in GUI, both of them didn't work. Not sure how to start the daemon via CLI.

cc45 commented 6 years ago

I have tried it every which way, nothing. Which is why I was wondering if you can mine directly to the light wallet which opens no problem.

leonklingele commented 6 years ago

@emminer please try this:

  1. Close the Monero GUI (and monerod CLI in case you've started it)
  2. Rename (or delete) the bitmonero.log log file
  3. Start the GUI
  4. Post the output of the full log file (preferably to https://paste.ubuntu.com/ so it doesn't clutter this conversation here)
emminer commented 6 years ago

thanks leoniingele, result is: https://paste.ubuntu.com/26474099/

cc45 commented 6 years ago

Here is what I deleted and just like that it connected - no errors. C:\ProgramData\bitmonero\lmdb - I am running windows 10. Hope this helps someone else.

olmie75 commented 6 years ago

I'm using Windows 7 Pro, installed Monero wallet GUI v0.11.1.0 today, and it worked and synced up. After computer crash, I can't get the daemon to start, tried the various suggestions above with no luck. Last several lines of log info below. Please advise. 2018-01-27 23:09:39.285 13056 ERROR net.http contrib/epee/include/net/http_client.h:444 Unexpected recv fail 2018-01-27 23:09:39.285 13056 ERROR WalletAPI src/wallet/api/wallet.cpp:738 daemonBlockChainTargetHeight: possibly lost connection to daemon 2018-01-27 23:11:22.536 13056 ERROR net.http contrib/epee/include/net/http_client.h:444 Unexpected recv fail 2018-01-27 23:11:22.536 13056 ERROR WalletAPI src/wallet/api/wallet.cpp:738 daemonBlockChainTargetHeight: possibly lost connection to daemon 2018-01-27 23:12:15.228 6420 ERROR net.http contrib/epee/include/net/http_client.h:444 Unexpected recv fail 2018-01-27 23:12:15.228 6420 ERROR WalletAPI src/wallet/api/wallet.cpp:738 daemonBlockChainTargetHeight: possibly lost connection to daemon 2018-01-27 23:17:02.285 13056 ERROR net.http contrib/epee/include/net/http_client.h:444 Unexpected recv fail 2018-01-27 23:17:02.285 13056 ERROR WalletAPI src/wallet/api/wallet.cpp:738 daemonBlockChainTargetHeight: possibly lost connection to daemon 2018-01-27 23:17:35.785 13056 ERROR net.http contrib/epee/include/net/http_client.h:444 Unexpected recv fail 2018-01-27 23:17:35.785 13056 ERROR WalletAPI src/wallet/api/wallet.cpp:738 daemonBlockChainTargetHeight: possibly lost connection to daemon 2018-01-27 23:18:55.786 13056 ERROR net.http contrib/epee/include/net/http_client.h:444 Unexpected recv fail 2018-01-27 23:18:55.786 13056 ERROR WalletAPI src/wallet/api/wallet.cpp:738 daemonBlockChainTargetHeight: possibly lost connection to daemon 2018-01-27 23:53:23.292 4544 INFO logging contrib/epee/src/mlog.cpp:148 New log categories: :WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO,logging:INFO,msgwriter:INFO 2018-01-27 23:53:25.106 4544 INFO logging contrib/epee/src/mlog.cpp:156 New log categories: :WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO,logging:INFO,msgwriter:INFO 2018-01-27 23:53:26.215 4544 INFO logging contrib/epee/src/mlog.cpp:156 New log categories: :WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO,logging:INFO,msgwriter:INFO 2018-01-27 23:53:26.244 3252 ERROR net.http contrib/epee/include/storages/portable_storage.h:161 portable_storage: wrong binary format - signature mismatch 2018-01-27 23:53:26.244 3252 ERROR wallet.wallet2 src/wallet/wallet2.cpp:2128 !r. THROW EXCEPTION: error::invalid_password 2018-01-27 23:53:26.244 3252 WARN net.http src/wallet/wallet_errors.h:707 C:/msys64/home/vagrant/slave/monero-core-win64/build/monero/src/wallet/wallet2.cpp:2128:N5tools5error16invalid_passwordE: invalid password 2018-01-27 23:53:26.244 3252 ERROR WalletAPI src/wallet/api/wallet.cpp:504 Error opening wallet: invalid password 2018-01-27 23:53:26.488 3252 ERROR WalletAPI src/wallet/api/wallet.cpp:553 Status_Critical - not storing wallet 2018-01-27 23:53:54.912 4544 INFO logging contrib/epee/src/mlog.cpp:156 New log categories: :WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO,logging:INFO,msgwriter:INFO 2018-01-27 23:53:54.942 3252 WARN wallet.wallet2 src/wallet/wallet2.cpp:2505 Loaded wallet keys file, with public address: 4APiNrDxSwCUnje57cDdiu7qNYLmpD2Aq5jCy9GuZMxr2G4SRGrCWsbWtwEV1pDVYTGJ22P9Lm1dR96rA1Z8gjReELic1zE 2018-01-27 23:55:23.725 5348 WARN net.dns src/common/dns_utils.cpp:487 WARNING: no two valid MoneroPulse DNS checkpoint records were received 2018-01-28 00:14:16.980 6084 INFO logging contrib/epee/src/mlog.cpp:148 New log categories: :WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO,logging:INFO,msgwriter:INFO 2018-01-28 00:14:18.966 6084 INFO logging contrib/epee/src/mlog.cpp:156 New log categories: :WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO,logging:INFO,msgwriter:INFO 2018-01-28 00:14:19.772 6084 INFO logging contrib/epee/src/mlog.cpp:156 New log categories: :WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO,logging:INFO,msgwriter:INFO 2018-01-28 00:14:19.802 1676 ERROR net.http contrib/epee/include/storages/portable_storage.h:161 portable_storage: wrong binary format - signature mismatch 2018-01-28 00:14:19.803 1676 ERROR wallet.wallet2 src/wallet/wallet2.cpp:2128 !r. THROW EXCEPTION: error::invalid_password 2018-01-28 00:14:19.804 1676 WARN net.http src/wallet/wallet_errors.h:707 C:/msys64/home/vagrant/slave/monero-core-win64/build/monero/src/wallet/wallet2.cpp:2128:N5tools5error16invalid_passwordE: invalid password 2018-01-28 00:14:19.804 1676 ERROR WalletAPI src/wallet/api/wallet.cpp:504 Error opening wallet: invalid password 2018-01-28 00:14:20.003 1676 ERROR WalletAPI src/wallet/api/wallet.cpp:553 Status_Critical - not storing wallet 2018-01-28 00:14:31.255 6084 INFO logging contrib/epee/src/mlog.cpp:156 New log categories: :WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO,logging:INFO,msgwriter:INFO 2018-01-28 00:14:31.274 1676 ERROR net.http contrib/epee/include/storages/portable_storage.h:161 portable_storage: wrong binary format - signature mismatch 2018-01-28 00:14:31.274 1676 ERROR wallet.wallet2 src/wallet/wallet2.cpp:2128 !r. THROW EXCEPTION: error::invalid_password 2018-01-28 00:14:31.274 1676 WARN net.http src/wallet/wallet_errors.h:707 C:/msys64/home/vagrant/slave/monero-core-win64/build/monero/src/wallet/wallet2.cpp:2128:N5tools5error16invalid_passwordE: invalid password 2018-01-28 00:14:31.274 1676 ERROR WalletAPI src/wallet/api/wallet.cpp:504 Error opening wallet: invalid password 2018-01-28 00:14:31.285 1676 ERROR WalletAPI src/wallet/api/wallet.cpp:553 Status_Critical - not storing wallet 2018-01-28 00:14:43.700 6084 INFO logging contrib/epee/src/mlog.cpp:156 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO,logging:INFO,msgwriter:INFO 2018-01-28 00:14:43.722 1676 WARN wallet.wallet2 src/wallet/wallet2.cpp:2505 Loaded wallet keys file, with public address: 4APiNrDxSwCUnje57cDdiu7qNYLmpD2Aq5jCy9GuZMxr2G4SRGrCWsbWtwEV1pDVYTGJ22P9Lm1dR96rA1Z8gjReELic1zE 2018-01-28 00:16:11.467 1752 WARN net.dns src/common/dns_utils.cpp:487 WARNING: no two valid MoneroPulse DNS checkpoint records were received

leonklingele commented 6 years ago

@emminer are you sure that's all? Do you still get the Daemon failed to start error message when starting the GUI?

Close the GUI and start monerod via CLI. This can be done as follows:

  1. Open the Terminal app
  2. Paste the following line (you might need to adjust the path): /Applications/monero-wallet-gui.app/Contents/MacOS/monerod --log-level 3
  3. Press Enter & wait for a few seconds / until error messages appear
  4. Paste the whole output, make sure to redact sensitive information
emminer commented 6 years ago

I renamed lmdb, the daemon started. But I have to re sync and download 35G file :(

leonklingele commented 6 years ago

@emminer sure, that'll work. Most likely your old blockchain is corrupted. Let's try to find the root cause. Please stop your daemon and undo the lmdb rename, then follow the instructions from my previous comment. Maybe there's an easier way than to resync the whole blockchain.

emminer commented 6 years ago

https://paste.ubuntu.com/26474319/

leonklingele commented 6 years ago

@emminer oops, try it again with --log-level 1 or --log-level 2 please.

emminer commented 6 years ago

level 2: https://paste.ubuntu.com/26474587/

emminer commented 6 years ago

level 1: https://paste.ubuntu.com/26474593/

leonklingele commented 6 years ago

@emminer looks like this has already been reported in https://github.com/monero-project/monero/issues/2669 and fixed&merged in https://github.com/monero-project/monero/pull/3019. Try building latest master and check if it works for you.

emminer commented 6 years ago

Got a ton of errors during build, tried to fix them but no luck. I've downloaded the 35G blockchain file.

drogongod commented 6 years ago

Had the same issue deleted C:\ProgramData\bitmonero issue fixed... painful to redownload but nothing else for it.So stop playing with it. The blockchain we downloaded corrupted delete restart problem solved.. Then have a good cry over the 35 gig sync you got redo.. We Really should have a torrent for first 35 (Tared) of C:\ProgramData\bitmonero ...then we just verify force check the torrent and untar it then slip it in and sync... Save us all a lot of pain

gaga9999 commented 6 years ago

I am on Ubuntu and monerod synced everything (v.0.12.0.0): 2018-04-15 16:02:13.432 [P2P5] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1557 SYNCHRONIZED OK

monero-cli works fine: Refreshed 1551837/1551837, synced, daemon RPC v1.19 [wallet 43o5JF]:

Running monero-gui does not work (while monerod is running): 1."network status disconnected" 2.show status: " Height: 1551837/1551837 (100.0%) on mainnet, not mining, net hash 481.44 MH/s, v7, up to date, 8(out)+0(in) connections, uptime 0d 0h 7m 18s"

nothing moves

When runnin monero-gui without monerod running and pressing "start daemon" it show: "cant connect do daemon".

in bitmonero.log I have this line repeating from monero-gui: "logging contrib/epee/src/mlog.cpp:185 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global::INFO,verify:FATAL,stacktrace:INFO,logging:INFO,msgwriter:INFO " then: ":INFO,verify:FATAL,stacktrace:INFO,logging:INFO,msgwriter:INFO" and ":INFO,verify:FATAL,stacktrace:INFO,logging:INFO,msgwriter:INFO " and "src/common/stack_trace.cpp:163 [1] ./monerod:__wrap___cxa_throw+0x10a [0x559c487c81ba]" etc etc

when the gui runs and not the daemon and i press "start daemon" i also get "WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,g..."

oblique99 commented 6 years ago

Hi everyone.

Running 0.12.0.0 in Win10x64 and getting the following error when manually starting monerod (GUI runs ok but always daemon failed to start message)

2018-05-30 00:20:29.190 5268 INFO global src/daemon/main.cpp:280 Monero 'Lithium Luna' (v0.12.0.0-master-release) 2018-05-30 00:20:29.190 5268 INFO global src/daemon/protocol.h:53 Initializing cryptonote protocol... 2018-05-30 00:20:29.190 5268 INFO global src/daemon/protocol.h:58 Cryptonote protocol initialized OK 2018-05-30 00:20:29.190 5268 INFO global src/daemon/p2p.h:63 Initializing p2p server... 2018-05-30 00:20:30.553 5268 INFO global src/daemon/p2p.h:68 p2p server initialized OK 2018-05-30 00:20:30.740 5268 INFO global src/daemon/rpc.h:63 Initializing core RPC server... 2018-05-30 00:20:30.740 5268 INFO global contrib/epee/include/net/http_server_impl_base.h:76 Binding on 127.0.0.1:18081 2018-05-30 00:20:30.740 5268 INFO global src/daemon/rpc.h:69 core RPC server initialized OK on port: 18081 2018-05-30 00:20:30.740 5268 INFO global src/daemon/core.h:86 Initializing core... 2018-05-30 00:20:30.740 5268 INFO global src/cryptonote_core/cryptonote_core.cpp:427 Loading blockchain from folder C:\ProgramData\bitmonero\lmdb ... 2018-05-30 00:20:30.740 5268 WARN blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:75 Failed to query m_blocks: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid 2018-05-30 00:20:30.740 5268 ERROR cn src/cryptonote_core/cryptonote_core.cpp:503 Error opening database: Failed to query m_blocks: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid 2018-05-30 00:20:30.740 5268 INFO global src/daemon/rpc.h:96 Deinitializing core RPC server... 2018-05-30 00:20:30.740 5268 INFO global src/daemon/p2p.h:90 Deinitializing p2p... 2018-05-30 00:20:31.963 5268 INFO global src/daemon/core.h:103 Deinitializing core... 2018-05-30 00:20:31.963 5268 ERROR daemon src/daemon/core.h:108 Failed to deinitialize core... 2018-05-30 00:20:31.963 5268 INFO global src/daemon/protocol.h:75 Stopping cryptonote protocol... 2018-05-30 00:20:31.963 5268 INFO global src/daemon/protocol.h:79 Cryptonote protocol stopped successfully

stoffu commented 6 years ago

@oblique99

The error MDB_BAD_TXN is likely due to the DB being corrupt:

Please try monerod --db-salvage. If it doesn't work, then try redoing the full syncing. If the problem persists, please open a new ticket under the Monero repository, not here.

cc45 commented 6 years ago

I did all the above, plus dragongod suggested. Still didn't work, ive moved on. I mean if you cant get something as basic as the wallet to function, if its this hard it will never catch on but for a small part of the population base. It needs to be "wellsfargo easy". Not wasting any more time on it, I do wish them well as I really like the coin and the fact its asic resistant.

stoffu commented 6 years ago

@cc45 Did you manage to get your monerod.exe fully synced (does it show SYNCHRONIZED OK message in green)? If not, open a new ticket in https://github.com/monero-project/monero, not here (this repo is specific to the GUI). Also, please post the content of C:/ProgramData/bitmonero/bitmonero.log to either fpaste.org or paste.debian.net.

daedalus21 commented 6 years ago

same problem. on Mac, running lithium luna. had to force quit the GUI and it have been unable to get it started ever since.

here's the error message from the terminal when I tried to start monerod manually, following @leonklingele's suggestion: https://paste.ubuntu.com/p/WZ5NB3vprN/

any help would be much appreciated.

edit: turns out monerod was running in the background already and was causing its failure to start. closing monerod in activity monitor and relaunching resolved it.

MattyBv3 commented 6 years ago

If you're using Win 7/8/10 be sure to right-click / run as admin I know, it's basic, but hadn't seen it posted and it solved the daemon not starting for quite a few friends of mine.

selsta commented 5 years ago

+invalid

Magu-James commented 2 years ago

There are 2 reasons why daemon fails to start. 1. Your antivirus might have deleted monerod.exe file or the firewall is stopping daemon from accessing the network. or 2. Your blockchain file might be corrupted due to ungraceful shutdown.