Help In Fixing Generic PdoException Sqlstate Hy000 2006 Error

November 10, 2021 By Lawrence Scanlon Off

Table of Contents

In some cases, your system may display a generic pdoException sqlstate hy000 2006 error. This error can have several causes.

Recommended: Fortect

1. Download and install Fortect

2. Open the program and click "Scan"

3. Click "Repair" to start the repair process

Download this software and fix your PC in minutes.

Want

I dare – let’s say the problem is in wait_timeout . On my shared host it is set to the lowest bit 30, and on my local host it is 28800.

I found that I can cancel it for the session to generate a request: SET class wait_timeout = 28800

UPDATE The customer has determined that the dog needs to change the interactive_timeout variable as well. This may or may not work for everyone.

The following code shows the settings before and after the change to make sure they have been changed.

So, set wait_timeout = 28800 (and interactive_timeout 28800) = in addition, take care of the beginning of your request to see if it completed.

Recommended: Fortect

Are you tired of your computer running slowly? Is it riddled with viruses and malware? Fear not, my friend, for Fortect is here to save the day! This powerful tool is designed to diagnose and repair all manner of Windows issues, while also boosting performance, optimizing memory, and keeping your PC running like new. So don't wait any longer - download Fortect today!

1. Download and install Fortect

2. Open the program and click "Scan"

3. Click "Repair" to start the repair process

Don’t forget to provide your own DB credentials according to DB_SERVER, DB_USER, DB_PASS, DB_NAME

UPDATE If that works, you’ll also want to know what families are doing by setting a wider wait_timeout value. Tuning to 28800 is 1 hour and a lot.

They will probably follow on this side. He may recommend setting the wait_timeout to 300 – and I’ll try to get my results back (in a few weeks).

pdoexception sqlstate hy000 general error 2006

Variable wait_timeout represents the amount of time that MySQL is executing Wait before breaking the unproductive connection. By default wait_timeout Aspect is 28,800 seconds, which corresponds to 5 hours. It’s a lot.

I’ve read on great forums / blogs that wait_timeout is too small. (e.g. 30, 60, 90) can cause MySQL to stop sending error messages. So You need to solve this for your installation.

   query ("SHOW = VARIABLES LIKE '% timeout%'", TRUE);echo "";var_dump ($ results);echo "

";$ results = $ db-> query ("SET Tutorial wait_timeout = 28800", FALSE);// UPDATE - if necessary, this can also be described$ results = $ db-> query ("SET Sitting interactive_timeout = 28800", FALSE);$ results $ db-> query ("SHOW = VARIABLES LIKE '% timeout%'", TRUE);echo "";var_dump ($ results);echo "";Class database public $ mysqli; public function __construct () $ this-> mysqli = new mysqli (DB_SERVER, DB_USER, DB_PASS, DB_NAME); if (mysqli_connect_errno ()) Exit (); public service __destruct () $ this -> disable (); disabled ($ this-> mysqli); Disconnect () manifest function $ this-> mysqli-> close ();Request to complete the task ($ q, $ result set) / * expand prepared statement * / so if (! ($ stmt = $ this-> mysqli-> prepare ($ q))) echo ("sql error: inside. $ q. 'sql error #:'. $ this-> mysqli-> errno. wi - '. $ this-> mysqli-> error); Return is bad; / * Run the situation * / $ stmt-> execute (); if if ($ stmt-> errno) echo ("SQL error:". $ q. 'SQL error #: wi. $ stmt-> errno.' - i. $ stmt-> error); send badly; and if ($ result set) $ result = $ stmt-> get_result (); for ($ set matches array (); $ row = $ result-> fetch_assoc ();) $ set [] is equal to $ row; $ stmt-> close (); keep returning $ set;