starred/ddns-updater
1
0
Fork 0
mirror of https://github.com/qdm12/ddns-updater.git synced 2026-05-29 19:31:56 -04:00
Code Issues 312 Packages Projects Releases 10 Wiki Activity

Container healthcheck: unhealty #105

New Issue
Closed
opened 2025-11-20 04:20:19 -05:00 by saavagebueno · 9 comments
saavagebueno commented 2025-11-20 04:20:19 -05:00
Owner
Copy Link

Originally created by @frepke on GitHub (Mar 12, 2021).

Originally assigned to: @qdm12 on GitHub.

TLDR: container is running unhealthy

  1. Is this urgent: No

  2. DNS provider(s) you use: duckdns.org and selfhost.de

  3. Program version:

    Running version latest built on 2021-03-04T14:37:47Z (commit d5e4936)

  4. What are you using to run the container: docker-compose

  5. Extra information (optional) - Container was running healthy in the past.

Logs:

    today at 12:53  =========================================
    today at 12:53  =========================================
    today at 12:53  ========= DDNS Universal Updater ========
    today at 12:53  =========================================
    today at 12:53  === Made with ❤️  by github.com/qdm12 ====
    today at 12:53  =========================================
    today at 12:53  
    today at 12:53  Running version latest built on 2021-03-04T14:37:47Z (commit d5e4936)
    today at 12:53  
    today at 12:53  
    today at 12:53  🔧  Need help? https://github.com/qdm12/ddns-updater/issues/new
    today at 12:53  💻  Email? quentin.mcgaw@gmail.com
    today at 12:53  ☕  Slack? Join from the Slack button on Github
    today at 12:53  💸  Help me? https://github.com/sponsors/qdm12
    today at 12:53  2021/03/12 12:53:24 INFO healthcheck server: listening on 127.0.0.1:9999
    today at 12:53  2021/03/12 12:53:24 INFO http server: listening on 0.0.0.0:8000
    today at 12:53  2021/03/12 12:53:24 INFO backup: disabled

Configuration file (remove your credentials!):

{
    "settings": [
        {
            "provider": "selfhost.de",
            "domain": "selfhost.co",
            "host": "testa",
            "username": "000000",
            "password": "XXXXXX",
            "ip_version": "ipv4"
        },
        {
            "provider": "duckdns",
            "host": "testa, testb, testc",
            "token": "abc-123",
            "ip_version": "ipv4"
        }
    ]
}

Host OS: Debian Buster

Originally created by @frepke on GitHub (Mar 12, 2021). Originally assigned to: @qdm12 on GitHub. <!-- YOU CAN CHAT THERE EVENTUALLY: https://github.com/qdm12/ddns-updater/discussions --> **TLDR**: *container is running unhealthy* 1. Is this urgent: No 2. DNS provider(s) you use: duckdns.org and selfhost.de 3. Program version: <!-- See the line at the top of your logs --> `Running version latest built on 2021-03-04T14:37:47Z (commit d5e4936)` 4. What are you using to run the container: docker-compose 5. Extra information (optional) - Container was running healthy in the past. Logs: ```logs today at 12:53 ========================================= today at 12:53 ========================================= today at 12:53 ========= DDNS Universal Updater ======== today at 12:53 ========================================= today at 12:53 === Made with ❤️ by github.com/qdm12 ==== today at 12:53 ========================================= today at 12:53 today at 12:53 Running version latest built on 2021-03-04T14:37:47Z (commit d5e4936) today at 12:53 today at 12:53 today at 12:53 🔧 Need help? https://github.com/qdm12/ddns-updater/issues/new today at 12:53 💻 Email? quentin.mcgaw@gmail.com today at 12:53 ☕ Slack? Join from the Slack button on Github today at 12:53 💸 Help me? https://github.com/sponsors/qdm12 today at 12:53 2021/03/12 12:53:24 INFO healthcheck server: listening on 127.0.0.1:9999 today at 12:53 2021/03/12 12:53:24 INFO http server: listening on 0.0.0.0:8000 today at 12:53 2021/03/12 12:53:24 INFO backup: disabled ``` Configuration file (**remove your credentials!**): ```json { "settings": [ { "provider": "selfhost.de", "domain": "selfhost.co", "host": "testa", "username": "000000", "password": "XXXXXX", "ip_version": "ipv4" }, { "provider": "duckdns", "host": "testa, testb, testc", "token": "abc-123", "ip_version": "ipv4" } ] } ``` Host OS: Debian Buster
saavagebueno commented 2025-11-20 04:20:20 -05:00
Author
Owner
Copy Link

@qdm12 commented on GitHub (Mar 12, 2021):

What does docker inspect ddns-updater give, especially what messages in the failed healthcheck section?

It's strange, usually it should be unhealthy on a failed update. Does the UI state any previous failed update?

@qdm12 commented on GitHub (Mar 12, 2021): What does `docker inspect ddns-updater` give, especially what messages in the failed healthcheck section? It's strange, usually it should be unhealthy on a failed update. Does the UI state any previous failed update?
saavagebueno commented 2025-11-20 04:20:21 -05:00
Author
Owner
Copy Link

