My main issue is, as the title says, that AFP became somewhat unresponsive a few days ago while the rest of the server was seemingly fine. I could see the AFP server, and I could see the list of shares, but I was unable to actually browse the shares. I tired toggling AFP on and off but this didn’t work. Literally. AFP never actually shut off, meaning on my Mac I never got the message that the AFP server was shutting down, and I was always able to see the AFP server and browse the list of shares. Eventually it started working again through no clear intervention of my own (I had planned to reboot, but hadn’t yet gotten around to it), however when it came up, I shortly after got the dreaded Time Machine completed a verification of your backups on “StrongBad-AFP”. To improve reliability, Time Machine must create a new backup for you.

 

I am including my log file (which is a little tough to read owing to my other problem that I will post about separately), but the relevant lines to my untrained eye are

Nov  2 08:44:06 StrongBad afpd[8881]: read: No route to host
Nov  2 08:44:06 StrongBad afpd[8881]: dsi_stream_read: len:-1, No route to host
Nov  2 08:44:06 StrongBad afpd[8881]: dsi_stream_read: len:0, unexpected EOF

This error is appearing several times a day, and from November 3 onward it always appears immediately after the Mover runs (my Time Machine share is not using the cache)

Other AFP related errors include

Nov  2 05:11:56 StrongBad afpd[8881]: afp_alarm: child timed out, entering disconnected state

Nov  2 16:24:22 StrongBad afpd[25638]: afp_alarm: reconnect timer expired, goodbye

Nov  3 21:15:28 StrongBad afpd[9159]: Session with different pid[18525]
Nov  3 21:15:32 StrongBad afpd[9159]: Session with different pid[18525]
Nov  3 21:15:34 StrongBad afpd[9159]: Session with different pid[18525]
Nov  3 21:15:38 StrongBad afpd[9159]: Session with different pid[18525]

Nov  3 21:19:35 StrongBad afpd[9159]: Terminated disconnected child[18525], client rebooted.
Nov  3 21:19:35 StrongBad afpd[9159]: Reading IPC header failed (-1 of 14 bytes read): Connection reset by peer
Nov  3 21:54:24 StrongBad afpd[27256]: afp_alarm: reconnect timer expired, goodbye

 

Any ideas on what happened and how to prevent it in the future before I go ahead and recreate my Time Machine backup?

 

https://www.dropbox.com/s/cczik2mujja6bpo/unRAID%20Log.txt?dl=0

This thread is fairly old, however I am having this same issue. On one of my two Unraid servers, time machine is backing up extremely slowly and the syslog is riddled with the same errors (see below). Eventually I will get the same problem of having to start the backup over and getting the "Time Machine completed a verification of your backups on “****-AFP”. To improve reliability, Time Machine must create a new backup for you."

 

On my second server (on a different network with different hosts) I also eventually get the "Time Machine completed a verification of your backups on “****-AFP”. To improve reliability, Time Machine must create a new backup for you." message on my Mac, although backups are normally quick and speedy. I have had this same issue since Unraid v5. I normally can go a month or two on this server before having to restart the backup.

 

Both of the Unraid servers are on v6b12 and both of the Macs on each network are running Yosemite. But I also had this problem in Mavericks and Mountain Lion. I can post full syslogs if needed when I get home.

 

 

Jan 22 21:52:15 Fred afpd[10712]: dsi_stream_read: len:0, unexpected EOF
Jan 22 21:53:29 Fred afpd[10822]: transmit: Request to dbd daemon (volume KarenMacTimeMachine) timed out.
Jan 22 22:43:39 Fred afpd[12313]: transmit: Request to dbd daemon (volume KarenMacTimeMachine) timed out.
Jan 22 23:33:04 Fred kernel: mdcmd (14): spindown 0
Jan 22 23:33:04 Fred kernel: mdcmd (15): spindown 1
Jan 22 23:33:16 Fred afpd[12313]: read: No route to host
Jan 22 23:33:16 Fred afpd[12313]: dsi_stream_read: len:-1, No route to host
Jan 22 23:33:16 Fred afpd[12313]: dsi_stream_read: len:0, unexpected EOF
Jan 22 23:33:17 Fred afpd[10740]: read: No route to host
Jan 22 23:33:17 Fred afpd[10740]: dsi_stream_read: len:-1, No route to host
Jan 23 01:08:47 Fred afpd[10740]: afp_alarm: child timed out, entering disconnected state
Jan 23 01:22:17 Fred kernel: mdcmd (16): spindown 0
Jan 23 01:22:18 Fred kernel: mdcmd (17): spindown 1
Jan 23 01:22:21 Fred afpd[12313]: read: No route to host
Jan 23 01:22:21 Fred afpd[12313]: dsi_stream_read: len:-1, No route to host
Jan 23 01:22:21 Fred afpd[12313]: dsi_stream_send: Broken pipe
Jan 23 01:22:21 Fred afpd[12313]: dsi_wrtreply: Broken pipe
Jan 23 02:57:47 Fred afpd[10740]: afp_alarm: child timed out, entering disconnected state
Jan 23 02:57:52 Fred afpd[12313]: afp_alarm: child timed out, entering disconnected state
Jan 23 03:11:04 Fred kernel: mdcmd (18): spindown 0
Jan 23 03:11:04 Fred kernel: mdcmd (19): spindown 1
Jan 23 03:22:47 Fred afpd[10740]: afp_alarm: child timed out, entering disconnected state
Jan 23 03:22:52 Fred afpd[12313]: afp_alarm: child timed out, entering disconnected state
Jan 23 03:35:39 Fred kernel: mdcmd (20): spindown 0
Jan 23 03:35:40 Fred kernel: mdcmd (21): spindown 1
Jan 23 03:40:01 Fred logger: mover started
Jan 23 03:40:06 Fred logger: skipping appdata/
Jan 23 03:40:06 Fred logger: mover finished
Jan 23 03:55:07 Fred kernel: mdcmd (22): spindown 1
Jan 23 07:23:59 Fred afpd[12313]: read: Connection reset by peer
Jan 23 07:23:59 Fred afpd[12313]: dsi_stream_read: len:-1, Connection reset by peer
Jan 23 07:23:59 Fred afpd[12313]: dsi_stream_read: len:0, unexpected EOF
Jan 23 07:46:47 Fred afpd[10740]: read: No route to host
Jan 23 07:46:47 Fred afpd[10740]: dsi_stream_read: len:-1, No route to host
Jan 23 07:46:47 Fred afpd[10740]: dsi_stream_read: len:0, unexpected EOF
Jan 23 07:46:49 Fred afpd[12313]: read: No route to host
Jan 23 07:46:49 Fred afpd[12313]: dsi_stream_read: len:-1, No route to host
Jan 23 07:46:49 Fred afpd[12313]: dsi_stream_read: len:0, unexpected EOF
Jan 23 07:46:51 Fred kernel: mdcmd (23): spindown 0
Jan 23 07:46:51 Fred kernel: mdcmd (24): spindown 1
Jan 23 09:38:06 Fred kernel: mdcmd (25): spindown 1

I've got nothing to add, but that I did a clean install of 6b12 and I forget what else and haven't had a troubles in the past month.