mirror of
https://github.com/healthchecks/healthchecks.git
synced 2026-04-25 06:55:53 +03:00
[GH-ISSUE #1057] [Django] ERROR (EXTERNAL IP): Internal Server Error... #734
Labels
No labels
bug
bug
bug
feature
good-first-issue
new integration
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/healthchecks#734
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kelvtech-co-uk on GitHub (Sep 5, 2024).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/1057
Just stated to recevie these email alerts sporadically. No change event and the pings to all my endpoints are showing as working. I've updated the docker image and rebuilt the container but am still getting them. Would appreicate some tshoot pointers?
Thx
@theprantadutta commented on GitHub (Sep 7, 2024):
@kelvtech-co-uk Did you find any solution, I tried adding
ALLOWED_HOSTS=['hc.example.net', '203.xx.xxx.xxx]
or
'hc.example.net,203.xx.xxx.xxx'
none of this seems to work
@kelvtech-co-uk commented on GitHub (Sep 7, 2024):
No, its still happening but it's not frequent and the web UI shows my pings are being received. The error message at the top of the text I posted says its a DB lock issue which is the oddity for me as this is all controlled by HC itself.
@aslirajesh commented on GitHub (Sep 8, 2024):
This is common issue with sqlite3, try using postgres or mysql.
see here
@kelvtech-co-uk commented on GitHub (Sep 8, 2024):
Thanks, just completed a migration to mysql.
Sharing this link with migration instructions which worked well for me.
@cuu508 commented on GitHub (Sep 9, 2024):
I could reproduce the "database is locked" error. I sent concurrent ping HTTP requests using the
abtool, and saw the "database is locked" errors even with concurrency of 2.Just pushed a commit which adds a couple sqlite configuration parameters:
PRAGMA busy_timeoutconfigures the database to wait when a database is locked instead of giving up immediately.transaction_mode IMMEDIATEstarts transactions in read/write mode, required to make busy_timeout work.With these in place, in my testing, I did not see "database is locked" errors any more.
@cuu508 commented on GitHub (Oct 21, 2024):
I've released v3.7 which includes a fix for this issue.