[GH-ISSUE #168] health and disk I/O error #67

New issue

Open

opened 2026-03-13 15:38:54 +03:00 by kerem · 6 comments

kerem commented

2026-03-13 15:38:54 +03:00

Owner

Originally created by @vm86 on GitHub (May 21, 2019).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/168

The acme-dns has a unexpected behavior. When I call https://github.com/joohoi/acme-dns#health-check-endpoint we see a report it works correct, but it doesn't correct, we can't do any operations with sqlite.

➜  curl -v http://acme.exapmle.com/health
*   Trying 192.168.10.250...
* TCP_NODELAY set
* Connected to acme.exapmle.com (192.168.10.250) port 80 (#0)
> GET /health HTTP/1.1
> Host: acme.exapmle.com
> User-Agent: curl/7.58.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: nginx/1.15.10
< Date: Tue, 21 May 2019 22:40:57 GMT
< Content-Length: 0
< Connection: keep-alive
< Vary: Origin
<
* Connection #0 to host acme.exapmle.com left intact

➜  curl -X POST http://acme.exapmle.com/register  
{"error": "disk I/O error"}

acme-dns version: 0.7.2

Originally created by @vm86 on GitHub (May 21, 2019). Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/168 The acme-dns has a unexpected behavior. When I call https://github.com/joohoi/acme-dns#health-check-endpoint we see a report it works correct, but it doesn't correct, we can't do any operations with sqlite. ``` ➜ curl -v http://acme.exapmle.com/health * Trying 192.168.10.250... * TCP_NODELAY set * Connected to acme.exapmle.com (192.168.10.250) port 80 (#0) > GET /health HTTP/1.1 > Host: acme.exapmle.com > User-Agent: curl/7.58.0 > Accept: */* > < HTTP/1.1 200 OK < Server: nginx/1.15.10 < Date: Tue, 21 May 2019 22:40:57 GMT < Content-Length: 0 < Connection: keep-alive < Vary: Origin < * Connection #0 to host acme.exapmle.com left intact ➜ curl -X POST http://acme.exapmle.com/register {"error": "disk I/O error"} ``` acme-dns version: 0.7.2

kerem commented

2026-03-13 15:39:00 +03:00

Author

Owner

@Kugelschieber commented on GitHub (Jun 13, 2019):

The health check endpoint can be used to ensure the server is reachable. But it does not validate the server is functioning properly.

@Kugelschieber commented on GitHub (Jun 13, 2019): The health check endpoint can be used to ensure the server is reachable. But it does not validate the server is functioning properly.

kerem commented

2026-03-13 15:39:05 +03:00

Author

Owner

@vm86 commented on GitHub (Sep 3, 2019):

@Kugelschieber
So why is health check here if it doesn't check anything?

@vm86 commented on GitHub (Sep 3, 2019): @Kugelschieber So why is health check here if it doesn't check anything?

kerem commented

2026-03-13 15:39:10 +03:00

Author

Owner

@Kugelschieber commented on GitHub (Sep 3, 2019):

It's just an endpoint to check wether the service is reachable or not. It does not make sure it's working correctly. My first guess is that you have misconfigured the server somehow.

@Kugelschieber commented on GitHub (Sep 3, 2019): It's just an endpoint to check wether the service is reachable or not. It does not make sure it's working correctly. My first guess is that you have misconfigured the server somehow.

kerem commented

2026-03-13 15:39:15 +03:00

Author

Owner

@vm86 commented on GitHub (Sep 3, 2019):

Acme-dns is working in kubernetes. SQLite located in cephfs. SQLite is becoming unreachable when cephfs doesn't availiable or restarted. Your health check doesn't check it, so kubernetes can't restart acme-dns. I receive I/O error after this situation.

@vm86 commented on GitHub (Sep 3, 2019): Acme-dns is working in kubernetes. SQLite located in cephfs. SQLite is becoming unreachable when cephfs doesn't availiable or restarted. Your health check doesn't check it, so kubernetes can't restart acme-dns. I receive I/O error after this situation.

kerem commented

2026-03-13 15:39:20 +03:00

Author

Owner

@Kugelschieber commented on GitHub (Sep 3, 2019):

Running acme-dns inside Kubernetes isn't a good idea. Kubernetes uses port 53 (DNS) for service discovery that collides with acme-dns.

@Kugelschieber commented on GitHub (Sep 3, 2019): Running acme-dns inside Kubernetes isn't a good idea. Kubernetes uses port 53 (DNS) for service discovery that collides with acme-dns.

kerem commented

2026-03-13 15:39:26 +03:00

Author

Owner

@vm86 commented on GitHub (Sep 5, 2019):

@socketpair

@vm86 commented on GitHub (Sep 5, 2019): @socketpair