NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Odd OS X Lion and 4.2.18 permission issue
Prior to updating to OS X Lion and RAIDiator 4.2.18, I had my UID/GID synchronized between OS X and the ReadyNAS Pro.
After upgrading to OS X Lion and RAIDiator 4.2.18 I can mount the shares using my account name and password but I do not have permissions to add, change or delete anything on the share.
Looking in the netatalk.log file I see afp start up just fine and I authenticate:
After that I see errors like:
I was playing with a clean Lion install where I had not synced my UID/GID and it all worked. So on a whim I decided to change my UID/GID on the ReadyNAS and I can update things on shares again.
After upgrading to OS X Lion and RAIDiator 4.2.18 I can mount the shares using my account name and password but I do not have permissions to add, change or delete anything on the share.
Looking in the netatalk.log file I see afp start up just fine and I authenticate:
Jul 22 11:27:49.309313 afpd[2986] {status.c:707} (I:AFPDaemon): "naspro"'s signature is 7BF3F0BED55B5B400EB0C9468D916ADE
Jul 22 11:27:49.310144 afpd[2986] {afp_config.c:372} (N:AFPDaemon): AFP/TCP started, advertising 192.168.100.11:548 (2.2-rc1)
Jul 22 11:27:50.915998 afpd[2986] {auth.c:148} (I:AFPDaemon): uam: "No User Authent" available
Jul 22 11:27:50.916049 afpd[2986] {auth.c:148} (I:AFPDaemon): uam: "DHX2" available
Jul 22 11:27:50.916067 afpd[2986] {auth.c:148} (I:AFPDaemon): uam: "DHCAST128" available
Jul 22 11:27:52.134000 afpd[2986] {cnid.c:53} (I:AFPDaemon): Registering CNID module [dbd]
Jul 22 11:27:52.134059 afpd[2986] {cnid.c:53} (I:AFPDaemon): Registering CNID module [tdb]
Jul 22 11:37:36.588245 afpd[2986] {main.c:396} (I:AFPDaemon): re-reading configuration file
Jul 22 11:37:36.588556 afpd[2986] {status.c:707} (I:AFPDaemon): "naspro"'s signature is 7BF3F0BED55B5B400EB0C9468D916ADE
Jul 22 11:37:36.588911 afpd[2986] {afp_config.c:372} (N:AFPDaemon): AFP/TCP started, advertising 192.168.100.11:548 (2.2-rc1)
Jul 22 11:37:38.237801 afpd[2986] {auth.c:148} (I:AFPDaemon): uam: "No User Authent" available
Jul 22 11:37:38.237848 afpd[2986] {auth.c:148} (I:AFPDaemon): uam: "DHX2" available
Jul 22 11:37:38.237865 afpd[2986] {auth.c:148} (I:AFPDaemon): uam: "DHCAST128" available
Jul 22 11:37:39.085731 afpd[2986] {main.c:183} (I:AFPDaemon): child[3704]: exited 1
Jul 22 11:37:39.086379 afpd[3706] {dsi_tcp.c:212} (I:DSI): AFP/TCP session from 192.168.100.115:51135
Jul 22 11:37:39.086647 afpd[2986] {main.c:183} (I:AFPDaemon): child[3705]: exited 1
Jul 22 11:37:39.087583 afpd[2986] {main.c:185} (I:AFPDaemon): child[3706]: done
Jul 22 11:37:41.940369 afpd[3708] {dsi_tcp.c:212} (I:DSI): AFP/TCP session from 192.168.100.115:51136
Jul 22 11:37:41.941177 afpd[3708] {uams_dhx2_pam.c:321} (I:UAMS): DHX2 login: clacour
Jul 22 11:37:42.038072 afpd[3708] {uams_dhx2_pam.c:210} (I:UAMS): PAM DHX2: PAM Success
Jul 22 11:37:42.039432 afpd[3708] {uams_dhx2_pam.c:653} (I:UAMS): DHX2: PAM Auth OK!
Jul 22 11:37:42.039463 afpd[3708] {auth.c:269} (N:AFPDaemon): AFP3.3 Login by clacour
Jul 22 11:37:42.050124 afpd[3708] {volume.c:2036} (I:AFPDaemon): CNID server: localhost:4700
Jul 22 11:37:42.100363 afpd[3708] {volume.c:2036} (I:AFPDaemon): CNID server: localhost:4700
Jul 22 11:37:42.129627 afpd[3708] {volume.c:2036} (I:AFPDaemon): CNID server: localhost:4700
Jul 22 11:37:42.181083 afpd[3708] {volume.c:2036} (I:AFPDaemon): CNID server: localhost:4700
Jul 22 11:37:42.225090 afpd[3708] {volume.c:2036} (I:AFPDaemon): CNID server: localhost:4700
Jul 22 11:37:42.272799 afpd[3708] {volume.c:2036} (I:AFPDaemon): CNID server: localhost:4700
Jul 22 11:37:42.333199 afpd[3708] {volume.c:2036} (I:AFPDaemon): CNID server: localhost:4700
Jul 22 11:37:42.370507 afpd[3708] {volume.c:2036} (I:AFPDaemon): CNID server: localhost:4700
Jul 22 11:37:42.397749 afpd[3708] {volume.c:2036} (I:AFPDaemon): CNID server: localhost:4700
Jul 22 11:37:42.436486 afpd[3708] {volume.c:2036} (I:AFPDaemon): CNID server: localhost:4700
Jul 22 11:37:42.468224 afpd[3708] {volume.c:2036} (I:AFPDaemon): CNID server: localhost:4700
Jul 22 11:37:42.507968 afpd[3708] {volume.c:2031} (I:AFPDaemon): Volume /c/home/clacour use CNID scheme dbd.
Jul 22 11:37:42.508024 afpd[3708] {volume.c:2036} (I:AFPDaemon): CNID server: localhost:4700
Jul 22 11:37:47.257260 afpd[3708] {volume.c:2036} (I:AFPDaemon): CNID server: localhost:4700After that I see errors like:
Jul 22 11:37:47.277225 afpd[3708] {uuid.c:275} (W:AFPDaemon): getnamefromuuid(F1BF78E8-6631-43EB-A91B-9E7D6763731F): no result from ldap_getnamefromuuid
Jul 22 11:37:47.277308 afpd[3708] {acls.c:1121} (E:Default): getnamefromuuid(uuid, &username, &uuidtype) failed: Resource temporarily unavailable
Jul 22 11:37:47.277395 afpd[3708] {acls.c:1121} (E:Default): getnamefromuuid(uuid, &username, &uuidtype) failed: Resource temporarily unavailable
Jul 22 11:37:47.277454 afpd[3708] {acls.c:1121} (E:Default): getnamefromuuid(uuid, &username, &uuidtype) failed: Resource temporarily unavailable
Jul 22 11:37:47.277628 afpd[3708] {acls.c:1121} (E:Default): getnamefromuuid(uuid, &username, &uuidtype) failed: Resource temporarily unavailable
Jul 22 11:37:47.288159 afpd[3708] {acls.c:1121} (E:Default): getnamefromuuid(uuid, &username, &uuidtype) failed: Resource temporarily unavailable
Jul 22 11:37:47.292781 afpd[3708] {acls.c:1121} (E:Default): getnamefromuuid(uuid, &username, &uuidtype) failed: Resource temporarily unavailable
Jul 22 11:37:47.294786 afpd[3708] {acls.c:1121} (E:Default): getnamefromuuid(uuid, &username, &uuidtype) failed: Resource temporarily unavailable
Jul 22 11:37:47.295095 afpd[3708] {acls.c:1121} (E:Default): getnamefromuuid(uuid, &username, &uuidtype) failed: Resource temporarily unavailable
Jul 22 11:37:47.295272 afpd[3708] {acls.c:1121} (E:Default): getnamefromuuid(uuid, &username, &uuidtype) failed: Resource temporarily unavailable
Jul 22 11:37:47.299045 afpd[3708] {acls.c:1121} (E:Default): getnamefromuuid(uuid, &username, &uuidtype) failed: Resource temporarily unavailable
Jul 22 11:37:50.589780 afpd[3708] {acls.c:1121} (E:Default): getnamefromuuid(uuid, &username, &uuidtype) failed: Resource temporarily unavailable
Jul 22 11:37:50.589858 afpd[3708] {acls.c:1121} (E:Default): getnamefromuuid(uuid, &username, &uuidtype) failed: Resource temporarily unavailable
Jul 22 11:37:50.589986 afpd[3708] {acls.c:1121} (E:Default): getnamefromuuid(uuid, &username, &uuidtype) failed: Resource temporarily unavailableI was playing with a clean Lion install where I had not synced my UID/GID and it all worked. So on a whim I decided to change my UID/GID on the ReadyNAS and I can update things on shares again.
3 Replies
Replies have been turned off for this discussion
- Same thing on my NV with RAIDiator 4.1.8 - T5 after changing my UID/GID on the NV.
- Ditto, changing the UID to not match the readynas fixed the problem (edited /etc/passwd, chowned the home directory). Looks like a netatalk bug, or it could be related to the missing staff group if you use ldap.
- OK, the Beta update 4.2.19-T4 is a success. It worked after the update and after changing my UID back so that are the same on the ReadyNAS and Lion and it still works.
The only thin his the Fan status. It is blinking yellow. It shows yellow for Fan CAS: 0. There is a value of 1720 for SYS and 3121 for CPU that are green.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
