On 1/28/25 02:20, Iain M Conochie wrote:
On Mon, 2025-01-27 at 15:00 -0700, Jim Fehlig wrote:
On 1/27/25 05:50, Iain M Conochie wrote:
Good day all,
I have having an issue starting virtual networks defined within
libvirt:
virsh # net-start cmdb
error: Failed to start network cmdb
error: internal error: Child process (VIR_BRIDGE_NAME=virbr3
/usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/cmdb.conf --
leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper)
unexpected exit status 2:
dnsmasq: failed to create listening socket for 172.26.80.1: Address
already in use
I saw similar reports recently and from the system journal noticed
that named
started listening on the address as soon as it appeared, before
dnsmasq could
begin listening. Is the named service running on your system? If so,
you could
try disabling it and then check if the cmdb network successfully
starts.
Hi Jim
I have locked named to only listen on the primary IP address, and my
networks are now starting! Thanks very much for your help.
Given several reports across different distros, it would be interesting to know
the source of this sudden change in behavior. A change to the bind package?
systemd? Something else?
Regards,
Jim
