Skip to content
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

Open
ansuz opened this issue Oct 3, 2015 · 8 comments
Open

add removal policy #4

ansuz opened this issue Oct 3, 2015 · 8 comments

Comments

@ansuz
Copy link
Member

ansuz commented Oct 3, 2015

At what point are credentials considered expired?

@dansup
Copy link
Contributor

dansup commented Oct 3, 2015

I think we should give operators some response time (say 48 hours) to
address credential issues, and if they do not respond to the issue that it
should be removed.

  • someone creates an issue about broken creds
  • operator is contacted and asked to respond
  • incident is addressed in issue or else it gets removed after X time

On Sat, Oct 3, 2015, 2:53 PM ansuz [email protected] wrote:

At what point are credentials considered expired?


Reply to this email directly or view it on GitHub
#4.

@ansuz
Copy link
Member Author

ansuz commented Oct 3, 2015

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?

@oxzi
Copy link
Contributor

oxzi commented Aug 31, 2016

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?

@ansuz
Copy link
Member Author

ansuz commented Aug 31, 2016

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?

@oniichaNj
Copy link
Contributor

My node should be up and running just fine, I used it the other day without issues whatsoever.

@jaythespacehound
Copy link
Contributor

It seems to go down every few hours for me with no errors in the log. Process just vanishes.
I've just pulled the latest version let's see if it stays up longer. If not I'll eventually cave and systemd it I guess.

@fbrandstetter
Copy link
Contributor

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.

@ansuz
Copy link
Member Author

ansuz commented Oct 24, 2016

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants