One more log.
I also test different upstream DNS server (hetzner.de; Google DNS) but
I'm not sure what is wrong here.
** Attachment added: "systemd-resolved.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981431/+attachment/5604817/+files/systemd-resolved.txt
--
You received th
Debug log of systemd-networkd
Shell script to reproduce it:
curl
https://raw.githubusercontent.com/opendns/public-domain-lists/master/opendns-random-domains.txt
-O
curl
https://raw.githubusercontent.com/opendns/public-domain-lists/master/opendns-top-domains.txt
-L >> opendns-random-domains.tx
** Attachment added: "systemd-resolved.log.gz"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981431/+attachment/5604656/+files/systemd-resolved.log.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ub
Thanks for your answer.
In mean time, I setup 2 additional lxd containers, one running jammy,
one running kinetic and I'm hit the error again on kinetic by running
dig +dnssec on random DNS names in a loop
I follow your instructions, but I used
`Environment=SYSTEMD_LOG_LEVEL=debug` to gain log me
I'm able to assist here, e.g. by enable debugging logs. I need some
instructions what I should setup and have to provide here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/
Public bug reported:
Hi,
I'm running Ubuntu 22.04 using systemd 249.11-0ubuntu3.4.
2 days ago, I enabled DNSSEC=true through:
# grep DNSSEC /etc/systemd/resolved.conf.d/dnssec.conf
DNSSEC=yes
After running some hours, systemd-resolved stop working. Log lines like
incompatible-server starts to
There is a upstream issue: https://github.com/sudo-
project/sudo/issues/42
A fixed versions is released, maybe it can be backported to ubuntu.
** Bug watch added: github.com/sudo-project/sudo/issues #42
https://github.com/sudo-project/sudo/issues/42
--
You received this bug notification beca
Public bug reported:
On LXD containers, the fstrim.service will errored permanently.
/sbin/fstrim -av
fstrim: /: FITRIM ioctl failed: Operation not permitted
The unit file should contain
ConditionVirtualization=!container
to prevent errors inside containers
** Affects: util-linux (Ubuntu)
8 matches
Mail list logo