Netatalk 2.2 - Problem with dbd cnid

[GaussNiwre]

Hi there,

After waiting for the netatalk 2.2 package for a while, I've installed and configured following the documentation on netatalk's homepage.

This is the message log I get when trying to connect to a configured share:

Aug 18 02:26:25 Proliant afpd[3451]: read: Connection reset by peer
Aug 18 02:26:26 Proliant afpd[3451]: read: Connection reset by peer
Aug 18 02:26:27 Proliant afpd[3451]: read: Connection reset by peer
Aug 18 02:26:28 Proliant afpd[3451]: read: Connection reset by peer
Aug 18 02:26:29 Proliant afpd[3451]: read: Connection reset by peer
Aug 18 02:26:30 Proliant afpd[3451]: read: Connection reset by peer
Aug 18 02:26:31 Proliant avahi-daemon[743]: Received response from host 192.168.1.1 with invalid source port 32768 on interface 'em1.0'
Aug 18 02:26:31 Proliant afpd[3451]: read: Connection reset by peer
Aug 18 02:26:32 Proliant afpd[3451]: read: Connection reset by peer
Aug 18 02:26:33 Proliant afpd[3451]: read: Connection reset by peer
Aug 18 02:26:34 Proliant afpd[3451]: read: Connection reset by peer
Aug 18 02:26:35 Proliant afpd[3451]: read: Connection reset by peer
Aug 18 02:26:36 Proliant afpd[3451]: read: Connection reset by peer
Aug 18 02:26:37 Proliant afpd[3451]: read: Connection reset by peer
Aug 18 02:26:38 Proliant afpd[3451]: read: Connection reset by peer
Aug 18 02:26:39 Proliant afpd[3451]: read: Connection reset by peer
Aug 18 02:26:40 Proliant afpd[3451]: read: Connection reset by peer
Aug 18 02:26:41 Proliant afpd[3451]: read: Connection reset by peer
Aug 18 02:26:42 Proliant afpd[3451]: read: Connection reset by peer
Aug 18 02:26:43 Proliant afpd[3451]: read: Connection reset by peer
Aug 18 02:26:43 Proliant afpd[3451]: transmit: Request to dbd daemon (db_dir /mnt/raid/media) timed out.
Aug 18 02:26:43 Proliant afpd[3451]: Reopen volume /mnt/raid/media using in memory temporary CNID DB.

As you can see, I get only read-only access since the dbd daemon timed out. According to netatalk's documentation:

"Note that the dbd backend needs an auxiliary daemon, called cnid_metad, to work. It should be started together with afpd. If the dbd backend is compiled into afpd (the default), this should happen automatically. If you cannot find it in the process list even though the dbd backend is used please check for errors in the startup scripts."

Well, this process is running:

[root@Proliant raid]# ps -A |grep cnid
 2719 ?        00:00:00 cnid_metad

Any ideas/help is very appreciated! Cheers,

GaussNiwre

[dbutlerman]

I am having the same problem - did you ever get this resolved?