@frepke commented on GitHub (Mar 12, 2021):

What does docker inspect ddns-updater give, especially what messages in the failed healthcheck section?

It's strange, usually it should be unhealthy on a failed update. Does the UI state any previous failed update?

            "Cmd": null,
            "Healthcheck": {
                "Test": [
                    "CMD",
                    "/updater/app",
                    "healthcheck"
                ],
                "Interval": 60000000000,
                "Timeout": 5000000000,
                "StartPeriod": 10000000000,
                "Retries": 2
            },

Don't see any failed updates in the GUI

@frepke commented on GitHub (Mar 12, 2021): > > > What does `docker inspect ddns-updater` give, especially what messages in the failed healthcheck section? > > It's strange, usually it should be unhealthy on a failed update. Does the UI state any previous failed update? ``` "Cmd": null, "Healthcheck": { "Test": [ "CMD", "/updater/app", "healthcheck" ], "Interval": 60000000000, "Timeout": 5000000000, "StartPeriod": 10000000000, "Retries": 2 }, ``` Don't see any failed updates in the GUI
saavagebueno commented 2025-11-20 04:20:21 -05:00
Author
Owner
Copy Link

@frepke commented on GitHub (Mar 13, 2021):

Hmmm, there's something wrong with duckdns

@frepke commented on GitHub (Mar 13, 2021): Hmmm, there's something wrong with duckdns
saavagebueno commented 2025-11-20 04:20:21 -05:00
Author
Owner
Copy Link

@qdm12 commented on GitHub (Mar 13, 2021):

If the healthcheck fails it should log something in the failed attempts though (in the docker inspect command).

I also use duckdns and the DNS resolutions of xxx.duckdns.org tend to fail occasionally, maybe that's related?

@qdm12 commented on GitHub (Mar 13, 2021): If the healthcheck fails it should log something in the failed attempts though (in the docker inspect command). I also use duckdns and the DNS resolutions of xxx.duckdns.org tend to fail occasionally, maybe that's related?
saavagebueno commented 2025-11-20 04:20:21 -05:00
Author
Owner
Copy Link

@frepke commented on GitHub (Mar 13, 2021):

                        "Start": "2021-03-13T17:17:46.956084129+01:00",
                        "End": "2021-03-13T17:17:47.693733184+01:00",
                        "ExitCode": 1,
                        "Output": "lookup IP addresses for xxxx.duckdns.org are xx.197.207.xxx instead of xx.144.217.xxx\n\n"

Where the first ip is my actual ip, the second ip is the ip from a few days ago.
The "set-ip" in the GUI from 1 of the 5 duckdns subdomains is wrong.

@frepke commented on GitHub (Mar 13, 2021): ``` "Start": "2021-03-13T17:17:46.956084129+01:00", "End": "2021-03-13T17:17:47.693733184+01:00", "ExitCode": 1, "Output": "lookup IP addresses for xxxx.duckdns.org are xx.197.207.xxx instead of xx.144.217.xxx\n\n" ``` Where the first ip is my actual ip, the second ip is the ip from a few days ago. The "set-ip" in the GUI from 1 of the 5 duckdns subdomains is wrong.
saavagebueno commented 2025-11-20 04:20:21 -05:00
Author
Owner
Copy Link

@frepke commented on GitHub (Mar 13, 2021):

Deleted the updates.json and now everything fine again.

@frepke commented on GitHub (Mar 13, 2021): Deleted the updates.json and now everything fine again.
saavagebueno commented 2025-11-20 04:20:21 -05:00
Author
Owner
Copy Link

@qdm12 commented on GitHub (Mar 13, 2021):

Well that's strange nonetheless, maybe and old version of the json. Let me know if it happens again

@qdm12 commented on GitHub (Mar 13, 2021): Well that's strange nonetheless, maybe and old version of the json. Let me know if it happens again
saavagebueno commented 2025-11-20 04:20:22 -05:00
Author
Owner
Copy Link

@redtripleAAA commented on GitHub (May 30, 2021):

I got the issue here

raspberry Pi4

2021/05/30 07:54:20 INFO healthcheck server: listening on 127.0.0.1:9999
2021/05/30 07:54:20 ERROR healthcheck server: listen tcp 127.0.0.1:9999: bind: address already in use
2021/05/30 07:54:20 INFO healthcheck server: restarting

