peers UNRESPONSIVE #106
Comments
|
I can confirm "Magik6k-sbg1" "jazzanet" "igel-amersfoort", many days, maybe weeks or months unresponsive |
|
@magik6k, @wfleurant, any comment? I've also pinged the other operators via email. I know that I've been having trouble pinging nodes lately, even when they are known to be available. If we don't get any feedback from the operators, then we can remove the listings. |
|
Should be fixed, can you confirm it's working? |
|
@magik6k: the ipv4 peer is still UNRESPONSIVE on my side. the details of the peer are the ones in magik6k.net.k |
|
Looks like it's fixed now: |
|
|
I've updated things; let me know if you've any issues (the keys have all changed though) |
|
@cwningen the updated IPv4 peers (coes, penfar, traed) are marked unresponsive on my side. I've tested this from two nodes on different networks. |
|
Odd, I can see they're all up and I have connection to and can see various things through them. Although given the timing of your comment it might be down to my upstreams AS44684 having issues over the weekend. Are they still appearing down to you? |
|
can't connect to eu/ru/spb/ru.spb.tokakoka.k from 2 different PC/networks |
|
@cwningen I am exhibiting the same issues on two of my nodes, toward the peers over IPv4, maybe someone else can join in and let us know if it's working for them? |
|
Can't connect to *.swningen.cymru ipv4 from NL and from RU
|
|
Odd. cjdroute was receiving the packets but not sending back on the correct address as these hosts have multiple addresses, it used the defaults. I've explicitly set the bind addresses for v4 and v6 accordingly so it should now work for others. Have confirmed it does work over v4 here post change and restart. |
|
I would like to close this issue. The following peers are still unresponsive on my side (IPv4 only): @ansuz let me know if this should be closed anytime soon. thanks! |
|
@lvlts by close do you mean resolve? Your Could you figure out who owns those nodes, and mention them all here? If it's @cwningen's nodes affected...
I'm not sure what to do if they've confirmed it's working from a different location. There could be lots of things interfering with your nodes, which would not necessarily affect other's usage of the same credentials, so I'm hesitant to remove them. Perhaps you could work out a time to chat via irc or some other im platform, and debug the issue. If the issue can't be narrowed down, but the nodes work for others, the best I can offer is to try using a different set of credentials. |
|
So, the following nodes, as of this writing, are appearing
I'm only able to validate these nodes from two locations, it would be great if someone else can also check the peering on these. Also, thank you @cwningen - nodes are working now. |
|
Thank you for noticing @lvlts, I'll fix my node. |
|
@kyrias The nodes listed in stash-crypto.k appear to be down at this time. Are you planning to bring these peers back up? |
|
it seems, that this nodes are offline more time:
|
|
@blackknight36 @CupIvan If either of you would have bothered actually looking at the last commit for the things you ping me for you would have realized that I have absolutely nothing to do with either server. |
|
Yes, remove mine please! |
|
Oh, hello! Sorry, I haven't been running those servers for quite a while 😿 I can make a pull request to clean them out :) Update! #141 🌈 |
|
Hi all, I can't maintain this any more and added a pull request to delete de/bavaria/hype.jazzanet.com.k |
|
please check this peers, it seems unresponsive long time (ping fail):
|
|
You can take down those servers, the ip's are dead as we have moved all are
servers to DigitalOcean
On Mon, Nov 5, 2018 at 10:43 AM CupIvan ***@***.***> wrote:
please check this peers, it seems unresponsive long time (ping fail):
owner node commit
@wfleurant <https://github.com/wfleurant>
/eu/nl/amsterdam/igel-amersfoort.ams.k 1e715a2
<1e715a2>
@kylerchin <https://github.com/kylerchin>
/na/us/northcarolina/charlotte/ic2.hellomouse.cf.k 350fdc4
<350fdc4>
@bug0000 <https://github.com/bug0000> /eu/ru/spb/ru.spb.tokakoka.k 53660ef
<53660ef>
@willeponken <https://github.com/willeponken>
/eu/se/lulea/bliss.willeponken.me.k dcd3963
<dcd3963>
@geistesk <https://github.com/geistesk> /eu/de/hesse/h.ancha.lurk.space.k
bfc3a41
<bfc3a41>
@iczero <https://github.com/iczero> /eu/ua/kiev/kiev/ic.hellomouse.cf.k
218e225
<218e225>
@oniichaNj <https://github.com/oniichaNj> /eu/nl/amsterdam/mrowr.me.k
a48b755
<a48b755>
@kylerchin <https://github.com/kylerchin>
/na/us/california/san-francisco/kylerchin/bootnode-2.k 350fdc4
<350fdc4>
@merkjinx <https://github.com/merkjinx> /eu/fr/paris/h.rwfr.k fed5ad7
<fed5ad7>
@cwningen <https://github.com/cwningen> /eu/uk/london/cwningen.cymru.k
ff568ce
<ff568ce>
@Show-vars <https://github.com/Show-vars>
/eu/ru/moscow/node01.msk.ru-mesh.net.k 5fc0fd9
<5fc0fd9>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#106 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHMJ5u50lTnI1YXjO4ZJ5SuUBNlEWjwbks5usIbogaJpZM4Pxm6I>
.
--
From Kyler Chin
|
|
My apologies I recently migrated servers, will update ASAP. |
|
Is there any way we could set up an automated process to monitor these nodes? |
|
My server (bliss.willeponken.me) has been down a while due to electrical
problems in the server hall at my university. I could remove it and re-add
later?
Den mån 5 nov. 2018 19:54Michael <notifications@github.com> skrev:
… Is there any way we could set up an automated process to monitor these
nodes?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#106 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEVK_ZijyzQLeefow4WnjJGgaai4kYj8ks5usIlIgaJpZM4Pxm6I>
.
|
wrote simple script for ping public peers by IP and IPv6: cjdelisle/cjdns#1188 |
|
@CupIvan please do! |
|
Mine ( |
|
I pinged all nodes in repo with my script. There are problem nodes in table: |
|
I'm migrating my node, will update once done |
|
I'm no longer hosting mrowr.me and it can be removed. |
|
|
|
My node is definitely online, IPv4 should respond. PING linux1.tor1.watters.ws (165.227.44.84) 56(84) bytes of data. |
ping from my computer is fail but I test from another server - it seems ok probably it is the russian blocking internet system :-( |
|
isn't cjdns supposed to be censorship proof? |
|
@obedm503 the network as a whole is supposed to be censorship proof, but specific links over the internet can be censored as everything else on the internet. |
|
hi, if you also want to double-check availability through an EC2 (afaik) instance, I have a Travis-CI build which runs on a daily basis located at: https://lvlts.github.io/hyperboria-peer-check/ Feel free to check out the repository, which contains the build scripts which output that page. The downside to it is that I have not been able to test the IPv6 builds, as Travis does not support IPv6, and other means (Miredo) do not work, due to the restricted capabilities the build environment has. I also noticed that the @magik6k node is no longer available on IPv4 lately. |
|
This peers unresponsive more than 3 weeks, please check it:
|
|
Pull request for deletion of /eu/de/bavaria/weuxel.modi.k created. |
hi.
several peers are no longer online and appear UNRESPONSIVE:
the peers above are used, in my specific environment, only over ipv4.
are there any plans on bringing them back on?
thanks
The text was updated successfully, but these errors were encountered: