[4.1.9-T2] First AFP connect fails after ReadyNAS Duo reboot
Seeing this problem since I upgraded from 4.1.6 to 4.1.9-T2. In a nutshell, if you connect (from Lion) to our ReadyNAS Duo via AFP, you will get an error the first time. From then on, until the Duo is restarted, subsequent connects are ok. The Duo shuts down over night hence the issue.
Here is the problem in terms of the timing and logs:
Before first connect (after Duo has re-booted)
NAS log entries:
ian@ianch-nas:/var/log$ grep "Mar 20" daemon.log | grep -i afp Mar 20 06:00:56 ianch-nas avahi-daemon[879]: Loading service file /etc/avahi/services/afp.service. Mar 20 06:00:58 ianch-nas avahi-daemon[879]: Service "ianch-nas (AFP)" (/etc/avahi/services/afp.service) successfully established. Mar 20 06:02:17 ianch-nas afpd[1266]: AFP/TCP started, advertising 192.168.0.2:548 (2-2-1-p6)
First connect (FAILS):
NAS log entries:
ian@ianch-nas:/var/log$ grep "Mar 20" daemon.log | grep -i afp Mar 20 06:00:56 ianch-nas avahi-daemon[879]: Loading service file /etc/avahi/services/afp.service. Mar 20 06:00:58 ianch-nas avahi-daemon[879]: Service "ianch-nas (AFP)" (/etc/avahi/services/afp.service) successfully established. Mar 20 06:02:17 ianch-nas afpd[1266]: AFP/TCP started, advertising 192.168.0.2:548 (2-2-1-p6) Mar 20 08:24:58 ianch-nas afpd[1266]: AFP/TCP started, advertising 192.168.0.2:548 (2-2-1-p6)
Mac error:
error popup "There was a problem connecting to the server “ianch-nas”"
Re: [4.1.9-T2] First AFP connect fails after ReadyNAS Duo re
mdgm wrote:
Can you try T6?: http://www.readynas.com/forum/viewtopic.php?f=17&t=59222
Though not mentioned in the release notes there is an update to the AFP service in T6.
T6 also has a major regression in samba functionality (see my other post and other people's reports). What information can we provide to help debug/resolve these issues? Im' happy to provide remote shell access or to bring in my device, if you guys are in the SF bay area.
Re: [4.1.9-T2] First AFP connect fails after ReadyNAS Duo re
Now on 4.1.9-T6 but still have the first connect problem.
When I was on 4.1.6 + Lion, I had to use this workaround: http://support.apple.com/kb/HT4700. Just to make sure, I have removed the /Library/Preferences/com.apple.AppleShareClient.plist file and rebooted to revert to (Lion) defaults.
After rebooting the Duo and Mac, log entries are listed below. The AFP messages now seem to be in netatalk.log in this build ...
Duo start-up:
Mar 21 09:14:52.115919 afpd[1236] {status.c:740} (I:AFPDaemon): "ianch-nas"'s signature is 42D0D918E181E9412C87FBF4A81BA8D0 Mar 21 09:14:52.171470 afpd[1236] {dsi_tcp.c:318} (I:DSI): dsi_tcp_init: socket: Address family not supported by protocol Mar 21 09:14:52.176359 afpd[1236] {afp_config.c:372} (N:AFPDaemon): AFP/TCP started, advertising 192.168.0.2:548 (2-2-2) Mar 21 09:18:11.139245 afpd[1236] {auth.c:136} (I:AFPDaemon): uam: "No User Authent" available Mar 21 09:18:11.139486 afpd[1236] {auth.c:136} (I:AFPDaemon): uam: "Cleartxt Passwrd" available Mar 21 09:18:11.139646 afpd[1236] {auth.c:136} (I:AFPDaemon): uam: "DHX2" available Mar 21 09:18:11.139806 afpd[1236] {auth.c:136} (I:AFPDaemon): uam: "DHCAST128" available Mar 21 09:18:11.221289 afpd[1236] {volume.c:2213} (I:AFPDaemon): read-only volume 'squeezeboxserver', can't test for EA support, disabling EAs Mar 21 09:18:11.221730 afpd[1236] {cnid.c:53} (I:AFPDaemon): Registering CNID module [dbd] Mar 21 09:18:11.221931 afpd[1236] {cnid.c:53} (I:AFPDaemon): Registering CNID module [tdb]
