I thought I would ask here too. I’m asking roughly the same questions on the TrueNAS community boards. I don’t seem to be alone in this problem.
TrueNAS is using version 0.7 of avahi. When I boot up fresh, things work fine. Eventually my Mac laptop can not find via the Finder the SMB shares that the NAS is providing. In my case there are two shares. One is for Time Machine and the other is Users. The Users share I can mount via the Mac’s “Go To Server” and I type in the address: smb://truenas.local/Users/pedz <smb://truenas.local/Users/pedz> and it connects. The Time Machine GUI interface really doesn’t allow me to do this. It has to find the share via mDNS and since it isn’t working, it can’t find it. I have a 3rd party app called Discovery that appears to work and tells me all of the mDNS stuff that is on the network. Nothing from the Truenas shows up when it is “broken”. To repeat, when I boot up fresh, it works and eventually stops working after a few weeks. The Truenas has a toggle via a web browser GUI to turn mDNS on or off. When it is on, there are 10 files in /usr/local/etc/avahi/services and a process that looks like: avahi 94347 5.1 0.0 13008 4148 - S 18:08 0:00.21 avahi-daemon: registering [truenas.local] (avahi-daemon) I make a copy of the 10 files in the services directory, then off mDNS in the Truenas GUI, copy the 10 files back, and then start avahi-daemon with —debug and get what appears to be all happy messages: Found user 'avahi' (UID 200) and group 'avahi' (GID 200). Successfully dropped root privileges. avahi-daemon 0.7 starting up. Loading service file /usr/local/etc/avahi/services/ADISK.service. Loading service file /usr/local/etc/avahi/services/AFPOVERTCP.service. Loading service file /usr/local/etc/avahi/services/DEV_INFO.service. Loading service file /usr/local/etc/avahi/services/HTTP.service. Loading service file /usr/local/etc/avahi/services/HTTPS.service. Loading service file /usr/local/etc/avahi/services/MIDDLEWARE.service. Loading service file /usr/local/etc/avahi/services/MIDDLEWARE_SSL.service. Loading service file /usr/local/etc/avahi/services/SFTP_SSH.service. Loading service file /usr/local/etc/avahi/services/SMB.service. Loading service file /usr/local/etc/avahi/services/SSH.service. Joining mDNS multicast group on interface ix0.IPv4 with address 192.168.1.3. New relevant interface ix0.IPv4 for mDNS. Network interface enumeration completed. Registering new address record for fe80::3cec:efff:fe6d:2ab6 on vnet0.3.*. Registering new address record for fe80::3cec:efff:fe2b:5fe2 on vnet0.1.*. Registering new address record for 192.168.1.3 on ix0.IPv4. Server startup complete. Host name is truenas.local. Local service cookie is 535196288. The IPv4 addresses above are correct. The interface is correct. The hostname is correct. The only thing I can find that looks odd are lines like this: [2022/04/28 17:01:19] (WARNING) middlewared.plugins.service_.services.base_freebsd.freebsd_service():136 - Failed to forcestop avahi-daemon with code 255 with error 'Stopping avahi-daemon.\nFailed to kill daemon: No such file or directory\n’ The first one of those is dated 4/9 and I believe things were still working up until 4/17. The Truenas is a Free BSD system. Thank you for your time and help, Perry
signature.asc
Description: Message signed with OpenPGP
