My Netlify build hangs after processing

Hi,
My site hangs after the post processing- see log below. I tried following https://github.com/netlify/build-image#step-2-start-the-script-to-run-interactively but when i tried step 2 nothing happens. it could be I am not understanding what the last command i supposed to be. Anyhow I saw elsewhere on docs that if the problem is post processing I should contact support. Here is log

1:32:04 PM: Build ready to start
1:32:05 PM: build-image version: b0258b965567defc4a2d7e2f2dec2e00c8f73ad6
1:32:05 PM: build-image tag: v3.4.1
1:32:05 PM: buildbot version: fcbc7a79f7372e5995cf02954ef19fc48d20c871
1:32:06 PM: Building without cache
1:32:06 PM: Starting to prepare the repo for build
1:32:06 PM: No cached dependencies found. Cloning fresh repo
1:32:06 PM: git clone https://github.com/yepstien1/pies-and-fries-3
1:32:07 PM: Preparing Git Reference refs/heads/master
1:32:08 PM: Different functions path detected, going to use the one specified in the Netlify configuration file: ‘functionsR’ versus ‘’ in the Netlify UI
1:32:08 PM: Starting build script
1:32:08 PM: Installing dependencies
1:32:08 PM: Python version set to 2.7
1:32:10 PM: v12.18.0 is already installed.
1:32:10 PM: Now using node v12.18.0 (npm v6.14.4)
1:32:10 PM: Started restoring cached build plugins
1:32:10 PM: Finished restoring cached build plugins
1:32:10 PM: Attempting ruby version 2.7.1, read from environment
1:32:12 PM: Using ruby version 2.7.1
1:32:12 PM: Using PHP version 5.6
1:32:12 PM: 5.2 is already installed.
1:32:12 PM: Using Swift version 5.2
1:32:12 PM: Started restoring cached node modules
1:32:12 PM: Finished restoring cached node modules
1:32:12 PM: Installing NPM modules using NPM version 6.14.4
1:32:46 PM: > core-js@2.6.11 postinstall /opt/build/repo/node_modules/babel-runtime/node_modules/core-js
1:32:46 PM: > node -e “try{require(’./postinstall’)}catch(e){}”
1:32:47 PM: > core-js@3.6.5 postinstall /opt/build/repo/node_modules/core-js
1:32:47 PM: > node -e “try{require(’./postinstall’)}catch(e){}”
1:32:47 PM: > core-js-pure@3.6.5 postinstall /opt/build/repo/node_modules/core-js-pure
1:32:47 PM: > node -e “try{require(’./postinstall’)}catch(e){}”
1:32:49 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/webpack-dev-server/node_modules/fsevents):
1:32:49 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
1:32:49 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/watchpack-chokidar2/node_modules/fsevents):
1:32:49 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
1:32:49 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/jest-haste-map/node_modules/fsevents):
1:32:49 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
1:32:49 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/fsevents):
1:32:49 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
1:32:49 PM: added 1848 packages from 885 contributors and audited 1855 packages in 36.349s
1:32:51 PM: 68 packages are looking for funding
1:32:51 PM: run npm fund for details
1:32:51 PM: found 1 low severity vulnerability
1:32:51 PM: run npm audit fix to fix them, or npm audit for details
1:32:51 PM: NPM modules installed
1:32:51 PM: Started restoring cached go cache
1:32:51 PM: Finished restoring cached go cache
1:32:51 PM: go version go1.14.4 linux/amd64
1:32:51 PM: go version go1.14.4 linux/amd64
1:32:51 PM: Installing missing commands
1:32:51 PM: Verify run directory
1:32:53 PM: ​
1:32:53 PM: ┌─────────────────────────────┐
1:32:53 PM: │ Netlify Build │
1:32:53 PM: └─────────────────────────────┘
1:32:53 PM: ​
1:32:53 PM: ❯ Version
1:32:53 PM: @netlify/build 3.3.0
1:32:53 PM: ​
1:32:53 PM: ❯ Flags
1:32:53 PM: deployId: 5f512894552c1a5ce33be4c0
1:32:53 PM: mode: buildbot
1:32:53 PM: ​
1:32:53 PM: ❯ Current directory
1:32:53 PM: /opt/build/repo
1:32:53 PM: ​
1:32:53 PM: ❯ Config file
1:32:53 PM: /opt/build/repo/netlify.toml
1:32:53 PM: ​
1:32:53 PM: ❯ Context
1:32:53 PM: production
1:32:54 PM: ​
1:32:54 PM: ┌────────────────────────────────────┐
1:32:54 PM: │ 1. build.command from netlify.toml │
1:32:54 PM: └────────────────────────────────────┘
1:32:54 PM: ​
1:32:54 PM: $ npm run build
1:32:54 PM: > pies-and-fries3@0.1.0 build /opt/build/repo
1:32:54 PM: > react-scripts build
1:32:55 PM: Creating an optimized production build…
1:33:16 PM: Compiled successfully.
1:33:16 PM:
1:33:16 PM: File sizes after gzip:
1:33:16 PM: 49.3 KB build/static/js/2.8c23d420.chunk.js
1:33:16 PM: 22.47 KB build/static/css/2.af3c1da9.chunk.css
1:33:16 PM: 3.54 KB build/static/js/main.fcd6e73e.chunk.js
1:33:16 PM: 780 B build/static/js/runtime-main.f273c63c.js
1:33:16 PM: 615 B build/static/css/main.691f6af0.chunk.css
1:33:16 PM: The project was built assuming it is hosted at /.
1:33:16 PM: You can control this with the homepage field in your package.json.
1:33:16 PM: The build folder is ready to be deployed.
1:33:16 PM: You may serve it with a static server:
1:33:16 PM: npm install -g serve
1:33:16 PM: serve -s build
1:33:16 PM: Find out more about deployment here:
1:33:16 PM: bit.ly/CRA-deploy
1:33:16 PM: ​
1:33:16 PM: (build.command completed in 21.8s)
1:33:16 PM: ​
1:33:16 PM: ┌────────────────────────────────────────────────────────────┐
1:33:16 PM: │ 2. onPostBuild command from @netlify/plugin-functions-core │
1:33:16 PM: └────────────────────────────────────────────────────────────┘
1:33:16 PM: ​
1:33:16 PM: Packaging Functions from functionsR directory:
1:33:16 PM: - acceptPayment.js
1:33:16 PM: - airTable.js
1:33:16 PM: - sendEmail.js
1:33:19 PM: ​
1:33:19 PM: (@netlify/plugin-functions-core onPostBuild completed in 3.1s)
1:33:19 PM: ​
1:33:19 PM: ┌─────────────────────────────┐
1:33:19 PM: │ Netlify Build Complete │
1:33:19 PM: └─────────────────────────────┘
1:33:19 PM: ​
1:33:19 PM: (Netlify Build completed in 26.4s)
1:33:19 PM: Caching artifacts
1:33:19 PM: Started saving node modules
1:33:19 PM: Finished saving node modules
1:33:19 PM: Started saving build plugins
1:33:19 PM: Finished saving build plugins
1:33:19 PM: Started saving pip cache
1:33:19 PM: Finished saving pip cache
1:33:19 PM: Started saving emacs cask dependencies
1:33:19 PM: Finished saving emacs cask dependencies
1:33:19 PM: Started saving maven dependencies
1:33:19 PM: Finished saving maven dependencies
1:33:19 PM: Started saving boot dependencies
1:33:19 PM: Finished saving boot dependencies
1:33:19 PM: Started saving go dependencies
1:33:19 PM: Finished saving go dependencies
1:33:22 PM: Build script success
1:33:22 PM: Starting to deploy site from ‘build’
1:33:22 PM: Creating deploy tree
1:33:22 PM: Creating deploy upload records
1:33:22 PM: 0 new files to upload
1:33:22 PM: 0 new functions to upload
1:33:22 PM: Starting post processing
1:33:49 PM: Finished processing build request in 1m43.79405471s
Name of site is https://pies-and-fries.netlify.app/
(it is currently up from a previous deploy)

