We've had a report with uploading large numbers of files using
ipfs-deploy with Fission support that you may need to increase the number of open files that your operating system supports. This could also occur with
For ubuntu, read underyx's article to increase the number of open files allowed.
For Mac OS, Wilson Mar has a one liner:
sudo launchctl limit maxfiles 65536 200000
As described in the article, you'll want to add it to your bash or other shell profile so this change is permanent.
On a Chromebook in the native ChromeOS shell? Yeah, Boris hit this issue too when running large jekyll or gatsby builds:
sudo sysctl fs.inotify.max_user_watches=1048576
We've had some hiccups with our brew formula recently. To re-install / reset brew, run the following:
brew untap fission-suite/fission
Now re-run the installation instructions, copied here for convenience:
brew tap fission-suite/fissionbrew install fission-cli
This is related to issue #37.
If you want to see what the Fission CLI is doing under the covers, you can turn on DEBUG mode by calling commands like this:
DEBUG=true fission up .
You'll see that
fission up calls your locally installed
ipfs command to add files to IPFS. We can see that it's using the 0.4.22 version of ipfs, installed using Homebrew in the "Cellar" where brew keeps installed items.
Then, it sends the hash of the entire directory to our web API, which pins it and fetches the files directly from your laptop and any other IPFS nodes that already have copies of those files in the network.
In this case, we can see that after the "Remote pinning Qm…", there is a 504 Gateway Time-out error from our server. This is a known issue, which we're working on to support large files / large quantities of files.
WSL doesn't have systemd, so this init.d script should work.
The Fission CLI automatically connects your local IPFS server to our peers. It does this by issuing the
ipfs swarm connect command (see IPFS docs). Running the following two commands will open a direct connection to the Fission peers.
ipfs swarm connect /ip4/220.127.116.11/tcp/4001/ipfs/QmVLEz2SxoNiFnuyLpbXsH6SvjPTrHNMU88vCQZyhgBzgwipfs swarm connect /ip4/18.104.22.168/tcp/4001/ipfs/QmXab6bcjmWUQZryEtmZfxS5hGoJAguw8bhLdUN5ZFQ2e5