Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

iocage stop/start messes up mDNS

Description

I find that if I do an iocage stop/start, my server's mDNS stops working (i.e., I can no longer reach the host using hostname.local ).

Restarting avahi-daemon resolves the problem.

Problem/Justification

None

Impact

None

SmartDraw Connector

Katalon Manual Tests (BETA)

Activity

Show:

Dawid Moś 
August 10, 2021 at 10:43 AM

I'm having same problems with "truenas.local" domain availability. I don't know how to check if this is related to jail restart (because I'm not restarting anything manually, maybe it happens during some automatic maintenance or backup job).
But it definitely happens regularly and after restarting mDNS (midclt call service.restart mdns) it starts worlking for some time. Then it stops working again and .local domain became unavailable (i.e. TimeMachine stops working)

I have latest Truenas update (TrueNAS-12.0-U5).

Rémi Zara 
December 29, 2020 at 10:19 AM

This issue is still present on TrueNAS-12.0-U1

ddrucker@mclean.harvard.edu 
July 28, 2020 at 10:41 PM

Is it possible to have this issue reexamined, or is it dead now that it's closed?

Sean McBride 
July 28, 2020 at 9:25 PM

That's why I wondered if Joe misunderstood.  I also don't imagine anyone expecting that kicking a jail should affect the host system. After all, one expects jails to be like VMs, and to be independent.

ddrucker@mclean.harvard.edu 
July 28, 2020 at 8:29 PM
(edited)

That's correct Sean. Stopping/starting a jail means that the top-level FreeNAS's .local name is no longer being broadcast and so the system's SMB shares are no longer available to any client.

 

I can't really imagine that is intended behavior!

Behaves as Intended

Details

Assignee

Reporter

Labels

Fix versions

Affects versions

Priority

More fields

Katalon Platform

Created July 27, 2020 at 1:18 PM
Updated July 1, 2022 at 4:51 PM
Resolved July 28, 2020 at 7:02 PM