hey there, can you explain a little bit more about what you expecting to see?

as far as i can tell, https://pies-and-fries.netlify.app/ is live?

It’s live from a previous deploy

Meaning I made some updates to my site- and when I tried building them they are hanging.


As shown i started building this on the 3rd and it is still “processing”

Hey bud, check this out! Let me know if it steers you in the right direction.

I am trying to debug the build with the docker image https://github.com/netlify/build-image#running-locally… In step one I am confused because I cannot find where the docker image is stored on my file system?

Hi, @yepstein1, you don’t attach to the image filesystem until you open the interactive shell.

Did you clone the build-image repository? If so change to the base directory of that repo and then run:

./test-tools/start-image.sh path/to/site/repo

This is what opens the interactive shell. If this works, you should see a new prompt, with the user buildbot .

Am I supposed to replace “path/to/site/repo” with a real path?

Also I am using windows and I installed docker desktop and I supposed to be using the cli on docker desktop- when I call docker pull there I get error bin/sh: docker: not found

I am getting error that ‘.’ is not recognized as a command. This is what I did
image . What am I doing wrong?

Hi, @yepstein1. Yes, path/to/site/repo is just “path to site repository”. It should be replaced with the actual path to the repo.

The newest error is because you are using the “command prompt” (or cmd.exe) to run the command and the syntax being used is for a Unix/Linux shell like bash.

