cronjobs targetting render.com was not working : "output too large"/"sortie trop grande"

boly38 / botEnSky

BlueSky bot account that bring happiness to BlueSky users

https://bsky.app/profile/botensky.bsky.social

MIT License

0 stars 0 forks source link

cronjobs targetting render.com was not working : "output too large"/"sortie trop grande" #9

Closed boly38 closed 4 months ago

boly38 commented 4 months ago

17h15 & 17h20 simulation job triggers

Échec (sortie trop grande) => not sure what that means
this two attempts were not seen from render.com backend log

no log in simulation time window / 05:27 is a manual check

boly38 commented 4 months ago

Yep too much verbose response errors-explained-output-too-large - faq : max size read per cronjob is 64KB

boly38 commented 4 months ago

Still same issue so reopen

boly38 commented 4 months ago

It seems that when render app first wake up, response can take up to 50 seconds

Your free instance will spin down with inactivity, which can delay requests by 50 seconds or more.

In case of 60+ sec response time I think that cronjob trigger stop waiting and return this error because trying with alive instance didn't reproduce this error response. So I will trigger a new call 2 min before

simulate : 17:13, 17:15, and 17:26, 17:28

boly38 commented 4 months ago

not fixed

(maybe cronjob timeout error itsef contains too big payload response and on aborted query, onrender didnt wake up the app)

onrender jobs are not free : Jobs are not supported for free instance types.
I'll switch on github actions

boly38 commented 4 months ago

github action simulation curl tooks 43s and report no issue