Topic: Monero Support - page 24. (Read 82975 times)
Been encountering a strange occurrence when trying to sync blockchain which is that my modem keeps resetting itself at least a couple of times every hour. Anyone else found anything like this? What could be causing that? It also often resets as I start up bitmonerod.. very strange
Got it compiled this time, now busy syncing the blockchain. Looks like it is going to take a while..
Its very verbose, lots of messages scrolling past which don't mean much to me. Guess that doesn't matter though.
Thanks for you help, much appreciated.
Its very verbose, lots of messages scrolling past which don't mean much to me. Guess that doesn't matter though.
Thanks for you help, much appreciated.
there's some flag to get rid of that verbosity.
Code:
./bitmonerod --show-time-stats 0
thats some debugging thinger, so you don't have to see all those stats.
Got it compiled this time, now busy syncing the blockchain. Looks like it is going to take a while..
Its very verbose, lots of messages scrolling past which don't mean much to me. Guess that doesn't matter though.
Thanks for you help, much appreciated.
Its very verbose, lots of messages scrolling past which don't mean much to me. Guess that doesn't matter though.
Thanks for you help, much appreciated.
Ginger Ale I'm using Ubuntu 14.04
Monero should have stable releases more frequently its crazy to either use a really out of date version or take pot luck what the latest version is like.
Anyway I'll give it another go pulling another version of the code down...
Monero should have stable releases more frequently its crazy to either use a really out of date version or take pot luck what the latest version is like.
Anyway I'll give it another go pulling another version of the code down...
@Ginger Ale, I've had a go at compiling the Monero code as you suggested a few pages back in this thread and and by using the instructions in your sig. Assuming latest version of code is best ?
I am hitting a problem which is after about 90% of the way through compiling after typing 'make' I get a fatal error like this
Wondered if you have any pointers how to get past that ?
There are some binary files in my bin folder but I prefer to see everything compile properly before trying them..
Thanks
I am hitting a problem which is after about 90% of the way through compiling after typing 'make' I get a fatal error like this
Quote
[ 89%] Building CXX object tests/unit_tests/CMakeFiles/unit_tests.dir/blockchain_db.cpp.o
In file included from /home/user/bitmonero/tests/unit_tests/blockchain_db.cpp:40:0:
/home/user/bitmonero/src/blockchain_db/berkeleydb/db_bdb.h:28:20: fatal error: db_cxx.h: No such file or directory
#include
^
compilation terminated.
make[3]: *** [tests/unit_tests/CMakeFiles/unit_tests.dir/blockchain_db.cpp.o] Error 1
make[3]: Leaving directory `/home/user/bitmonero/build/release'
make[2]: *** [tests/unit_tests/CMakeFiles/unit_tests.dir/all] Error 2
make[2]: Leaving directory `/home/user/bitmonero/build/release'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/user/bitmonero/build/release'
make: *** [release-all] Error 2
In file included from /home/user/bitmonero/tests/unit_tests/blockchain_db.cpp:40:0:
/home/user/bitmonero/src/blockchain_db/berkeleydb/db_bdb.h:28:20: fatal error: db_cxx.h: No such file or directory
#include
^
compilation terminated.
make[3]: *** [tests/unit_tests/CMakeFiles/unit_tests.dir/blockchain_db.cpp.o] Error 1
make[3]: Leaving directory `/home/user/bitmonero/build/release'
make[2]: *** [tests/unit_tests/CMakeFiles/unit_tests.dir/all] Error 2
make[2]: Leaving directory `/home/user/bitmonero/build/release'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/user/bitmonero/build/release'
make: *** [release-all] Error 2
Wondered if you have any pointers how to get past that ?
There are some binary files in my bin folder but I prefer to see everything compile properly before trying them..
Thanks
so, it depends on when you pulled from github. For instance, this morning, when I cloned the repo, it built fine. But since then, there's been some development, so things may have changed (damn monero devs, developing too much!!!
). I am trying to build from source on a fresh lubuntu VM to see if I can do it. the above looks like the berkely db thing, which I thought the lib++ and the other one at the end took care of.
sometimes, a package installer / hoster won't work during a specific apt-get install session, so running it again may help.
sometimes, logging into and out of a terminal session helps.
and always apt-get update and apt-get upgrade are always good. I'll post in a bit.
edited to add: what OS are you building on? I personally only check building on lubuntu... though I can add ubuntu. I don't have an iso of mint, maybe I'll get one.
edited to add: built fine on lubuntu. Lemme try ubuntu.
edited to add: built fine on ubuntu
@Ginger Ale, I've had a go at compiling the Monero code as you suggested a few pages back in this thread and and by using the instructions in your sig. Assuming latest version of code is best ?
I am hitting a problem which is after about 90% of the way through compiling after typing 'make' I get a fatal error like this
Wondered if you have any pointers how to get past that ?
There are some binary files in my bin folder but I prefer to see everything compile properly before trying them..
Thanks
I am hitting a problem which is after about 90% of the way through compiling after typing 'make' I get a fatal error like this
Quote
[ 89%] Building CXX object tests/unit_tests/CMakeFiles/unit_tests.dir/blockchain_db.cpp.o
In file included from /home/user/bitmonero/tests/unit_tests/blockchain_db.cpp:40:0:
/home/user/bitmonero/src/blockchain_db/berkeleydb/db_bdb.h:28:20: fatal error: db_cxx.h: No such file or directory
#include
^
compilation terminated.
make[3]: *** [tests/unit_tests/CMakeFiles/unit_tests.dir/blockchain_db.cpp.o] Error 1
make[3]: Leaving directory `/home/user/bitmonero/build/release'
make[2]: *** [tests/unit_tests/CMakeFiles/unit_tests.dir/all] Error 2
make[2]: Leaving directory `/home/user/bitmonero/build/release'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/user/bitmonero/build/release'
make: *** [release-all] Error 2
In file included from /home/user/bitmonero/tests/unit_tests/blockchain_db.cpp:40:0:
/home/user/bitmonero/src/blockchain_db/berkeleydb/db_bdb.h:28:20: fatal error: db_cxx.h: No such file or directory
#include
^
compilation terminated.
make[3]: *** [tests/unit_tests/CMakeFiles/unit_tests.dir/blockchain_db.cpp.o] Error 1
make[3]: Leaving directory `/home/user/bitmonero/build/release'
make[2]: *** [tests/unit_tests/CMakeFiles/unit_tests.dir/all] Error 2
make[2]: Leaving directory `/home/user/bitmonero/build/release'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/user/bitmonero/build/release'
make: *** [release-all] Error 2
Wondered if you have any pointers how to get past that ?
There are some binary files in my bin folder but I prefer to see everything compile properly before trying them..
Thanks
there's your problem 
. It goes tits up.
. It goes tits up.rofl
I was playing a bit with the daemon to reproduce this, the one time I stumbled upon it I typed exit again and it gracefully quit.
Typing exit twice works ok
Thank you
difficult exits have been a persistent problem with all of the non-release builds.
When I type the extit command, the window doesn't close
there's your problem
. It goes tits up.joke aside: I have the same issue on linux. First I thought it might be waiting for something to gracefully quit, but I'm ending up killing the process after some minutes.
I was playing a bit with the daemon to reproduce this, the one time I stumbled upon it I typed exit again and it gracefully quit.
When I type the extit command, the window doesn't close
there's your problem
. It goes tits up.joke aside: I have the same issue on linux. First I thought it might be waiting for something to gracefully quit, but I'm ending up killing the process after some minutes.
It has synchronized perfectly but I have an issue. When I type the extit command, the window doesn't close, Here is what happens
I'm running monero whith this command
My machine:
Quote
You are now synchronized with the network. You may now start simplewallet.
Please note, that the blockchain will be saved only after you quit the daemon with "exit" command or if you use "save" command. Otherwise, you will possibly need to synchronize the blockchain again.
Use "help" command to see the list of available commands.
Save commandPlease note, that the blockchain will be saved only after you quit the daemon with "exit" command or if you use "save" command. Otherwise, you will possibly need to synchronize the blockchain again.
Use "help" command to see the list of available commands.
Quote
2015-Aug-21 21:48:12.711828 Blockchain stored OK, took: 1461 ms
Exit commandQuote
2015-Aug-21 21:48:15.868391 [node] Stop signal sent
2015-Aug-21 21:48:19.696808 [SRV_MAIN]net_service loop stopped.
2015-Aug-21 21:48:19.696808 [SRV_MAIN]p2p net loop stopped
And the window stays this way untill I force it to close2015-Aug-21 21:48:19.696808 [SRV_MAIN]net_service loop stopped.
2015-Aug-21 21:48:19.696808 [SRV_MAIN]p2p net loop stopped
I'm running monero whith this command
Quote
bitmonerod.exe --data-dir D:\XMR\blockchain
My machine:
Quote
OS Windows 10 Pro 64Bit
CPU Intel Core i5-3570k
Ram 16Gb
HDD where the blockchain is stored Toshiba DT01ACA050 500GB 7200 SATA 3
CPU Intel Core i5-3570k
Ram 16Gb
HDD where the blockchain is stored Toshiba DT01ACA050 500GB 7200 SATA 3
Code:
Problem signature:
Problem Event Name: APPCRASH
Application Name: bitmonerod.exe
Application Version: 0.0.0.0
Application Timestamp: 55ccf6d6
Fault Module Name: msvcrt.dll
Fault Module Version: 7.0.7601.17744
Fault Module Timestamp: 4eeb033f
Exception Code: c0000005
Exception Offset: 0000000000015a01
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1033
Additional Information 1: 71eb
Additional Information 2: 71eb0f7aea07f9843231a2fb78721e7b
Additional Information 3: 460a
Additional Information 4: 460addc13e0c64c0d1af5d425b8bdd83
http://pastebin.com/RvSXQxkf
happy to continue testing, if this is helpful
Quote from: canth
I got 2 crashes during the initial sync but once that was finished bitmonerod ran stable for ~ 24 hours without issue. I renamed data.mdb and restarted bitmonerod to try to recreate the problem. Just happened below.
Note: you might prefer to use --data-dir to specify different directories when running tests, without having to share the same directory and rename files.
Quote from: canth
One non-default setting for windows 7 - I have DEP for all programs enabled. Going to try to put that to default and see if it has any impact. Any logging level that I should turn up? I can also run procdump if that's helpful.
Running with --log-level 2 or even 3 would be helpful. That's a lot of output, but it will be saved to bitmonero.log. Its last parts could be pasted to pastebin.
It's too bad the specific exception on crash isn't being shown though. It is on Linux and OS X, and I thought it does on Windows too. If you're using a version you compiled yourself, recompiling with debugging, and running bitmonerod from a MinGW-w64 shell might show the exception upon crash, but I'm not sure.
- Thanks - using the --data-dir is a better method of testing.
- I'm testing again with --log-level 3 - so far bitmonerod runs flawlessly once caught up and synced but the initial download/verification of the chain tends to crash at least twice. Hopefully I'll catch some info this time.
- I'm running the pre-compiled binary on Win7 64 SP1 - haven't had the time to recompile yet
Quote from: canth
I got 2 crashes during the initial sync but once that was finished bitmonerod ran stable for ~ 24 hours without issue. I renamed data.mdb and restarted bitmonerod to try to recreate the problem. Just happened below.
Note: you might prefer to use --data-dir to specify different directories when running tests, without having to share the same directory and rename files.
Quote from: canth
One non-default setting for windows 7 - I have DEP for all programs enabled. Going to try to put that to default and see if it has any impact. Any logging level that I should turn up? I can also run procdump if that's helpful.
Running with --log-level 2 or even 3 would be helpful. That's a lot of output, but it will be saved to bitmonero.log. Its last parts could be pasted to pastebin.
It's too bad the specific exception on crash isn't being shown though. It is on Linux and OS X, and I thought it does on Windows too. If you're using a version you compiled yourself, recompiling with debugging, and running bitmonerod from a MinGW-w64 shell might show the exception upon crash, but I'm not sure.
The logging shown above doesn't include any errors. If you have the error messages available, paste those too.
Maybe by "crash" he meant that it got stuck and stopped making progress syncing? That is one issue we have seen elsewhere.
I got 2 crashes during the initial sync but once that was finished bitmonerod ran stable for ~ 24 hours without issue. I renamed data.mdb and restarted bitmonerod to try to recreate the problem. Just happened below.
Code:
Problem signature:
Problem Event Name: APPCRASH
Application Name: bitmonerod.exe
Application Version: 0.0.0.0
Application Timestamp: 55ccf6d6
Fault Module Name: msvcrt.dll
Fault Module Version: 7.0.7601.17744
Fault Module Timestamp: 4eeb033f
Exception Code: c0000005
Exception Offset: 0000000000015a01
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1033
Additional Information 1: 71eb
Additional Information 2: 71eb0f7aea07f9843231a2fb78721e7b
Additional Information 3: 460a
Additional Information 4: 460addc13e0c64c0d1af5d425b8bdd83
Code:
Last log details:
2015-Aug-22 16:56:05.822885 [P2P9]Height: 430619 blob: 211 cumm: 211 p/t: 0 (0/0/0/0/0/0/0/0/0/0/0)ms
2015-Aug-22 16:56:05.822885 [P2P9]Height: 430620 blob: 211 cumm: 211 p/t: 0 (0/0/0/0/0/0/0/0/0/0/0)ms
2015-Aug-22 16:56:05.822885 [P2P9]Height: 430621 blob: 249 cumm: 249 p/t: 0 (0/0/0/0/0/0/0/0/0/0/0)ms
2015-Aug-22 16:56:05.822885 [P2P9]HASH: - VIN/VOUT: 2/8 H: 0 chcktx: 0
2015-Aug-22 16:56:05.822885 [P2P9]Height: 430622 blob: 291 cumm: 1022 p/t: 0 (0/0/0/0/0/0/0/0/0/0/0)ms
One non-default setting for windows 7 - I have DEP for all programs enabled. Going to try to put that to default and see if it has any impact. Any logging level that I should turn up? I can also run procdump if that's helpful.
The logging shown above doesn't include any errors. If you have the error messages available, paste those too.
Maybe by "crash" he meant that it got stuck and stopped making progress syncing? That is one issue we have seen elsewhere.
The release binaries suck. Compile from source. A good starting point is in my signature. (page 11 of this thread).
Genuinely, follow his sig and you will have totally different experience. No mess with boost 1.54 and master branch is ridiculously further along than release. No need to bootstrap. It tempts me to put on tinfoil hat when wondering why release is soo far behind master branch. Almost seems like intentional barrier but that is always denied with sound logic.
No conspiracy, just continued testing and refinement. If you check the recent commits there are still edge cases being addressed. When it is ready it will be epic. For now it is just epic for people willing to test on the bleeding edge.
As the stinging in the child's cheeks subsided and the basketball bounced from his face to the floor, a chorus of laughter erupted from those who had thrown it. "Who reads a book in gym class!" yelled one of them, and for a brief moment the child considered that maybe he had made poor choices in life and was doomed to an existence consisting exclusively of this. But lo, and behold, the clouds parted and a voice from the future spake. To the amazement of the child, it appeared that he alone could hear it.
"Do not worry my son, and let them enjoy their moment in their own sun. For I have seen the future, and it is the nerds that shall inherit the Earth. Now get your shit together and compile the source."
"What source? What do you mean?" he said to the air of the classroom. The one who had thrown the basketball thought the child was responding to him, and made a confused and insulting gesture which only brought more guffaws from the class.
"That's enough questions!" bellowed the voice and vanished entirely.
Months, years, and decades passed. The trials of school faded to trials of adulthood, but the child always kept that advice with him, waiting for the day when it would be relevant.
Today is that day.
Compile the fucking source.
The logging shown above doesn't include any errors. If you have the error messages available, paste those too.
Running v 9 beta on Windows 7 SP1 64 bit and I've gotten a couple of crashes during initial blockchain download. With default logging, here's the last state:
2015-Aug-21 16:09:11.190673 [P2P3]Height: 506996 blob: 254 cumm: 5223 p/t: 1 (0/0/0/0/0/0/0/0/0/0/0)ms
2015-Aug-21 16:09:11.190673 [P2P3]Height: 506997 blob: 210 cumm: 210 p/t: 1 (1/0/0/0/0/0/0/0/0/0/0)ms
2015-Aug-21 16:09:11.190673 [P2P3]Height: 506998 blob: 172 cumm: 172 p/t: 0 (0/0/0/0/0/0/0/0/0/0/1)ms
2015-Aug-21 16:09:11.206298 [P2P3]Height: 506999 blob: 210 cumm: 210 p/t: 0 (0/0/0/0/0/0/0/0/0/0/0)ms
2015-Aug-21 16:09:11.206298 [P2P3]Height: 507000 blob: 210 cumm: 210 p/t: 0 (0/0/0/0/0/0/0/0/0/0/0)ms
2015-Aug-21 16:09:11.206298 [P2P3]LMDB memory map needs resized, doing that now.
2015-Aug-21 16:09:11.190673 [P2P3]Height: 506996 blob: 254 cumm: 5223 p/t: 1 (0/0/0/0/0/0/0/0/0/0/0)ms
2015-Aug-21 16:09:11.190673 [P2P3]Height: 506997 blob: 210 cumm: 210 p/t: 1 (1/0/0/0/0/0/0/0/0/0/0)ms
2015-Aug-21 16:09:11.190673 [P2P3]Height: 506998 blob: 172 cumm: 172 p/t: 0 (0/0/0/0/0/0/0/0/0/0/1)ms
2015-Aug-21 16:09:11.206298 [P2P3]Height: 506999 blob: 210 cumm: 210 p/t: 0 (0/0/0/0/0/0/0/0/0/0/0)ms
2015-Aug-21 16:09:11.206298 [P2P3]Height: 507000 blob: 210 cumm: 210 p/t: 0 (0/0/0/0/0/0/0/0/0/0/0)ms
2015-Aug-21 16:09:11.206298 [P2P3]LMDB memory map needs resized, doing that now.
The release binaries suck. Compile from source. A good starting point is in my signature. (page 11 of this thread).
Genuinely, follow his sig and you will have totally different experience. No mess with boost 1.54 and master branch is ridiculously further along than release. No need to bootstrap. It tempts me to put on tinfoil hat when wondering why release is soo far behind master branch. Almost seems like intentional barrier but that is always denied with sound logic.
No conspiracy, just continued testing and refinement. If you check the recent commits there are still edge cases being addressed. When it is ready it will be epic. For now it is just epic for people willing to test on the bleeding edge.
Jump to: