Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
WebUI hammers my daemon
See original GitHub issueWhen I open the webUI (maybe after clicking Files) it starts triggering hundreds http://127.0.0.1:5001/api/v0/object/get requests to the IPFS daemon and everything stops working well (my browser, my daemon, my computer). I feel things shouldn’t be like this?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Failing to geolocate any peers · Issue #918 · ipfs/ipfs-webui · GitHub
Web UI no longer shows any peers on the map. Calls to ipfs-geoip are ... https://github.com/ipfs-shipyard/ipfs-webui/blob/ ... WebUI hammers my daemon #882.
Read more >Chapter 5. Troubleshooting Red Hat Satellite 6.4
All virt-who instances configured and deployed using either the Satellite web UI or hammer are reported in the Satellite web UI. Those virt-who...
Read more >Managing Hosts - Foreman documentation
You can manage your hosts from the Foreman web UI or from the command line. ... For the list of available interface settings,...
Read more >Monit Manual
Monit is particularly useful for monitoring daemon processes, ... To protect the security of your control file and passwords the control file must...
Read more >Reef Pi web interface not working - Reef2Reef
Hi all, I recently moved my reef pi to a new tank today. ... 0 0 0.0.0.0:5353 0.0.0.0:* 382/avahi-daemon: r udp 0 0...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’ve dialled it right down, so we queue the requests and excute them one by one rather than in parallel. I plan to redesign the peers page this quarter so that it focuses on highlighting peers near you, and lets you connect to peers manually, rather than just “geolocate them all”, to reduce the issue further.
Yes. We feel the same feels. There is a runaway cpu load issue caused by using the ipfs-geoip db ipfs/go-ipfs#5613
We’ve dialled it down, but it could do less. In the short term I will have move the geolocation logic to just the peers page. It will still hammer the daemon, but only when you go looking at your peers list / map. There is #848 to track that.
Longer term we need to calm ipfs down. It should be possible to look up all the ipfs-geoip blocks for 800 ipv4 addresses, without causing the fans to spin.