It doesn't say much unfortunately, just two lines .... Aug 13 11:41:47 knotd[12591]: info: control, received command 'zone-backup' Aug 13 11:41:47 knotd[12591]: error: backup init failed (operation not permitted) ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, August 13th, 2021 at 11:46 AM, libor.peltan <libor.peltan(a)nic.cz> wrote: > Hi Laura, > > may you check the Knot log, please? > > Libor > > Dne 13. 08. 21 v 12:44 Laura Smith napsal(a): > > > Any ideas what might be causing the following error ? > > > > knotc (Knot DNS), version 3.1.0 > > > > $ sudo /usr/sbin/knotc zone-backup -- +backupdir /home/foo/test > > > > error: (operation not permitted) > > > > The destination directory exits. It doesn't matter if I run the command as root or knot user, the error is the same.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, August 13th, 2021 at 12:37 PM, David Vasek <david.vasek(a)nic.cz> wrote: Thanks David, that worked. As an aside, I have noticed that the CLI exits 0 with "OK" even though the backup is still running (and so I have found problems calling tar immediately because "file being changed")

That's because in normal (that is non-blocking) mode knotc just schedules operations in the server and reports whether the scheduling was successful or not. You can start putting other operations in the queue just after the command prompt returns. On the other hand, if you want to wait until the operation finishes and immediately see a brief result of it (or get an exit status reflecting the actual operation), you must use the blocking mode (knotc -b zone-backup ...). See the last paragraphs in the Note section here: https://www.knot-dns.cz/docs/3.1/html/man_knotc.html Regards, David On 2021-08-13 17:49, Laura Smith wrote: > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > > On Friday, August 13th, 2021 at 12:37 PM, David Vasek > > david.vasek(a)nic.cz wrote: > > > Hi Laura, > > > > the ownership of the backup directory, its permissions and the user > > > > (and > > > > group) under which knotd is running are important here. > > > > Regards, > > > > David > > Thanks David, that worked. > > As an aside, I have noticed that the CLI exits 0 with "OK" even though > > the backup is still running (and so I have found problems calling tar > > immediately because "file being changed")

On Fri, 13 Aug 2021 10:52:55 +0000 Laura Smith n5d9xq3ti233xiyif2vp(a)protonmail.ch wrote: knotd writes the backups. So make sure knot user can write the files. I used /var/spool/knot/* directory structue for backups in our systems.