Jekyll Build Error with large site

Hello,
I am evaluating moving my site to Netlify and so far I am delighted! My Jekyll site was successfully built and deployed with my test data. Unfortunately, I get an error message when I try to build the site with the “real” data. The error message is:
“Command did not finish within the time limit”

Is it possible to increase the build time limit?

I am looking forward to any support.

Many greetings
Oliver

It is possible, but you’ll have to add a payment method to your account as with longer build times you’re more likely to go over the 300 minutes limit. More info here:

https://answers.netlify.com/t/deploy-error-command-did-not-finish-within-the-time-limit/9234/12?u=tomrutgers

Alright! A Netlify employee still has to change your settings, so just a little more patience :sweat_smile:

2 Likes

Hey there, @RumX :wave:

Please respond to this thread with your Netlify site name, as well as the number of minutes you would like to be increased to.

Thanks!

1 Like

Hello hillary,

the page name is flamboyant-jackson-4861b3. Let’s start with a timeout of 60 minutes please.

Thanks for the super fast support!

Hey there, @RumX

Thanks so much for confirming! You will be contacted soon via email by one of our teams to talk more about your options. Stay tuned to your inbox :slight_smile:

Hello again,

unfortunately since today I can not deploy my site anymore. Timeout problems occur again.
Is it possible that the manual increase was reset in mai?

Thank you very much for your support!

Hey there, @RumX :wave:

Thank you so much for letting us know. I just checked, and it does say that you should have a limit of 60 minutes on our end. What error message are you receiving? Does it happen every time you deploy?

Hello Hillary,

thank you for your feedback. Yes the failure takes place on every build attempt unfortunately. I was not able to push out the important update the last few days because of this…

I get the following log:

