unable to compile and run 0.9.7.4 on ubuntu 20.04 #107

melvincarvalho · 2021-04-13T10:06:17Z

New Machine

./configure 
./configure --with-incompatible-bdb
./configure --without-bdb

Tried these three and it gives the error

checking for Berkeley DB C++ headers... no
configure: error: libdb_cxx headers missing

Seeing if I can figure this out

Older machine

It does actually compile and bitcoind + bitcoin-cli make (but not bitcoin-qt for some reason)

Issue here is that it stalls at:

"blocks" : 119808,

Been there for about an hour. Other commands are working tho

Good progress on libssl and libboost, I'll keep seeing if I can figure out the issues

The text was updated successfully, but these errors were encountered:

melvincarvalho · 2021-04-13T10:12:37Z

Debug:

2021-04-13 10:10:42 Misbehaving: 31.25.241.224:9265 (0 -> 20)
2021-04-13 10:10:42 ERROR: non-continuous headers sequence
2021-04-13 10:10:42 ProcessMessage(headers, 178534 bytes) FAILED
2021-04-13 10:10:42 Misbehaving: 91.206.16.214:9265 (20 -> 40)
2021-04-13 10:10:42 ERROR: non-continuous headers sequence
2021-04-13 10:10:42 ProcessMessage(headers, 178534 bytes) FAILED
2021-04-13 10:10:42 Misbehaving: 91.134.145.201:9265 (20 -> 40)
2021-04-13 10:10:42 ERROR: non-continuous headers sequence
2021-04-13 10:10:42 ProcessMessage(headers, 178534 bytes) FAILED
2021-04-13 10:10:42 Misbehaving: 66.151.242.154:9265 (20 -> 40)
2021-04-13 10:10:42 ERROR: non-continuous headers sequence
2021-04-13 10:10:42 ProcessMessage(headers, 178534 bytes) FAILED
2021-04-13 10:10:42 Misbehaving: 85.15.179.171:9265 (20 -> 40)
2021-04-13 10:10:42 ERROR: non-continuous headers sequence
2021-04-13 10:10:42 ProcessMessage(headers, 178534 bytes) FAILED
2021-04-13 10:10:43 Misbehaving: 45.33.65.161:9265 (20 -> 40)
2021-04-13 10:10:43 ERROR: non-continuous headers sequence
2021-04-13 10:10:43 ProcessMessage(headers, 178534 bytes) FAILED
2021-04-13 10:10:43 Misbehaving: 95.78.252.70:9265 (40 -> 60)
2021-04-13 10:10:43 ERROR: non-continuous headers sequence
2021-04-13 10:10:43 ProcessMessage(headers, 178534 bytes) FAILED
2021-04-13 10:10:43 Misbehaving: 139.162.122.138:9265 (0 -> 20)
2021-04-13 10:10:43 ERROR: non-continuous headers sequence
2021-04-13 10:10:43 ProcessMessage(headers, 178534 bytes) FAILED

melvincarvalho · 2021-04-13T10:24:42Z

After a while it gives:

9265 failed: Network is unreachable (101)

Perhaps I need an IP address to connect to? But it synced the first blocks fine.

melvincarvalho · 2021-04-13T12:06:19Z

Tried a new install on the working machine

This time it stalled at:

    "blocks" : 17350,

Same message

2021-04-13 12:02:06 Misbehaving: 173.255.252.140 (0 -> 20)
2021-04-13 12:02:06 ERROR: non-continuous headers sequence
2021-04-13 12:02:06 ProcessMessage(headers, 178534 bytes) FAILED

dbkeys · 2021-04-16T09:22:31Z

In regards to Berkeley DB ... these are my notes on how to install it on a new machine so that it is recognized:

wget http://download.oracle.com/berkeley-db/db-4.8.30.zip
unzip db-4.8.30.zip
cd db-4.8.30/build_unix/
../dist/configure --prefix=/usr/local --enable-cxx
sed -i 's/__atomic_compare_exchange/__atomic_compare_exchange_db/g' ../dbinc/atomic.h
make
make install

dbkeys · 2021-04-16T09:28:41Z

