Instances failes to initialize using default parameters and returns unclear error message

Description

Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/middlewared/job.py", line 515, in run
await self.future
File "/usr/lib/python3/dist-packages/middlewared/job.py", line 560, in __run_body
rv = await self.method(*args)
^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/middlewared/api/base/decorator.py", line 88, in wrapped
result = await func(*args)
^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/middlewared/plugins/virt/global.py", line 126, in do_update
await job.wait(raise_error=True)
File "/usr/lib/python3/dist-packages/middlewared/job.py", line 463, in wait
raise self.exc_info[1]
File "/usr/lib/python3/dist-packages/middlewared/job.py", line 515, in run
await self.future
File "/usr/lib/python3/dist-packages/middlewared/job.py", line 560, in __run_body
rv = await self.method(*args)
^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/middlewared/plugins/virt/global.py", line 218, in setup
await self._setup_impl()
File "/usr/lib/python3/dist-packages/middlewared/plugins/virt/global.py", line 302, in _setup_impl
raise CallError(result.get('error'))
middlewared.service_exception.CallError: [EFAULT] The DNS and DHCP service exited prematurely: exit status 2 ("dnsmasq: failed to create listening socket for 10.151.217.1: Address already in use")

I suspect this has something to do with the fact that I am currently running AdGuard Home and it is using the host's port 53. This shouldn't impact Incus startup imho because incus shouldn't by default be trying to use 53 on the host system. If this is intended behavior, then a more clear error message along the lines of "It appears as though you are already running a DNS server from this host; this configuration is not supported. You may run Incus OR a DNS server, but not both."

Session ID: a6c91a68-1834-54c2-cdd6-e760f424e1bc

Problem/Justification

None

Impact

None

Activity

Show:

Bug Clerk 3 days ago

This issue has now been closed. Comments made after this point may not be viewed by the TrueNAS Teams. Please open a new issue if you have found a problem or need to re-engage with the TrueNAS Engineering Teams.

Bug Clerk 3 days ago

Instances is an experimental feature that we’re actively working on. This might be resolved in 25.04.0 when it’s released. We suggest waiting for that to be released to see if this is still an issue.

William Gryzbowski 3 days ago

You can/should run your DNS server on a specific interface, and not every ip/interface.

Michelle Johnson 3 days ago

Thank you for your report, !

This issue ticket is in the queue for review. An Engineering representative will update with further details or questions in the near future.

mrlenny 3 days ago

Is this intended behavior? Will we be unable to run Incus if we’re also running a DNS server? Or is this something that will be addressed?

Not Applicable
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Fix versions

Priority

More fields

Katalon Platform

Created 4 days ago
Updated 3 days ago
Resolved 3 days ago