-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
webhook fails with 500 #158
Comments
access.log
error.log
|
Ok, tak to nie je skutocna chyba. Toto je chyba, ze sa nepodarilo reportovat inu chybu, ktora sa snazila reportovat, ze ina chyba, ktora sa snazila reportovat, ... az kym databaza netimeoutla. Je chyba, ze sa snazime kazdu chybu hned reportnut a ked sa nepodari odoslat email s chybou, tak sa to zacykli. Mali sme chyby pekne akumulovat a posielat raz za cas, ako som povodne mal. |
Este ze git vie revertnut aj random commit daleko zahrabany v historii: Revert "Use standard Django error reports" |
Skutocna chyba:
|
Hadam fixnute. Fix som deployol. Pockam kym to mandrill submitne opatovne, resp. pls klikni v mandrill rozhrani, nech to resubmitne. Rucne cez curl to uz nesubmituj, nech nevyrobime nasobne maily. Od teraz by nam aj naozaj mali chodit maily s chybami na servri. Raz za hodinu report s tym, co sa za ten cas stalo. |
Vyzera, ze preslo. Akurat tam svieti este ina (starsia) chyba, 413 Request Entity Too Large, neviem, ci to s tym suvisi. |
aha, uh, 31MB. To asi nemohlo prejst. Vieme to pozriet, ze co to je, kto to posiela? |
Od vcera vecera nejake webhooky boli a zatial ziaden nespadol. Ak nejaky spadne mal by prijst mail na admin@chv, ale pre istotu pozriem aj logy na servri. To 31MB je z akeho datumu? Po neprejde ani cez apache, kedze uz tam je nizsi limit. Ak si vies z mandrillu stiahnut Otazka je, co s tym webhookom potom mandrill spravil. Zrejme to casom vzdal postovat. Co potom spravil s mailom? Vratil bounce ako nedoruceny, alebo len zahodil? |
Po polroku mozeme povedat, ze to asi funguje. |
Madrill reports, and Rrnning the webook from command line confirms, that server ends with:
500 Internal Server Error
more info in mail.
The text was updated successfully, but these errors were encountered: