Package: unbound-anchor Version: 1.4.16-1 Severity: normal Dear Maintainer,
today I wondered about an error message in my syslog: Apr 6 11:27:49 ossietzky unbound-anchor: /var/lib/unbound/root.key has content Apr 6 11:27:49 ossietzky unbound-anchor: fail: the anchor is NOT ok and could not be fixed When run by hand, unbound-anchor told me: $ sudo unbound-anchor -a /var/lib/unbound/root.key -v /var/lib/unbound/root.key has content success: the anchor is ok And the same for an older root.key I had around. The unbound-anchor HOWTO says: "Set the unbound-anchor tool to run at system startup, it is part of the unbound package. This tool checks if the anchor is out-of-date and attempts to update it. A good way is to run it from the init scripts, with sudo -u unbound so that the file permissions work out. Before unbound-anchor is run inside the init scripts, you must run NTP (in secure mode), so that the time and date have been set properly. " So unbound-anchor needs a network connection and correct time. In my case, it was run before the (WLAN) network connection was set up, and of course also before the time could be set via NTP. I guess this caused my error message. Cheers Michael -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable'), (10, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages unbound-anchor depends on: ii libc6 2.13-27 ii libexpat1 2.1.0~beta3-2 ii libgcc1 1:4.7.0-1 ii libldns1 1.6.12-1 ii libssl1.0.0 1.0.1-4 ii libunbound2 1.4.16-1 unbound-anchor recommends no packages. unbound-anchor suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
