You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Someitmes we kill the node without allowing it to remove lock file and it fails launch start next time with error brave_ipfs/repo.lock: someone else has the lock
Steps to Reproduce
Fast start/stop node on macos, especially when node is busy with something as migration
If the node will not respond more than 2 seconds it will be killed without removing lock file
The node will fail start next time with brave_ipfs/repo.lock: someone else has the lock error
Actual result:
Unable to start node
Expected result:
Start/stop node works correctly
Reproduces how often:
rare, only if start/stop when node is busy with something
The text was updated successfully, but these errors were encountered:
What is the mechanism Brave uses for stopping go-ipfs?
iirc there ipfs shutdown CLI command can be used for graceful shutdown, alternative is to send SIGHUP, SIGINT or SIGTERM – those should trigger graceful shutdown as well. It will make sure ongoing file transfers finish before shutting down, so may take some time.
If graceful shutdown does not finish within your time budget, SIGKILL will trigger forced shutdown.
When go-ipfs is no longer running, there should be no $IPFS_PATH/repo.lock. If it was left due to forceful shutdown, Brave should remove it before starting it again.
launched Brave using --enable-logging=stderr --vmodule="*/variations/*"=6,"*/bat-native-ledger/*"=6,"*/brave_rewards/*"=6,"*/bat-native-ads/*"=6,"*/bat-native-confirmations/*"=6,"*/brave_ads/*"=9,"*/brave_user_model/*"=6 --brave-ads-staging --brave-ads-debug --rewards=staging=true,reconcile-interval=3
load brave://ipfs-internals/
click Install and start
clicked Start, Restart, and Stop repeatedly, varying timing a bit (but usually doing so quickly)
Confirmed I never saw Error: lock /Users/stephendonner/Library/Application Support/BraveSoftware/Brave-Browser/brave_ipfs/repo.lock: someone else has the lock which is easily reproducible in earlier builds
Description
Someitmes we kill the node without allowing it to remove lock file and it fails launch start next time with error
brave_ipfs/repo.lock: someone else has the lock
Steps to Reproduce
brave_ipfs/repo.lock: someone else has the lock
errorActual result:
Unable to start node
Expected result:
Start/stop node works correctly
Reproduces how often:
rare, only if start/stop when node is busy with something
The text was updated successfully, but these errors were encountered: