Overnight, our site has stopped building due to a timeout. I’ve tried re-deploying successful builds from yesterday, and they are also timing out before the site can build (build time is usually about 1 minute). Using Jekyll. Has anyone run into this before. Thanks for your help!
6:07:50 AM: Jekyll Feed: Generating feed for posts
6:36:04 AM: Build exceeded maximum allowed runtime
sounds to me like your build is indeed timing out - why, i can’t say without knowing things like your instance (netlify) name. But it seems likely that something to do with jekyll isn’t completing, so the build times out.
Give us a shout if neither of those posts help you identify the culprit. Mention what you’ve tried, and what your netlify name is.
I have yes, thanks. Adding “&& ps auxw ; false” doesn’t seem to give any additional information and the blog with further debug steps doesn’t exist anymore.
2:03:40 PM: Executing user command: jekyll build && ps auxw ; false
(Doesn’t do anything)
What’s strange about this is that previous commits that have worked just fine in the past are now failing, which is the major other thing I’ve also tried – rewinding to known good code. I’ve also tried deploying other branches; all fail. I’ve tried pre-building the site locally, that seems to work fine.
Not sure how to get my Netlify name but I believe it may be “Justin Dunham”?
no real smoking guns there - it seems like the feed generation is just taking forever Does it scrape data from other sources, and maybe there is more data there or a network timeout? I guess when you build locally it doesn’t take 30 minutes (or many minutes) for that part?
You might also try running jekyll in verbose mode even in our CI to see if it will “be more talkative” about what is happening during that step so you can see if it hangs on some particular spot… That’s a bit less effort than installing docker if you want to try it first
Thank you – that suggestion to run Jekyll in verbose mode is really helpful, helped me zero in on the file that was causing the problem. That should be in your docs, maybe it is and I missed it. Again, really appreciate that.
Here was the culprit, a blog post containing the following. Removing the “created_at” line fixes the build on Netlify.
(To answer your question, I’ve never had a problem on my local machine or even on Netlify until I posted this question, and nothing has changed in this file in about two years. Usually takes about a minute to build. And attempting to re-deploy previously successful builds failed as well.)