[Resolved in 11.2U1] TimeMachine stopped working. Not sure if caused by Mojave 11.14.2 update or 11.2 RELEASE update

[norbs]

This is the afp.log snippet from the point that I try to connect to the point the I get the above error.

Code:

Dec 24 10:56:09.677798 afpd[95980] {main.c:149} (info:AFPDaemon): child[96058]: exited 4
Dec 24 10:56:09.679886 afpd[96059] {dsi_tcp.c:241} (info:DSI): AFP/TCP session from 10.0.2.60:52051
Dec 24 10:56:09.682563 afpd[95980] {main.c:151} (info:AFPDaemon): child[96059]: done
Dec 24 10:56:19.068579 afpd[96062] {dsi_tcp.c:241} (info:DSI): AFP/TCP session from 10.0.2.60:52054
Dec 24 10:56:19.071499 afpd[96062] {uams_dhx2_pam.c:330} (info:UAMS): DHX2 login: tm
Dec 24 10:56:19.089642 afpd[96062] {uams_dhx2_pam.c:215} (info:UAMS): PAM DHX2: PAM Success
Dec 24 10:56:19.093216 afpd[96062] {uams_dhx2_pam.c:710} (info:UAMS): DHX2: PAM Auth OK!
Dec 24 10:56:19.093474 afpd[96062] {auth.c:235} (note:AFPDaemon): Login by tm (AFP3.4)
Dec 24 10:57:20.608240 afpd[96141] {dsi_tcp.c:241} (info:DSI): AFP/TCP session from 10.0.2.60:52071
Dec 24 10:57:20.611197 afpd[96141] {uams_dhx2_pam.c:330} (info:UAMS): DHX2 login: tm
Dec 24 10:57:20.632755 afpd[96141] {uams_dhx2_pam.c:215} (info:UAMS): PAM DHX2: PAM Success
Dec 24 10:57:20.636240 afpd[96141] {uams_dhx2_pam.c:710} (info:UAMS): DHX2: PAM Auth OK!
Dec 24 10:57:20.636481 afpd[96141] {auth.c:235} (note:AFPDaemon): Login by tm (AFP3.4)
Dec 24 10:57:20.638955 afpd[96141] {auth.c:536} (note:AFPDaemon): afp_disconnect: trying primary reconnect
Dec 24 10:57:20.639257 afpd[95980] {server_child.c:256} (note:Default): Reconnect: transferring session to child[96062]
Dec 24 10:57:20.639503 afpd[95980] {server_ipc.c:235} (note:AFPDaemon): Reconnect: killing new session child[96141] after transfer
Dec 24 10:57:22.701853 afpd[96141] {auth.c:561} (note:AFPDaemon): afp_disconnect: primary reconnect succeeded
Dec 24 10:57:22.702825 afpd[95980] {main.c:151} (info:AFPDaemon): child[96141]: done

 

[Constantin]

You may want to search for the work that Anodos has done to make Time Machine support possible on FreeNAS 11.2.

As I understand it, you may have to transition to SMB and enable various fruits in the SMB config. Time Machine over SMB may become fully supported as of 11.3.

This issue is one reason I have yet to upgrade my Mac from Sierra. Too many unknowns re: the new APFS file system (i.e. Apple only recently started releasing documentation to developers outside Apple) and Mojave turned off AFP-based Time Machine backups, IIRC.

 

[norbs]

Thanks for that. Maybe I'll just use an external disk until everything is a bit more supported. Do you happen to know what broke the functionality? I know it just stopped working on 12/8/18, so I'm assuming it was 11.2 Release. Just weird that it would work in all the previous RC of 11.2 and not in the release.

 

[anodos]

Thanks for that. Maybe I'll just use an external disk until everything is a bit more supported. Do you happen to know what broke the functionality? I know it just stopped working on 12/8/18, so I'm assuming it was 11.2 Release. Just weird that it would work in all the previous RC of 11.2 and not in the release.

Not much has changed on the AFP side for quite a long time. You can check the value of the sysctl net.inet.tcp.reass.maxqueuelen, setting this too low has caused problems for OS-X clients in my experience. You can try boosting it up to 1448. I haven't done any testing with Mojave and Time Machine over AFP. It is possible that something broke. If you don't mind, post the output of dns-sd -B _adisk._tcp. .. Do you see your time machine share?

To clarify, you run the dns-sd command from the terminal on MacOS (not from the FreeNAS server).

 

[norbs]

Not much has changed on the AFP side for quite a long time. You can check the value of the sysctl net.inet.tcp.reass.maxqueuelen, setting this too low has caused problems for OS-X clients in my experience. You can try boosting it up to 1448. I haven't done any testing with Mojave and Time Machine over AFP. It is possible that something broke. If you don't mind, post the output of dns-sd -B _adisk._tcp. .. Do you see your time machine share?

To clarify, you run the dns-sd command from the terminal on MacOS (not from the FreeNAS server).

net.inet.tcp.reass.maxqueuelen: 100
(I'll try the 1448 setting soon)

EDIT: I tried setting it to 1448 and it doesn't seem to be working.

Seeing this not sure if that is the AFP share. I use a ".local" for most my devices at home. This freenas box should be called "nas.local"

Timestamp A/R Flags if Domain Service Type Instance Name
14:26:08.386 Add 2 1 local. _adisk._tcp. nas


 

[norbs]

Look like the 11.2U1 update fixed the issue.

 

[Constantin]

Great news. I may try out Time machine over SMB and if it works, I may finally take the plunge re: mojave.

 

[anodos]

Great news. I may try out Time machine over SMB and if it works, I may finally take the plunge re: mojave.

Time Machine over SMB is not available in 11.2-U1. The U1 release was an emergency security release for AFP. I will try to have it working over SMB in 11.2-U2.

 

[Constantin]

No worries and thank you so much for all the work you have put into making FreeNAS more compatible with the Mac!

 

[adrianwi]

Time Machine over SMB is not available in 11.2-U1. The U1 release was an emergency security release for AFP. I will try to have it working over SMB in 11.2-U2.

It would be great to have a "how to.." guide for getting Time Machine working over SMB once it's fixed in U2?

Thanks

 

[Constantin]

It would be great to have a "how to.." guide for getting Time Machine working over SMB once it's fixed in U2?

That's pretty much covered here already. However, that post would likely benefit from being transferred to the resources page, along with some tips for better OSX performance and a link to the article / resource page that describes how to speed up SMB directory browsing and the like. Great stuff!