Error writing value to wfsd_engine (MySQLi error: [2006] MySQL server has gone a

Hi @raizq, thanks for reaching out!

We’ve seen this before and when looking at customer diagnostics, the MySQL server has gone away error has been a symptom of the database server restarting/crashing and starting up again automatically.

Running out of memory can be a cause for this happening. If the database server is crashing or running out of memory, yet your plugins (including Wordfence) are up-to-date, your server admin or host should be able to diagnose and resolve the problem for you. This can be a problem with sites on shared servers where another site is to blame for the loss of memory, affecting yours – but is not limited to that kind of setup. The server logs referenced for the error could provide some insight into what precisely caused the database issue.

Thanks,
Peter.

Hi Peter!

I contacted my hosting and there is no problem. I did a test by changing the scan mode from custom to high sensitivity and it performed the scan normally. The issue occurs in custom scan mode.

Hi @raizq, that’s certainly interesting information as I’ve not seen a connection between this type of failure and which scan is chosen.

When making a custom scan, could you possibly do the following for me so I can see what was being attempted when the error occurred?

• Go to the Wordfence > Tools > Diagnostics page
• In the “Debugging Options” section check the circle “Enable debugging mode” 
• Click to “Save Changes”.
• CANCEL any current scan and start a NEW scan
• Copy the last 20 lines from the Log (click the “Show Log” link) or so of the activity log once the scan finishes and paste them in this post.

Wordfence > Tools > Diagnostic > Debugging Screenshot

Thanks again,
Peter.

Hi @raizq,

I just found your diagnostic report in our inbox when checking the status of this topic. Whilst useful to see that your permissions, connectivity, IP detection and firewall optimization seem good, there are 0 scan issues displayed as if a successful scan had been completed.

I would need the instructions given above to be followed in order to see a scan stage at which they’re failing in conjunction with the diagnostic report as the status of your site suggests that everything should be working as expected.

As both IPv4 and IPv6 seem to be operational on your site, try setting the checkbox for?Use only IPv4 to start scans from Wordfence > All Options > Advanced Scan Options, saving, then try another scan before pasting me the log information.

Thanks again,
Peter.

Hi
Getting the same error on our WF installation.

• This reply was modified 10 months ago by mferraz.

Next the log we get:

• [Feb 02 02:32:51] Analyzed 44300 files containing 817.15 MB of data so far
• [Feb 02 02:32:52] Analyzed 44400 files containing 817.8 MB of data so far
• [Feb 02 02:32:53] Analyzed 44500 files containing 818.2 MB of data so far
• [Feb 02 02:32:54] Analyzed 44600 files containing 818.45 MB of data so far
• [Feb 02 02:32:56] Analyzed 44700 files containing 820.41 MB of data so far
• [Feb 02 02:32:57] Analyzed 44800 files containing 820.78 MB of data so far
• [Feb 02 02:32:58] Analyzed 44900 files containing 822.25 MB of data so far
• [Feb 02 02:32:59] Analyzed 45000 files containing 822.46 MB of data so far
• [Feb 02 02:33:00] Analyzed 45100 files containing 822.73 MB of data so far
• [Feb 02 02:33:01] Analyzed 45200 files containing 825.49 MB of data so far
• [Feb 02 02:33:03] Analyzed 45300 files containing 826.36 MB of data so far
• [Feb 02 02:33:04] Analyzed 45400 files containing 827.22 MB of data so far
• [Feb 02 02:33:05] Analyzed 45500 files containing 827.92 MB of data so far
• [Feb 02 02:33:06] Analyzed 45600 files containing 828.78 MB of data so far
• [Feb 02 02:35:42] Error writing value for wfsd_engine (MySQLi error: [2006] MySQL server has gone away)
• [Feb 02 15:33:43] Scan stop request received.
• [Feb 02 15:59:12] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=7c1843a296c0cd842d2ca93e0dc353a6a289852a21b668ed077b9aedb107f348&s=eyJ3cCI6IjYuNC4zIiwid2YiOiI3LjExLjEiLCJtcyI6IjE5NyIsImgiOiJodHRwczpcL1wvd3AudXAucHQiLCJzc2x2Ijo4MDUzMDY0MDAsInB2IjoiOC4yLjE1IiwicHQiOiJhcGFjaGUyaGFuZGxlciIsImN2IjoiNy44MS4wIiwiY3MiOiJPcGVuU1NMXC8zLjAuMiIsInN2IjoiQXBhY2hlIiwiZHYiOiIxMC42LjE2LU1hcmlhREItMHVidW50dTAuMjIuMDQuMSIsImxhbmciOiJwdF9QVCJ9&action=timestamp
• [Feb 02 16:00:24] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=7c1843a296c0cd842d2ca93e0dc353a6a289852a21b668ed077b9aedb107f348&s=eyJ3cCI6IjYuNC4zIiwid2YiOiI3LjExLjEiLCJtcyI6IjE5NyIsImgiOiJodHRwczpcL1wvd3AudXAucHQiLCJzc2x2Ijo4MDUzMDY0MDAsInB2IjoiOC4yLjE1IiwicHQiOiJhcGFjaGUyaGFuZGxlciIsImN2IjoiNy44MS4wIiwiY3MiOiJPcGVuU1NMXC8zLjAuMiIsInN2IjoiQXBhY2hlIiwiZHYiOiIxMC42LjE2LU1hcmlhREItMHVidW50dTAuMjIuMDQuMSIsImxhbmciOiJwdF9QVCJ9&action=timestamp
• [Feb 02 16:07:18] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=7c1843a296c0cd842d2ca93e0dc353a6a289852a21b668ed077b9aedb107f348&s=eyJ3cCI6IjYuNC4zIiwid2YiOiI3LjExLjEiLCJtcyI6IjE5NyIsImgiOi

I have this same error. I cancelled the scan. Enabled Debugging and now it says Scan Stop Request Received literally as soon as I click the scan button. It runs for maybe 1 millisecond.