I have experienced something like what you describe, where for some reason not clear to me yet, all the peers are judged "misbehaving" .. this lower their score and eventually they are discarded, leading to having no peers at all and of course, this stalls the initial blockchain download.

melvincarvalho · 2021-04-16T09:30:14Z

@dbkeys thanks is there a peer that can be used with the -connect parameter that is known to be synced?

dbkeys · 2021-04-16T09:42:02Z

Yes, these are in the source ( src/chainparams.cpp) as hard coded nodes:
`139.162.128.92

45.33.65.161

173.255.252.140
`

but, also, the DNS seeeder / Node trackers do a good job of keeping a real-time list of up-to date active nodes. (These are the vSeed in chainparams.cpp)
With the dig tool they can be queried from the comman line:
dig da.bitmark.guru
should produce a list of currently active node IP's
like this:
`i7-LapMacNu:~ padiaz$ dig da.bitmark.guru

; <<>> DiG 9.10.6 <<>> da.bitmark.guru
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44490
;; flags: qr rd ra; QUERY: 1, ANSWER: 11, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;da.bitmark.guru. IN A

;; ANSWER SECTION:
da.bitmark.guru. 3599 IN A 139.162.128.92
da.bitmark.guru. 3599 IN A 139.162.35.170
da.bitmark.guru. 3599 IN A 172.104.110.155
da.bitmark.guru. 3599 IN A 91.206.16.214
da.bitmark.guru. 3599 IN A 178.238.224.213
da.bitmark.guru. 3599 IN A 157.161.128.56
da.bitmark.guru. 3599 IN A 83.221.211.116
da.bitmark.guru. 3599 IN A 70.20.216.235
da.bitmark.guru. 3599 IN A 173.255.252.140
da.bitmark.guru. 3599 IN A 192.64.80.50
da.bitmark.guru. 3599 IN A 91.134.145.201

;; Query time: 415 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Fri Apr 16 02:58:21 PDT 2021
;; MSG SIZE rcvd: 220`

There's also a web page: https://chainetics.com/bitmark-nodes.php

melvincarvalho · 2021-04-16T09:57:32Z

@dbkeys thanks for the pointers, I've added this to bitmark.rocks

When I try:

bitmarkd -connect 66.151.242.154
error: couldn't connect to server

But when I try

telnet 66.151.242.154 9265
Trying 66.151.242.154...
Connected to 66.151.242.154.
Escape character is '^]'.

So I can connect via telnet, but bitmarkd throws an error hmmm

melvincarvalho · 2021-04-16T10:06:22Z

Putting them in bitmark.conf seems allow the exe to run

Taking a given node:

2021-04-16 10:01:55 Misbehaving: 91.134.145.201:9265 (0 -> 20)
2021-04-16 10:01:55 ERROR: non-continuous headers sequence
2021-04-16 10:01:55 ProcessMessage(headers, 178534 bytes) FAILED

This node, 91.134.145.201, is in the DNS list

telnet 91.134.145.201 9265
Trying 91.134.145.201...
Connected to 91.134.145.201.
Escape character is '^]'.

dbkeys · 2021-04-16T10:14:37Z

the DNS seeder's list are very dynamic, because it's keeping track of active nodes in real-time;

melvincarvalho · 2021-04-16T10:21:11Z

I tried a new install on my working machine, this time it got as far as:

Block: 175933

Then:

2021-04-16 10:17:49 connect() to [2600:3c03::f03c:91ff:fef1:60bb]:9265 failed: Network is unreachable (101)
2021-04-16 10:17:50 Misbehaving: 91.206.16.214:9265 (80 -> 100) BAN THRESHOLD EXCEEDED
2021-04-16 10:17:50 ERROR: non-continuous headers sequence
2021-04-16 10:17:50 ProcessMessage(headers, 178534 bytes) FAILED
2021-04-16 10:17:50 receive version message: /Pfennig:0.9.7.2/: version 70003, blocks=1160642, us=:51608, them=45.33.65.161:9265, peer=45.33.65.161:9265
2021-04-16 10:17:50 Added time data, samples 13, offset +0 (+0 minutes)
2021-04-16 10:17:50 nTimeOffset = +0  (+0 minutes)
2021-04-16 10:17:50 Misbehaving: 91.134.145.201:9265 (80 -> 100) BAN THRESHOLD EXCEEDED
2021-04-16 10:17:50 ERROR: non-continuous headers sequence
2021-04-16 10:17:50 ProcessMessage(headers, 178534 bytes) FAILED
2021-04-16 10:17:50 Misbehaving: 172.104.110.155:9265 (20 -> 40)
2021-04-16 10:17:50 ERROR: non-continuous headers sequence
2021-04-16 10:17:50 ProcessMessage(headers, 178534 bytes) FAILED
2021-04-16 10:17:50 connect() to [2404:2ac0:0:d::a]:9265 failed: Network is unreachable (101)
2021-04-16 10:17:50 Misbehaving: 83.221.211.116:9265 (80 -> 100) BAN THRESHOLD EXCEEDED
2021-04-16 10:17:50 ERROR: non-continuous headers sequence
2021-04-16 10:17:50 ProcessMessage(headers, 178534 bytes) FAILED
2021-04-16 10:17:51 connect() to [2600:3c01::f03c:91ff:fe6d:1241]:9265 failed: Network is unreachable (101)
2021-04-16 10:17:51 connect() to [2001:4060:4419:1::56]:9265 failed: Network is unreachable (101)
2021-04-16 10:17:52 Misbehaving: 173.255.252.140:9265 (0 -> 20)
2021-04-16 10:17:52 ERROR: non-continuous headers sequence
2021-04-16 10:17:52 ProcessMessage(headers, 178534 bytes) FAILED
2021-04-16 10:17:52 connect() to [2400:8901::f03c:91ff:fea1:117a]:9265 failed: Network is unreachable (101)
2021-04-16 10:17:52 Misbehaving: 172.104.110.155:9265 (40 -> 60)
2021-04-16 10:17:52 ERROR: non-continuous headers sequence
2021-04-16 10:17:52 ProcessMessage(headers, 178534 bytes) FAILED

melvincarvalho · 2021-04-16T10:24:30Z

On restart it connects but does not move forward:

2021-04-16 10:22:39 receive version message: /Pfennig:0.9.7.2/: version 70003, blocks=1160648, us=:53578, them=31.25.241.224:9265, peer=31.25.241.224:9265
2021-04-16 10:22:39 Added time data, samples 6, offset +0 (+0 minutes)
2021-04-16 10:22:39 receive version message: /Pfennig:0.9.7.2/: version 70003, blocks=1160648, us=:50336, them=139.162.35.170:9265, peer=139.162.35.170:9265
2021-04-16 10:22:39 Added time data, samples 7, offset +0 (+0 minutes)
2021-04-16 10:22:39 nTimeOffset = +0  (+0 minutes)
2021-04-16 10:22:39 receive version message: /Pfennig:0.9.7.3/: version 70003, blocks=1160648, us=:34246, them=178.238.224.213:9265, peer=178.238.224.213:9265
2021-04-16 10:22:39 Added time data, samples 8, offset +0 (+0 minutes)
2021-04-16 10:22:39 receive version message: /Pfennig:0.9.7.2/: version 70003, blocks=1160644, us=:41600, them=157.161.128.56:9265, peer=157.161.128.56:9265

dbkeys · 2021-04-16T10:25:02Z

I have always used the ~/.bitmark/bitmark.conf file for specifying nodes
(I get a "Method not found" error if I specify -connect on the command line )

This is some info on the difference between addnode vs. connect :

	##############################################################
	##            Quick Primer on addnode vs connect            ##
	##  Let's say for instance you use addnode=4.2.2.4          ##
	##  addnode will connect you to and tell you about the      ##
	##    nodes connected to 4.2.2.4.  In addition it will tell ##
	##    the other nodes connected to it that you exist so     ##
	##    they can connect to you.                              ##
	##  connect will not do the above when you 'connect' to it. ##
	##    It will *only* connect you to 4.2.2.4 and no one else.##
	##                                                          ##
	##  So if you're behind a firewall, or have other problems  ##
	##  finding nodes, add some using 'addnode'.                ##
	##                                                          ##
	##  If you want to stay private, use 'connect' to only      ##
	##  connect to "trusted" nodes.                             ##
	##                                                          ##
	##  If you run multiple nodes on a LAN, there's no need for ##
	##  all of them to open lots of connections.  Instead       ##
	##  'connect' them all to one node that is port forwarded   ##
	##  and has lots of connections.                            ##
	##       Thanks goes to [Noodle] on Freenode.               ##
	##############################################################