Inspect shows:

        },
        "Healthcheck": {
            "Interval": 60000000000,
            "Retries": 2,
            "StartPeriod": 10000000000,
            "Test": [
                "CMD",
                "/updater/app",
                "healthcheck"
            ],
            "Timeout": 5000000000
        },

        "Health": {
            "FailingStreak": 0,
            "Log": [
                {
                    "End": "2021-05-30T03:46:52.298492958-04:00",
                    "ExitCode": 0,
                    "Output": "",
                    "Start": "2021-05-30T03:46:51.907187919-04:00"
                },
                {
                    "End": "2021-05-30T03:51:18.53787352-04:00",
                    "ExitCode": 0,
                    "Output": "",
                    "Start": "2021-05-30T03:51:18.156313776-04:00"
                },
                {
                    "End": "2021-05-30T03:52:19.044550991-04:00",
                    "ExitCode": 0,
                    "Output": "",
                    "Start": "2021-05-30T03:52:18.587554873-04:00"
                },
                {
                    "End": "2021-05-30T03:53:19.473498734-04:00",
                    "ExitCode": 0,
                    "Output": "",
                    "Start": "2021-05-30T03:53:19.093848526-04:00"
                },
                {
                    "End": "2021-05-30T03:54:51.428834567-04:00",
                    "ExitCode": 0,
                    "Output": "",
                    "Start": "2021-05-30T03:54:51.05729881-04:00"
                }
            ],
            "Status": "healthy"
        },
        "OOMKilled": false,
        "Paused": false,
        "Pid": 4561,
        "Restarting": false,
        "Running": true,
        "StartedAt": "2021-05-30T07:53:51.056939893Z",
        "Status": "running"
    }
}

and the strange thing, that it's showing as healthy
image

and it's still accessible to the GUI and updated the IP

@redtripleAAA commented on GitHub (May 30, 2021): I got the issue here raspberry Pi4 ``` 2021/05/30 07:54:20 INFO healthcheck server: listening on 127.0.0.1:9999 2021/05/30 07:54:20 ERROR healthcheck server: listen tcp 127.0.0.1:9999: bind: address already in use 2021/05/30 07:54:20 INFO healthcheck server: restarting ``` Inspect shows: ``` }, "Healthcheck": { "Interval": 60000000000, "Retries": 2, "StartPeriod": 10000000000, "Test": [ "CMD", "/updater/app", "healthcheck" ], "Timeout": 5000000000 }, ``` + ``` "Health": { "FailingStreak": 0, "Log": [ { "End": "2021-05-30T03:46:52.298492958-04:00", "ExitCode": 0, "Output": "", "Start": "2021-05-30T03:46:51.907187919-04:00" }, { "End": "2021-05-30T03:51:18.53787352-04:00", "ExitCode": 0, "Output": "", "Start": "2021-05-30T03:51:18.156313776-04:00" }, { "End": "2021-05-30T03:52:19.044550991-04:00", "ExitCode": 0, "Output": "", "Start": "2021-05-30T03:52:18.587554873-04:00" }, { "End": "2021-05-30T03:53:19.473498734-04:00", "ExitCode": 0, "Output": "", "Start": "2021-05-30T03:53:19.093848526-04:00" }, { "End": "2021-05-30T03:54:51.428834567-04:00", "ExitCode": 0, "Output": "", "Start": "2021-05-30T03:54:51.05729881-04:00" } ], "Status": "healthy" }, "OOMKilled": false, "Paused": false, "Pid": 4561, "Restarting": false, "Running": true, "StartedAt": "2021-05-30T07:53:51.056939893Z", "Status": "running" } } ``` and the strange thing, that it's showing as healthy ![image](https://user-images.githubusercontent.com/5244872/120096735-28df9e00-c0fb-11eb-8fbf-521fc855c58b.png) and it's still accessible to the GUI and updated the IP
saavagebueno commented 2025-11-20 04:20:22 -05:00
Author
Owner
Copy Link

@qdm12 commented on GitHub (May 30, 2021):

Ah bummer. It's listening on port 9999 and gluetun already has its own healthcheck server listening on port 9999. I created https://github.com/qdm12/ddns-updater/issues/211 for it, feel free to subscribe to it and continue discussing there. Other repos like gluetun would benefit from that too. Maybe I'll switch to writing to a /tmp file instead of using the network to avoid conflicting with Ports, I'll see what's best...

@qdm12 commented on GitHub (May 30, 2021): Ah bummer. It's listening on port 9999 and gluetun already has its own healthcheck server listening on port 9999. I created https://github.com/qdm12/ddns-updater/issues/211 for it, feel free to subscribe to it and continue discussing there. Other repos like gluetun would benefit from that too. Maybe I'll switch to writing to a /tmp file instead of using the network to avoid conflicting with Ports, I'll see what's best...
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Category: Config problem 📝
Category: Database 🗃️
Category: Documentation ✒️
Category: Foolproof settings 👼
Category: Good idea 🎯
Category: Healthcheck 🩺
Category: IP fetching 📥
Category: Label missing ❗
Category: Maintenance ⛓️
Category: Motivated! 🙌
Category: New provider 🆕
Category: Provider update ♻️
Category: Shoutrrr 📢
Category: Web UI 🖱️
Category: Wildcard 🃏
Closed: ⚰️ Inactive
Closed: 👥 Duplicate
Closed: 🗑️ Bad issue
Complexity: ☣️ Hard to do
Complexity: 🟩 Easy to do
Priority: 💤 Low priority
Priority: 🚨 Urgent
pull-request
Mirrored from GitHub Pull Request
 Status: 🔒 After next release
Status: 🔴 Blocked
Status: 🗯️ Waiting for feedback
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ddns-updater#105
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?