Bootstrap test inconsistent #1597

New Issue

2020-01-30T07:02:57+01:00

PeterSurda commented

2020-01-30 07:02:57 +01:00

(Migrated from github.com)

The boostrap test (e.g. on travis) sometimes fails. It probably is due to a fault in the test, client connection handling (drop a connection before downloading all the data), server connection handling (they drop connection before sending addresses or flushing the stream) or some combination thereof.

It's not exclusively a problem of travis, I'm moving the tests to buildbot and the same happens there. If you retry the test enough it will eventually succeed.

I'll check if the bootstrap servers that I have access to have the latest code, if that doesn't fix it maybe someone can look at it in more detail.

fix #1598
check bootstrap servers up to date
check if test is working correctly
check if servers send addresses if full / duplicate IP
check if servers close the connection after the stream is flushed
check if client closes connection after all data is read
if it's still broken, investigate what else it could be

The boostrap test (e.g. on travis) sometimes fails. It probably is due to a fault in the test, client connection handling (drop a connection before downloading all the data), server connection handling (they drop connection before sending addresses or flushing the stream) or some combination thereof. It's not exclusively a problem of travis, I'm moving the tests to buildbot and the same happens there. If you retry the test enough it will eventually succeed. I'll check if the bootstrap servers that I have access to have the latest code, if that doesn't fix it maybe someone can look at it in more detail. - [x] fix #1598 - [x] check bootstrap servers up to date - [ ] check if test is working correctly - [ ] check if servers send addresses if full / duplicate IP - [ ] check if servers close the connection after the stream is flushed - [ ] check if client closes connection after all data is read - [ ] if it's still broken, investigate what else it could be

👍 1

g1itch commented

2020-01-30 16:50:39 +01:00

(Migrated from github.com)

Maybe this is related:

ERROR - bootstrap8080.bitmessage.org:8080 error: 2, Too many connections from your IP. Closing connection.

Maybe this is related: ``` ERROR - bootstrap8080.bitmessage.org:8080 error: 2, Too many connections from your IP. Closing connection. ```

PeterSurda commented

2020-01-31 02:03:17 +01:00

(Migrated from github.com)

@g1itch In such a case, the server is supposed to send an addr command before dropping the connection. But maybe it wasn't correctly implemented or refactored to asyncore as I don't remember ever testing it.

@g1itch In such a case, the server is supposed to send an `addr` command before dropping the connection. But maybe it wasn't correctly implemented or refactored to asyncore as I don't remember ever testing it.

PeterSurda commented

2020-01-31 07:02:36 +01:00

(Migrated from github.com)

Update: bootstrap servers don't have the latest code, but there are excessive memory usage problems with the latest code, so I'm postponing upgrades until #1598 is resolved.

PeterSurda commented

2020-02-06 16:56:26 +01:00

(Migrated from github.com)

So I updated the bootstrap servers and while checking them, only those that I operate appear to be online. All the others probably belonged to former users who don't run a node anymore or their IP changed. One I think belongs to Jonathan Warren but don't know about the others.

I made sure all mine ( 5 ) are up and running with the latest code. There is currently no working IPv6 boostrap, and I haven't checked the tor bootstrap (which also is run by me but it's an weak system so want to setup a different one).

I'll keep rerunning the test job to see if it improves. Maybe this (making sure mine work and have the latest code) is enough to fix it, but over longer period of time more servers run by others would be welcome, and I need to adjust the DNS records accordingly.

So I updated the bootstrap servers and while checking them, only those that I operate appear to be online. All the others probably belonged to former users who don't run a node anymore or their IP changed. One I think belongs to Jonathan Warren but don't know about the others. I made sure all mine ( 5 ) are up and running with the latest code. There is currently no working IPv6 boostrap, and I haven't checked the tor bootstrap (which also is run by me but it's an weak system so want to setup a different one). I'll keep rerunning the test job to see if it improves. Maybe this (making sure mine work and have the latest code) is enough to fix it, but over longer period of time more servers run by others would be welcome, and I need to adjust the DNS records accordingly.

PeterSurda commented

2020-08-27 16:17:06 +02:00

(Migrated from github.com)

Update: Today I removed non-responding servers from DNS records and updated all those servers that I control to the current v0.6.

👍 1

This repo is archived. You cannot comment on issues.