My netlfy sunddenly have thrown this error

Support
1

5:47:47 AM: [notice] A new release of pip is available: 24.3.1 → 25.1.1
5:47:47 AM: [notice] To update, run: pip install --upgrade pip
5:47:47 AM: bash: line 1: jupyter-book: command not found
5:47:47 AM: ​
5:47:47 AM: “build.command” failed
5:47:47 AM: ────────────────────────────────────────────────────────────────
5:47:47 AM: ​
5:47:47 AM: Error message
5:47:47 AM: Command failed with exit code 127: pip install -r requirements.txt && jupyter-book build . (Search results for '"non-zero exit code: 127"' - Netlify Support Forums)
5:47:47 AM: ​
5:47:47 AM: Error location
5:47:47 AM: In Build command from Netlify app:
5:47:47 AM: pip install -r requirements.txt && jupyter-book build .
5:47:47 AM: ​
5:47:47 AM: Resolved config
5:47:47 AM: build:
5:47:47 AM: command: pip install -r requirements.txt && jupyter-book build .
5:47:47 AM: commandOrigin: ui
5:47:47 AM: publish: /opt/build/repo/_build/html
5:47:47 AM: publishOrigin: ui
5:47:48 AM: Failed during stage ‘building site’: Build script returned non-zero exit code: 2 (Search results for '"non-zero exit code: 2"' - Netlify Support Forums)
5:47:48 AM: Build failed due to a user error: Build script returned non-zero exit code: 2
5:47:48 AM: Failing build: Failed to build site
5:47:48 AM: Finished processing build request in 57.49s

2

@Andre_Lages It might be the same as this:
https://answers.netlify.com/t/mkdocs-suddenly-not-working/152460

Which may be related to this:
https://answers.netlify.com/t/deploy-now-using-noble-instead-of-focal-even-when-configured-to-use-focal/152185

1 Like
3

Thanks for the reply, but I didn’t get. My requirements.txt has the jupyter-book package. It was working normally, and suddenly stopped. Should I change the build command? The build command is the same as found here:

4

Hi, @Andre_Lages. The 127 exit code means “command not found”. That is also in the output you shared:

It appears that jupyter-book either failed to be installed or it was installed at some location where it not in the PATH for the shell.

If you are still seeing this issue, please let us know and we’ll open a support ticket to troubleshoot with you.