Author Topic: !!!CAUTION!!! All public seed nodes down??  (Read 15074 times)

0 Members and 1 Guest are viewing this topic.

iHashFury

  • Guest
we should get these out of the default seed node list for the next update ..

Happy to remove 104.168.154.160:50696 from the default list as it not playing nice,  my other seed node is solid.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
we should get these out of the default seed node list for the next update ..


Offline wackou

Please vote for witness wackou! More info at http://digitalgaia.io

Offline wackou

Please add my primary seed node to your list.

212.47.249.84:50696

Hm... it should get added automatically, eventually. Provided that it is well-connected itself, and accepts connections.

Strange - my node is up and has been for some time according to http://status.bitsharesnodes.com/

Why is it strange? I ran all of my nodes on port 1779 for months and they always had between 40 and 60 connections each, despite them not being advertised. Now that they're running on port 1776 I get closer to 100 connections on each node.

Apparently the nodes have a way of finding each other. Also, for whatever reason, all 4 of my nodes have not experienced the "stuck" state for a full week now.

iHashFury's node should get added with time as pc mentioned, as I guess his crawler hasn't been running for too long on the bitshares network and hasn't had the time to map the entire network yet. I believe there are more nodes in the bitshares network than the ~10 nodes on pc's page. Give it some time :)

As for you, Thom, what happened is that your nodes are declared to be on port 1776 in the official list of the bitshares client (see https://github.com/BitShares/bitshares-2/blob/bitshares/libraries/app/application.cpp#L154).
When they were running on port 1779 they were not acting as seed nodes and so were "just" full nodes. Now that you are on port 1776 you get connected to as seed nodes by people starting the client, hence the higher number of connections I guess.
Please vote for witness wackou! More info at http://digitalgaia.io

Offline Thom

Please add my primary seed node to your list.

212.47.249.84:50696

Hm... it should get added automatically, eventually. Provided that it is well-connected itself, and accepts connections.

Strange - my node is up and has been for some time according to http://status.bitsharesnodes.com/

Why is it strange? I ran all of my nodes on port 1779 for months and they always had between 40 and 60 connections each, despite them not being advertised. Now that they're running on port 1776 I get closer to 100 connections on each node.

Apparently the nodes have a way of finding each other. Also, for whatever reason, all 4 of my nodes have not experienced the "stuck" state for a full week now.
Injustice anywhere is a threat to justice everywhere - MLK |  Verbaltech2 Witness Reports: https://bitsharestalk.org/index.php/topic,23902.0.html

iHashFury

  • Guest
Please add my primary seed node to your list.

212.47.249.84:50696

Hm... it should get added automatically, eventually. Provided that it is well-connected itself, and accepts connections.

Strange - my node is up and has been for some time according to http://status.bitsharesnodes.com/

Offline pc

  • Hero Member
  • *****
  • Posts: 1530
    • View Profile
    • Bitcoin - Perspektive oder Risiko?
  • BitShares: cyrano
Please add my primary seed node to your list.

212.47.249.84:50696

Hm... it should get added automatically, eventually. Provided that it is well-connected itself, and accepts connections.
Bitcoin - Perspektive oder Risiko? ISBN 978-3-8442-6568-2 http://bitcoin.quisquis.de

iHashFury

  • Guest
Please add my primary seed node to your list.

212.47.249.84:50696

Offline pc

  • Hero Member
  • *****
  • Posts: 1530
    • View Profile
    • Bitcoin - Perspektive oder Risiko?
  • BitShares: cyrano
Bump!

We're still low on reliable seed nodes, see http://seeds.quisquis.de/bitshares.html .

If you want to run a seed node you should apply this fix to avoid crashes:
https://github.com/abitmore/bitshares-2/commit/aa844f56faac4dda0d542520a672c4704fb0e617

And please use port 1776 for the p2p socket. That will make your node reachable under our new DNS seed seeds.bitshares.eu:1776 .
Bitcoin - Perspektive oder Risiko? ISBN 978-3-8442-6568-2 http://bitcoin.quisquis.de

Offline Thom

A view of the status of all seed nodes can be seen here:

http://seed.bitsharesnodes.com/network/bts/seednodes

As you can see, the situation is pretty dire, so let's make this a wake up call:

Quote
SEED NODE OPERATORS, PLEASE FIX YOUR SEED NODES!!

This is very useful.  +5% +5%

By the way my node got stuck again. Same situation: "accept_loop" is destroyed. However the latest incoming connection was successfully established, so it should not be the cause.

Will add more logs and check next time.

I fixed mine today. Have you discovered why the seeds get "stuck"?  You mention accept_loop so I presume you're looking into a bug in the code. Any more news or info to report?

Injustice anywhere is a threat to justice everywhere - MLK |  Verbaltech2 Witness Reports: https://bitsharestalk.org/index.php/topic,23902.0.html

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
A view of the status of all seed nodes can be seen here:

http://seed.bitsharesnodes.com/network/bts/seednodes

As you can see, the situation is pretty dire, so let's make this a wake up call:

Quote
SEED NODE OPERATORS, PLEASE FIX YOUR SEED NODES!!

This is very useful.  +5% +5%

By the way my node got stuck again. Same situation: "accept_loop" is destroyed. However the latest incoming connection was successfully established, so it should not be the cause.

Will add more logs and check next time.
BitShares committee member: abit
BitShares witness: in.abit

Offline wackou

A view of the status of all seed nodes can be seen here:

http://seed.bitsharesnodes.com/network/bts/seednodes

As you can see, the situation is pretty dire, so let's make this a wake up call:

Quote
SEED NODE OPERATORS, PLEASE FIX YOUR SEED NODES!!
Please vote for witness wackou! More info at http://digitalgaia.io

Offline wackou

Here is the first few lines in my config.ini file. I see no reason why it should use port 1779 instead of port 1776:

Quote
# Endpoint for P2P node to listen on
p2p-endpoint = 0.0.0.0:1776

# P2P nodes to connect to on startup (may specify multiple times)
#seed-node = 45.55.6.216:1776
#seed-node = 114.92.254.159:62015
#seed-node = seed01.bitsharesnodes.com:1776
#seed-node = seed02.bitsharesnodes.com:1776
#seed-node = seed03.bitsharesnodes.com:1776
#seed-node = seed04.bitsharesnodes.com:1776
#seed-node = seed05.bitsharesnodes.com:1776
#seed-node = seed06.bitsharesnodes.com:1776
#seed-node = seed07.bitsharesnodes.com:1776
#seed-node = 188.165.233.53:1777
#seed-node = 104.236.51.238:2005
#seed-node = 114.92.254.159:62015


As you can see the p2p-endpoint is defined to use 1776 and all of the seed definitions are built into the code, none are configured in the runtime config file. When I use netstat there are no listeners on 1776 but plenty on 1779, so the only conclusion I would be inclined to make is the definitions in the code must specify 1779 to override the p2p-endpoint defined in the config file.
You're starting with bts_tools right? @wackou any idea?

yes, you should look into the "~/.bts_tools/config.yaml" file that defines the clients to run, not in the config.ini file. There you can add the "p2p_port" field set to 1776, eg:

Code: [Select]
nodes:
    bts:
        p2p_port: 1776
        ...

and restart your seed node for the change to take effect.
Please vote for witness wackou! More info at http://digitalgaia.io