Cleanup Ellaism bootnodes

[ellaismer]

Removed several bootnodes known not to be running anymore. Added two new ones.

[parity-cla-bot]

It looks like @ellaismer signed our Contributor License Agreement. 👍

Many thanks,

Parity Technologies CLA Bot

[5chdn]

None of the nodes are working for me. Are that actual peers or just some kind of boot node that seeds peers and disconnects?

[ellaismer]

@5chdn That's weird. Most of those bootnodes are actual peers, and I'm able to use them to successfully sync the network. It might be that some peers are full so they reject new peers. And how did you test whether they're working?

[5chdn]

$ parity --chain ./ellaism.json --reserved-peers ./ellaism.peer --reserved-only                                                                                                                               

with ellaism.json and where ellaism.peer contains the bootnodes

[5chdn]

maybe you should increase the max-peers of the bootnodes?

[ellaismer]

I checked bootnodes that I have control (the first three). None of them reached max-peers.

There're some nodes there I need to run an older Parity version (v1.6.10), would that be an issue?

[ellaismer]

And I'm able to at least connect to 2 peers using the command you provided, with ellaism.json file as in this PR and ellaism.peer file set as the bootnodes.

 Syncing #1252020 d6e9…e917     0 blk/s    0 tx/s   0 Mgas/s    246+    0 Qed  #1252305    2/25 peers   79 KiB chain 7 KiB db 1 MiB queue 601 KiB sync  RPC:  0 conn,  0 req/s,   0 µs
 Syncing #1252909 6f7f…df26    88 blk/s  817 tx/s  22 Mgas/s      0+    0 Qed  #1252909    2/25 peers   2 MiB chain 361 KiB db 0 bytes queue 452 KiB sync  RPC:  0 conn,  0 req/s,   0 µs

Hmm just wonder what might be the problem..

[5chdn]

It's working well if I drop the reserved-only option, so I'm fine with merging this.