8:45:29 AM: Build ready to start
8:45:31 AM: build-image version: e4d2dbe4cfec46db257e869258461ded89b75c9b
8:45:31 AM: build-image tag: v3.7.3
8:45:31 AM: buildbot version: ad3fcf6020c7aec15071db43b748eaa0b3f039c5
8:45:31 AM: Building without cache
8:45:31 AM: Starting to prepare the repo for build
8:45:32 AM: No cached dependencies found. Cloning fresh repo
8:45:32 AM: git clone …
8:45:50 AM: Preparing Git Reference refs/heads/master
8:45:51 AM: Parsing package.json dependencies
8:45:52 AM: Starting build script
8:45:53 AM: Installing dependencies
8:45:53 AM: Python version set to 2.7
8:45:54 AM: v12.18.0 is already installed.
8:45:54 AM: Now using node v12.18.0 (npm v6.14.4)
8:45:54 AM: Started restoring cached build plugins
8:45:54 AM: Finished restoring cached build plugins
8:45:54 AM: Attempting ruby version 2.7.1, read from environment
8:45:56 AM: Using ruby version 2.7.1
8:45:56 AM: Using bundler version 2.2.7 from Gemfile.lock
8:45:57 AM: Successfully installed bundler-2.2.7
8:45:57 AM: 1 gem installed
8:45:57 AM: Using PHP version 5.6
8:45:57 AM: Started restoring cached ruby gems
8:45:57 AM: Finished restoring cached ruby gems
8:45:57 AM: Installing gem bundle
8:45:57 AM: [DEPRECATED] The --path flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use bundle config set --local path '/opt/build/cache/bundle', and stop using this flag
8:45:57 AM: [DEPRECATED] The --binstubs option will be removed in favor of bundle binstubs --all
8:45:57 AM: Fetching https://github.com/jekyll/jekyll.git
8:46:04 AM: Fetching gem metadata from https://rubygems.org/
8:46:04 AM: Resolving dependencies…
8:46:04 AM: Using bundler 2.2.7
8:46:04 AM: Fetching concurrent-ruby 1.1.8
8:46:04 AM: Fetching eventmachine 1.2.7
8:46:04 AM: Fetching colorator 1.1.0
8:46:04 AM: Fetching ffi 1.15.0
8:46:04 AM: Fetching http_parser.rb 0.6.0
8:46:04 AM: Fetching public_suffix 4.0.6
8:46:04 AM: Fetching forwardable-extended 2.6.0
8:46:04 AM: Fetching rb-fsevent 0.10.4
8:46:04 AM: Installing forwardable-extended 2.6.0
8:46:04 AM: Installing colorator 1.1.0
8:46:04 AM: Installing rb-fsevent 0.10.4
8:46:04 AM: Installing public_suffix 4.0.6
8:46:05 AM: Installing eventmachine 1.2.7 with native extensions
8:46:05 AM: Installing http_parser.rb 0.6.0 with native extensions
8:46:05 AM: Installing concurrent-ruby 1.1.8
8:46:05 AM: Fetching rexml 3.2.4
8:46:05 AM: Fetching liquid 4.0.3
8:46:05 AM: Installing ffi 1.15.0 with native extensions
8:46:05 AM: Fetching mercenary 0.4.0
8:46:05 AM: Installing liquid 4.0.3
8:46:05 AM: Installing rexml 3.2.4
8:46:05 AM: Installing mercenary 0.4.0
8:46:05 AM: Fetching rouge 3.26.0
8:46:05 AM: Installing rouge 3.26.0
8:46:20 AM: Fetching safe_yaml 1.0.5
8:46:20 AM: Fetching unicode-display_width 1.7.0
8:46:20 AM: Fetching pathutil 0.16.2
8:46:20 AM: Fetching webrick 1.7.0
8:46:20 AM: Installing pathutil 0.16.2
8:46:20 AM: Installing unicode-display_width 1.7.0
8:46:20 AM: Installing safe_yaml 1.0.5
8:46:20 AM: Installing webrick 1.7.0
8:46:28 AM: Fetching addressable 2.7.0
8:46:28 AM: Fetching i18n 1.8.10
8:46:28 AM: Fetching kramdown 2.3.1
8:46:28 AM: Fetching terminal-table 3.0.0
8:46:28 AM: Fetching em-websocket 0.5.2
8:46:28 AM: Installing terminal-table 3.0.0
8:46:28 AM: Installing i18n 1.8.10
8:46:28 AM: Installing em-websocket 0.5.2
8:46:28 AM: Installing addressable 2.7.0
8:46:28 AM: Installing kramdown 2.3.1
8:46:28 AM: Fetching rb-inotify 0.10.1
8:46:28 AM: Fetching sassc 2.4.0
8:46:29 AM: Installing rb-inotify 0.10.1
8:46:29 AM: Installing sassc 2.4.0 with native extensions
8:46:29 AM: Fetching listen 3.5.1
8:46:29 AM: Fetching kramdown-parser-gfm 1.1.0
8:46:29 AM: Installing listen 3.5.1
8:46:29 AM: Installing kramdown-parser-gfm 1.1.0
8:46:29 AM: Fetching jekyll-watch 2.2.1
8:46:29 AM: Installing jekyll-watch 2.2.1
8:49:18 AM: Fetching jekyll-sass-converter 2.1.0
8:49:18 AM: Installing jekyll-sass-converter 2.1.0
8:49:18 AM: Using jekyll 4.2.0 from https://github.com/jekyll/jekyll.git (at master@c7ccec2)
8:49:18 AM: Fetching jekyll-include-cache 0.2.1
8:49:18 AM: Fetching jekyll-sitemap 1.4.0
8:49:18 AM: Fetching jekyll-redirect-from 0.16.0
8:49:18 AM: Fetching jekyll-seo-tag 2.7.1
8:49:18 AM: Fetching jekyll-feed 0.15.1
8:49:18 AM: Installing jekyll-feed 0.15.1
8:49:18 AM: Installing jekyll-redirect-from 0.16.0
8:49:18 AM: Installing jekyll-seo-tag 2.7.1
8:49:18 AM: Installing jekyll-include-cache 0.2.1
8:49:18 AM: Installing jekyll-sitemap 1.4.0
8:49:19 AM: Fetching minima 2.5.1
8:49:19 AM: Installing minima 2.5.1
8:49:19 AM: Bundle complete! 7 Gemfile dependencies, 35 gems now installed.
8:49:19 AM: Bundled gems are installed into /opt/build/cache/bundle
8:49:19 AM: Execution timed out after 3m26.280476762s
8:49:19 AM: Error running command: Command did not finish within the time limit
8:49:19 AM: Creating deploy upload records
8:49:19 AM: Failing build: Failed to build site
8:49:19 AM: Failed during stage ‘building site’: Command did not finish within the time limit
8:49:19 AM: Finished processing build request in 3m47.85452261s

The error message is unfortunately very generic and I can’t see the cause of the problem.

I therefore urgently ask for help.

Many greetings
Oliver

Hey there, @RumX

I have gone ahead and reset the build timeout again for you internally. I believe that you should be good to go here! Please attempt to build again and confirm if this has solved your problem :slight_smile:

Hello Hillary,

thank you very much for your support! The build is now running through successfully. That’s awesome!

Does the build limit reset monthly or was this a one off?

Many greetings and thanks again!

Great question, @RumX. These will not reset each month, and I believe this was a one off. If you encounter any additional hangups regarding your build timeout, don’t hesitate to follow up on this thread :slight_smile:

1 Like