You will likely need to install a shell and run the command from the shell. There is an example of how to install the shell here:

Ok thanks. I have Bash that ships with Git.

on git bash this happens


on git.exe
I also noticed that git.exe does not even recognize the docker command . I talso tried to install docker with sudo apt and that didnt work either
image
Any help would be appreciated. Thank you.

Hi, @yepstein1, I don’t have a Window’s system to troubleshoot this in but I took a closer look and I don’t think a stuck background process is the issue.

Based on how the logs end, I suspect there is actually an error on our side in the site post processing. Can I have your permission to completely disable all post processing (including any forms processing)?

I don’t see this site using any forms so this shouldn’t change anything but it might help resolve the issue.

Sure, thanks if indeed there are any errors because post-processing was disabled will I know and what I should I do then?

Actually, @yepstein1, there is still forms post processing enabled. I don’t think the error is because it is disabled but because it is enabled.

I’m hoping that disabling that will resolve the issue but I need your permission to do so. Do I have your permission to disable forms processing for this site?

Yes you do.
I understood what you meant but I was asking if in the future I have an issue because the lack of post processing will I know?

Hi, @yepstein1. The forms processing is now disabled for that site.

If this test works then we’ll know this is the root cause. As far as how to tell if this is happening in the future, that would most likely be determined by looking for similar behavior in the logs.

