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

provide error data per respondd and add a command to empty reboot count #6

Open
rubo77 opened this issue Jul 30, 2018 · 3 comments
Open

Comments

@rubo77
Copy link

rubo77 commented Jul 30, 2018

This way we could monitor the whole mesh, which routers have problems

@TobleMiner
Copy link
Collaborator

TobleMiner commented Jul 30, 2018

We could do that if we knew why the router rebooted. Most of the time reboots are a result of errors in kernel space. We can not capture the error messages without external hardware.

@rubo77
Copy link
Author

rubo77 commented Jul 30, 2018

Ok. But better than nothing

@TobleMiner
Copy link
Collaborator

Are you talking about gluon-quickfix specifically? We could of course capture error output generated by it, that's true. I guess it could actually prove quite helpful since we do at the moment not really have any idea if quickfix is helping and on how many devices it does actually perform reboots. Monitoring its activity might be a good idea.

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

No branches or pull requests

2 participants