Home
Support Forums

Netlfiy is not building anymore after todays maintenance update

Hi,

After todays maintenance update 16 Nov 2021, the netlify app is not building after publishing on netlify CMS. The issue is that Netlfiy is not detecting a build nor a failed build command, basically nothing is happening after publishing.

my website is https://www.securiwiser.com/

Please can anyone help?

Hi @securiwiser-shams,

Could you try again? This had affected other users too and even pushing a blank commit now works according to them.

It’s still not working and it’s becoming a joke.

I am really not happy about this. Siince you last update we have been unable to post any articles to our blog.

This has to be fixed asap otherwise I will lodge an official complaint.

Warm Regards,

info@justgetvisible.com

Unit C203, The Chocolate Factory,
Clarendon Road, London, N22 6XJ

jgv signature.jpg

hi there @securiwiser-shams ,

sorry to hear this is still happening.

Can you tell us a netlify site name - not custom domain? do you have any error messages, screenshots any more information at all about what isnt working? thank you so much.

Hi Perry,

Netlify site name is Securiwiser and here’s the netlify domain for it https://securiwiser.netlify.app/.

Theres is no actual error apart from it not building after we save an article.

It saves the article, but it does not build and appear in front end.

Before you update we use to save the articles and then it used to build and then show up in our blog here https://www.securiwiser.com/blog/

Why on earth have you performed an update which has now affected us from adding content to our site now. It’s very unprofessional, we wasn’t even aware what you was doing. Now we are sitting around waiting for you to fix this issue.

If it’s not sorted I will be looking around for better and more reliable solutions.

I’m really not happy about this.

Warm Regards,

info@justgetvisible.com

Unit C203, The Chocolate Factory,
Clarendon Road, London, N22 6XJ

jgv signature.jpg

hi there @securiwiser-shams - thanks for that info. I do understand that this is a frustrating situation for you - the information my colleague hrishikesh posted yesterday is correct but wasn’t quite complete - they problems you have been experiencing are actually not related to any maintenance that netlify has performed - there was a large scale google outage yesterday:

https://status.cloud.google.com/incidents/6PM5mNd43NbMqjCZ5REh
The extent/complexity of what was going on yesterday wasn’t immediately apparent until the situation was resolved.

and while Netlify is a seperate service from Google, there are parts of our infrastructure that do depend on google and were affected (the same way other large companies were - Spotify, for example, was down because of this issue). So, while i know its frustrating to be unable to push any updates, the assertion that we mislead you or didnt communicate about planned maintenance isn’t actually so!

I realize that the end result for you is the same - but, i’m sure you appreciate the extra information. :slight_smile:
Hopefully this makes you feel more inclined to trust our service once we have things working again.

So, onto that topic - seems like the fix we had suggested for you didn’t quite work, which is of course frustrating as well. This did indeed work for another customer, but we have some more things we can try.

Looking at your account, i do see that we have had no successful deploys via the CMS since yesterday.

As you don’t seem to have any error messages to report - the next thing we might suggest is to log into GitHub, and revoke access to netlify there. Then, please re-authenticate Netlify for GitHub, and that might fix things. At the moment, my working hypothesis is that there is that the CMS and our service and GitHub are not communicating correctly.

Do let us know if that does make things work, and I will ask Hrishikesh to take another look at your account if this doesn’t help when he comes on shift.

thanks again for your patience.

1 Like

Hi, we managed to revoke and re-authenticate, and it is deploying but now it gives the following error, please help. Thank you.

5:26:37 PM: ────────────────────────────────────────────────────────────────
5:26:37 PM: β€œbuild.command” failed
5:26:37 PM: ────────────────────────────────────────────────────────────────
5:26:37 PM: ​
5:26:37 PM: Error message
5:26:37 PM: Command failed with exit code 1: cd site && gatsby clean && gatsby build
5:26:37 PM: ​
5:26:37 PM: Error location
5:26:37 PM: In Build command from Netlify app:
5:26:37 PM: cd site && gatsby clean && gatsby build
5:26:37 PM: ​
5:26:37 PM: Resolved config
5:26:37 PM: build:
5:26:37 PM: base: /opt/build/repo
5:26:37 PM: command: cd site && gatsby clean && gatsby build
5:26:37 PM: commandOrigin: ui
5:26:37 PM: environment:
5:26:37 PM: - MAILCHIMP_ENABLED
5:26:37 PM: - MAILCHIMP_END_POINT
5:26:37 PM: publish: /opt/build/repo/site/public
5:26:37 PM: publishOrigin: ui

