SQLSTATE[HY000] [2002] Connection refused (Connection: mysql, SQL: select name, payload from `se...

[jobara]

Illuminate\Database\QueryException

SQLSTATE[HY000] [2002] Connection refused (Connection: mysql, SQL: select name, payload from settings where group = general)

🎯 Illuminate\Database\Connection::runQueryCallback
📄 /vendor/laravel/framework/src/Illuminate/Database/Connection.php

820   }
821   
822*  throw new QueryException(
823       $this->getName(), $query, $this->prepareBindings($bindings), $e
824   );

Open in Flare

[marvinroman]

@JureUrsic can you help me resolve the following error so we can have MySQL slow logging on the container?

Could not use /opt/bitnami/mysql/logs/mysqld.log for logging (error 2 - No such file or directory). Turning logging off for the server process. To turn it on again: fix the cause, then either restart the query logging by using "SET GLOBAL SLOW_QUERY_LOG=ON" or restart the MySQL server.

[jobara]

See @marvinroman's comment #2131 (comment)

[jobara]

As @marvinroman mentioned this occurs during a database reset. In particular we are seeing this on the dev site during the nightly refresh when the site is being hit by the health check. It's probably because the 503 error page returned when the site is in maintenance mode includes the footer. The footer populates contact information from the settings which are stored in the database. Of course during a database reset this table is dropped and recreated, hence the error.

A few possible solutions to try:

• pre-render the 503 error page when going into maintenance mode
• see if we can check the table's existence before trying to access the settings in the settings helper function
• remove the footer from the 503 error page