The following error occurs during a MySQL database backup:
InnoDB: Operating system error number 24 in a file operation.
InnoDB: Error number 24 means ‘Too many open files’
InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
It is found that there are too many data files:
a total of 90811 data files.
View number of open files:
[root@localhost ~]# ulimit -Sn
1024
[root@localhost ~]# ulimit -Hn
4096
Description of this check command:
ulimit [-HSTabcdefilmnpqrstuvx [limit]]
Provides control over the resources available to the shell and to processes started by it, on systems that allow such control. The -H and -S options specify that the hard or soft
limit is set for the given resource. A hard limit cannot be increased by a non-root user once it is set; a soft limit may be increased up to the value of the hard limit.
-n The maximum number of open file descriptors (most systems do not allow this value to be set)
Query the maximum number of files opened by the operating system:
# cat /proc/sys/fs/nr_open
1048576
In the file/etc/security/limits Conf settings:
mysql hard nofile 65535
mysql soft nofile 65535
mysql hard nproc 65535
mysql soft nproc 65535
You can also replace MySQL with *
the problem of re backup is solved.
Read More:
- Es Container Error: too many open files [How to Solve]
- Error: Too many open files in system error [How to Solve]
- Linux system service command error: Failed to allocate directory watch: Too many open files
- [Solved] Linux Error: ENOSPC: System limit for number of file watchers
- [Solved] Linux Error: Error: ENOSPC: System limit for number of file watchers
- [Solved] Error: ENOSPC: System limit for number of file watchers reached
- [Solved] docker Error: System has not been booted with systemd as init system (PID 1). Can‘t operate. Failed to con
- System has not been booted with systemd as init system (PID 1). Can‘t operate
- Petalinux Failed to open PetaLinux lib: librdi_commonxillic.so: cannot open shared object file:
- Vmware virtual Mechine connect VScode Error: channel 3: open failed: administratively prohibited: open failed
- [Solved] libvirtd Error: virNetServerAddClient:271 : Too many active clients
- [Solved] FATAL CONFIG FILE ERROR: Bad directive or wrong number of arguments
- See system logs and ‘systemctl status docker.service‘ for details
- [Solved] mongo Startup Error: ERROR: child process failed, exited with error number 1
- Grep: How to Find All the Files Containing a String in Linux
- The Linux setroubleshootd process occupies too much memory [How to Solve]
- How to Solve Git Filename too long Error
- [Solved] Esxi Warning: System Management Software 1 SEL Fullness
- [Solved] Some index files failed to download.They have been ignored, or old ones used instead
- [Solved] Compose error “HTTP request took too long to complete“