Bug#1078413: pdns: FTBFS: make[6]: *** [Makefile:3871: test-suite.log] Error 1
The interesting part of that build log (the bit that fits the test failure) is "configure: OpenSSL ecdsa: no". (I'm off work for another week, I'm happy to debug after that)
Bug#1070136: openjdk-17-jre-headless: error creating symbolic link '/usr/share/man/man1/java.1.gz.dpkg-tmp': No such file or directory
Package: openjdk-17-jre-headless Version: 17.0.11+9-1~deb12u1 Severity: normal X-Debbugs-Cc: pe...@7bits.nl Dear Maintainer, * What led up to the situation? Installing openjdk-17-jre-headless on a very minimal base system. The 12-slim Docker image is not minimal enough to reproduce this (it has an empty /usr/share/man/man1) but an mkosi-build Debian Bookworm image reproduces it (by not having /usr/share/man/man1) * What exactly did you do (or not do) that was effective (or ineffective)? As suggested in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863199 (which appears to be a previous instanc e of the same problem), mkdir -p /usr/share/man/man1 followed by apt install -f sorted the situation. The fix ap plied to close that bug would likely help here too. Please note that the System Information below is from after: * attempting to install openjdk-17-jre-headless * the mkdir -p * installing reportbug and its dependencies although I have the impression installing reportbug did not change any of the information mentioned below. -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_DIE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages openjdk-17-jre-headless depends on: ii ca-certificates-java 20230710~deb12u1 ii java-common 0.74 ii libasound21.2.8-1+b1 ii libc6 2.36-9+deb12u1 ii libcups2 2.4.2-3+deb12u5 ii libfontconfig12.14.1-4 ii libfreetype6 2.12.1+dfsg-5 ii libgcc-s1 12.2.0-14 ii libharfbuzz0b 6.0.0+dfsg-3 ii libjpeg62-turbo 1:2.1.5-2 ii liblcms2-22.14-2 ii libnss3 2:3.87.1-1 ii libpcsclite1 1.9.9-2 ii libstdc++612.2.0-14 ii util-linux2.38.1-5+b1 ii zlib1g1:1.2.13.dfsg-1 openjdk-17-jre-headless recommends no packages. Versions of packages openjdk-17-jre-headless suggests: pn fonts-dejavu-extra pn fonts-indic pn fonts-ipafont-gothic pn fonts-ipafont-mincho pn fonts-wqy-microhei | fonts-wqy-zenhei pn libnss-mdns -- no debconf information
Bug#1050600: pdns_control: list-zones appears to require a type filter, returns empty without
This was fixed upstream in https://github.com/PowerDNS/pdns/pull/12181 which is part of version 4.7.3
Bug#1035304: Bug#1038451: bullseye-pu: package systemd/247.3-7+deb11u4
text looks good to me, but I think u3 also fixed a memory leak?
Bug#1035304: Info received (please ship this to bullseye-updates)
plus Cc to pkg-systemd-maintainers
Bug#1035304: please ship this to bullseye-updates
Hello! Just in my immediate surroundings, around one person a week is hit by the udev serial/by-id bug that this version (deb11u3) fixes. Can you push it to bullseye-updates? I understand this will also push deb11u4, which seems good to me too. Thank you! -- Peter van Dijk pe...@7bits.nl
Bug#986564: evolution: crash in camel_imapx_folder_set_mailbox
I have taken `apt-get source evolution-data-server` on an up to date Bullseye
system, and imported the patch Chris mentioned above. The package I built from
that has been stable for several days now.
Please find my diff attached. I hope the maintainer can import it into Bullseye.
commit 77914836bb483673261377a737cfb8f72efff81c
Author: Peter van Dijk
Date: Wed Jan 5 13:51:23 2022 +0100
import upstream patch to fix Evolution crashes
diff --git a/debian/changelog b/debian/changelog
index 0a21d5f..e60e774 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+evolution-data-server (3.38.3-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Import https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/1f1017492
+to fix https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986564
+
+ -- Peter van Dijk Wed, 05 Jan 2022 13:49:49 +0100
+
evolution-data-server (3.38.3-1) unstable; urgency=medium
* New upstream release
diff --git a/debian/libcamel-1.2-62.symbols b/debian/libcamel-1.2-62.symbols
index 467511e..0cf7260 100644
--- a/debian/libcamel-1.2-62.symbols
+++ b/debian/libcamel-1.2-62.symbols
@@ -1359,6 +1359,8 @@ libcamel-1.2.so.62 libcamel-1.2-62 #MINVER#
camel_util_bdata_get_string@Base 3.24.1
camel_util_bdata_put_number@Base 3.24.1
camel_util_bdata_put_string@Base 3.24.1
+ camel_utils_weak_ref_free@Base 3.38.3-1.1
+ camel_utils_weak_ref_new@Base 3.38.3-1.1
camel_uudecode_step@Base 3.19.92
camel_uuencode_close@Base 3.19.92
camel_uuencode_step@Base 3.19.92
diff --git a/debian/patches/evolution-crash.patch b/debian/patches/evolution-crash.patch
new file mode 100644
index 000..0270049
--- /dev/null
+++ b/debian/patches/evolution-crash.patch
@@ -0,0 +1,253 @@
+import https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/1f1017492
+
+this fixes https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986564
+--- a/src/camel/camel-folder.c
b/src/camel/camel-folder.c
+@@ -152,50 +152,61 @@
+ camel_folder_synchronize_sync (folder, FALSE, cancellable, error);
+ }
+
++static void
++folder_schedule_store_changes_job (CamelFolder *folder)
++{
++ CamelSession *session;
++ CamelStore *parent_store;
++
++ g_return_if_fail (CAMEL_IS_FOLDER (folder));
++
++ parent_store = camel_folder_get_parent_store (folder);
++ session = parent_store ? camel_service_ref_session (CAMEL_SERVICE (parent_store)) : NULL;
++ if (session) {
++ gchar *description;
++
++ /* Translators: The first â%sâ is replaced with an account name and the second â%sâ
++ is replaced with a full path name. The spaces around â:â are intentional, as
++ the whole â%s : %sâ is meant as an absolute identification of the folder. */
++ description = g_strdup_printf (_("Storing changes in folder â%s : %sâ"),
++ camel_service_get_display_name (CAMEL_SERVICE (parent_store)),
++ camel_folder_get_full_name (folder));
++
++ camel_session_submit_job (session, description,
++ folder_store_changes_job_cb,
++ g_object_ref (folder), g_object_unref);
++
++ g_free (description);
++ }
++
++ g_clear_object (&session);
++}
++
+ static gboolean
+-folder_schedule_store_changes_job (gpointer user_data)
++folder_schedule_store_changes_job_cb (gpointer user_data)
+ {
+- CamelFolder *folder = user_data;
++ GWeakRef *weak_ref = user_data;
+ GSource *source;
++ CamelFolder *folder;
+
+ source = g_main_current_source ();
+
+ if (g_source_is_destroyed (source))
+ return FALSE;
+
+- g_return_val_if_fail (CAMEL_IS_FOLDER (folder), FALSE);
+-
+- g_mutex_lock (&folder->priv->store_changes_lock);
+-
+- if (folder->priv->store_changes_id == g_source_get_id (source)) {
+- CamelSession *session;
+- CamelStore *parent_store;
+-
+- folder->priv->store_changes_id = 0;
+-
+- parent_store = camel_folder_get_parent_store (folder);
+- session = parent_store ? camel_service_ref_session (CAMEL_SERVICE (parent_store)) : NULL;
+- if (session) {
+- gchar *description;
++ folder = g_weak_ref_get (weak_ref);
++ if (folder) {
++ g_mutex_lock (&folder->priv->store_changes_lock);
+
+- /* Translators: The first â%sâ is replaced with an account name and the second â%sâ
+- is replaced with a full path name. The spaces around â:â are intentional, as
+- the whole â%s : %sâ is meant as an absolute identification of the folder. */
+- description = g_strdup_printf (_("Storing changes in folder â%s : %sâ"),
+-camel_service_get_display_name (CAMEL_SERVICE (parent_store)),
+-camel_folder_get_full_name (folder));
+-
+- camel_session_submit_job (session, description,
+-folder_store_changes_job_cb,
+-g_object_ref (folder), g_object_unref);
+-
+- g_free (description);
++ if (folder->priv->store_changes_id == g_source_get_id (source)) {
++ folder->priv->store_changes_id = 0;
++ folder_schedule_store_changes_job (folder);
+ }
+
+- g_clear_object (&
Bug#1003245: release-notes: sections in Upgrade guide could be ordered more usefully
Package: release-notes Severity: normal X-Debbugs-Cc: pe...@7bits.nl Dear Maintainer, as I was upgrading a system from Debian 10 to Debian 11, I dutifully read https://www.debian.org/releases/bullseye/amd64/release-notes/ch-upgrading.en.html I ran into 4.2.7 (The security section) and 4.2.8 (The proposed-updates section). They contain relevant information that I was happy to receive. However, this information comes some time before the point that I am actually editing sources.list files. My suggestion: put these two explanations early in 4.3 - either as extra sentences after "add sources for bullseye and typically to remove sources for buster." or as extra sections between what currently is 4.3 (Preparing APT source-list files) and 4.3.1 (Adding APT Internet sources). Thank you.
Bug#1003244: openssh-client: ssh_config manpage has conflicting information about Debian-specific changes to defaults
Package: openssh-client Version: 1:8.4p1-5 Severity: normal X-Debbugs-Cc: pe...@7bits.nl Dear Maintainer, * What led up to the situation? After upgrading to Debian 11, using ssh to connect to one of my machines took a very long time. The time is spent in: debug1: Next authentication method: gssapi-with-mic debug1: Unspecified GSS failure. Minor code may provide more information No Kerberos credentials available (default cache: FILE:/tmp/krb5cc_1000) This happens twice and takes a total of around 100 seconds. The first few tries I figured my VM had half-died because ssh just sat there. After a while I figured out disabling GSSAPIAuthentication helped. But the manpage is confusing. ssh_config(5) says: GSSAPIAuthentication Specifies whether user authentication based on GSSAPI is allowed. The default is no. it also says: Note that the Debian openssh-client package sets several options as standard in /etc/ssh/ssh_config which are not the default in ssh(1): o Include /etc/ssh/ssh_config.d/*.conf o SendEnv LANG LC_* o HashKnownHosts yes o GSSAPIAuthentication yes but I usually search manpages, not read them end to end. So, the bit about Debian defaults being different is very hard to miss. Perhaps the sections on those four options could grow a few words repeating the changes that Debian did. -- System Information: Debian Release: 11.2 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-10-amd64 (SMP w/12 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openssh-client depends on: ii adduser 3.118 ii dpkg 1.20.9 ii libc6 2.31-13+deb11u2 ii libedit2 3.1-20191231-2+b1 ii libfido2-11.6.0-2 ii libgssapi-krb5-2 1.18.3-6+deb11u1 ii libselinux1 3.1-3 ii libssl1.1 1.1.1k-1+deb11u1 ii passwd1:4.8.1-1 ii zlib1g1:1.2.11.dfsg-2 Versions of packages openssh-client recommends: ii xauth 1:1.1-1 Versions of packages openssh-client suggests: pn keychain pn libpam-ssh pn monkeysphere pn ssh-askpass -- Configuration Files: /etc/ssh/ssh_config changed: Include /etc/ssh/ssh_config.d/*.conf Host * SendEnv LANG LC_* HashKnownHosts yes GSSAPIAuthentication no -- no debconf information
Bug#962870: tracker-miner-fs: Repeated SIGABRT crashes due to file_tree_lookup assertion failed
> After that (30 minutes ago now), nothing has crashed - not tracker-miner-fs, > not tracker-store, and, to my surprise, not Evolution either. I am sad to report that Evolution's unexplained recovery was temporary. So ignore what I said about Evolution - it still crashes which then likely is unrelated. -- Peter van Dijk pe...@7bits.nl
Bug#962870: tracker-miner-fs: Repeated SIGABRT crashes due to file_tree_lookup assertion failed
After upgrading from Debian 10 to Debian 11, I found Evolution crashing whenever I tried to delete a few messages. Looking at coredumpctl, I noticed tracker-miner-fs crashing every few minutes, as you mention. I let myself be distracted by that for a bit, so I dug in with gdb, and found: #4 0x7f3955ceca82 in file_tree_lookup (tree=0x7f394400d320, file=file@entry=0x5644bfbfe2c0, parent_node=parent_node@entry=0x7fff51069238, uri_remainder=uri_remainder@entry=0x7fff51069240) at ../src/libtracker-miner/tracker-file-system.c:259 259 ../src/libtracker-miner/tracker-file-system.c: No such file or directory. (gdb) print ptr $15 = (gchar *) 0x5644bfb3c74f "-expenses" So I looked around my homedir for that string, and I found ~/Documents/ox-expenses/ Thinking it might be treating the ox- prefix as special (wouldn't know why), I renamed the dir to oxexpenses. Then tracker-store crashed! Jan 04 15:36:12 plato tracker-store[873997]: SQLite error: database disk image is malformed (errno: Success) Jan 04 15:36:12 plato tracker-store[873997]: SQLite experienced an error with file:'/home/peter/.cache/tracker/meta.db'. It is either NOT a SQLite database or it is corrupt or there was an IO error accessing the data. This file has now been removed and will be recreated on the next start. Shutting down now. Jan 04 15:36:13 plato systemd-coredump[874163]: Process 873997 (tracker-store) of user 1000 dumped core. Stack trace of thread 874001: #0 0x7f2214af9ca7 g_log_structured_array (libglib-2.0.so.0 + 0x58ca7) #1 0x7f2214afa0b5 g_log_default_handler (libglib-2.0.so.0 + 0x590b5) #2 0x7f2214afa309 g_logv (libglib-2.0.so.0 + 0x59309) #3 0x7f2214afa59f g_log (libglib-2.0.so.0 + 0x5959f) #4 0x7f2214c08e83 n/a (libtracker-data.so + 0x38e83) #5 0x7f2214bfe03c n/a (libtracker-data.so + 0x2e03c) #6 0x7f2214c016dc n/a (libtracker-data.so + 0x316dc) After that (30 minutes ago now), nothing has crashed - not tracker-miner-fs, not tracker-store, and, to my surprise, not Evolution either. I don't have an explanation for what happened here, but perhaps you can try removing your meta.db (plus meta.db-* in the same dir) to see if it helps? -- Peter van Dijk pe...@7bits.nl
Bug#964544: gist: version of gist in buster uses deprecated GitHub APIs
Package: gist Version: 5.0.0-2 Severity: important Tags: patch Dear Maintainer, please consider backporting Authorization header support for gist-paste to the gist package in Debian buster. Right now, every few pastes I do, I get an email '[GitHub API] Deprecation notice for authentication via URL query parameters'. Additional info on the deprecation can be found at https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/ The API change will be mandatory starting May 5, 2021. This is well within buster's expected life time. Upstream has a patch at https://github.com/defunkt/gist/commit/635b1437a513e9a13367827ee3f74fbbdaa54aa8 ; this patch is part of 5.1.0 as currently available in testing and unstable. Can this patch be backported to Buster? Thank you. -- System Information: Debian Release: 10.4 APT prefers stable-debug APT policy: (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.5.0-0.bpo.2-amd64 (SMP w/12 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gist depends on: ii ruby1:2.5.1 ii ruby-json 2.1.0+dfsg-2+b1 ii sensible-utils 0.0.12 gist recommends no packages. gist suggests no packages. -- no debconf information
Bug#957670: pdns: ftbfs with GCC-10
Hello Matthias, On Fri, 17 Apr 2020 11:08:30 + Matthias Klose wrote: > Package: src:pdns > Version: 4.2.1-1 > Severity: normal > Tags: sid bullseye > User: debian-...@lists.debian.org > Usertags: ftbfs-gcc-10 This should help: https://github.com/PowerDNS/pdns/pull/8640/files Alternatively, as this is for sid/bullseye, when 4.3.0 comes to Debian soon (we released it upstream last week), it already includes this fix. Kind regards, -- Peter van Dijk PowerDNS.COM BV - https://www.powerdns.com/
Bug#918661:
On Tue, 29 Jan 2019 23:43:58 +0100 StalkR wrote: > I couldn't find a packet cache setting on > https://doc.powerdns.com/md/authoritative/settings/ or > https://doc.powerdns.com/md/authoritative/performance/#packet-cache other > than cache-ttl/max-cache-entries. > (I'm using a bind backend, in case it matters.) cache-ttl=0 is the setting you are looking for. Kind regards, -- Peter van Dijk PowerDNS.COM BV - https://www.powerdns.com/
Bug#918661: pdns-server: EDNS Compliance Steps
On Tue, 8 Jan 2019 22:24:21 +1100 Dean Hamstead wrote: The same results are given when tested against: pdns-server (3.4.1-4+deb8u8) pdns-server (4.0.3-1~bpo8+1) pdns-server (4.0.3-1+deb9u2) To get a clean slate on 4.0, you need to disable the packet cache. However, as Christian noted, the errors reported otherwise do not actually hurt production usage. Kind regards, -- Peter van Dijk PowerDNS.COM BV - https://www.powerdns.com/
Bug#912735: ITP: dnsperf -- DNS server and recursor performance testing tools
On Sat, 03 Nov 2018 10:45:54 +0100 Stefan Nachtnebel wrote: Currently, there are no other packages providing dns performance testing tools. Just for the record, the pdns-tools package provides a few. Co-maintainers are welcome, but not needed. I would need a sponsor. You may want to get in touch with the DNS Team (https://salsa.debian.org/dns-team, team+...@tracker.debian.org). Kind regards, -- Peter van Dijk PowerDNS.COM BV - https://www.powerdns.com/
Bug#900277: Found the issue
I can reproduce this ‘hang’ (actually it’s a very busy read() loop). A simpler ‘echo 1,2,3 > test2.csv’ does work, so this is just exposing a bug in the CSV implementation.
Bug#844275: mysql_config injects build flags which breaks the build for other packages
Hi, On Mon, 14 Nov 2016 00:39:50 +0100 Michael Biebl wrote: Looking a bit closer, this is a bug in mysql_config, which injects bogus build flags. # mysql_config --cflags # mysql_config --cflags -I/usr/include/mysql -fdebug-prefix-map=/build/mysql-5.7-Q0jPG6/mysql-5.7-5.7.16=. .specs -fabi-version=2 -fno-omit-frame-pointer -fno-expensive-optimizations Marking as RC, as this breaks the build for other packages. Using --include instead may help here. Peter
Bug#829647: fixed upstream
This was fixed upstream in release 3.4.2, please see https://github.com/PowerDNS/pdns/issues/2836
Bug#807285: "invoke.rc-d iptables-persistent save" does nothing
On Mon, 7 Dec 2015 02:37:08 + Mike wrote: Package: iptables-persistent Version: 1.0.3 With the split of this package to netfilter-persistent, the command "invoke.rc-d iptables-persistent save" no longer does anything. What's worse: it completes with no output or indication of error. If one happens to remember that it used to output "saved" messages, one might notice that. Otherwise, one would think it did its work. Clearly one must use "invoke.rc-d netfilter-persistent save" now. I don't recall being given any warning on upgrade of this change, and the README still gives the old instructions. I lost quite a few rules with my last reboot. I also got bitten by this just now - funny how your bug report is just hours old because this bug is quite a bit older apparently. I can confirm the same behaviour (on Raspbian in my case), the suggested command fails silently (although it does exit with 102). invoke-rc.d netfilter-persistent save does work. Cheers, Peter
Bug#804596: pdns-server: New version fails to sign axfrs
Hello, On 10 Nov 2015, at 17:25, James Cloos wrote: "PvD" == Peter van Dijk writes: So it looks like running check-all-zones changed something. PvD> That doesn’t make any sense :( check-all-zones is a readonly PvD> operation. That is what I had previously presumed but something changed. I only changed two of the zones based on the check-all-zones output and that allowed all of the zones to *start* working again. Ah, so more happened than just the running of check-all-zones. That is a bit less confusing at least. Perhaps the issue then is that the geoip backend changed its name and thus failed to upgrade with the server and the pg backend. Although my config didn't load the geo backend... geo did not change its name - geoip is a different backend. I noticed when I grabbed the old debs from the pool that the package name changed from pdns-backend-geo to pdns-backend-geoip. After Christian's first reply I manually removed the geo backend, fixed the couple of errors reported by check (a couple of duplicate CNAME records and an OPENPGPKEY records in raw syntax from when I was trying to add support back before the stroke). Ah yes, raw syntax for a type we support is a known bug, sorry about that. Kind regards, -- Peter van Dijk PowerDNS.COM BV - https://www.powerdns.com/
Bug#804596: pdns-server: New version fails to sign axfrs
Hello, On 10 Nov 2015, at 0:15, James Cloos wrote: "CH" == Christian Hofstaedtler writes: CH> Upstream suggested to run 'pdnssec check-zone' on any zone that CH> shows this behaviour, as they think that "just failing it" should be CH> covered by their testsuite. That helped. Now only one zone fails (even though only two zones had any errors, and previously all zones failed), and it gives a different error pattern: pdns[25904]: Signing thread died because of std::exception: Reading from socket in Signing Pipe loop: Connection reset by peer but I cannot tell from the log which zone failed. The AXFR which initiated just before that log succeeded. And each of them have the correct (new) SOA values on the secondaries. So it looks like running check-all-zones changed something. That doesn’t make any sense :( check-all-zones is a readonly operation. Thanks for the quick reply. Given that running check-all-zones seems to have cured things (notwithstanding that one std::exception), I think we can close this (or at least lower its severity) and I'll followup on the upstream mailing list. Given that it works now, yes, let’s move it to the upstream lists so we get a bigger set of useful eyes on it. Kind regards, -- Peter van Dijk PowerDNS.COM BV - https://www.powerdns.com/
Bug#769944: The server can't load /usr/lib/powerdns/libbindbackend.so, it's actually located at /usr/lib/x86_64-linux-gnu/pdns/libbindbackend.so
On 17 Nov 2014, at 20:32 , Debian bug at v.nix.is wrote: > Package: pdns-server > Version: 3.4.1-3 > Severity: grave > > When I upgraded from 3.3.* I started getting this in error log: > >Nov 17 19:28:30 u pdns[14671]: Loading > '/usr/lib/powerdns/libbindbackend.so' >Nov 17 19:28:30 u pdns[14671]: Unable to load module > '/usr/lib/powerdns/libbindbackend.so': /usr/lib/powerdns/libbindbackend.so: > cannot open shared object file: No such file or directory >Nov 17 19:28:30 u pdns[14671]: dnsbackend unable to load module in bind >Nov 17 19:28:31 u pdns[14500]: Our pdns instance exited with code 1 >Nov 17 19:28:31 u pdns[14500]: Respawning Your pdns.conf file (or a file included from it) may have a module-dir line. Try removing it, or if that fails, set it correctly so you do not need the symlink. Kind regards, -- Peter van Dijk Netherlabs Computer Consulting BV - http://www.netherlabs.nl/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#757242: pdns-server: PowerDNS not transfer primary-level zones
Please provide a database dump for the local zone. Please run 'pdnssec check-zone local'. Please provide select * from records where content='.' On 6 August 2014 16:09:05 CEST, Matyashov Andrey wrote: >Package: pdns-server >Version: 3.1-4.1 >Severity: normal >Tags: upstream > > >Dear Maintainer! >I use 2 pdns-servers (master and slave) with mysql-backend. >If in zone 2-level or greater (e. g.: myzone.net or subzone.zone.net), >slave server normal getting updates from master. >If zone - up-level (e. g.: local), transfer zone failed. > >Log-records in master: >Aug 6 16:21:24 ns-01 pdns[17538]: gmysql Connection successful >Aug 6 16:21:24 ns-01 pdns[17538]: AXFR of domain 'local' initiated by >10.10.2.104 >Aug 6 16:21:24 ns-01 pdns[17538]: AXFR of domain 'local' allowed: >client IP 10.10.2.104 is in allow-axfr-ips >Aug 6 16:21:24 ns-01 pdns[17538]: gmysql Connection successful >Aug 6 16:21:24 ns-01 pdns[17538]: gmysql Connection successful >Aug 6 16:21:24 ns-01 pdns[17538]: Exception: Unknown record was stored >incorrectly, need 3 fields, got 1: . >Aug 6 16:21:24 ns-01 pdns[17538]: TCP Connection Thread died because >of STL error: Unknown record was stored incorrectly, need 3 fields, got >1: . > > >Log-records in slave: >Aug 6 16:23:22 ns-02 pdns[10884]: 1 slave domain needs checking, 0 >queued for AXFR >Aug 6 16:23:22 ns-02 pdns[10884]: Received serial number updates for 1 >zones, had 0 timeouts >Aug 6 16:23:22 ns-02 pdns[10884]: Domain local is stale, master serial >2014080624, our serial 2014080611 >Aug 6 16:23:22 ns-02 pdns[10884]: Initiating transfer of 'local' from >remote '10.10.2.2' >Aug 6 16:23:22 ns-02 pdns[10884]: gmysql Connection successful >Aug 6 16:23:22 ns-02 pdns[10884]: gmysql Connection successful >Aug 6 16:23:22 ns-02 pdns[10884]: gmysql Connection successful >Aug 6 16:23:22 ns-02 pdns[10884]: AXFR started for 'local', >transaction started >Aug 6 16:23:22 ns-02 pdns[10884]: Unable to AXFR zone 'local' from >remote '10.10.2.2' (resolver): Remote nameserver closed TCP connection >Aug 6 16:23:22 ns-02 pdns[10884]: Aborting possible open transaction >for domain 'local' AXFR > > >-- System Information: >Debian Release: 7.6 > APT prefers stable-updates > APT policy: (500, 'stable-updates'), (500, 'stable') >Architecture: amd64 (x86_64) > >Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) >Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) >Shell: /bin/sh linked to /bin/dash > >Versions of packages pdns-server depends on: >ii adduser 3.113+nmu3 >ii debconf [debconf-2.0] 1.5.49 >ii libboost-program-options1.49.0 1.49.0-3.2 >ii libboost-serialization1.49.01.49.0-3.2 >ii libc6 2.13-38+deb7u3 >ii libcrypto++95.6.1-6 >ii libgcc1 1:4.7.2-5 >ii liblua5.1-0 5.1.5-4 >ii libpolarssl01.2.9-1~deb7u3 >ii libsqlite3-03.7.13-1+deb7u1 >ii libstdc++6 4.7.2-5 >ii ucf 3.0025+nmu3 >ii zlib1g 1:1.2.7.dfsg-13 > >pdns-server recommends no packages. > >Versions of packages pdns-server suggests: >ii pdns-backend-mysql [pdns-backend] 3.1-4.1 >ii pdns-recursor 3.3-3 > >-- Configuration Files: >/etc/powerdns/pdns.conf >allow-axfr-ips=10.10.2.2 >allow-recursion=127.0.0.1 10.0.0.0/8 >cache-ttl=20 >config-dir=/etc/powerdns >daemon=yes >default-soa-name=ns-02.local >disable-axfr=no >disable-tcp=no >guardian=yes >local-address=10.10.2.104 >local-port=53 >log-dns-details=yes >log-failed-updates=yes >master=no >module-dir=/usr/lib/powerdns >query-cache-ttl=20 >queue-limit=1500 >recursor=127.0.0.1:53 >setgid=pdns >setuid=pdns >slave=yes >slave-cycle-interval=30 >socket-dir=/var/run >webserver=yes >webserver-address=10.10.2.104 >webserver-password=*mypass* >webserver-port=8081 >webserver-print-arguments=yes >version-string=powerdns >include=/etc/powerdns/pdns.d -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Bug#752678: [Pkg-pdns-maintainers] Bug#752678: pdns: FTBFS on hurd-i386
Hello,
On 25 Jun 2014, at 23:06 , Christian Hofstaedtler wrote:
>> 2) pdns/nameserver.c: IPV6_RECVPKTINFO is not defined on GNU/Hurd, use
>> IPV6_RXINFO instead.
>>
>> Index: pdns-3.3.1/pdns/nameserver.cc
>> ===
>> --- pdns-3.3.1.orig/pdns/nameserver.cc
>> +++ pdns-3.3.1/pdns/nameserver.cc
>> @@ -213,7 +213,11 @@ void UDPNameserver::bindIPv6()
>> if(IsAnyAddress(locala)) {
>> int val=1;
>> setsockopt(s, IPPROTO_IP, GEN_IP_PKTINFO, &val, sizeof(val)); //
>> linux supports this, so why not - might fail on other systems
>> +#ifndef IPV6_RECVPKTINFO // IPV6_RXINFO same as IPV6_PKTINFO on GNU/Hurd
>> + setsockopt(s, IPPROTO_IPV6, IPV6_RXINFO, &val, sizeof(val));
>> +#else
>> setsockopt(s, IPPROTO_IPV6, IPV6_RECVPKTINFO, &val, sizeof(val));
>> +#endif
>> setsockopt(s, IPPROTO_IPV6, IPV6_V6ONLY, &val, sizeof(val)); //
>> if this fails, we report an error in tcpreceiver too
>> }
>> g_localaddresses.push_back(locala);
>
>
> Could you turn that into an autoconf thing? I think having it as an autoconf-
> detected and aliased thing would be preferred upstream (CC'ed
> upstream for their opinion).
We would prefer that, but we would accept something like #ifndef
IPV6_RECVPKTINFO #define IPV6_RECVPKTINFO IPV6_RXINFO #endif in a suitable
header file.
Kind regards,
--
Peter van Dijk
Netherlabs Computer Consulting BV - http://www.netherlabs.nl/
signature.asc
Description: Message signed with OpenPGP using GPGMail
Bug#726945: pdns-backend-pgsql: fails to upgrade from testing: ERROR: syntax error at or near "NOT" LINE 1: ...ABLE supermasters ALTER COLUMN ip TYPE VARCHAR(64) NOT NULL; ^
Hello Julien, On Dec 22, 2013, at 15:37 , Julien Cristau wrote: > On Sun, Oct 20, 2013 at 22:40:04 +0200, Peter van Dijk wrote: > >> I have a patch for this, will submit it to the maintainers soon, if >> it's not already fixed in their git. >> > Hi Peter, > > I can't see the patch at > http://anonscm.debian.org/gitweb/?p=pkg-pdns/pdns.git;a=summary > > Any chance you could send it to this bug? Please find it attached. This is the version from October, I have not verified it against PowerDNS 3.3.1 (but the differences should be minor, if at all present). Kind regards, -- Peter van Dijk Netherlabs Computer Consulting BV - http://www.netherlabs.nl/ pdns-backend-pgsql-726945.patch Description: Binary data signature.asc Description: Message signed with OpenPGP using GPGMail
Bug#726863: pdns: FTBFS on s390x
Hello, On Oct 22, 2013, at 23:31 , Peter van Dijk wrote: > We now have an upstream patch for this at > https://github.com/PowerDNS/pdns/commit/0c3742099d6f94a8928ac5e6eca11f8d3f4cb3ad > > Maintainers, please pick this patch up for 3.3-2 With that patch, one failing test remains. https://github.com/PowerDNS/pdns/commit/916a0fda31405290cedac058aab7f5d9f9c26a7b fixes it. Please pick this patch as well. Kind regards, -- Peter van Dijk Netherlabs Computer Consulting BV - http://www.netherlabs.nl/ signature.asc Description: Message signed with OpenPGP using GPGMail
Bug#726863: pdns: FTBFS on s390x
We now have an upstream patch for this at https://github.com/PowerDNS/pdns/commit/0c3742099d6f94a8928ac5e6eca11f8d3f4cb3ad Maintainers, please pick this patch up for 3.3-2 Kind regards, -- Peter van Dijk Netherlabs Computer Consulting BV - http://www.netherlabs.nl/ signature.asc Description: Message signed with OpenPGP using GPGMail
Bug#726945: pdns-backend-pgsql: fails to upgrade from testing: ERROR: syntax error at or near "NOT" LINE 1: ...ABLE supermasters ALTER COLUMN ip TYPE VARCHAR(64) NOT NULL; ^
I have a patch for this, will submit it to the maintainers soon, if it's not already fixed in their git. On Oct 20, 2013, at 22:36 , Andreas Beckmann wrote: > Package: pdns-backend-pgsql > Version: 3.3-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package fails to upgrade from > 'jessie'. > It installed fine in 'jessie', then the upgrade to 'sid' fails. > >> From the attached log (scroll to the bottom...): > > Setting up pdns-server (3.3-1) ... > Installing new version of config file /etc/init.d/pdns ... > Installing new version of config file /etc/insserv.d/pdns-server ... > Replacing config file /etc/powerdns/pdns.conf with new version > invoke-rc.d: policy-rc.d denied execution of start. > Setting up pdns-backend-pgsql (3.3-1) ... > dbconfig-common: writing config to > /etc/dbconfig-common/pdns-backend-pgsql.conf > creating database backup in > /var/cache/dbconfig-common/backups/pdns-backend-pgsql_3.1-4.pgsql. > applying upgrade sql for 3.1-4 -> 3.3-1. > error encountered processing > /usr/share/dbconfig-common/data/pdns-backend-pgsql/upgrade/pgsql/3.3-1: > ERROR: syntax error at or near "NOT" LINE 1: ...ABLE supermasters ALTER > COLUMN ip TYPE VARCHAR(64) NOT NULL; ^ > dbconfig-common: pdns-backend-pgsql configure: aborted. > dbconfig-common: flushing administrative password > dpkg: error processing pdns-backend-pgsql (--configure): > subprocess installed post-installation script returned error exit status 1 > Processing triggers for libc-bin ... > Errors were encountered while processing: > pdns-backend-pgsql > > > cheers, > > Andreas > Kind regards, -- Peter van Dijk Netherlabs Computer Consulting BV - http://www.netherlabs.nl/ signature.asc Description: Message signed with OpenPGP using GPGMail
Bug#707761: pdns-backend-pgsql: IP fields too short for master/slave operation over IPv6
Hello James, On May 30, 2013, at 17:00 , James Cloos wrote: > The ip column should not be varchar or text. > > It should be inet. > > The proper fix is: > > alter table supermasters alter COLUMN ip type inet using ip::inet; > > and change the sql which creates the table during install to use inet > for that column. > > That column is only supposed to hold ipv4 or ipv6 addresses, which is > exactly what the inet type is for. > > As an added bonus, inet stores the address as an integer, so it should > take up less space than a text/varchar/char column. We are happy to consider this change upstream - please file your request at https://github.com/PowerDNS/pdns/issues Kind regards, -- Peter van Dijk Netherlabs Computer Consulting BV - http://www.netherlabs.nl/ signature.asc Description: Message signed with OpenPGP using GPGMail
Bug#710360: First autoremovals happen in about 8 days
Hi, On Oct 6, 2013, at 22:47 , James Cloos wrote: > This bug report is about to get pdns kicked out of Jessie. > > Please do something about that. pdns no longer appears to be listed at http://udd.debian.org/cgi-bin/autoremovals.cgi Kind regards, -- Peter van Dijk Netherlabs Computer Consulting BV - http://www.netherlabs.nl/ signature.asc Description: Message signed with OpenPGP using GPGMail
Bug#376036:
forwarded #376036 https://github.com/PowerDNS/pdns/issues/467 thanks signature.asc Description: Message signed with OpenPGP using GPGMail
Bug#716859: point out another bug indicated in first message log
Hello, the output in Message #5 also shows another problem with this package (still present in master as of this moment): Creating config file /etc/powerdns/pdns.d/pdns.local.conf with new version followed by Not replacing deleted config file /etc/powerdns/pdns.d/pdns.local.conf makes no sense. The same happens for simplebind, which indeed ends up not being present after fresh install on a clean system. Kind regards, -- Peter van Dijk Netherlabs Computer Consulting BV - http://www.netherlabs.nl/ signature.asc Description: Message signed with OpenPGP using GPGMail
Bug#716859: simple patch for this issue
Just a workaround but it should help. Kind regards, -- Peter van Dijk Netherlabs Computer Consulting BV - http://www.netherlabs.nl/ 0001-only-chmod-pdns.local.conf-if-it-exists.patch Description: Binary data signature.asc Description: Message signed with OpenPGP using GPGMail
Bug#656292: fixed upstream
Upstream has merged https://github.com/PowerDNS/pdns/pull/812 which offers include-dir support for both pdns_server and pdnssec. Kind regards, -- Peter van Dijk Netherlabs Computer Consulting BV - http://www.netherlabs.nl/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#374779: fixed upstream
Upstream ticket #468 has been closed: https://github.com/PowerDNS/pdns/issues/468 Kind regards, -- Peter van Dijk Netherlabs Computer Consulting BV - http://www.netherlabs.nl/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#701798: pdns-server package depends on libsqlite3-0 for no practical reason
Hi, On Mar 3, 2013, at 17:44 , Marc Haber wrote: > On Wed, Feb 27, 2013 at 11:01:51AM +0100, Peter van Dijk wrote: >> The bindbackend, which is part of pdns-server 3.1, uses sqlite3 for >> key storage. > > So a system running without libsqlite3-0 with bind backend won't be > able to do DNSSEC? Would it fail gracefully or fatally in that > situation? I'm pretty sure the answer is 'fatally'. Kind regards, -- Peter van Dijk Netherlabs Computer Consulting BV - http://www.netherlabs.nl/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#701798: pdns-server package depends on libsqlite3-0 for no practical reason
The bindbackend, which is part of pdns-server 3.1, uses sqlite3 for key storage. On Feb 27, 2013, at 10:16 , Nikolay Shaplov wrote: > Package: pdns-server > Version: 3.1-4 > Severity: normal > > pnds-server package depends on libsqlite3-0 for no practical reason. > > If I manually remove gsqlite3 backend from building and packaging, and > uninstall libsqlite3-dev > and try to build pdns package manually, pdns-sever and all other backends > builds successfully and > all packages creates properly. And in this case pdsn-server does not depends > on libsqlite3-0. > So it is not source code, it might be some building options or something... > > It it not a very good idea to bring libsqlite3-0 on servers where it is not > really used... > > > -- System Information: > Debian Release: 6.0.7 > APT prefers stable-updates > APT policy: (500, 'stable-updates'), (500, 'stable') > Architecture: i386 (i686) > > Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages pdns-server depends on: > ii adduser 3.112+nmu2 add and remove users and groups > ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management > sy > ii libboost-program-option 1.42.0-4 program options library for C++ > ii libboost-serialization1 1.42.0-4 serialization library for C++ > ii libc6 2.11.3-4 Embedded GNU C Library: Shared > lib > ii libcrypto++85.6.0-6 General purpose cryptographic > libr > ii libgcc1 1:4.4.5-8GCC support library > ii liblua5.1-0 5.1.4-5 Simple, extensible, embeddable > pro > ii libsqlite3-03.7.3-1 SQLite 3 shared library > ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3 > ii ucf 3.0025+nmu1 Update Configuration File: > preserv > ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime > > pdns-server recommends no packages. > > Versions of packages pdns-server suggests: > ii pdns-backend-pgsql [pdns-back 3.1-4 generic PostgreSQL backend for > Pow > pn pdns-recursor (no description available) > > -- Configuration Files: > /etc/powerdns/pdns.d/pdns.simplebind [Errno 2] No such file or directory: > u'/etc/powerdns/pdns.d/pdns.simplebind' > > -- debconf information: > * pdns-server/localaddress: 0.0.0.0 > * pdns-server/allowrecursion: 127.0.0.1 > * pdns-server/autostart: true > Kind regards, -- Peter van Dijk Netherlabs Computer Consulting BV - http://www.netherlabs.nl/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#691717: pdns-server: zone2sql does not accept documented --bare switch
Hello, On Oct 29, 2012, at 2:59 , Donald Gordon wrote: > The manpage for zone2sql documents the existence of a --bare switch: > > --bare Output in a bare format, suitable for further parsing. [...] > > However the zone2sql executable shipped as part of the pdns-server package > does not recognise this switch: > > donald@vm5:~$ zone2sql --bbare --named-conf=/etc/bind/named.conf > > Fatal error: Trying to set unexisting parameter 'bbare' > > When passed one of the other output format options, e.g. --gmysql, the same > command returns a pile of insert statements, as expected. > > A fix (ideally to make --bare work) would be greatly appreciated. This issue is already being tracked as upstream bug #509, at http://wiki.powerdns.com/trac/ticket/509 The proposal there is to add a zone2json tool instead of putting --bare back. If this would not suffice for you, please comment on the upstream ticket. Thanks! Kind regards, -- Peter van Dijk Netherlabs Computer Consulting BV - http://www.netherlabs.nl/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#689540: kgb-client: add test command
Package: kgb-client Version: 1.05-1+squeeze1 Severity: wishlist While setting up kgb-client, it would be useful to have a 'test' command (kgb-client --conf kgb.conf test) that sends some fake commit data to the bot, to test bot interaction independently of SVN/git hook operation. -- System Information: Debian Release: 6.0.6 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-openvz-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages kgb-client depends on: ii libclass-accessor-perl 0.34-1Perl module that automatically gen ii libdigest-sha1-perl2.13-1NIST SHA-1 message digest algorith ii libsoap-lite-perl 0.712-2 Perl implementation of a SOAP clie ii libsvn-perl1.6.12dfsg-6 Perl bindings for Subversion ii libyaml-perl 0.71-1YAML Ain't Markup Language ii perl 5.10.1-17squeeze3 Larry Wall's Practical Extraction Versions of packages kgb-client recommends: ii kgb-client-git 1.05-1+squeeze1 client for KGB (IRC collaboration Versions of packages kgb-client suggests: pn kgb-bot(no description available) -- debconf information: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#675410: fixed upstream
Upstream revision 2720 fixes storage of Botan keys, making sure that Polar can read them. Kind regards, -- Peter van Dijk Netherlabs Computer Consulting BV - http://www.netherlabs.nl/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#656292: pdnssec doesn't recognize "include" directive in pdns.conf
Hello Nikolav, On Aug 29, 2012, at 20:25 , Nikolay Shaplov wrote: >> forwared #656292 http://wiki.powerdns.com/trac/ticket/493 >> thanks >> >> I have forwarded this upstream. > Bad Idea. > > Include -- is a debian specific config option, it is added by > debian/patches/addconfigdir patch. > > So upstream has nothing to do with it. While upstream has nothing to do with the patch, include has in general been requested upstream quite a lot. We are treating the forwarded ticket as a feature request to implement include sanely (the Debian patch is not acceptable for us) in both pdns_server and pdnssec (and, I suppose, also pdns_recursor). See also the second comment at http://wiki.powerdns.com/trac/ticket/493 Thank you for your concern! Kind regards, -- Peter van Dijk Netherlabs Computer Consulting BV - http://www.netherlabs.nl/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#681248: pdns-server: Fatal error: Trying to set unexisting parameter 'gmysql-host'
Hello, On Jul 11, 2012, at 19:13 , Juha Heinanen wrote: > After I did yesterday 'apt-get dist-upgrade' of my debian wheezy host, pdns > server started to repeatedly write to syslog these messages: > > Jul 11 07:28:15 siika pdns[3366]: Our pdns instance exited with code 1 > Jul 11 07:28:15 siika pdns[3366]: Respawning > Jul 11 07:28:16 siika pdns[4916]: Guardian is launching an instance > Jul 11 07:28:16 siika pdns[4916]: Reading random entropy from '/dev/urandom' > Jul 11 07:28:16 siika pdns[4916]: This is a guarded instance of pdns > Jul 11 07:28:16 siika pdns[4916]: Fatal error: Trying to set unexisting > parameter 'gmysql-host' > > Before this dist-upgrade pdns had worked fine in my wheezy host. This happens when you have multiple launch= lines (possibly spread over different config files). Perhaps the dist-upgrade added a bind config file in /etc/powerdns/pdns.d? Kind regards, -- Peter van Dijk Netherlabs Computer Consulting BV - http://www.netherlabs.nl/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#423822: fixed in upstream
Marked 'fixed' in upstream, presumably since 3.0. http://wiki.powerdns.com/trac/ticket/465#comment:2 Kind regards, -- Peter van Dijk Netherlabs Computer Consulting BV - http://www.netherlabs.nl/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#666957: pdns-server does not work with more than one backend anymore
You need to say launch=gmysql,ldap -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. Dominik George wrote: Package: pdns-server Version: 3.0-1.1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The 3.0-1.1 version of pdns-server does not work anymore when more than one backend is enabled. I used to run both the LDAP and the gmysql backends, with LDAP serving for master zones and MySQL holding slave zones from other DNS services (strange setup, I agree, but necessary). Before upgrading to the version from testing, this worked great, but now the first backend module being loaded gets preference and the other isn't even loaded. Relevant pasrts of my config: launch=gmysql gmysql-host=localhost gmysql-port= gmysql-dbname=pdns gmysql-user=pdns gmysql-password= gmysql-dnssec=yes launch=ldap ldap-host=ldap://x.x.x.x:389/ ldap-basedn=ou=DNS,ou=Hosting,* ldap-method=tree As I mentioned, this used to work great and now the launch=ldap line is ignored, resulting in this log output: Apr 2 22:55:51 hosting01 pdns[29893]: Guardian is launching an instance Apr 2 22:55:51 hosting01 pdns[29893]: Reading random entropy from '/dev/urandom' Apr 2 22:55:51 hosting01 pdns[29893]: This is module gmysqlbackend.so reporting Apr 2 22:55:51 hosting01 pdns[29893]: This is a guarded instance of pdns Apr 2 22:55:51 hosting01 pdns[29893]: Fatal error: Trying to set unexisting parameter 'ldap-host' Can we get old functionality back? Or is this intended behaviour ;)? - -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQHOBAEBAgA4BQJPehcdMRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n cGctcG9saWN5LnR4dC5hc2MACgkQ2w6kvOIQdBLyFAv/YPgZZEpX3EJsceCHaNgI 73lZuoDFiA2BVYWCd37HHPojOA1ou/4VJbP/9MKXQlIuqXJpnvGlblTuL6KfiGs7 xBmhmDFC1Cgr8NqDlavit9XUmojnalHMOfnVuYCNYmjSS85w+zTbobZYcOBAQ2qA tVnvfPjN8+4+jJh4ZQ0SeMJzlchQCO4edQPpsyh88l1sBsOcyHxJM8lyiT655Wtx biGEPXdIc6LwzETwsDgscciIvqUp2YUYbbjCI3kWTLX4GSYSBN4h4xkFiNAyJ9yg y9XimC91pqyDff+J95HBteZyc9yRXRYm14m3JHUdy94ffxW5Wg8hldQQDYbYMqoD JHyW7a6HwSbt+dXNmE0q6WmcE4qFsIGsMnW4xvhrdIzgyWKd9pFBPO5mql0uG8aA djEprI3ehRhXTODs8ceGJrW0L3G/cklwalP1OBlMZVwJJzdyiRJyr+zw1DX+QKsY 3JJSwIhyLglYngrWkk509UfW0/WZx/Zgx5aGisS/neCP =8mhu -END PGP SIGNATURE-
Bug#662935: pdns-backend-mysql: MySQL upgrade from 2.9.x if database uses multibyte encoding
The upstream fix (SVN revision 2400) is to reduce the column size for 'algorithm' to 50. Kind regards, Peter van Dijk On Mar 7, 2012, at 12:48 , Michael Wikberg wrote: > Package: pdns-backend-mysql > Version: 3.0-1.1 > Severity: normal > Tags: sid wheezy patch > > MySQL database uprgrade script fails with "ERROR 1071 (42000) at line 30: > Specified key was too long; max key length is 1000 bytes" while running > "create unique index namealgoindex on tsigkeys(name, algorithm);" if the > database uses unicode collation (server-wide default of utf8_general_ci). > The reason being two varchar(255) columns being used as the key (apparently > resulting in 2*2*255=1020 bytes for the key. > The problem can be fixed by specifying a single byte encoding, like: > > create table tsigkeys ( > id INT auto_increment, > name VARCHAR(255), > algorithm VARCHAR(255), > secret VARCHAR(255), > primary key(id) > ) COLLATE = ascii_bin; > > > I'm not sure what the ideal encoding would be though, or if the size of the > columns could/should be changed. > > -- > Micu > > > -- System Information: > Debian Release: 6.0.4 > APT prefers stable > APT policy: (990, 'stable'), (600, 'stable-updates'), (500, 'oldstable'), > (100, 'testing'), (2, 'unstable') > Architecture: i386 (i686) > > Kernel: Linux 2.6.32.16domU-32 (SMP w/1 CPU core) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/bash > > Versions of packages pdns-backend-mysql depends on: > ii dbconfig-common 1.8.46+squeeze.0 common framework for packaging > dat > ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management > sy > ii libc6 2.11.3-2 Embedded GNU C Library: Shared > lib > ii libgcc1 1:4.4.5-8GCC support library > ii libmysqlclient165.1.49-3 MySQL database client library > ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3 > ii pdns-server 3.0-1.1 extremely powerful and versatile > n > ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime > > Versions of packages pdns-backend-mysql recommends: > ii mysql-client-5.1 [mysql-clien 5.1.49-3 MySQL database client binaries > > Versions of packages pdns-backend-mysql suggests: > ii mysql-server 5.1.49-3 MySQL database server > (metapackage > ii mysql-server-5.1 [mysql-serve 5.1.49-3 MySQL database server binaries > and > > -- debconf information excluded > > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#592898: not a bug
User needs to use query-local-address setting for this. Kind regards, Peter van Dijk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#656788: pdns: bind backend patch to handle smallcaps RRs
This has been applied in upstream SVN, it will be in upstream's 3.1.
Kind regards,
Peter van Dijk
upstream PowerDNS maintainer
On Jan 21, 2012, at 18:53 , grin wrote:
> Package: pdns-server
> Version: 3.0-1.1
> Severity: normal
> File: pdns
>
>
> http://wiki.powerdns.com/trac/ticket/390
>
> the patch works, until upstream includes it would be nice to patch it.
>
>
> --- pdns-3.0.orig/pdns/dnsparser.hh
> +++ pdns-3.0/pdns/dnsparser.hh
> @@ -200,7 +200,7 @@ public:
>
> static uint16_t TypeToNumber(const string& name)
> {
> -n2typemap_t::const_iterator iter = getN2Typemap().find(name);
> +n2typemap_t::const_iterator iter = getN2Typemap().find(toUpper(name));
> if(iter != getN2Typemap().end())
> return iter->second.second;
>
>
>
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#649724: pdns-recursor: did not resolve www.spoluzaci.cz
I believe this bug has been fixed upstream. I am unable to reproduce this issue with newer versions. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#500572: not a bug
Hello Martin, On Nov 21, 2011, at 11:19 , martin f krafft wrote: > also sprach Peter van Dijk [2011.11.19.0906 > +0100]: >> If you could demonstrate that this difference exists, I would be >> happy to look deeper into the issue. > > I was about to get back into this, but I noticed that Mattijs has > since added a patch from upstream to fix this issue. Does this mean > you found the problem? No - there is no upstream patch and I doubt there is a downstream patch. Matthijs, can you clarify? Kind regards, Peter van Dijk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#500572: not a bug
Hello Martin, On Nov 18, 2011, at 11:34 , martin f krafft wrote: > also sprach Peter van Dijk [2011.11.18.0951 > +0100]: >> the DNS packet format is binary. There is no notion of inserting >> or not inserting a zero. What you are seeing is how dig decides to >> represent an address. Other DNS-servers have the same "issue". > > I have never seen this with any other DNS-server. As soon as > I switched to nsd3, the problem was gone. If you could demonstrate that this difference exists, I would be happy to look deeper into the issue. Kind regards, Peter van Dijk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#500572: not a bug
Hello, the DNS packet format is binary. There is no notion of inserting or not inserting a zero. What you are seeing is how dig decides to represent an address. Other DNS-servers have the same "issue". I recommend closing this bug. Kind regards, Peter van Dijk (upstream maintainer) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#583161: not a bug
Hello, this is not a bug. Queries to check for actual DNS wildcard records should, correctly, be of the form where name='*.srv.hostarium.com' Note the documentation line "A wildcard query is an internal concept - it has no relation to *.domain-type lookups.". Debian administrator, I suggest closing this bug. Kind regards, Peter van Dijk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#533023: fix
Hello,
reproduced upstream. Here is a version of the patch that actually applies:
diff --git a/pdns/resolver.cc b/pdns/resolver.cc
index d3fc8ae..4263465 100644
--- a/pdns/resolver.cc
+++ b/pdns/resolver.cc
@@ -185,6 +185,8 @@ static int parseResult(MOADNSParser& mdp, const
std::string& origQname, uint16_t
rr.priority = atoi(parts[0].c_str());
if(parts.size() > 1)
rr.content=parts[1];
+ else
+rr.content=".";
} else if(rr.qtype.getCode() == QType::SRV) {
rr.priority = atoi(rr.content.c_str());
vector > fields;
This patch will go into upstream SVN shortly.
Kind regards,
Peter van Dijk
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#590285: fixed upstream
I believe • sqlite2 and sqlite3 backends used MySQL-style escaping, leading to SQL errors in some cases. Discovered by Sten Spans. Fixed in commit 1342. from the upstream 3.0-RC3 change log covers this issue. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#499396: fixed upstream in 2.9.22
Can reproduce upstream with 2.9.21.x, cannot reproduce with 2.9.22 and current SVN. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#510861: Bug closed at powerdns tracker
Hello, just letting you know that http://wiki.powerdns.com/trac/ticket/286 was closed with this comment: the s_timeout var is not actually used currently. Rejecting patch, please re-file as full feature request if so desired. Kind regards, Peter van Dijk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#573563: please fix
This bug just cost me four hours of pointless debugging. Please fix it :) Thank you. Kind regards, Peter van Dijk OpenPanel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#287152: arch repo with fix
I have Arch'd my patch for this problem. My archive [EMAIL PROTECTED] is at http://apache.dataloss.nl/~peter/arch/[EMAIL PROTECTED]/ Please cherry-pick [EMAIL PROTECTED]/dpkg--devel--1.13--patch-1 for this fix. Thank you. Cheers, Peter -- [EMAIL PROTECTED]| ~ tonight tonight, what is this potion http://blog.dataloss.nl/ | ~ that makes a fool of me UnderNet/#clue | Wayfinder, fr-025 soundtrack -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
