aboutsummaryrefslogtreecommitdiff
path: root/src/blockchain_utilities/blockchain_import.cpp (follow)
AgeCommit message (Collapse)AuthorFilesLines
2017-10-15Merge pull request #2589Riccardo Spagni1-5/+5
8f0cea63 add a command_line function to check for defaulted options (moneromooo-monero)
2017-10-15Merge pull request #2568Riccardo Spagni1-1/+1
7130cf0c Add tools::on_startup, and warn about glibc 2.25 bug if found (moneromooo-monero)
2017-10-15Merge pull request #2567Riccardo Spagni1-3/+0
54940d8c blockchain_import: remove a few commented out obsolete lines (moneromooo-monero)
2017-10-15Merge pull request #2469Riccardo Spagni1-0/+20
7adceee6 precomputed block hashes are now in blocks of N (currently 256) (moneromooo-monero)
2017-10-14Add tools::on_startup, and warn about glibc 2.25 bug if foundmoneromooo-monero1-1/+1
https://sourceware.org/bugzilla/show_bug.cgi?id=21778
2017-10-06add a command_line function to check for defaulted optionsmoneromooo-monero1-5/+5
2017-10-03blockchain_import: remove a few commented out obsolete linesmoneromooo-monero1-3/+0
2017-09-18precomputed block hashes are now in blocks of N (currently 256)moneromooo-monero1-0/+20
This shaves a lot of space off binaries
2017-09-17Use actual batch size for resize estimatesHoward Chu1-19/+44
And optimize import startup: Remember start_height position during initial count_blocks pass to avoid having to reread entire file again to arrive at start_height
2017-09-02Merge pull request #2384Riccardo Spagni1-24/+24
4e0e4e99 blockchain_import: warn for chunks over 500000, not 100000 (moneromooo-monero) 5b29e87f blockchain_import: properly cleanup core/db on exit (moneromooo-monero) e167c4d9 blockchain_import: do not error out on truncated files (moneromooo-monero)
2017-09-01blockchain_import: warn for chunks over 500000, not 100000moneromooo-monero1-2/+2
We have a lot of 350000 byte blocks now.
2017-09-01blockchain_import: properly cleanup core/db on exitmoneromooo-monero1-19/+9
2017-09-01blockchain_import: do not error out on truncated filesmoneromooo-monero1-3/+13
This will happen often when downloading from a live file
2017-08-29Fix blockchain_import wedge on exception in cleanup_handle_incoming_blocksmoneromooo-monero1-1/+5
2017-08-20More DB support cleanupHoward Chu1-44/+2
Hide DB types from db_types.h - no reason to recompile dependencies when DB types change. Also remove lingering in-memory DB references, they've been obsolete since 9e82b694da120708652871b55f639d1ef306a7ec
2017-08-19DB cleanupHoward Chu1-69/+5
Hide LMDB-specific stuff behind blockchain_db.h. Nobody besides blockchain_db.cpp should ever be including DB-specific headers any more.
2017-08-07blockchain_import: much faster when verifying with cryptonote::coremoneromooo-monero1-152/+140
Quick test with the first 56569 blocks from mainnet version verify batch time old 0 200 1:16 new 0 200 0:57 old 0 5000 0:53 new 0 5000 0:51 old 1 200 est > 1h new 1 200 10:21 old 1 5000 est > 1h new 1 5000 8:27
2017-05-25Move txpool to the databasemoneromooo-monero1-1/+1
Integration could go further (ie, return_tx_to_pool calls should not be needed anymore, possibly other things). poolstate.bin is now obsolete.
2017-03-05blockchain_import: make --log-level understand categoriesmoneromooo-monero1-3/+6
2017-03-05blockchain_import: error out nicely on exceptionsmoneromooo-monero1-0/+4
2017-03-03Fix double-importHoward Chu1-8/+10
Incomplete ifdef cleanup in 9e82b694da120708652871b55f639d1ef306a7ec
2017-02-21update copyright year, fix occasional lack of newline at line endRiccardo Spagni1-1/+1
2017-02-12tools: log to the correct filemoneromooo-monero1-1/+3
2017-02-12tools: set requested log levelmoneromooo-monero1-1/+2
also move a couple logs from INFO to DEBUG
2017-02-08extract some basic code from libcryptonote_core into libcryptonote_basickenshi841-1/+1
2017-01-16fixups in logging init calls, and add missing net context in a logmoneromooo-monero1-1/+1
2017-01-16Change logging to easylogging++moneromooo-monero1-55/+56
This replaces the epee and data_loggers logging systems with a single one, and also adds filename:line and explicit severity levels. Categories may be defined, and logging severity set by category (or set of categories). epee style 0-4 log level maps to a sensible severity configuration. Log files now also rotate when reaching 100 MB. To select which logs to output, use the MONERO_LOGS environment variable, with a comma separated list of categories (globs are supported), with their requested severity level after a colon. If a log matches more than one such setting, the last one in the configuration string applies. A few examples: This one is (mostly) silent, only outputting fatal errors: MONERO_LOGS=*:FATAL This one is very verbose: MONERO_LOGS=*:TRACE This one is totally silent (logwise): MONERO_LOGS="" This one outputs all errors and warnings, except for the "verify" category, which prints just fatal errors (the verify category is used for logs about incoming transactions and blocks, and it is expected that some/many will fail to verify, hence we don't want the spam): MONERO_LOGS=*:WARNING,verify:FATAL Log levels are, in decreasing order of priority: FATAL, ERROR, WARNING, INFO, DEBUG, TRACE Subcategories may be added using prefixes and globs. This example will output net.p2p logs at the TRACE level, but all other net* logs only at INFO: MONERO_LOGS=*:ERROR,net*:INFO,net.p2p:TRACE Logs which are intended for the user (which Monero was using a lot through epee, but really isn't a nice way to go things) should use the "global" category. There are a few helper macros for using this category, eg: MGINFO("this shows up by default") or MGINFO_RED("this is red"), to try to keep a similar look and feel for now. Existing epee log macros still exist, and map to the new log levels, but since they're used as a "user facing" UI element as much as a logging system, they often don't map well to log severities (ie, a log level 0 log may be an error, or may be something we want the user to see, such as an important info). In those cases, I tried to use the new macros. In other cases, I left the existing macros in. When modifying logs, it is probably best to switch to the new macros with explicit levels. The --log-level options and set_log commands now also accept category settings, in addition to the epee style log levels.
2017-01-15blockchain_import: fix build after tx_pool::add_tx changesmoneromooo-monero1-1/+1
2016-08-28remove original Cryptonote blockchain_storage blockchain formatmoneromooo-monero1-40/+0
2016-03-21Revert "Print stack trace upon exceptions"moneromooo-monero1-3/+3
Ain't nobody got time for link/cmake skullduggery. This reverts commit fff238ec94ac6d45fc18c315d7bc590ddfaad63d.
2016-03-19Print stack trace upon exceptionsmoneromooo-monero1-3/+3
Useful for debugging users' logs
2016-02-22move g_test_dbg_lock_sleep from a global to a function level staticmoneromooo-monero1-2/+0
This avoids the need to define that variable in every program which uses epee.
2016-02-17blockchain_import: Check bit width for more than just WIN32warptangent1-2/+2
Pass the CMake bit width setting to compile flags for blockchain_import and blockchain_converter. For LMDB on 32-bit, hyc has found that batch size of 100 appears to be a good default.
2016-02-14blockchain_import: Build string for db type listwarptangent1-2/+15
2016-02-14blockchain_import: Add mode argument representing multiple DB flagswarptangent1-31/+82
These modes match those optionally provided as part of the daemon's --db-type argument. Argument after the # is interpreted as a composite mode if there's only one (no comma separated arguments). Sample usage: blockchain_import --database lmdb#fastest blockchain_import --database berkeley#fastest Multiple specific DB flags are still supported, e.g. blockchain_import --database lmdb#nosync,nordahead blockchain_import --database berkeley#txn_nosync
2016-02-14blockchain_import: Support BerkeleyDBwarptangent1-20/+54
2016-02-14blockchain_import: Add database type argumentwarptangent1-2/+2
Default to LMDB.
2016-02-14blockchain_import: Make LMDB-specific names generalwarptangent1-28/+28
Also update terms to better distinguish blockchain management/engine from database type.
2016-02-08blockchain_import: Get hard fork version from HardForkwarptangent1-4/+1
Replace temporary assignment that used hardcoded values.
2016-02-08Move HardFork DB update to BlockchainDB::add_block()warptangent1-3/+0
Ensures the database is consistent. Also simplifes blockchain_import in that verify mode off has less to work around.
2016-02-08blockchain_import: Add hard fork data for each block when verify mode is offwarptangent1-0/+3
2016-02-08blockchain_import: Add --drop-hard-fork commandwarptangent1-0/+11
2016-02-08blockchain_import: Add exception to log outputwarptangent1-1/+1
2016-01-29Fix V1/V2 use of hard fork related parametersmoneromooo-monero1-1/+7
Some of it uses hardcoded height, which will need some thinking for next (voted upon) fork.
2015-12-31update versionRiccardo Spagni1-1/+1
2015-12-31updated copyright yearRiccardo Spagni1-1/+1
2015-12-19Add missing semicolons after log statementsmoneromooo-monero1-1/+1
2015-11-21Merge pull request #493Riccardo Spagni1-0/+2
f3724ae Fix startup crash when using a locale boost does not like (moneromooo-monero) 0c1dae3 i18n: allow language to be passed as a parameter (moneromooo-monero)
2015-11-21Fix startup crash when using a locale boost does not likemoneromooo-monero1-0/+2
There are various locale related bugs in various versions of boost, where exceptions are thrown in boost::filesystem APIs when the current locale is not to boost's liking. It's not clear what "not to boost's liking" means in detail, though "en" and "en_US.UTF-8" are not to its liking. Fix it by running a test function that's known to throw in such a case, and resetting LANG and LC_ALL to C if an exception is thrown. In simplewallet, the locale is queried before that so the correct translations will still be used.
2015-11-21Relay transactions when they linger too long in the poolmoneromooo-monero1-1/+1
The last relayed time of a transaction is maintained, and transactions will be relayed again if they are still in the pool after a certain amount of time, which increases with the transaction's age. All such transactions are resent, whether or not they originated on the local node.
2015-08-14blockchain_import: Add --input-file optionwarptangent1-1/+9
This option specifies the input file path for importing. The default remains <data-dir>/export/blockchain.raw
2015-08-14blockchain_import: Updates for naming consistencywarptangent1-15/+14
2015-07-11blockchain_utilities: Pass expected number of blocks when starting batchwarptangent1-2/+2
2015-05-16Support debugging command --pop-blocks on in-memory blockchainwarptangent1-9/+14
Add public method blockchain_storage::debug_pop_block_from_blockchain() Ensure blockchain_import calls destructors before exit. To test: DATABASE=memory make release // create blockchain.bin from blockchain.raw if needed build/release/bin/blockchain_import --block-stop 1000 // try popping a single block build/release/bin/blockchain_import --pop-blocks 1
2015-05-15Rename "--block-number" option to "--block-stop"warptangent1-26/+21
Update help output for this and other options.
2015-05-15Check if chunk size is zero instead of negativewarptangent1-2/+2
This corrects an unnecessary check and fixes compile error on OS X.
2015-05-08Rename src/blockchain_converter/ to src/blockchain_utilities/warptangent1-0/+770
Update appropriate files (CMakeLists.txt, README.md)
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-19 20:29:17 +0000