By default is seems the soft and hard open files limits on MariaDB in CentOS 7 are 1024 and 4096 respectfully. You can see these limits by first getting the process ID:
Shell
1
cat/var/run/mariadb/mariadb.pid
And then looking at the limits in the proc filesystem:
Shell
1
cat/proc/XXXXX/limits
You’ll see something like this:
Shell
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
[root@web1~]# cat /proc/7688/limits
Limit Soft Limit Hard Limit Units
Max cpu timeunlimited unlimited seconds
Max filesize unlimited unlimited bytes
Max data size unlimited unlimited bytes
Max stack size8388608unlimited bytes
Max core filesize0unlimited bytes
Max resident set unlimited unlimited bytes
Max processes3120931209processes
Max open files10244096files
Max locked memory6553665536bytes
Max address space unlimited unlimited bytes
Max filelocks unlimited unlimited locks
Max pending signals3120931209signals
Max msgqueue size819200819200bytes
Max nicepriority00
Max realtime priority00
Max realtime timeout unlimited unlimited us
Notice the numbers for “Max open files”.
If you run into problems with MariaDB failing and you see errors like this in the log:
1
[ERROR]Error inaccept:Too many open files
Then you need to increase the open files limits by editing:
The CanaKit comes with a pre-loaded SD card that includes the same version of Debian Wheezy that I used for this project. However, in an effort to get a little more speed out of the system, I used the 95MB/s Sandisk extreme listed above. It seemed to help, but I did not bench mark it beyond observation.
Anyway, lets get down to building a Raspberry Pi Web Kiosk.