Nico Kruber created FLINK-13018: ----------------------------------- Summary: Serving docs locally with jekyll fails with inotify limit Key: FLINK-13018 URL: https://issues.apache.org/jira/browse/FLINK-13018 Project: Flink Issue Type: Bug Components: Documentation Affects Versions: 1.9.0 Reporter: Nico Kruber Assignee: Nico Kruber
Both {{build-docs.sh -i}} and {{build-docs.sh -p}} currently fail (also in the dockerized builds in {{docs/docker}}): {code} $ ./build_docs.sh -p Fetching gem metadata from https://rubygems.org/.......... ... Bundle complete! 8 Gemfile dependencies, 36 gems now installed. Bundled gems are installed into `./.rubydeps` Configuration file: /home/nico/Projects/flink/docs/_config.yml Source: /home/nico/Projects/flink/docs Destination: /home/nico/Projects/flink/docs/content Incremental build: disabled. Enable with --incremental Generating... done in 167.943 seconds. jekyll 3.7.2 | Error: Too many open files - Failed to initialize inotify: the user limit on the total number of inotify instances has been reached. {code} Probably, {{inotify}} is used in a way to monitor single files and not just directories but I don't know that and couldn't find a way to change how jekyll is using inotify. I wouldn't suggest working around by setting a higher inotify limit but upgrading jekyll did not solve it and so far there are two options: # disable watching files via {{--no-watch}} # use polling instead of `inotify` via `--force_polling` # try to reduce the set of files by adding excludes for (expected) static files -- This message was sent by Atlassian JIRA (v7.6.3#76005)