-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add removal policy #4
Comments
I think we should give operators some response time (say 48 hours) to
On Sat, Oct 3, 2015, 2:53 PM ansuz [email protected] wrote:
|
48 is probably a little short. It's a volunteer project and people will get annoyed if they go on vacation and their server goes down. A week? |
I just wanted to open a similar issue before I found this one. It seems like a lot of the offered peers (tested only EU) are no longer reachable and it's quite frustrating to try to connect to dead nodes. A simple UDP-portscan with nmap resulted in closed ports for: Is there something planed which isn't written in this issue so far? |
we were planning on setting up some automated testing, but it hasn't happened yet. @jaythespacehound, @oniichaNj, @fbrandstetter, maybe you folks can report on the status of your nodes? |
My node should be up and running just fine, I used it the other day without issues whatsoever. |
It seems to go down every few hours for me with no errors in the log. Process just vanishes. |
I've removed this server it seems like. I'll fastly grab another one and setup CJDNS there and edit the config, so please don't delete it so far. Feel free to mark it as "down" meanwhile though. |
We should probably remove public peers that aren't up to date (currently v18). There are a number of fixes, and public peers should be a shining example for the rest of the network. |
At what point are credentials considered expired?
The text was updated successfully, but these errors were encountered: