Bug 13324 - timemachine share not being advertised by avahi-daemon
Summary: timemachine share not being advertised by avahi-daemon
Status: RESOLVED DUPLICATE of bug 14574
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: VFS Modules (show other bugs)
Version: unspecified
Hardware: All All
: P5 minor (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-12 10:21 UTC by roland
Modified: 2021-05-10 08:02 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description roland 2018-03-12 10:21:07 UTC 
When adding a new share to smb.conf and "pkill -HUP smbd/nmbd" , i would expect that this share would be also added to avahi-daemon running config to be advertised there, but apparently i need to restart avahi-daemon to make it appear.

i'm not sure if this is a bug or if this is by design or a "missing feature", though.

this happens with latest samba 4.8.0rc4
Comment 1 roland 2018-03-12 14:12:48 UTC 
apparently, after pkill -HUP smbd/nmbd, restarting avahi-daemon (added sleep 5 after pkill) seems to be unreliable, i had at least one occurence where smbd did not re-register the shares after that and so no user could do timemachine backups.
Comment 2 Mario Lipinski 2019-06-16 21:53:39 UTC 
I am running 4.9.5-Debian on Debian buster and am experiencing similar problems.

It looks like Samba registers with Avahi when starting up or avahi starting up and uses a TTL of 120 (at least for the smb service).

After these 120 seconds it seems macOS no longer can find Samba via mDNS/Avahi.
Comment 3 Bill Burgess 2021-05-09 21:32:18 UTC 
The symptoms of this issue are very similar to those I encountered as a result of the firewall in my vanilla configuration of CentOS blocking mDNS by default.  When I explicitly allowed mDNS through the firewall, vfs_fruit worked great.  Please see Bug 14574.
Comment 4 Björn Jacke 2021-05-10 08:02:28 UTC 

*** This bug has been marked as a duplicate of bug 14574 ***