search for: xfrd

Hi, I had a problem trying to migrate domains, in trying to locate it I noticed that saving domains doesn''t work either, which I believe explains why the receiving xfrd doesn''t actually receive anything. So here it goes... xenone:/tmp# xm list Name Id Mem(MB) CPU State Time(s) Console Domain-0 0 123 0 r---- 900.6 sky 9 128 1 -b--- 32.8 9609 xenone:/tmp# xm save 9 test Error: Error:...

...saved in memory. 2) When NSD service is 'reloaded' for example by running 'systemctl reload nsd' does NSD check the serial number (SOA) for each record and tries to initiate a zone transfer? After performing a service reload the following entries are logged. nsd[1704236]: error: xfrd: zone testnsdexp01.tk received error code SERVER NOT AUTHORITATIVE FOR ZONE from xx.xx.xx.xx nsd[1704236]: error: xfrd: zone testnsdexp01.tk, from xx.xx.xx.xx: no tsig in first packet of reply nsd[1704236]: info: xfrd: zone testnsdexp01.tk bad transfer 0 from xx.xx.xx.xx The zone records for testn...

Hi all, I''ve been trying to figure out a way to trigger the balloon driver for a domain from within xfrd (specifically, libxc). So far, it doesn''t look like there''s a straightforward way. Is this even possible given the current structure of the system? Thanks, -A. -- Aaron Marks ajmarks@cis.upenn.edu Distributed Systems Lab University of Pennsylvania www.cis.upenn.edu/~ajmarks __...

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-2 Severity: important the xen-utils packages lack xfrd, which is required for live domain migrations using xm migrate. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-1-686 Locale: LA...

...RBD, only one host can write on a drbd device at the same time). This script sets the current host as master (bind) or secondary (unbind) in a DRBD "Netword-RAID" Bringing up a domain works fine. But when I try to migrate it ( live with -l flag as well as non-live) I get an error from xfrd. The xfrd.log says: ==> xfrd.log <== 2508 [INF] XFRD> Accepted connection from 127.0.0.1:1327 on 2 2790 [INF] XFRD> Xfr service for 127.0.0.1:1327 [DEBUG] Conn_init> flags=1 [DEBUG] Conn_init> write stream... [DEBUG] stream_init>mode=w flags=1 compress=0 [DEBUG] stream_init&...

...event, and not at any of the other > known masters therefore I expect that upon receiving NOTIFY from 172.16.100.114, my slave server will send AXFR to it. But this doesn't happen, I see the following in the logs: [1342626791] nsd[12538]: info: Notify received and accepted, forward to xfrd [1342626791] nsd[7729]: info: Handle incoming notify for zone black [1342626791] nsd[7729]: error: xfrd: connect 172.16.100.199 failed: Host is down [1342626791] nsd[7729]: error: xfrd: connect 172.16.100.199 failed: Host is down [1342626791] nsd[7729]: error: xfrd: connect 172.16.100.199 failed:...

