-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
panic in "ipfs bitswap reprovide" #9418
Comments
2022-12-13 converstaion:
|
2023-01-03 conversation: we suspect this isn't happening in the default configuration. After we have 0.18 RC2, we'll ask the original reporters to see if the issue still manifests. |
@AnnaArchivist: is this issue still happening with 0.18-rc2? |
Closing since don't have a reproducible case and haven't heard it happening in 0.18 and beyond. |
"ipfs bitswap reprovide" needs to be fixed, I got a similar problem with "Reprovider.Strategy" not set. (The default is "all", I belive). "ipfs bitswap reprovide" apparently "triggers reprovider to announce our data to network" and is a recommended way to make IPFS work better on forums. Having only a 20mb website (about 100 files) on IPFS, I set a cron job on two different servers, to do "ipfs bitswap reprovide" every hour on two different VPS's. Doing the command manually appeared to just hang, no info whatsoever, and I had to "ctrl+C" out of it, but tried it anyway. TL,DR: Don't. My website was always online when I visited it, but "Uptimia" told me, multiple times per day, there was a "503 service unavailable" error. i.e.: IPFS was crashing/restarting. So, I investigated. "journalctl -u ipfs" on server 1
"journalctl -u ipfs" on server 2
But no restarts since 4 days ago on server2? "ps aux | grep ipfs" on server2:
...gave me 26 instances of "ipfs bitswap reprovide" running Long story short: executing "ipfs bitswap reprovide", even for 20mb (about 200 files), is too much for 512mb or 1gb of ram, and will systematically crash your IPFS daemon every time. I cannot try that on servers with multiple cores and multiple gb's of ram, but... big server or not, this is definitely not the intended result. IPFS worked fine, stable, no crashes, for multiple months, without "ipfs bitswap reprovide" as a cron job. |
Hi, @LeDechaine, thank you for feedback, but this is unrelated to this already closed bug. Please see https://github.com/ipfs/kubo#minimal-system-requirements |
Problem
Panic manifests only when
Reprovider.Strategy
is set toroots
and/or some of the blocks are missing.
Version
Config
Click to expand
Description
Sometimes, but not always, the
ipfs bitswap reprovide
step mentioned above crashes the daemon with the following message:The text was updated successfully, but these errors were encountered: