menu
up-caret
down-caret

ZEIT

Our mission is to make cloud computing as easy and accessible as mobile computing. You can find our Next.js community here.

# Now

Instant global deployments

Trending conversations
503 on deployment
@codelayer · 22d
BRU1 instances are timing out
@helguita · 31d
Images not showing on CRA deployment
@passingmagic · 4h
$ now --target doing nothing
@spy-seth · 13h
Deploying Node v6
@mkern · 34d

'npm start' triggered for no apparent reason

ZEIT/Now · October 8, 2018 at 7:58pm

'npm start' triggered for no apparent reason

October 8, 2018 at 7:58pm (Edited 6 months ago)

I deployed about 24 hours ago (scaling it to min 1 max 1) and when I checked the logs just now, I saw that about 2 hours ago, npm start was run.

I seem to recall possibly reading that you try restarting errored servers a certain number of times but... there was no error or anything in the log.

Is this a known issue? Or in some way intentional that I'm not aware of? (I'm on the OSS plan currently)


October 8, 2018 at 8:24pm

Every application on now needs to be stateless! Yes, your app can restart many times for various reasons, but that shouldn't be a problem if you design them stateless...

like-fill
2
  • reply
  • like

I see... that's really good to know. Makes me wonder about the reliability then though. Because what if an incoming request is directed to an instance that is currently restarting?

  • reply
  • like

Good question! That would require an answer from the team with specifics...

  • reply
  • like

October 9, 2018 at 4:35am

We stop sending new requests before relocating or restarting your deployments. In a rare occasion the whole underlying system should crash then there is of course nothing we can do but reschedule all the deployments as fast as possible. Even in such a case we actually do try to wait a bit and resend the request.

like-fill
2
  • reply
  • like

October 9, 2018 at 7:19pm

Alright, thanks!

  • reply
  • like