Hi, I tried to issue: xm save VMID FILE, and got the following error: Error: Error: [Failure instance: Traceback: twisted.internet.error.ConnectionRefusedError, Connection was refused by other side: 111: Connection refused. xm create works fine, xend is running on domain 0, I can log in the VM through xm console VMID and ssh without problems. I can also stop and restart the domain.

...ypted, unauthenticated UDP packets? next note: I used an IPv6 network for my zone transfer tests and have the impression, the outgoing-interface statement at the secondary is not working if AXFR-over-tls is used. next note: while trying to get AXFR-over-tls working, I saw errors like "error: xfrd tls: TLS verify failed - (62) depth: 0 error: hostname mismatch" It would be helpful to see there "... hostname mismatch: expected 'foo', got 'bar'" funny side note: after "error: xfrd tls: TLS verify failed - (62) depth: 0 error: hostname mismatch" I also...

Hello friends, I''ve got problems starting xfrd to migrate domains. I installed xen-2.0.6 a couple months ago and I could migrate domains. But now, I''ve installed xen3.0-dev and when I run xfrd, I get that message in /var/log/xfrd.log: bind: Address already in use Then I do a "ps -ef | grep xfrd", and no xfrd process is run...

Hi, I am trying to migrate a domain (testDomain) from node1 to node2. Here is some information about the problem: node1#: xm migrate testDomain node2 After the command is executed, there is some communication between the node1 and node2 Xen hosts. xfrd daemon (which is forked by xend) is primarily responsible for vm migration and there is error in its log (/var/log/xfrd.log) The exact error is (on node2): Unrecognised state format -- no signature found (The logs at node1 show that the state of the domain was sent but error was received) On n...

Hi Andreas, The suggestions I captured in GitHub issues. Thanks for sharing. Regarding whether notifies are still plain UDP. Yes, the config parser doesn't accept additional arguments to "notify" and judging by the xfrd code anything to do with notify is using UDP, so no TLS yet. I've added a GitHub issue for this too. Thanks for the suggestions. They make for nice additions/improvements. I'll try to get to them for the next release (>4.10.1). Best regards, Jeroen On Thu, 2024-07-25 at 00:00 +0200,...

...-disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu --runstatedir=/run --disable-maintainer-mode --disable-dependency-tracking --with-configdir=/etc/nsd --with-nsd_conf_file=/etc/nsd/nsd.conf --with-pidfile=/run/nsd/nsd.pid --with-dbfile=/var/lib/nsd/nsd.db --with-zonesdir=/etc/nsd --with-xfrdfile=/var/lib/nsd/xfrd.state --disable-largefile --disable-recvmmsg --enable-root-server --enable-mmap --enable-ratelimit --enable-zone-stats --enable-systemd --enable-checking --enable-dnstap --disable-radix-tree --enable-packed Event loop: libevent 2.1.12-stable (uses epoll) Linked with OpenSSL 3....

...ready in use (or similar), I'm guessing the address is not configured? Best regards, Jeroen On Fri, 2023-04-21 at 18:03 +0200, HAKIZIMANA Jean Claude via nsd-users wrote: > Dear nsd Users, > kindly can you help me?to trace the cause of this error in nsd > "?nsd[25372]: warning: xfrd: could not bind source address:port to > socket: Cannot assign requested address". > I use?NSD version 4.0.1 > > Thank?you, > _______________________________________________ > nsd-users mailing list > nsd-users at lists.nlnetlabs.nl > https://lists.nlnetlabs.nl/mailman...

Hi, NSD 4.10.1rc2 pre-release is available: https://nlnetlabs.nl/downloads/nsd/nsd-4.10.1rc2.tar.gz sha256 ce2e82bc673aeff3a71aeb422fa38fb8db0a591edb76c13b0e4dde83ec8253e9 pgp https://nlnetlabs.nl/downloads/nsd/nsd-4.10.1rc2.tar.gz.asc Version 4.10.1 consists primarily of bug fixes. @bilias implemented mutual TLS authentication for zone transfers. Please consult the nsd.conf manual for details

I rebooted xenU from console (dom2) and exited (ctr-]). xm list does not report 2 anymore yet I can log into 2 via console and it is running just fine. Is this a bug? I''ll pull/rebuild and see what happens.. (this is xen-2.0, cset 1.1321.1.1, rh7.3 dom0/dom1) ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on

Dear nsd Users, kindly can you help me to trace the cause of this error in nsd " nsd[25372]: warning: xfrd: could not bind source address:port to socket: Cannot assign requested address". I use NSD version 4.0.1 Thank you, -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20230421/6a7c7340/attachment.htm&gt...

...(blkif:203) Connecting blkif to event channel <BlkifBackendInterface 14 0> ports=16:4 [2005-12-06 15:56:02 xend] DEBUG (XendDomain:244) XendDomain>reap> domain died name=debian1 id=14 [2005-12-06 15:56:02 xend] INFO (XendDomain:568) Destroying domain: name=debian1 </snip> xfrd.log on both dom0s says migration was successful OR B) domU is in paused-state on the target machine after migration, xend.log and xfrd.log seem to be ok on both dom0s domU _cannot_ be unpaused nor directly accessed using xm console xm vbd-destroy is working the only thing that can be d...

Hi Peter, NSD processes updates in batches. xfrd receives the [AI]XFR and schedules a reload for the main process, which in turn forks new serve children. The served-serial is updated after main reports success, the commit-serial (update written to disk) is updated before the reload (to explain the serials). The difference in timestamp can be ex...

...verbosity: 2 chroot: "/usr/local/etc/nsd" zonesdir: "/usr/local/etc/nsd" zonelistfile: "zone.list" database: "var/db/nsd/nsd.db" logfile: "/var/log/nsd.log" pidfile: "var/run/nsd.pid" xfrdfile: "var/db/nsd/xfrd.state" xfrdir: "var/db/nsd/" hide-version: yes key: name: "tsig.upu.sha256.plain" algorithm: hmac-sha256 secret: "xxx" key: name: "tsig.upu.sha256.signed" algorithm: hma...

...eroen, I just realised that the version I use is very old -- 4.1. So first what I should do -- updating it and only then come here , asking for clarification. ??, 27 ????. 2024??. ? 14:19, Jeroen Koekkoek <jeroen at nlnetlabs.nl>: > Hi Peter, > > NSD processes updates in batches. xfrd receives the [AI]XFR and > schedules a reload for the main process, which in turn forks new serve > children. The served-serial is updated after main reports success, the > commit-serial (update written to disk) is updated before the reload (to > explain the serials). > > The diff...