

table_definition_cache(2097152) is upper than number of tables(984) Table cache hit rate: 99% (865 hits / 872 requests) Thread cache hit rate: 99% (10 created / 1K connections) Temporary tables created on disk: 87% (28K on disk / 32K total) Sorts requiring temporary tables: 0% (0 temp sorts / 40K sorts) Query cache is disabled by default due to mutex contention on multiprocessor machines. CPanel and Flex system skip-name-resolve should be on Highest usage of available connections: 6% (10/151) Overall possible memory usage with other process exceeded memory

Maximum possible memory usage: 45.1G (590.18% of installed RAM) Maximum reached memory usage: 3.4G (45.17% of installed RAM) Total buffers: 416.0M global + 302.3M per thread (151 max threads) Skipped due to -cvefile option undefined All database users have passwords assigned There are no anonymous accounts for any database users No stat updates during querying INFORMATION_SCHEMA. Data in InnoDB tables: 3.9G (Tables: 718) Status: +Aria +CSV +InnoDB +MEMORY +MRG_MyISAM +MyISAM +PERFORMANCE_SCHEMA +SEQUENCE 49 shutdown(s) detected in /var/log/mysqld.log 68 start(s) detected in /var/log/mysqld.log var/log/mysqld.log contains 2416 error(s). var/log/mysqld.log contains 7295 warning(s). Log file /var/log/mysqld.log is readable. Log file /var/log/mysqld.log is smaller than 32 Mb Log file /var/log/mysqld.log is not empty
#Mysql limit upgrade
Your MySQL version 10.2.43-MariaDB-log is EOL software! Upgrade soon! Skipped version check for MySQLTuner script

> Run with '-help' for additional options and output filtering > Bug reports, feature requests, and downloads at You may use the table method provided by the DB facade to begin a query.I'm trying to understand what is not working in my configuration. Therefore, you should never allow user input to dictate the column names referenced by your queries, including "order by" columns. PDO does not support binding column names. There is no need to clean or sanitize strings passed to the query builder as query bindings. The Laravel query builder uses PDO parameter binding to protect your application against SQL injection attacks. It can be used to perform most database operations in your application and works perfectly with all of Laravel's supported database systems. Laravel's database query builder provides a convenient, fluent interface to creating and running database queries.
