readynasd not starting - "Error rndb_import() ==> rc=3"

[therealcmj]

ReadyNAS 2304 / RNR-4C

Running ReadyNASOS 6.10.5

I was traveling and it seems like something went wrong. Someone in site did a hard power down and when I returned the admin page is offline.

SSH-ing into the machine and running "systemctl restart readynasd" shows a failure so I ran readynasd directly to acquire this info:

[22/02/21 13:38:49] 11302:11302 readynasd.c:1043 () readynasd log started
[22/02/21 13:38:49] 11302:11302 context.c:239 (debug) NEW GLOBAL_CONTEXT: db.sq3=0x11122d8
[22/02/21 13:38:49] 11302:11302 context.c:286 (debug) NEW GLOBAL_CONTEXT: event.sq3=0x115d158
[22/02/21 13:38:49] 11302:11302 context.c:289 (debug) NEW GLOBAL_CONTEXT: globalctx=0x1110240
[22/02/21 13:38:49] 11302:11302 readynasd.c:1313 () readynasd started. (restarted=0)
[22/02/21 13:38:49] 11302:11302 db_access.c:127 (error) Error rndb_import() ==> rc=3
[22/02/21 13:38:49] 11302:11302 readynasd.c:1372 (error) dba import failed

The systems journal shows some additional info:

-- Unit readynasd.service has begun starting up.
Feb 21 12:53:43 NASty readynasd[10651]: readynasd log started
Feb 21 12:53:43 NASty readynasd[10651]: readynasd started. (restarted=0)
Feb 21 12:53:43 NASty readynasd[10651]: DB (main) schema version: 24 ==> 24
Feb 21 12:53:43 NASty readynasd[10651]: DB (queue) schema version: new ==> 0
Feb 21 12:53:43 NASty readynasd[10651]: Failed to insert into $timemachine_quota table
Feb 21 12:53:43 NASty readynasd[10651]: _rndb_update_timemachine_user() ==> 3 (0ms)
Feb 21 12:53:43 NASty readynasd[10651]: rndb_account_import() ==> 3 (239ms)
Feb 21 12:53:44 NASty readynasd[10651]: rndb_import() ==> 3 (348ms)
Feb 21 12:53:44 NASty readynasd[10651]: Error rndb_import() ==> rc=3
Feb 21 12:53:44 NASty readynasd[10651]: dba import failed
Feb 21 12:53:44 NASty systemd[1]: readynasd.service: Main process exited, code=exited, status=255/n/a
Feb 21 12:53:44 NASty systemd[1]: Failed to start ReadyNAS System Daemon.

The database appears to be OK:

root@NASty:~# sqlite3 /var/readynasd/db.sq3 'pragma integrity_check'
ok

And I can select from that table no problem:

root@NASty:~# sqlite3 --header --column /var/readynasd/db.sq3 'select * from "$timemachine_quota"'
user_id enabled capacity_mb
---------- ---------- -----------
102 1 1000000

I copied the database to another file and tried inserting another row:

root@NASty:~# cp /var/readynasd/db.sq3 /tmp/
.font-unix/ .ICE-unix/ .Test-unix/ .X11-unix/ xagent.pid .XIM-unix/
root@NASty:~# cp /var/readynasd/db.sq3 /tmp/
root@NASty:~# sqlite3 --header --column /tmp/db.sq3 'select * from "$timemachine_quota"'
user_id enabled capacity_mb
---------- ---------- -----------
102 1 1000000
root@NASty:~# sqlite3 --header --column /tmp/db.sq3 'insert into "$timemachine_quota" (user_id,enabled,capacity_mp) values (103,1,1000000)'
Error: table $timemachine_quota has no column named capacity_mp
root@NASty:~# sqlite3 --header --column /tmp/db.sq3 'insert into "$timemachine_quota" (user_id,enabled,capacity_mb) values (103,1,1000000)'
root@NASty:~# sqlite3 --header --column /tmp/db.sq3 'select * from "$timemachine_quota"'
user_id enabled capacity_mb
---------- ---------- -----------
102 1 1000000
103 1 1000000

So this all looks OK.

Anyone have any ideas?

[therealcmj · Accepted solution]

I looked at that post and it provided some ideas of what to look at. But I definitely don't think it's appropriate to go down the path of restoring random database backups.

What's also interesting is that I do not seem to have any time machine config in the specified place:

cat /etc/netatalk/timemachine.conf

This file doesn't exist.

the /etc/netatalk/afp.conf refers to several other files:

include = /etc/frontview/netatalk/Shares.conf
include = /run/usb/netatalk/Shares.conf
include = /etc/netatalk/timemachine.conf

The first 2 files existed and, on a hunch, I touched the third one.

touch  /etc/netatalk/timemachine.conf

One reboot later and the NAS came back to life.

So there's a code bug here your developers should fix. But I'm back in business now.

Thanks!

[JeraldM]

Hi @therealcmj,

By any chance, have you checked the related community post here?

I'd also suggest performing an OS Reinstall.

Lastly, you could try opening a support case regarding this.

Regards,

JeraldM

NETGEAR Community Team

[therealcmj · Accepted solution]

I looked at that post and it provided some ideas of what to look at. But I definitely don't think it's appropriate to go down the path of restoring random database backups.

What's also interesting is that I do not seem to have any time machine config in the specified place:

cat /etc/netatalk/timemachine.conf

This file doesn't exist.

the /etc/netatalk/afp.conf refers to several other files:

include = /etc/frontview/netatalk/Shares.conf
include = /run/usb/netatalk/Shares.conf
include = /etc/netatalk/timemachine.conf

The first 2 files existed and, on a hunch, I touched the third one.

touch  /etc/netatalk/timemachine.conf

One reboot later and the NAS came back to life.

So there's a code bug here your developers should fix. But I'm back in business now.

Thanks!