Saving the network by killing the network
summary
Raspberry Pi cameras push images to a central server over WebSockets and occasionally Nerves forgets its WiFi config and stops connecting. a short wrapper watches the binary WebSocket process, waits five seconds then kills and restarts it, and a separate app called the network killing supervisor links a network killer to the Nerves networking wrapper so that failing networking processes get killed and restarted under a supervision tree until the whole app is restarted on repeated failures.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:31Why not a brick
- 0:59How it works
- 1:28The 404
- 1:47Leaking processes
- 2:25The workaround
- 3:35The network killing supervisor
- 4:00Restart strategy
- 4:14Conclusion
related talks
38mNerves + Phoenix Saves a Father's Sanity!
32mTaking back control of your life with Nerves
40mNervous System - Nerves Clustering Using Your Own Distribution
46mFunctional IoT with Elixir and Nerves
18mNetKeeper: Enhancing Network Resilience with Autonomous Network Configuration...
16mWiFröst: Bridging the Information Gap for Debugging of Networked Embedded Systems
01h 01mMachine Learning, Networks, and IoT
46mSelf-Programming Networks: Network Clock Synchronization, Event Playback and Real-time Action