# Use as many addnode= settings as you like to connect to specific peers
#addnode=173.255.252.140
#addnode=139.162.128.92:9265

# Alternatively use as many connect= settings as you like to connect ONLY to specific peers
#connect=172.105.182.91
    #connect=192.168.1.88
    #connect=10.0.0.1:9265

melvincarvalho · 2021-04-16T10:48:20Z

Tried running it again:

This time it got to block: 135775,

It seems to have the misbehaving message a few times. Sometimes it recovers, some times it does not

It seems to stop at a different block each time

melvincarvalho · 2021-04-16T10:55:50Z

Fresh try, it gets to

Block: 37612

Another run

Block: 108722

dbkeys · 2021-04-16T11:11:49Z

Which code are you running (repo & branch) ?

melvincarvalho · 2021-04-16T11:15:46Z

Latest master : 69c1656

This was referenced Apr 13, 2021

TLS / SSL Updates #108

Open

Faster Initial Blockchain Download (IBD) #109

Open

melvincarvalho mentioned this issue May 6, 2021

The network does not appear to fully agree #116

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

unable to compile and run 0.9.7.4 on ubuntu 20.04 #107

unable to compile and run 0.9.7.4 on ubuntu 20.04 #107

melvincarvalho commented Apr 13, 2021

melvincarvalho commented Apr 13, 2021

melvincarvalho commented Apr 13, 2021

melvincarvalho commented Apr 13, 2021

dbkeys commented Apr 16, 2021

dbkeys commented Apr 16, 2021

melvincarvalho commented Apr 16, 2021

dbkeys commented Apr 16, 2021 •

edited

Loading

melvincarvalho commented Apr 16, 2021

melvincarvalho commented Apr 16, 2021

dbkeys commented Apr 16, 2021

melvincarvalho commented Apr 16, 2021 •

edited

Loading

melvincarvalho commented Apr 16, 2021 •

edited

Loading

dbkeys commented Apr 16, 2021 •

edited

Loading

melvincarvalho commented Apr 16, 2021 •

edited

Loading

melvincarvalho commented Apr 16, 2021 •

edited

Loading

dbkeys commented Apr 16, 2021

melvincarvalho commented Apr 16, 2021

unable to compile and run 0.9.7.4 on ubuntu 20.04 #107

unable to compile and run 0.9.7.4 on ubuntu 20.04 #107

Comments

melvincarvalho commented Apr 13, 2021

New Machine

Older machine

melvincarvalho commented Apr 13, 2021

melvincarvalho commented Apr 13, 2021

melvincarvalho commented Apr 13, 2021

dbkeys commented Apr 16, 2021

dbkeys commented Apr 16, 2021

melvincarvalho commented Apr 16, 2021

dbkeys commented Apr 16, 2021 • edited Loading

melvincarvalho commented Apr 16, 2021

melvincarvalho commented Apr 16, 2021

dbkeys commented Apr 16, 2021

melvincarvalho commented Apr 16, 2021 • edited Loading

melvincarvalho commented Apr 16, 2021 • edited Loading

dbkeys commented Apr 16, 2021 • edited Loading

melvincarvalho commented Apr 16, 2021 • edited Loading

melvincarvalho commented Apr 16, 2021 • edited Loading

dbkeys commented Apr 16, 2021

melvincarvalho commented Apr 16, 2021

dbkeys commented Apr 16, 2021 •

edited

Loading

melvincarvalho commented Apr 16, 2021 •

edited

Loading

melvincarvalho commented Apr 16, 2021 •

edited

Loading

dbkeys commented Apr 16, 2021 •

edited

Loading

melvincarvalho commented Apr 16, 2021 •

edited

Loading

melvincarvalho commented Apr 16, 2021 •

edited

Loading