It seems to still be hanging
8:54:00 PM: Build ready to start
8:54:03 PM: build-image version: b0258b965567defc4a2d7e2f2dec2e00c8f73ad6
8:54:03 PM: build-image tag: v3.4.1
8:54:03 PM: buildbot version: 8c957a6d09a03023cea4239847cc73a9cb64eeb7
8:54:03 PM: Building without cache
8:54:03 PM: Starting to prepare the repo for build
8:54:03 PM: No cached dependencies found. Cloning fresh repo
8:54:03 PM: git clone https://github.com/yepstien1/pies-and-fries-3
8:54:04 PM: Preparing Git Reference refs/heads/master
8:54:06 PM: Different functions path detected, going to use the one specified in the Netlify configuration file: ‘functionsR’ versus ‘’ in the Netlify UI
8:54:06 PM: Starting build script
8:54:06 PM: Installing dependencies
8:54:06 PM: Python version set to 2.7
8:54:07 PM: v12.18.0 is already installed.
8:54:08 PM: Now using node v12.18.0 (npm v6.14.4)
8:54:08 PM: Started restoring cached build plugins
8:54:08 PM: Finished restoring cached build plugins
8:54:08 PM: Attempting ruby version 2.7.1, read from environment
8:54:10 PM: Using ruby version 2.7.1
8:54:10 PM: Using PHP version 5.6
8:54:10 PM: 5.2 is already installed.
8:54:10 PM: Using Swift version 5.2
8:54:10 PM: Started restoring cached node modules
8:54:10 PM: Finished restoring cached node modules
8:54:10 PM: Installing NPM modules using NPM version 6.14.4
8:54:50 PM: > core-js@2.6.11 postinstall /opt/build/repo/node_modules/babel-runtime/node_modules/core-js
8:54:50 PM: > node -e “try{require(’./postinstall’)}catch(e){}”
8:54:50 PM: > core-js@3.6.5 postinstall /opt/build/repo/node_modules/core-js
8:54:50 PM: > node -e “try{require(’./postinstall’)}catch(e){}”
8:54:50 PM: > core-js-pure@3.6.5 postinstall /opt/build/repo/node_modules/core-js-pure
8:54:50 PM: > node -e “try{require(’./postinstall’)}catch(e){}”
8:54:53 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/webpack-dev-server/node_modules/fsevents):
8:54:53 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
8:54:53 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/watchpack-chokidar2/node_modules/fsevents):
8:54:53 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
8:54:53 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/jest-haste-map/node_modules/fsevents):
8:54:53 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
8:54:53 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/fsevents):
8:54:53 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
8:54:53 PM: added 1848 packages from 885 contributors and audited 1855 packages in 41.486s
8:54:55 PM: 68 packages are looking for funding
8:54:55 PM: run npm fund for details
8:54:55 PM: found 9 low severity vulnerabilities
8:54:55 PM: run npm audit fix to fix them, or npm audit for details
8:54:55 PM: NPM modules installed
8:54:55 PM: Started restoring cached go cache
8:54:55 PM: Finished restoring cached go cache
8:54:55 PM: go version go1.14.4 linux/amd64
8:54:55 PM: go version go1.14.4 linux/amd64
8:54:55 PM: Installing missing commands
8:54:55 PM: Verify run directory
8:54:57 PM: ​
8:54:57 PM: ┌─────────────────────────────┐
8:54:57 PM: │ Netlify Build │
8:54:57 PM: └─────────────────────────────┘
8:54:57 PM: ​
8:54:57 PM: ❯ Version
8:54:57 PM: @netlify/build 3.3.5
8:54:57 PM: ​
8:54:57 PM: ❯ Flags
8:54:57 PM: deployId: 5f64052845a0b7a72123808e
8:54:57 PM: mode: buildbot
8:54:57 PM: ​
8:54:57 PM: ❯ Current directory
8:54:57 PM: /opt/build/repo
8:54:57 PM: ​
8:54:57 PM: ❯ Config file
8:54:57 PM: /opt/build/repo/netlify.toml
8:54:57 PM: ​
8:54:57 PM: ❯ Context
8:54:57 PM: production
8:54:58 PM: ​
8:54:58 PM: ┌────────────────────────────────────┐
8:54:58 PM: │ 1. build.command from netlify.toml │
8:54:58 PM: └────────────────────────────────────┘
8:54:58 PM: ​
8:54:58 PM: $ npm run build
8:54:58 PM: > pies-and-fries3@0.1.0 build /opt/build/repo
8:54:58 PM: > react-scripts build
8:55:00 PM: Creating an optimized production build…
8:55:22 PM: Compiled successfully.
8:55:22 PM:
8:55:22 PM: File sizes after gzip:
8:55:22 PM: 49.3 KB build/static/js/2.8c23d420.chunk.js
8:55:22 PM: 22.47 KB build/static/css/2.af3c1da9.chunk.css
8:55:22 PM: 3.55 KB build/static/js/main.0c0074ef.chunk.js
8:55:22 PM: 780 B build/static/js/runtime-main.f273c63c.js
8:55:22 PM: 615 B build/static/css/main.691f6af0.chunk.css
8:55:22 PM: The project was built assuming it is hosted at /.
8:55:22 PM: You can control this with the homepage field in your package.json.
8:55:22 PM: The build folder is ready to be deployed.
8:55:22 PM: You may serve it with a static server:
8:55:22 PM: npm install -g serve
8:55:22 PM: serve -s build
8:55:22 PM: Find out more about deployment here:
8:55:22 PM: bit.ly/CRA-deploy
8:55:23 PM: ​
8:55:23 PM: (build.command completed in 24.6s)
8:55:23 PM: ​
8:55:23 PM: ┌────────────────────────────────────────────────────────────┐
8:55:23 PM: │ 2. onPostBuild command from @netlify/plugin-functions-core │
8:55:23 PM: └────────────────────────────────────────────────────────────┘
8:55:23 PM: ​
8:55:23 PM: Packaging Functions from functionsR directory:
8:55:23 PM: - acceptPayment.js
8:55:23 PM: - airTable.js
8:55:23 PM: - sendEmail.js
8:55:26 PM: ​
8:55:26 PM: (@netlify/plugin-functions-core onPostBuild completed in 3.4s)
8:55:26 PM: ​
8:55:26 PM: ┌─────────────────────────────┐
8:55:26 PM: │ Netlify Build Complete │
8:55:26 PM: └─────────────────────────────┘
8:55:26 PM: ​
8:55:26 PM: (Netlify Build completed in 29.7s)
8:55:26 PM: Caching artifacts
8:55:26 PM: Started saving node modules
8:55:26 PM: Finished saving node modules
8:55:26 PM: Started saving build plugins
8:55:26 PM: Finished saving build plugins
8:55:26 PM: Started saving pip cache
8:55:26 PM: Finished saving pip cache
8:55:26 PM: Started saving emacs cask dependencies
8:55:26 PM: Finished saving emacs cask dependencies
8:55:26 PM: Started saving maven dependencies
8:55:26 PM: Finished saving maven dependencies
8:55:26 PM: Started saving boot dependencies
8:55:26 PM: Finished saving boot dependencies
8:55:26 PM: Started saving go dependencies
8:55:26 PM: Finished saving go dependencies
8:55:29 PM: Build script success
8:55:29 PM: Starting to deploy site from ‘build’
8:55:29 PM: Creating deploy tree
8:55:29 PM: Creating deploy upload records
8:55:30 PM: 0 new files to upload
8:55:30 PM: 0 new functions to upload
8:55:30 PM: Starting post processing
8:55:56 PM: Finished processing build request in 1m53.00345172s