Hello, It took me some time, but I got new information here: Dec 07 04:02:01 nexus systemd[1]: Assertion 'path_is_absolute(p)' failed at src/basic/chase.c:648, function chase(). Aborting. Dec 07 04:02:01 nexus systemd[1]: Caught <ABRT>, from our own process. Dec 07 04:03:34 nexus systemd[1]: Caught <ABRT>, dumped core as pid 23619. Dec 07 04:03:34 nexus systemd[1]: Freezing execution. Dec 07 04:05:01 nexus systemd-journald[345]: Failed to send WATCHDOG=1 notification message: Connection refused Dec 07 04:06:32 nexus systemd-journald[345]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected Dec 07 04:08:01 nexus systemd-journald[345]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
This is right after borgbackup starts. I use a bind-mount of my root filesystem to perform the backup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2120756 Title: DNS problems with borgbackup after systemd update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2120756/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
