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

acnodes need to fail gracefully in event of network failure to acserver #57

Open
zymurgic opened this issue Jan 29, 2019 · 1 comment
Open
Labels
bug Critical Stability Issues identified as being critical stability issues that need fixing

Comments

@zymurgic
Copy link
Contributor

In the event of network failure between a booted acnode and acserver, it shouldn't mis-interpret the failure to connect to acserver as a tool-should-be-out-of-service error.
especiallly when the tool is currently in use.
it should also be able to gracefully fall back to using cached credentials, especially where it's using sdcard or eeprom card caches.

Today, this occurred when a network switch crashed and failed to forward packets), taking out both the 3d printers.

@mich181189 mich181189 added bug Critical Stability Issues identified as being critical stability issues that need fixing labels Jul 8, 2019
@zymurgic
Copy link
Contributor Author

zymurgic commented Jul 9, 2019

acserver has been moved to the same VLAN as the acnodes themselves, which removes one point of failure. Still reliant on working network switches, but no longer reliant (at least from a packet-forwarding perspective) on a working router/firewall. Still requires DHCP leases to be able to renew or fail gracefully; A working DNS resolver is still very useful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Critical Stability Issues identified as being critical stability issues that need fixing
Projects
None yet
Development

No branches or pull requests

2 participants