I'm having a problem using Apple Filing Protocol (AFP) services provided by
netatalk on OpenBSD, from an OS X Mountain Lion client.
I have OpenBSD 5.2 running on an old iMac, with the netatalk-2.2.3p0 package.
I made no changes to the default configuration beyond editing
/etc/netatalk/afpd.conf to assign the server its name and IP address.
I started afpd (the AFP daemon provided by netatalk).
>From another Mac, I can connect to the resulting server, but get:
Message from server "oldMac"
Something wrong with the volume's CNID DB, using
temporary CNID DB instead.Check server messages
for details. Switching to read-only mode.
I looked for help on the web and found
[Solved] [netatalk] Something wrong with CNID DB - The FreeBSD Forums
(http://forums.freebsd.org/showthread.php?t=20324)
which suggested
1. Stop netatalk.
2. Delete the .AppleDB cnid db in the root of your share(s).
3. Make sure that the cnidscheme is set to dbd in AppleVolumes.default
4. Crucially, make sure that the cnid_metad daemon has been started, by
adding the following line to /etc/rc.conf:
cnid_metad_enable="YES"
5. Start netatalk.
Following that suggestion, I stopped afpd, enabled cnid_metad_enable in
/etc/rc.conf.local, and restarted afpd.
I did not change AppleVolumes.default because the cnidscheme is already dbd by
default.
I did not delete an .AppleDB folder or its contents because none exists
(though there is a .AppleDouble folder).
The changes did not solve the problem.
I also found
0000609: Mac OS X Mountain Lion & Lion clients receive CNID DB error
when
connecting to OMV AFP shares - MantisBT
(http://bugtracker.openmediavault.org/print_bug_page.php?bug_id=609)
which suggested
Edit /etc/netatalk/afpd.conf and change the entry to:
- -tcp -noddp -uamlist uams_dhx.so,uams_dhx2_passwd.so
Edit /etc/default/netatalk and add this line at the end:
AFPD_UAMLIST="-U uams_dhx.so,uams_dhx2_passwd.so"
I added the suggested switches to the configuration line in afpd.conf.
I did not add anything to a /etc/default/netatalk because I don't have such a
file. Other web pages imply that that file is Debian-ish rather than
OpenBSD-ish.
I stopped and restarted afpd.
The changes did not solve the problem.
Do any of you have other suggestions?
