 Show Posts
|
|
Pages: [1]
|
Although if you have an application which depend on Bitcoin Core, you need to check whether RPC call you used change it's behavior, deprecated or removed on newer version.
Yes, I'm presently trying to developing an application using Bitcoin Core, etc. Truthfully, I started looking into Bitcoin Core code just about a month ago. Also, I have to define a clear process in order to do a backup, etc. |
|
|
|
Hi, I would like to know if there is query allowing at install Bitcoin Core with for example only the genesis block, its next three blocks and the last three blocks. I know, one can use prune in order to have a minimum of 550 blocks corresponding to 550Mb. However, this feature was available since 2014-2015. -prune= Reduce storage requirements by enabling pruning (deleting) of old blocks. This allows the pruneblockchain RPC to be called to delete specific blocks, and enables automatic pruning of old blocks if a target size in MiB is provided. This mode is incompatible with -txindex and -rescan. Warning: Reverting this setting requires re-downloading the entire blockchain. (default: 0 = disable pruning blocks, 1 = allow manual pruning via RPC, 550 = automatically prune block files to stay under the specified target size in MiB) |
|
|
|
--snip--
I'm trying to understand Bitcoin Core and started reading the code on Bitcoin Core 22.0. I see. You might want to check https://doxygen.bitcoincore.org/ since it's recommended by few Bitcoin Core contributor. According to the compile guides, these dependencies are the same than for Bitcoin Core 24 and in fact they are included in Bitcoin Core 24 depencies. Bitcoin Core 24 depencies have in addition User-Space, Statically Defined Tracing (USDT) dependencies and GUI. There are few difference though. I didn't compare everything, but here's an example Now, you can either build from self-compiled depends or install the required dependencies: sudo apt-get install libevent-dev libboost-dev libboost-system-dev libboost-filesystem-dev libboost-test-dev
Now, you can either build from self-compiled depends or install the required dependencies: sudo apt-get install libevent-dev libboost-dev
Take notice guide for Bitcoin Core 22.0 include 3 additional development file for Boost C++. Earlier when i tried to compile Bitcoin Core 22.0 without installing those 3 development file, i hit error when running command ./configure. My real issue is based on the fact that I like to have a full understanding of the source code I use. However, while I installed Bitcoin Core 24.0 without issue it still important for me to understand the migration process between the different Bitcoin Core versions. |
|
|
|
Did you checkout to specific commit/branch which represent source code of stable Bitcoin Core version before compile?
I'm trying to reproduce a bug I was having using Bitcoin Core 22.0. I don't know your goal, but why don't you just update to Bitcoin Core 24.0.1? I'm trying to understand Bitcoin Core and started reading the code on Bitcoin Core 22.0. It seems that the issue comes from GCC Autotools.
Do you mean version of your GCC autotools on your Ubuntu device? Anyway i tried compile Bitcoin Core 22.0 and 24.0.1 on Debian 11 and doesn't see error message you mentioned when you create this thread. I use Ubuntu 20.4 for Windows. According to the compile guides, these dependencies are the same than for Bitcoin Core 24 and in fact they are included in Bitcoin Core 24 depencies. Bitcoin Core 24 depencies have in addition User-Space, Statically Defined Tracing (USDT) dependencies and GUI. |
|
|
|
Did you checkout to specific commit/branch which represent source code of stable Bitcoin Core version before compile?
I'm trying to reproduce a bug I was having using Bitcoin Core 22.0. It seems that the issue comes from GCC Autotools. I would like to understand how this last works. I got this issue in Bitcoin Core 22.0 compile but not in Bitcoin Core 24.0.1. |
|
|
|
They were installed. However, I just tried to install them again after your post and below the print of the messages received (confirming that the depencies were already installed) : user1@UBUNTU-DESKTOP:~/bitcoin$ sudo apt-get install build-essential libtool autotools-dev automake pkg-config bsdmainutils python3
[sudo] password for bluefalcon:
Reading package lists... Done
Building dependency tree
Reading state information... Done
automake is already the newest version (1:1.16.1-4ubuntu6).
autotools-dev is already the newest version (20180224.1).
bsdmainutils is already the newest version (11.1.2ubuntu3).
libtool is already the newest version (2.4.6-14).
pkg-config is already the newest version (0.29.1-0ubuntu4).
python3 is already the newest version (3.8.2-0ubuntu2).
build-essential is already the newest version (12.8ubuntu1.1).
0 upgraded, 0 newly installed, 0 to remove and 22 not upgraded.
user1@UBUNTU-DESKTOP:~/bitcoin$ sudo apt-get install libevent-dev libboost-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
libboost-dev is already the newest version (1.71.0.0ubuntu2).
libboost-dev set to manually installed.
libevent-dev is already the newest version (2.1.11-stable-1).
0 upgraded, 0 newly installed, 0 to remove and 22 not upgraded.
user1@UBUNTU-DESKTOP:~/bitcoin$ sudo apt install libsqlite3-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
libsqlite3-dev is already the newest version (3.31.1-4ubuntu0.5).
0 upgraded, 0 newly installed, 0 to remove and 22 not upgraded.
user1@UBUNTU-DESKTOP:~/bitcoin$ sudo apt install libminiupnpc-dev libnatpmp-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
libminiupnpc-dev is already the newest version (2.1.20190824-0ubuntu2).
The following NEW packages will be installed:
libnatpmp-dev
0 upgraded, 1 newly installed, 0 to remove and 22 not upgraded.
Need to get 7036 B of archives.
After this operation, 30.7 kB of additional disk space will be used.
Do you want to continue? [Y/n]
y
Get:1 http://archive.ubuntu.com/ubuntu focal/main amd64 libnatpmp-dev amd64 20150609-7build1 [7036 B]
Fetched 7036 B in 1s (5178 B/s)
Selecting previously unselected package libnatpmp-dev:amd64.
(Reading database ... 357018 files and directories currently installed.)
Preparing to unpack .../libnatpmp-dev_20150609-7build1_amd64.deb ...
Unpacking libnatpmp-dev:amd64 (20150609-7build1) ...
Setting up libnatpmp-dev:amd64 (20150609-7build1) ...
user1@UBUNTU-DESKTOP:~/bitcoin$ sudo apt install systemtap-sdt-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
systemtap-sdt-dev
0 upgraded, 1 newly installed, 0 to remove and 22 not upgraded.
Need to get 16.4 kB of archives.
After this operation, 75.8 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 systemtap-sdt-dev amd64 4.2-3ubuntu0.1 [16.4 kB]
Fetched 16.4 kB in 1s (11.1 kB/s)
Selecting previously unselected package systemtap-sdt-dev.
(Reading database ... 357022 files and directories currently installed.)
Preparing to unpack .../systemtap-sdt-dev_4.2-3ubuntu0.1_amd64.deb ...
Unpacking systemtap-sdt-dev (4.2-3ubuntu0.1) ...
Setting up systemtap-sdt-dev (4.2-3ubuntu0.1) ...
Processing triggers for man-db (2.9.1-1) ...
user1@UBUNTU-DESKTOP:~/bitcoin$ sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools
Reading package lists... Done
Building dependency tree
Reading state information... Done
qttools5-dev is already the newest version (5.12.8-0ubuntu1).
qttools5-dev-tools is already the newest version (5.12.8-0ubuntu1).
libqt5core5a is already the newest version (5.12.8+dfsg-0ubuntu2.1).
libqt5dbus5 is already the newest version (5.12.8+dfsg-0ubuntu2.1).
libqt5gui5 is already the newest version (5.12.8+dfsg-0ubuntu2.1).
0 upgraded, 0 newly installed, 0 to remove and 22 not upgraded. I'm trying to install Bitcoin Core 22.0. |
|
|
|
Hi all, I'm trying to compile Bitcoin Core but I'm getting an error message. After the following commands, $./autogen.sh
$./configure
$sudo make I got the the following error message : make: *** No targets specified and no makefile found. Stop. A Makefile.am exists in the main folder so I don't see where come from. |
|
|
|
It's normal there is no genesis black since I'm trying to locally generate a blockchain based Bitcoin Core. For this purpose, I have changed the port, reproduce a Genesis block hash, etc. and succesfully rebuilt and compile without error. There is a chance you've screwed it up with reproduction, and have a logical error (which wouldn't appear after compiling). But, I doubt that's the case. The above error message started after I've created the bitcoin.conf file. Does it print it if you delete bitcoin.conf? After I deleted bitcoin.conf then run : bitcoind -debug -printtoconsole -regtest It was then printing in an unlimited loop [in contrary to yesterday when the print was limited (maybe because I restarted my computer today)] the following (I ended the process using the top command): user1@UBUNTU-DESKTOP:~/code/bitcoin$ bitcoind -debug -printtoconsole -regtest
2022-12-19T18:36:05Z Bitcoin Core version v24.99.0-968f03e65c98-dirty (release build)
2022-12-19T18:36:05Z Using the 'sse4(1way),sse41(4way)' SHA256 implementation
2022-12-19T18:36:05Z Default data directory /home/user1/.bitcoin
2022-12-19T18:36:05Z Using data directory /home/user1/.bitcoin/regtest
2022-12-19T18:36:05Z Config file: /home/user1/.bitcoin/bitcoin.conf (not found, skipping)
2022-12-19T18:36:05Z Command-line arg: debug=""
2022-12-19T18:36:05Z Command-line arg: printtoconsole=""
2022-12-19T18:36:05Z Command-line arg: regtest=""
2022-12-19T18:36:05Z Using at most 125 automatic connections (1024 file descriptors available)
2022-12-19T18:36:05Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements
2022-12-19T18:36:05Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements
2022-12-19T18:36:05Z Script verification uses 1 additional threads
2022-12-19T18:36:05Z scheduler thread start
2022-12-19T18:36:05Z [http] Allowing HTTP connections from: 127.0.0.0/8 ::1/128
2022-12-19T18:36:05Z [libevent:debug] event_add: event: 0x563eb981fe30 (fd 10), EV_READ call 0x7ffa0786d1c0
2022-12-19T18:36:05Z [libevent:debug] Epoll ADD(1) on fd 10 okay. Old events were 0; read change was 1 (add); write change was 0 (none); close change was 0 (none)
2022-12-19T18:36:05Z Binding RPC on address ::1 port 19084
2022-12-19T18:36:05Z [libevent:debug] event_add: event: 0x563eb98205d8 (fd 11), EV_READ call 0x7ffa0787a230
2022-12-19T18:36:05Z [libevent:debug] Epoll ADD(1) on fd 11 okay. Old events were 0; read change was 1 (add); write change was 0 (none); close change was 0 (none)
2022-12-19T18:36:05Z [libevent:debug] Bound to port 19084 - Awaiting connections ...
2022-12-19T18:36:05Z Binding RPC on address 127.0.0.1 port 19084
2022-12-19T18:36:05Z [libevent:debug] event_add: event: 0x563eb980a6b8 (fd 12), EV_READ call 0x7ffa0787a230
2022-12-19T18:36:05Z [libevent:debug] Epoll ADD(1) on fd 12 okay. Old events were 0; read change was 1 (add); write change was 0 (none); close change was 0 (none)
.
.
.
2022-12-19T18:39:25Z Shutdown: done As one can see, the process still connecting to port 19084 [despite of bitcoin.conf file being now deleted (with its associated .bitcoin folder)]. |
|
|
|
2022-12-19T10:43:04Z Error: Incorrect or no genesis block found. Wrong datadir for network? There's your problem. It's normal there is no genesis black since I'm trying to locally generate a blockchain based Bitcoin Core. For this purpose, I have changed the port, reproduce a Genesis block hash, etc. and succesfully rebuilt and compile without error. The above error message started after I've created the bitcoin.conf file. I supposed Bitcoin Core automatically generate a local genesis block if is this last does not exist. |
|
|
|
And what logs says? tail -f .bitcoin/debug.log On the other hand - is .cookie file created? Did you try to connect to server using that file instead of hardcoded password? It seems no .cookie file has been creates since I receive not output doing a search with the following on /home/user1/: $ find . -name "*.cookie" $ find . -name ".cookie" Yes, I tried to login using the bitcoin.conf file I created in .bitcoin. |
|
|
|
but apparently bitcoind stopped running for an unknown reason.
Then this should be solved first before the original question since this must be the vey reason why bitcoin-cli can't query bitcoind. For that, provide the whole logs as instructed above. 2022-12-19T10:43:03Z Bitcoin Core version v24.99.0-968f03e65c98-dirty (release build)
2022-12-19T10:43:03Z Using the 'sse4(1way),sse41(4way)' SHA256 implementation
2022-12-19T10:43:03Z Default data directory /home/user1/. bitcoin
2022-12-19T10:43:03Z Using data directory /home/user1/. bitcoin
2022-12-19T10:43:03Z Config file: /home/user1/. bitcoin/ bitcoin.conf
2022-12-19T10:43:03Z Config file arg: rpcallowip="127.0.0.1"
2022-12-19T10:43:03Z Config file arg: rpcbind=****
2022-12-19T10:43:03Z Config file arg: rpcpassword=****
2022-12-19T10:43:03Z Config file arg: rpcport="19084"
2022-12-19T10:43:03Z Config file arg: rpcuser=****
2022-12-19T10:43:03Z Config file arg: server="1"
2022-12-19T10:43:03Z Command-line arg: daemon=""
2022-12-19T10:43:03Z Command-line arg: debug=""
2022-12-19T10:43:03Z Using at most 125 automatic connections (1024 file descriptors available)
2022-12-19T10:43:03Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements
2022-12-19T10:43:03Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements
2022-12-19T10:43:03Z Script verification uses 1 additional threads
2022-12-19T10:43:03Z scheduler thread start
2022-12-19T10:43:03Z [http] Allowing HTTP connections from: 127.0.0.0/8 ::1/128 127.0.0.1/32
2022-12-19T10:43:03Z [libevent:debug] event_add: event: 0x55ade8d64610 (fd 10), EV_READ call 0x7f981e6d81c0
2022-12-19T10:43:03Z [libevent:debug] Epoll ADD(1) on fd 10 okay. Old events were 0; read change was 1 (add); write change was 0 (none); close change was 0 (none)
2022-12-19T10:43:03Z Binding RPC on address 127.0.0.1 port 19084
2022-12-19T10:43:03Z [libevent:debug] event_add: event: 0x55ade8d64708 (fd 11), EV_READ call 0x7f981e6e5230
2022-12-19T10:43:03Z [libevent:debug] Epoll ADD(1) on fd 11 okay. Old events were 0; read change was 1 (add); write change was 0 (none); close change was 0 (none)
2022-12-19T10:43:03Z [libevent:debug] Bound to port 19084 - Awaiting connections ...
2022-12-19T10:43:03Z [http] Initialized HTTP server
2022-12-19T10:43:03Z [http] creating work queue of depth 16
2022-12-19T10:43:03Z [rpc] Starting RPC
2022-12-19T10:43:03Z [rpc] Starting HTTP RPC server
2022-12-19T10:43:03Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation.
2022-12-19T10:43:03Z [http] Registering HTTP handler for / (exactmatch 1)
2022-12-19T10:43:03Z [http] Registering HTTP handler for /wallet/ (exactmatch 0)
2022-12-19T10:43:03Z [http] Starting HTTP server
2022-12-19T10:43:03Z [http] starting 4 worker threads
2022-12-19T10:43:03Z [http] Entering http event loop
2022-12-19T10:43:03Z Using wallet directory /home/user1/. bitcoin/wallets
2022-12-19T10:43:03Z init message: Verifying wallet(s)…
2022-12-19T10:43:03Z Using /16 prefix for IP bucketing
2022-12-19T10:43:03Z init message: Loading P2P addresses…
2022-12-19T10:43:04Z [addrman] CheckAddrman: new 709, tried 0, total 709 started
2022-12-19T10:43:04Z [addrman] CheckAddrman: completed (4.03ms)
2022-12-19T10:43:04Z Loaded 709 addresses from peers.dat 64ms
2022-12-19T10:43:04Z init message: Loading banlist…
2022-12-19T10:43:04Z [net] Loaded 0 banned node addresses/subnets 0ms
2022-12-19T10:43:04Z [net] setting try another outbound peer=false
2022-12-19T10:43:04Z SetNetworkActive: true
2022-12-19T10:43:04Z [estimatefee] Reading estimates: 190 buckets counting confirms up to 48 blocks
2022-12-19T10:43:04Z [estimatefee] Reading estimates: 190 buckets counting confirms up to 12 blocks
2022-12-19T10:43:04Z [estimatefee] Reading estimates: 190 buckets counting confirms up to 1008 blocks
2022-12-19T10:43:04Z Cache configuration:
2022-12-19T10:43:04Z * Using 2.0 MiB for block index database
2022-12-19T10:43:04Z * Using 8.0 MiB for chain state database
2022-12-19T10:43:04Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2022-12-19T10:43:04Z init message: Loading block index…
2022-12-19T10:43:04Z Validating signatures for all blocks.
2022-12-19T10:43:04Z Setting nMinimumChainWork=00000000ffffffffffffffffffffffffffffffffffffffffffffffffffffffff
2022-12-19T10:43:04Z [leveldb] LevelDB using max_open_files=1000 (default=1000)
2022-12-19T10:43:04Z Opening LevelDB in /home/user1/. bitcoin/blocks/index
2022-12-19T10:43:04Z [leveldb:debug] Recovering log #44
2022-12-19T10:43:04Z [leveldb:debug] Delete type=0 #44
2022-12-19T10:43:04Z [leveldb:debug] Delete type=3 #43
2022-12-19T10:43:04Z Opened LevelDB successfully
2022-12-19T10:43:04Z Using obfuscation key for /home/user1/. bitcoin/blocks/index: 0000000000000000
2022-12-19T10:43:04Z LoadBlockIndexDB: last block file = 0
2022-12-19T10:43:04Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=1, size=293, heights=0...0, time=2009-01-03...2009-01-03)
2022-12-19T10:43:04Z Checking all blk files are present...
2022-12-19T10:43:04Z Error: Incorrect or no genesis block found. Wrong datadir for network?
2022-12-19T10:43:04Z [http] Interrupting HTTP server
2022-12-19T10:43:04Z [rpc] Interrupting HTTP RPC server
2022-12-19T10:43:04Z [rpc] Interrupting RPC
2022-12-19T10:43:04Z Shutdown: In progress...
2022-12-19T10:43:04Z [rpc] Stopping HTTP RPC server
2022-12-19T10:43:04Z [http] Unregistering HTTP handler for / (exactmatch 1)
2022-12-19T10:43:04Z [http] Unregistering HTTP handler for /wallet/ (exactmatch 0)
2022-12-19T10:43:04Z [rpc] Stopping RPC
2022-12-19T10:43:04Z [rpc] RPC stopped.
2022-12-19T10:43:04Z [http] Stopping HTTP server
2022-12-19T10:43:04Z [http] Waiting for HTTP worker threads to exit
2022-12-19T10:43:04Z [libevent:debug] event_del: 0x55ade8d64708 (fd 11), callback 0x7f981e6e5230
2022-12-19T10:43:04Z [libevent:debug] Epoll DEL(1) on fd 11 okay. Old events were 2; read change was 2 (del); write change was 0 (none); close change was 0 (none)
2022-12-19T10:43:04Z [http] Waiting for HTTP event thread to exit
2022-12-19T10:43:04Z [libevent:debug] event_del: 0x55ade8d64708 (fd 11), callback 0x7f981e6e5230
2022-12-19T10:43:04Z [libevent:debug] Epoll DEL(1) on fd 11 okay. Old events were 2; read change was 2 (del); write change was 0 (none); close change was 0 (none)
2022-12-19T10:43:04Z [http] Waiting for HTTP event thread to exit
2022-12-19T10:43:04Z [libevent:debug] epoll_dispatch: epoll_wait reports 1
2022-12-19T10:43:04Z [libevent:debug] event_active: 0x55ade8d64610 (fd 10), res 2, callback 0x7f981e6d81c0
2022-12-19T10:43:04Z [libevent:debug] event_process_active: event: 0x55ade8d64610, EV_READ call 0x7f981e6d81c0
2022-12-19T10:43:04Z [libevent:debug] event_base_loop: no events registered.
2022-12-19T10:43:04Z [http] Exited http event loop
2022-12-19T10:43:04Z [libevent:debug] event_del: 0x55ade8d64610 (fd 10), callback 0x7f981e6d81c0
2022-12-19T10:43:04Z [libevent:debug] Epoll DEL(1) on fd 10 okay. Old events were 2; read change was 2 (del); write change was 0 (none); close change was 0 (none)
2022-12-19T10:43:04Z [libevent:debug] event_base_free_: 0 events freed
2022-12-19T10:43:04Z [http] Stopped HTTP server
2022-12-19T10:43:04Z scheduler thread exit
2022-12-19T10:43:04Z [estimatefee] Recorded 0 unconfirmed txs from mempool in 7e-07s
2022-12-19T10:43:04Z Shutdown: done
2022-12-19T12:42:12Z Bitcoin Core version v24.99.0-968f03e65c98-dirty (release build)
2022-12-19T12:42:12Z Using the 'sse4(1way),sse41(4way)' SHA256 implementation
2022-12-19T12:42:12Z Default data directory /home/user1/. bitcoin
2022-12-19T12:42:12Z Using data directory /home/user1/. bitcoin
2022-12-19T12:42:12Z Config file: /home/user1/. bitcoin/ bitcoin.conf
2022-12-19T12:42:12Z Config file arg: rpcallowip="127.0.0.1"
2022-12-19T12:42:12Z Config file arg: rpcbind=****
2022-12-19T12:42:12Z Config file arg: rpcpassword=****
2022-12-19T12:42:12Z Config file arg: rpcport="19084"
2022-12-19T12:42:12Z Config file arg: rpcuser=****
2022-12-19T12:42:12Z Config file arg: server="1"
2022-12-19T12:42:12Z Using at most 125 automatic connections (1024 file descriptors available)
2022-12-19T12:42:12Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements
2022-12-19T12:42:12Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements
2022-12-19T12:42:12Z Script verification uses 1 additional threads
2022-12-19T12:42:12Z scheduler thread start
2022-12-19T12:42:12Z Binding RPC on address 127.0.0.1 port 19084
2022-12-19T12:42:12Z [http] creating work queue of depth 16
2022-12-19T12:42:12Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation.
2022-12-19T12:42:12Z [http] starting 4 worker threads
2022-12-19T12:42:12Z Using wallet directory /home/user1/. bitcoin/wallets
2022-12-19T12:42:12Z init message: Verifying wallet(s)…
2022-12-19T12:42:12Z Using /16 prefix for IP bucketing
2022-12-19T12:42:12Z init message: Loading P2P addresses…
2022-12-19T12:42:12Z Loaded 709 addresses from peers.dat 8ms
2022-12-19T12:42:12Z init message: Loading banlist…
2022-12-19T12:42:12Z SetNetworkActive: true
2022-12-19T12:42:12Z Cache configuration:
2022-12-19T12:42:12Z * Using 2.0 MiB for block index database
2022-12-19T12:42:12Z * Using 8.0 MiB for chain state database
2022-12-19T12:42:12Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2022-12-19T12:42:12Z init message: Loading block index…
2022-12-19T12:42:12Z Validating signatures for all blocks.
2022-12-19T12:42:12Z Setting nMinimumChainWork=00000000ffffffffffffffffffffffffffffffffffffffffffffffffffffffff
2022-12-19T12:42:12Z Opening LevelDB in /home/user1/. bitcoin/blocks/index
2022-12-19T12:42:13Z Opened LevelDB successfully
2022-12-19T12:42:13Z Using obfuscation key for /home/user1/. bitcoin/blocks/index: 0000000000000000
2022-12-19T12:42:13Z LoadBlockIndexDB: last block file = 0
2022-12-19T12:42:13Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=1, size=293, heights=0...0, time=2009-01-03...2009-01-03)
2022-12-19T12:42:13Z Checking all blk files are present...
2022-12-19T12:42:13Z Error: Incorrect or no genesis block found. Wrong datadir for network?
2022-12-19T12:42:13Z Shutdown: In progress...
2022-12-19T12:42:13Z scheduler thread exit
2022-12-19T12:42:13Z Shutdown: done |
|
|
|
I tryied querying Bitcoin-cli (Bitcoin Core 24.0.1) in Ubuntu 20.04 WSL2 doing the following commands : $ bitcoind -debug -daemon Bitcoin Core starting $bitcoin-cli -rpcuser=user -rpcpassword=pass -rpcport=19084 but for this last command I get the following error : error: timeout on transient error: Could not connect to the server
127.0.0.1:19084
Make sure the bitcoind server is running and that you are
connecting to the correct RPC port. My bitcoin.conf file parameters are : rpcuser=user
rpcpassword=pass
rpcallowip=127.0.0.1
rpcport=19084
server=1
I then tried the following command in order to check if bitcoind still running in the background : USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 0.0 896 532 ? Sl 05:10 0:00 /init
root 212 0.0 0.0 896 88 ? Ss 07:22 0:00 /init
root 213 0.0 0.0 896 88 ? R 07:22 0:00 /init
username 214 0.0 0.1 10288 5548 pts/0 Ss 07:22 0:02 -bash
root 248 0.0 0.0 896 88 ? Ss 07:30 0:00 /init
root 249 0.0 0.0 896 88 ? S 07:30 0:00 /init
username 250 0.0 0.1 10176 5404 pts/1 Ss 07:30 0:00 -bash
username 296 0.0 0.3 23572 9756 pts/1 S+ 07:33 0:01 vi bitcoin.conf
root 367 0.0 0.0 896 88 ? Ss 09:26 0:00 /init
root 368 0.0 0.0 896 88 ? S 09:26 0:00 /init
username 369 0.0 0.1 10176 5572 pts/2 Ss+ 09:26 0:01 -bash
username 1035 0.0 0.1 10856 3460 pts/0 R+ 10:51 0:00 ps -aux but apparently bitcoind stopped running for an unknown reason. |
|
|
|
|
Hi all,
I try to create an altcoin, and successfully recompiled the code.
However, I received an error when trying to make a regression test. I then look for the log file but apparently it was not generated.
Also, I'm looking for a guide to set up a debuging environment.
|
|
|
|
|
