!!!CAUTION!!! All public seed nodes down??

[abit]

Yeah, I get the same results.

I don't understand the logic of that script, or perhaps I don't understand the protocol. Looks like you send EOF to a node with netcat and wait 2 seconds for a response then terminate the connection. The script will wait up to 10 seconds to establish the connection. If the witness doesn't return a string the script result is failed otherwise it's ok.

Is EOF End of File or End of Frame? Either way the witness is supposed to respond to basically null data with an ack of some sort?

As I said I get the same result as you, yet as you say the nodes are all talking. Sorry if this sounds negative, but this is pretty much what frustrates me about how the devs in this community communicate. It's just too terse and abbreviated and I struggle to follow as a result. I think it's safe to say if transactions weren't being processed the indication would be more obvious.

You clearly have deeper knowledge of BitShares internals than I do, but I'm afraid you'll have to provide a few more details before I'll understand what the issue is. As for monitoring my nodes I am using wackou's bts_tools which is far more comprehensive at monitoring the nodes than I've seen from other sources. Not saying it's the best at it, there may be other tools which are better but I haven't seen them described or documented as well as bts_tools. The tools could use some refinement, but no code is perfect.

If you want me to do other tests or want me to check anything just let me know and I'll do my best to help you out.

Sorry I have no time to explain. Perhaps I'll get @wackou to talk with you, seems you trust him more. Best if @bytemaster has written a white paper for the protocol, but right now all info is in the code.

[Thom]

Yeah, I get the same results.

I don't understand the logic of that script, or perhaps I don't understand the protocol. Looks like you send EOF to a node with netcat and wait 2 seconds for a response then terminate the connection. The script will wait up to 10 seconds to establish the connection. If the witness doesn't return a string the script result is failed otherwise it's ok.

Is EOF End of File or End of Frame? Either way the witness is supposed to respond to basically null data with an ack of some sort?

As I said I get the same result as you, yet as you say the nodes are all talking. Sorry if this sounds negative, but this is pretty much what frustrates me about how the devs in this community communicate. It's just too terse and abbreviated and I struggle to follow as a result. I think it's safe to say if transactions weren't being processed the indication would be more obvious.

You clearly have deeper knowledge of BitShares internals than I do, but I'm afraid you'll have to provide a few more details before I'll understand what the issue is. As for monitoring my nodes I am using wackou's bts_tools which is far more comprehensive at monitoring the nodes than I've seen from other sources. Not saying it's the best at it, there may be other tools which are better but I haven't seen them described or documented as well as bts_tools. The tools could use some refinement, but no code is perfect.

If you want me to do other tests or want me to check anything just let me know and I'll do my best to help you out.

[abit]

Are we talking BitShares or STEEM? The OP says BitShares, but your last post looks like STEEM. Don't you guys have a separate channel for STEEM witnesses, and why post here on BitShares General Discussion? For those witnesses like myself who aren't engaged as a STEEM witness (I find ramping up on STEEM project too frustrating, knowledge limited and scattered, making it hard to follow), please be clear so as not to give us false alerts.

According to my tools bitshares seeds (at least the 4 I run) have not shown any issues in the last 24 hours.

Thanks.

@Thom Please try the script by yourself.
Your BitShares seed nodes are either refusing or not responding to new connections, although they are in sync (which means established connections and perhaps outgoing connections are working fine so far).

Code: [Select]

$ [ -n "`echo EOF | nc seed04.bitsharesnodes.com 1776 -w 10 -q 2`" ] && echo Ok || echo Failed
Failed

Thanks @ripplexiaoshan for the explanation.

[ripplexiaoshan]

You misunderstood it. abit just illustrated a method to monitor the seed node of bitshares, and that method is got from steem.

Are we talking BitShares or STEEM? The OP says BitShares, but your last post looks like STEEM. Don't you guys have a separate channel for STEEM witnesses, and why post here on BitShares General Discussion? For those witnesses like myself who aren't engaged as a STEEM witness (I find ramping up on STEEM project too frustrating, knowledge limited and scattered, making it hard to follow), please be clear so as not to give us false alerts.

According to my tools bitshares seeds (at least the 4 I run) have not shown any issues in the last 24 hours.

Thanks.

[Thom]

Are we talking BitShares or STEEM? The OP says BitShares, but your last post looks like STEEM. Don't you guys have a separate channel for STEEM witnesses, and why post here on BitShares General Discussion? For those witnesses like myself who aren't engaged as a STEEM witness (I find ramping up on STEEM project too frustrating, knowledge limited and scattered, making it hard to follow), please be clear so as not to give us false alerts.

According to my tools bitshares seeds (at least the 4 I run) have not shown any issues in the last 24 hours.

Thanks.

[abit]

FYI steempty@steem made a simple bash script to monitor seed node:

Code: [Select]

[ -n "`echo EOF | nc steem.clawmap.com 2001 -w 10 -q 2`" ] && echo Ok || echo Failed


[xeroc]

And I thought it's just been my connection .. will check more closely when I run into this again

[cube]

Thanks for the alert. Restarted bitcube seed. It is working now.

[abit]

Someone is attacking BitShares? Or bug?

Code: [Select]

1535394ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 83.221.132.47:1776
1541939ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 188.40.91.213:1776
1541939ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 114.92.236.175:62015
1556942ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 71.197.2.119:1776
1561942ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 45.32.247.234:1776
1567965ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 82.211.31.175:1776
1571306ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 159.203.15.153:1776
1572544ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 188.166.188.206:1776
1573421ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 107.170.245.89:1777
1573421ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 54.85.252.77:39705
1573421ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 104.236.144.84:1777
1573421ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 40.127.190.171:1777
1573421ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 185.25.22.21:1776
1573422ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 23.95.43.126:50696
1573422ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 109.73.172.144:50696
1573422ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 128.199.143.47:2015


Code: [Select]

~$ telnet 83.221.132.47 1776
Trying 83.221.132.47...
^C
~$ telnet 188.40.91.213 1776
Trying 188.40.91.213...
telnet: Unable to connect to remote host: Connection refused
~$ telnet 71.197.2.119 1776
Trying 71.197.2.119...
telnet: Unable to connect to remote host: Connection refused
~$ telnet 45.32.247.234 1776
Trying 45.32.247.234...
telnet: Unable to connect to remote host: Connection refused
~$ telnet 82.211.31.175 1776
Trying 82.211.31.175...
telnet: Unable to connect to remote host: Connection refused
~$ telnet 159.203.15.153 1776
Trying 159.203.15.153...
telnet: Unable to connect to remote host: Connection refused
~$ telnet 188.166.188.206 1776
Trying 188.166.188.206...
telnet: Unable to connect to remote host: Connection refused
~$ telnet 107.170.245.89 1777
Trying 107.170.245.89...
Connected to 107.170.245.89.
Escape character is '^]'.
^]
telnet> quit
Connection closed.
~$ telnet 54.85.252.77 39705
Trying 54.85.252.77...
^C
~$ telnet 104.236.144.84 1777
Trying 104.236.144.84...
^C
~$ telnet 40.127.190.171 1777
Trying 40.127.190.171...
^C
~$ telnet 185.25.22.21 1776
Trying 185.25.22.21...
^C
~$ telnet 23.95.43.126 50696
Trying 23.95.43.126...
^C
~$ telnet 109.73.172.144 50696
Trying 109.73.172.144...
^C
~$ telnet 128.199.143.47 2015
Trying 128.199.143.47...
telnet: Unable to connect to remote host: Connection refused

After found it's not responding, I just restarted my seed node. A working seed node should respond like this:

Code: [Select]

~$ telnet 114.92.236.175 62015
Trying 114.92.236.175...
Connected to 114.92.236.175.
Escape character is '^]'.
]▒▒a▒X
      ▒o▒▒▒g▒▒s▒a▒Z▒f▒^]