AFP not working on 6.2-rc5

[mxmod]

When my mac systems try to connect via AFP it fails they can however connect via CIFS fine, i see the following in the unraid log. Any help would be appreciated

Sep 8 21:14:09 HyperNAS cnid_dbd[5650]: error opening DB environment after recovery: No such device
Sep 8 21:14:09 HyperNAS cnid_dbd[5650]: Failed to open CNID database for volume "Archive"
Sep 8 21:14:09 HyperNAS cnid_dbd[5650]: Recreated CNID BerkeleyDB databases of volume "Archive"
Sep 8 21:14:09 HyperNAS cnid_dbd[5650]: error opening DB environment after recovery: No such device
Sep 8 21:14:09 HyperNAS cnid_dbd[5650]: open_db() failed: No such device
Sep 8 21:14:09 HyperNAS cnid_dbd[5650]: reinit_db() failed: No such device
Sep 8 21:14:09 HyperNAS afpd[651]: read: Connection reset by peer
Sep 8 21:14:09 HyperNAS cnid_dbd[5677]: error opening DB environment after recovery: No such device
Sep 8 21:14:09 HyperNAS cnid_dbd[5677]: Failed to open CNID database for volume "Archive"
Sep 8 21:14:09 HyperNAS cnid_dbd[5677]: Recreated CNID BerkeleyDB databases of volume "Archive"
Sep 8 21:14:09 HyperNAS cnid_dbd[5677]: error opening DB environment after recovery: No such device
Sep 8 21:14:09 HyperNAS cnid_dbd[5677]: open_db() failed: No such device
Sep 8 21:14:09 HyperNAS cnid_dbd[5677]: reinit_db() failed: No such device
Sep 8 21:14:09 HyperNAS afpd[651]: read: Connection reset by peer
Sep 8 21:14:10 HyperNAS cnid_metad[5719]: Multiple attempts to start CNID db daemon for "/mnt/user/Archive" failed, wiping the slate clean...
Sep 8 21:14:10 HyperNAS cnid_dbd[5719]: error opening DB environment after recovery: No such device
Sep 8 21:14:10 HyperNAS cnid_dbd[5719]: Failed to open CNID database for volume "Archive"
Sep 8 21:14:10 HyperNAS cnid_dbd[5719]: Recreated CNID BerkeleyDB databases of volume "Archive"
Sep 8 21:14:11 HyperNAS cnid_dbd[5719]: error opening DB environment after recovery: No such device
Sep 8 21:14:11 HyperNAS cnid_dbd[5719]: open_db() failed: No such device
Sep 8 21:14:11 HyperNAS cnid_dbd[5719]: reinit_db() failed: No such device
Sep 8 21:14:11 HyperNAS afpd[651]: read: Connection reset by peer
Sep 8 21:14:12 HyperNAS cnid_dbd[5754]: error opening DB environment after recovery: No such device
Sep 8 21:14:12 HyperNAS cnid_dbd[5754]: Failed to open CNID database for volume "Archive"
Sep 8 21:14:12 HyperNAS cnid_dbd[5754]: Recreated CNID BerkeleyDB databases of volume "Archive"
Sep 8 21:14:12 HyperNAS cnid_dbd[5754]: error opening DB environment after recovery: No such device
Sep 8 21:14:12 HyperNAS cnid_dbd[5754]: open_db() failed: No such device
Sep 8 21:14:12 HyperNAS cnid_dbd[5754]: reinit_db() failed: No such device
Sep 8 21:14:12 HyperNAS afpd[651]: read: Connection reset by peer
Sep 8 21:14:13 HyperNAS afpd[651]: read: Connection reset by peer
Sep 8 21:14:14 HyperNAS afpd[651]: read: Connection reset by peer
Sep 8 21:14:15 HyperNAS afpd[651]: read: Connection reset by peer
Sep 8 21:14:16 HyperNAS afpd[651]: read: Connection reset by peer
Sep 8 21:14:17 HyperNAS afpd[651]: read: Connection reset by peer
Sep 8 21:14:17 HyperNAS afpd[651]: transmit: Request to dbd daemon (volume Archive) timed out.
Sep 8 21:14:17 HyperNAS afpd[651]: afp_openvol(/mnt/user/Archive): Fatal error: Unable to get stamp value from CNID backend
Sep 8 21:14:17 HyperNAS afpd[651]: dsi_stream_read: len:0, unexpected EOF
Sep 8 21:14:17 HyperNAS afpd[32263]: child[651]: asev_del_fd: 4

[Frank1940]

First thing first!  I am NOT an Apple user.  But since you have not received any replies, I do have a few suggestions for you. 

 

You need to post up the diagnostics file.  ('Tools', then click on the 'Diagnostics' icon.)  That will provide much more information to the gurus who can help.

 

You also need to give the exact text of the error message that you are getting and what steps/procedure/program that occurred to get to that point. 

[mxmod]

Hi,

 

Thanks for the help i have attached the diag file.

 

From any of the macs on the network when trying to connect to any AFP shares finder sits with the status of Connecting... and the log data i posted before is output on the unRaid server, then after a few minutes the mac shows connection failed.

hypernas-diagnostics-20160909-1606_1.zip

[mxmod]

I have done some further testing by not exporting any AFP shares and restarting adding a new share and exporting AFP with public permissions. I now get the following errors.

 

Sep 14 13:11:59 HyperNAS emhttp: shcmd (2684): /usr/local/sbin/update_cron &> /dev/null
Sep 14 13:11:59 HyperNAS emhttp: shcmd (2695): /etc/rc.d/rc.atalk start |& logger
Sep 14 13:11:59 HyperNAS root: starting netatalk: netatalk
Sep 14 13:11:59 HyperNAS emhttp: shcmd (2696): cp /tmp/emhttp/afp.service /etc/avahi/services/afp.service
Sep 14 13:11:59 HyperNAS avahi-daemon[14323]: Files changed, reloading.
Sep 14 13:11:59 HyperNAS avahi-daemon[14323]: Loading service file /services/afp.service.
Sep 14 13:12:00 HyperNAS avahi-daemon[14323]: Service "HyperNAS-AFP" (/services/afp.service) successfully established.
Sep 14 13:12:05 HyperNAS afpd[28821]: dsi_stream_read: len:0, unexpected EOF

[micokeman]

Were you ever able to get AFP to work successfully? I am have real issues trying to connect my Mac machines to my UnRaid server.

[mxmod]

Yes AFP is working for me i had turned on the Tunable (enable Direct IO) this is what broke AFP after i set it back to Auto or No i have had no issues since.

 

 

 

[micokeman]

Is that the same as "Tunable (enable NCQ):" I am thinking that something on my Disk Settings is not set correctly. I am at 4 GB and am researching the best settings

[mxmod]

No the setting i am referring to is in the Global Share Settings

[micokeman]

Thank you. Mine is set to 'Auto'. There has been to suggestions to convert my drives to XFS format. The large amount of writing to the drives is probably the problem.