Site is down after deploys & log is filled with Go-http-client/1.1 requests


After each deploy (which is simply a data update), my website can’t be accessed.
If I check the log I see this request that pops every 2/3s as soon as the site is deployed and honestly I don’t know what it means : - - [28/Apr/2024:17:05:21 +0000] “HEAD / HTTP/1.1” 200 0 “-” “Go-http-client/1.1”

Then after a lot of time it becomes fine. I used to redeploy the site once or twice and it was enough but it isn’t anymore.

CPU usage looks like that : it moves to >100% after deploys. Meanwhile when it is used CPU doesn’t really go up.

Edit : it worked again after 20 minutes, with logs indicating : “Handling signal : term” then “Worer exiting” then “Shutting down: Master”

Thanks for the help

Hey Joris,

It’s hard to pinpoint the issue with the limited information we have, and I understand it can be confusing, especially if it’s intermittent. I’m not sure what’s happening, but if the CPU usage spikes after a deployment, it suggests that some processing is happening. Are you sure this isn’t related to your service? Every time I try to access your service URL, it takes a few seconds to load the page, which indicates it might be fetching or processing something each time someone visits the site/root path. This could be causing issues during and after deploy with health checks, etc.

Perhaps consider moving the data to a separate storage, like a database, to speed up site loading. I’m not sure how you’re currently handling data storage or retrieval. It might be worthwhile to contact us directly through the ‘Help’ button in the dashboard so we can take a closer look at your service operations and metrics.

Render Support, UTC+3