CNID DB error using AFP in Lion

I started getting the CNID DB error this morning.

OS X 10.7.2
RAIDiator 4.2.20-T32


I tried to connect to the share via AFP and the computer hung completely. I rebooted the computer and tried to connect again as guest and admin. Both times, I got the error message. It will open, but only in Read-Only.

I'm also having problems with CNID DB. I have a ReadyNAS NV+ and the latest RAIDiator 4.1.8 installed. iMac, Lion 10.7.2

It's going into read-only and now won't sync?

Can anyone give me a step by step guide to fix this?

I also have CNID DB since changing but I am still using Snow Leopard. (I have put in support trouble ticket 18008111)

Wed Feb 22 16:19:34 CET 2012 System is up.
Wed Feb 22 16:11:42 CET 2012 Volume scan found no errors.
Wed Feb 22 15:17:19 CET 2012 Rebooting device...
Wed Feb 22 15:17:19 CET 2012 Please close this browser session and use RAIDar to reconnect to the device. System rebooting...
Mon Feb 20 22:17:54 CET 2012 System is up.
Mon Feb 20 22:09:49 CET 2012 Volume scan found and corrected errors.
Mon Feb 20 21:17:50 CET 2012 Rebooting device... First time discover the CNID DB error. Tried rebooting to fix
Mon Feb 20 21:17:49 CET 2012 Please close this browser session and use RAIDar to reconnect to the device. System rebooting...
Sun Feb 19 09:53:22 CET 2012 HTTP service restarted.
Sat Feb 18 10:03:35 CET 2012 Successfully started Firefly (iTunes) Media Server.
Sat Feb 18 10:02:59 CET 2012 Successfully enabled optimized SqueezeCenter scanner.
Sat Feb 18 09:44:58 CET 2012 System is up.
Sat Feb 18 09:44:05 CET 2012 Your ReadyNAS device has been updated with a new firmware image. (RAIDiator 4.1.8)
Sat Feb 18 09:33:05 CET 2012 Rebooting device...
Sat Feb 18 09:33:05 CET 2012 Please close this browser session and use RAIDar to reconnect to the device. System rebooting...
Sat Feb 18 03:26:31 CET 2012 Backup finished. [Job 007] Note: it took nearly 2 weeks to backup 2TB
Sun Feb 5 13:26:47 CET 2012 Backup started. [Job 007]

I recieved the same error from OSX 10.7.3 with my Intel Readynas after a powerfailure, resynched and scanned without errors. But after starting the Mac this morning I got this error too.

I have an Ultra 6 with Mac OS X 10.7.3 on iMac 2011 and Radiator 4.2.19 and latest update done. AFP give me the CNID DB error. Urgent resolution would be appreciated. :rofl:

Add me to the "problems with Lion" category (10.7.3). I have a ReadyNAS Pro Business Edition [X-RAID2] and I recently updated RAIDiator 4.2.17 to RAIDiator 4.2.19. I never had problems with 4.2.17 regarding getting a directory listing of a share. Since moving to 4.2.19 I often get "0 items, 2.28 TB available" displayed in my status bar on a share that has several directories. Do I really have to reboot the ReadyNAS to solve this problem each time?

This is a log of the CNID error being generated:

ReadyNAS:~# tail -f /var/log/netatalk.log
Mar 12 18:11:49.501555 afpd[12911] {uams_dhx2_pam.c:653} (I:UAMS): DHX2: PAM Auth OK!
Mar 12 18:11:49.501836 afpd[12911] {auth.c:266} (N:AFPDaemon): AFP3.3 Login by ReadyNAS
Mar 12 18:11:49.636085 afpd[12911] {volume.c:2045} (I:AFPDaemon): CNID server: localhost:4700
Mar 12 18:12:33.023880 afpd[12911] {cnid_dbd.c:439} (E:CNID): transmit: Request to dbd daemon (db_dir /c/.timemachine) timed out.
Mar 12 18:12:33.024161 afpd[12911] {file.c:264} (E:AFPDaemon): Reopen volume /c/.timemachine using in memory temporary CNID DB.
Mar 12 18:13:15.387267 afpd[12911] {auth.c:924} (N:AFPDaemon): AFP logout by ReadyNAS
Mar 12 18:13:15.394101 afpd[12911] {afp_dsi.c:99} (N:AFPDaemon): AFP statistics: 15.56 KB read, 752.70 KB written
Mar 12 18:13:15.394381 afpd[12911] {dircache.c:616} (I:AFPDaemon): dircache statistics: entries: 15, lookups: 354, hits: 335, misses: 19, added: 15, removed: 0, expunged: 0, evicted: 0
Mar 12 18:13:15.394962 afpd[12911] {afp_dsi.c:570} (N:AFPDaemon): done
Mar 12 18:13:15.403119 afpd[1394] {main.c:216} (I:AFPDaemon): child[12911]: done
Mar 12 18:14:20.762137 afpd[12963] {dsi_tcp.c:212} (I:DSI): AFP/TCP session from 192.168.1.141:63242
Mar 12 18:14:20.776505 afpd[1394] {main.c:214} (I:AFPDaemon): child[12962]: exited 1
Mar 12 18:14:20.776826 afpd[1394] {main.c:216} (I:AFPDaemon): child[12963]: done
Mar 12 18:14:20.856485 afpd[12964] {dsi_tcp.c:212} (I:DSI): AFP/TCP session from 192.168.1.141:63243
Mar 12 18:14:20.863519 afpd[12964] {uams_dhx2_pam.c:321} (I:UAMS): DHX2 login: ReadyNAS
Mar 12 18:14:22.000894 afpd[12964] {uams_dhx2_pam.c:210} (I:UAMS): PAM DHX2: PAM Success
Mar 12 18:14:22.017087 afpd[12964] {uams_dhx2_pam.c:653} (I:UAMS): DHX2: PAM Auth OK!
Mar 12 18:14:22.017367 afpd[12964] {auth.c:266} (N:AFPDaemon): AFP3.3 Login by ReadyNAS
Mar 12 18:14:22.055103 afpd[12964] {volume.c:2045} (I:AFPDaemon): CNID server: localhost:4700

Any idea why requests to dbd are timing out?

Fandu wrote:
This is a log of the CNID error being generated: ReadyNAS:~# tail -f /var/log/netatalk.log ... Mar 12 18:12:33.023880 afpd[12911] {cnid_dbd.c:439} (E:CNID): transmit: Request to dbd daemon (db_dir /c/.timemachine) timed out. ...

Either the CNID database deamon (cnid_metad) is not running or hanging. You have ssh access to this unit? Are you somewhat familiar with CLI?
Checking whether cnid_metad is running could be done with a command like this:
$ ps -efl | grep cnid

Some background on the CNID stuff:
http://netatalk.sourceforge.net/2.2/htmldocs/configuration.html#CNID-backends

Can you PM me all available Netatalk logs please?!

chid appears to be running:

ReadyNAS:/var/log# ps -efl |grep cnid
5 S root 1506 1 0 81 0 - 728 - 20:54 ? 00:00:00 /usr/sbin/cnid_metad
0 S root 2226 807 0 77 0 - 1064 - 21:21 pts/0 00:00:00 grep cnid

logs pm'd.

Thanks!

Fandu wrote:
chid appears to be running: ReadyNAS:/var/log# ps -efl |grep cnid 5 S root 1506 1 0 81 0 - 728 - 20:54 ? 00:00:00 /usr/sbin/cnid_metad 0 S root 2226 807 0 77 0 - 1064 - 21:21 pts/0 00:00:00 grep cnid

So it seems to be running but not responding. We'd need stuff like strace or gdb installed on the box in order to determine why and where it's hanging. From your logs the main CNID daemon cnid_metad seems be hanging very early in its startup, because it is not even printing this messages

Feb 26 12:37:59 ReadyNAS cnid_metad[1556]: Set syslog logging to level: LOG_NOTE

which it should display every time its starting. Is there a chance you can install gdb on the unit? Is gcore installed? I can't check because our test unit just died and we're awaiting replacement.

-f