• Community Support
  • USEnglish

  • Unbound is always unhealthy - watchdog nagios check_dns issue?

DocFraggle

No it’s x86

# inxi -Sz
System:
Kernel: 5.14.0-362.24.1.el9_3.0.1.x86_64
arch: x86_64 bits: 64
Console: pty pts/0 Distro: Rocky Linux
9.3 (Blue Onyx)

    DocFraggle

    Yeah looks like the same issue. Also, mailcow/mailcow-dockerizedissues/5121. Seems they all gave up since nagios has no way to debug it, but while I did comment out the check in the script for now so it’s not constantly restarting the unbound container, I don’t like to give up. Lol.

    Nothing really special about the setup except that I’m using the Keycloak functionality. The server itself has nothing significant installed, not even firewalls. It’s a pretty ordinary KVM based VPS. Clean install of docker and mailcow. I do have IPv6 in use, but I see someone else mentioned they had the issue with it disabled. No real customizations added yet.

      Is -V throwing the segfault as well?

      f87b47a44e88:/# /usr/lib/nagios/plugins/check_dns -V
check_dns v (nagios-plugins 2.4.5)

      The version of the installed APK would be interesting, too:

      f87b47a44e88:/# apk info nagios-plugins-dns
nagios-plugins-dns-2.4.5-r2 description:
Nagios plugin check_dns

nagios-plugins-dns-2.4.5-r2 webpage:
https://nagios-plugins.org/

nagios-plugins-dns-2.4.5-r2 installed size:
80 KiB

        DocFraggle

        It does respond fine to the -h and -V options. And the version is the same as you posted. I also verified that the Dockerfile is the same between the latest nightly branch commit and the 2024-04 tag. So the actual docker images should be basically identical.

        And I ran nslookup since I read that the dns_check is just calling that tool and it returns expected values.

        fc042ba8c1d5:/# /usr/lib/nagios/plugins/check_dns -V
        check_dns v (nagios-plugins 2.4.5)
        fc042ba8c1d5:/# apk info nagios-plugins-dns
        nagios-plugins-dns-2.4.5-r2 description:
        Nagios plugin check_dns
        nagios-plugins-dns-2.4.5-r2 webpage:
        https://nagios-plugins.org/
        nagios-plugins-dns-2.4.5-r2 installed size:
        80 KiB
        fc042ba8c1d5:/# nslookup stackexchange.com
        Server: 127.0.0.11
        Address: 127.0.0.11#53
        Non-authoritative answer:
        Name: stackexchange.com
        Address: 172.64.144.30
        Name: stackexchange.com
        Address: 104.18.43.226

          If you use the Google DNS, does it segfault as well?

          /usr/lib/nagios/plugins/check_dns -s 8.8.8.8 -H stackoverflow.com

            DocFraggle
            Yes, I tried various combinations of servers and hosts. Everything I’ve tried causes the segfault so far.

              Last thing I can think of is that the installed package is corrupt… what’s your md5sum?

              f87b47a44e88:/# md5sum /usr/lib/nagios/plugins/check_dns
42aaa5fc36dcecda78f83d1048e7861b  /usr/lib/nagios/plugins/check_dns

              Maybe try to reinstall it inside the watchdog container with the apk command

                DocFraggle

                Yep md5sum is identical, too.

                And I tried deleting all nagios plugins and reinstalling and no help. So I’m guessing there’s some kind of conflict or bug with docker or the host OS rather than anything wrong with the container itself. Too bad it can’t be debugged.

                  What’s your current setup? Do you have selinux in place?

                    DocFraggle

                    It’s a totally fresh install of Rocky Linux 9.3. selinux is enabled but in permissive state. Just for the heck of it I disabled it totally and restarted. But no change.

                      No one is typing