Good morning everyone ReadyNAS 314Firmare 6.10.5 Hotfix 1 Installed apps:MySQLDB 1.0.5 from ReadyNAS XtrasNextcloud 20.0.1-rnx1 from ReadyNAS XtrasPHP7.4 from ReadyNAS XtrasPHPMyAdmin 4 from ReadyNAS Xtras This morning I woke up to this annoying error. MySQLDB turned itself off and will no longer start. "The app failed to start, Please update or contact developer. Code 22002010000" I see in this thread https://community.netgear.com/t5/ReadyNAS-Storage-Apps-Current/MYSQL/m-p/1113575 that the answer is to "bind address to my IP but after changing it back to 127.0.0.1 it is now back working." Unfortunately, I've no idea how to do that. I've e-mailed ReadyNAS Xtras for help but they did not respond yet. If anyone could help I'd be greatful.

BuckoA512 wrote: I see in this thread https://community.netgear.com/t5/ReadyNAS-Storage-Apps-Current/MYSQL/m-p/1113575 that the answer is to "bind address to my IP but after changing it back to 127.0.0.1 it is now back working." Not quite. The original poster was saying that he had changed the binding to his IP address, but that changing it back to 127.0.0.1 resolved his problem. It's a 5 year-old thread, and it is possible that your problem is caused by something different. In any event, that setting should be in /etc/mysql/my.cnf It's conceivable it's in a different folder - if so, mysqld --help --verbose should find it. Note you need to use ssh. Did this happen immediately after you updated to 6.10.5?

Hi StephenB thank you for replying.I've never had to ssh since my university days so I'm a little rusty on that to say the least.No, it didn't happen right after I updated. Everything was working fine yesterday, then today this happens and MySQLDB won't start. ReadyNAS Xtras has replied to me by e-mail too so I'll update if he can figure anything out.

It looks like the failure is down to a bad disk in the array, or so it seems from the logs. I didn't realise that downloading the logs gave you more information than you get on the web page. Aug 31 10:13:48 ReadyNAS mysqld[6853]: 2021-08-31 10:13:48 7fd324f26780 InnoDB: Error: Write to file ./nextcloud/oc_filecache.ibd failed at offset 25690112.Aug 31 10:13:48 ReadyNAS mysqld[6853]: InnoDB: 8192 bytes should have been written, only 0 were written.Aug 31 10:13:48 ReadyNAS mysqld[6853]: InnoDB: Operating system error number 5.Aug 31 10:13:48 ReadyNAS mysqld[6853]: InnoDB: Check that your OS and file system support files of this size.Aug 31 10:13:48 ReadyNAS mysqld[6853]: InnoDB: Check also that the disk is not full or a disk quota exceeded.Aug 31 10:13:48 ReadyNAS mysqld[6853]: InnoDB: Error number 5 means 'Input/output error'.Aug 31 10:13:48 ReadyNAS mysqld[6853]: InnoDB: Some operating system error numbers are described atAug 31 10:13:48 ReadyNAS mysqld[6853]: InnoDB: (link removed)Aug 31 10:13:48 ReadyNAS mysqld[6853]: 2021-08-31 10:13:48 7fd324f26780 InnoDB: Operating system error number 5 in a file I thought if a bad disk was detected the ReadyNAS would alert me via notiifcation, rather surprised that it didn't.

BuckoA512 wrote: It looks like the failure is down to a bad disk in the array, or so it seems from the logs. I didn't realise that downloading the logs gave you more information than you get on the web page. Aug 31 10:13:48 ReadyNAS mysqld[6853]: 2021-08-31 10:13:48 7fd324f26780 InnoDB: Error: Write to file ./nextcloud/oc_filecache.ibd failed at offset 25690112. Aug 31 10:13:48 ReadyNAS mysqld[6853]: InnoDB: 8192 bytes should have been written, only 0 were written. Not convinced it's a failed disk, though is it clearly a failed write. How full is your OS partition (root)? You can see this by looking at volume.log - scroll down to the df -h section, and look at the /dev/md0 line. === df -h === Filesystem Size Used Avail Use% Mounted on udev 10M 4.0K 10M 1% /dev /dev/md0 4.0G 524M 3.2G 15% / Similarly, how full is your data volume?

=== df -h === Filesystem Size Used Avail Use% Mounted on udev 10M 4.0K 10M 1% /dev /dev/md0 4.0G 2.1G 1.6G 58% /ReadyNAS data has 4.40tb free space. It has 4 x 3tb drives in Xraid.

MySQLDB will not start code 22002010000

17 Replies

Replies have been turned off for this discussion

StephenB
Guru - Experienced User
Aug 31, 2021
BuckoA512 wrote:

I see in this thread https://community.netgear.com/t5/ReadyNAS-Storage-Apps-Current/MYSQL/m-p/1113575 that the answer is to "bind address to my IP but after changing it back to 127.0.0.1 it is now back working."

Not quite. The original poster was saying that he had changed the binding to his IP address, but that changing it back to 127.0.0.1 resolved his problem. It's a 5 year-old thread, and it is possible that your problem is caused by something different. In any event, that setting should be in /etc/mysql/my.cnf It's conceivable it's in a different folder - if so, mysqld --help --verbose should find it. Note you need to use ssh.

Did this happen immediately after you updated to 6.10.5?
- BuckoA512
  Aspirant
  Aug 31, 2021
  Hi StephenB thank you for replying.
  I've never had to ssh since my university days so I'm a little rusty on that to say the least.
  No, it didn't happen right after I updated. Everything was working fine yesterday, then today this happens and MySQLDB won't start.
  
  ReadyNAS Xtras has replied to me by e-mail too so I'll update if he can figure anything out.
  - BuckoA512
    Aspirant
    Aug 31, 2021
    It looks like the failure is down to a bad disk in the array, or so it seems from the logs. I didn't realise that downloading the logs gave you more information than you get on the web page.
    
    Aug 31 10:13:48 ReadyNAS mysqld[6853]: 2021-08-31 10:13:48 7fd324f26780 InnoDB: Error: Write to file ./nextcloud/oc_filecache.ibd failed at offset 25690112.
    Aug 31 10:13:48 ReadyNAS mysqld[6853]: InnoDB: 8192 bytes should have been written, only 0 were written.
    Aug 31 10:13:48 ReadyNAS mysqld[6853]: InnoDB: Operating system error number 5.
    Aug 31 10:13:48 ReadyNAS mysqld[6853]: InnoDB: Check that your OS and file system support files of this size.
    Aug 31 10:13:48 ReadyNAS mysqld[6853]: InnoDB: Check also that the disk is not full or a disk quota exceeded.
    Aug 31 10:13:48 ReadyNAS mysqld[6853]: InnoDB: Error number 5 means 'Input/output error'.
    Aug 31 10:13:48 ReadyNAS mysqld[6853]: InnoDB: Some operating system error numbers are described at
    Aug 31 10:13:48 ReadyNAS mysqld[6853]: InnoDB: (link removed)
    Aug 31 10:13:48 ReadyNAS mysqld[6853]: 2021-08-31 10:13:48 7fd324f26780 InnoDB: Operating system error number 5 in a file
    
    I thought if a bad disk was detected the ReadyNAS would alert me via notiifcation, rather surprised that it didn't.

Forum Discussion

MySQLDB will not start code 22002010000

17 Replies

Related Content

Getting Started - Registration

Frequency start Value

My CAX80 started acting up

MySQL starting problem - error code: 22002010000

MySQL starting problem - error code: 22002010000

NETGEAR Academy

ProSupport for Business