While the portion of the log you have provided @securiwiser-shams show failure, it doesn’t give a reason. If you could post more of the log, of provide the public link to the log (if you have make logs public) this may assist in helping you debug.

is this better

:24:03 PM: success run page queries - 59.059s - 173/173 2.93/s
5:24:03 PM: success write out requires - 0.010s
5:26:01 PM: success Building production JavaScript and CSS bundles - 117.599s
5:26:01 PM: success Rewriting compilation hashes - 0.010s
5:26:01 PM: success Writing page-data.json files to public directory - 0.528s - 173/173 327.59/s
5:26:16 PM: success Building HTML renderer - 14.960s
5:26:36 PM: success Building static HTML for pages - 19.440s - 173/173 8.90/s
5:26:37 PM: error β€œgatsby-node.js” threw an error while running the onPostBuild lifecycle:
5:26:37 PM: You ended the stream without writing anything.
5:26:37 PM:
5:26:37 PM:
5:26:37 PM: EmptySitemap: You ended the stream without writing anything.
5:26:37 PM:
5:26:37 PM: not finished Caching JavaScript and CSS webpack compilation - 36.301s
5:26:37 PM: not finished Caching HTML renderer compilation - 20.350s
5:26:37 PM: not finished onPostBuild - 0.881s
5:26:37 PM: ​
5:26:37 PM: ────────────────────────────────────────────────────────────────
5:26:37 PM: β€œbuild.command” failed
5:26:37 PM: ────────────────────────────────────────────────────────────────
5:26:37 PM: ​
5:26:37 PM: Error message
5:26:37 PM: Command failed with exit code 1: cd site && gatsby clean && gatsby build
5:26:37 PM: ​
5:26:37 PM: Error location
5:26:37 PM: In Build command from Netlify app:
5:26:37 PM: cd site && gatsby clean && gatsby build
5:26:37 PM: ​
5:26:37 PM: Resolved config
5:26:37 PM: build:
5:26:37 PM: base: /opt/build/repo
5:26:37 PM: command: cd site && gatsby clean && gatsby build
5:26:37 PM: commandOrigin: ui
5:26:37 PM: environment:
5:26:37 PM: - MAILCHIMP_ENABLED
5:26:37 PM: - MAILCHIMP_END_POINT
5:26:37 PM: publish: /opt/build/repo/site/public
5:26:37 PM: publishOrigin: ui
5:26:37 PM: Caching artifacts
5:26:37 PM: Started saving workspace packages/blocks/gatsby-blocks-core node modules
5:26:37 PM: Finished saving workspace packages/blocks/gatsby-blocks-core node modules
5:26:37 PM: Started saving workspace packages/blog/gatsby-blog-core node modules
5:26:37 PM: Finished saving workspace packages/blog/gatsby-blog-core node modules
5:26:37 PM: Started saving workspace packages/flow-ui/flow-ui-widgets node modules
5:26:37 PM: Finished saving workspace packages/flow-ui/flow-ui-widgets node modules
5:26:37 PM: Started saving workspace site node modules
5:26:37 PM: Finished saving workspace site node modules
5:26:37 PM: Started saving workspace root node modules
5:26:37 PM: Finished saving workspace root node modules
5:26:37 PM: Started saving build plugins
5:26:37 PM: Finished saving build plugins
5:26:37 PM: Started saving yarn cache
5:26:49 PM: Finished saving yarn cache
5:26:49 PM: Started saving pip cache
5:26:49 PM: Finished saving pip cache
5:26:49 PM: Started saving emacs cask dependencies
5:26:49 PM: Finished saving emacs cask dependencies
5:26:49 PM: Started saving maven dependencies
5:26:49 PM: Finished saving maven dependencies
5:26:49 PM: Started saving boot dependencies
5:26:49 PM: Finished saving boot dependencies
5:26:49 PM: Started saving rust rustup cache
5:26:49 PM: Finished saving rust rustup cache
5:26:49 PM: Started saving go dependencies
5:26:49 PM: Finished saving go dependencies
5:26:49 PM: Build failed due to a user error: Build script returned non-zero exit code: 2
5:26:50 PM: Creating deploy upload records
5:26:50 PM: Failing build: Failed to build site
5:26:50 PM: Failed during stage β€˜building site’: Build script returned non-zero exit code: 2
5:26:50 PM: Finished processing build request in 5m15.296909477s

From this, it looks like you tried to create a stream in Node.js and closed it with stream.end() without actually writing any data.

Looks like an automatic sitemap that’s being generated.