Commands out of sync

Resolved

(@swissspaceboy)

Again this error like many other people. Strangely, this is 99% with the WF plugin. I have >50 other plugins running, and none give this out of sync database error. All seems to be running fine. Live traffic is enabled. The table wfblocks7 is repaired.

I have no pattern to reproduce this.

Any fix is in the roadmap for this? Catch the error and do a retry?

WordPress database error Commands out of sync; you can't run this command now for query SHOW FULL COLUMNS FROM ctn_wfhits made by wfLog->logHit, wfRequestModel->save, wfModel->save, wfModel->insert

WordPress database error Commands out of sync; you can't run this command now for query SELECT *, CASE 
WHEN type = 3 THEN 0
WHEN type = 4 THEN 1
WHEN type = 7 THEN 2
WHEN type = 6 THEN 3
WHEN type = 5 THEN 4
WHEN type = 9 THEN 5
WHEN type = 8 THEN 6
WHEN type = 2 THEN 7
WHEN type = 1 THEN 8
ELSE 9999
END AS typeSort, CASE 
WHEN type = 3 THEN parameters
WHEN type = 4 THEN parameters
WHEN type = 1 THEN IP
WHEN type = 9 THEN IP
WHEN type = 5 THEN IP
WHEN type = 6 THEN IP
WHEN type = 7 THEN IP
WHEN type = 2 THEN IP
WHEN type = 8 THEN IP
ELSE 9999
END AS detailSort
 FROM ctn_wfblocks7 WHERE type IN (4) AND (expiration = 0 OR expiration > UNIX_TIMESTAMP()) ORDER BY typeSort ASC, id DESC made by wfShutdownRegistry->handleShutdown, wfShutdownFunction->invoke, wfWAFIPBlocksController::synchronizeConfigSettings, wfBlock::patternBlocks, wfBlock::allBlocks

Didier.

Viewing 4 replies - 1 through 4 (of 4 total)

Plugin Support wfpeter
(@wfpeter)

2 years, 11 months ago

Hi @swissspaceboy, thanks for getting in touch.

As you may have seen with the other topics regarding this error, we do genuinely see other plugin tables affected by the same error in customer error logs we have been sent when investigating it.

If you have WP-CLI you can run a query like
wp db query ‘\s’
…which should show you the database server’s uptime. The same can be done on the MySQL command line by just typing \s. In a couple cases reported to us where users had the access to do this, they did find that the database server had recently restarted when they saw these errors.

We’re always open to trying to combat problems from our end when possible, so if your host is willing to send us logs, including mysql/mariadb logs and the syslog, we may be able to help determine the cause. The reason we’d need these is due to a ‘commands out of sync’ error not being the cause, but rather side-effects of the database getting disconnected.

Let us know what you find out!
Peter.

Thread Starter swissspaceboy
(@swissspaceboy)

2 years, 11 months ago

Hi Peter,

Thanks for the reply. I have seen this error with other plugins too, but mostly with WF. I have no CLI access, but I can see how long the database is running via phpmyadmin. The next time I will check the timestamp of one error and eventual database restart.

I fully understand that the problem is caused by a database connection loss. In this case, as not much can be done from a database or end user POV, this error could be catched from application POV. Why do not a retry of the request if it has failed?…

I’ll try to provide some more info, but I don’t have much access as I am on a shared server.

Didier.
Thread Starter swissspaceboy
(@swissspaceboy)

2 years, 10 months ago
I am back.

So 3 errors on 2 different sites/databases but all on the same sql server. mariaDB is running since 08 June, and I have errors with table wfblocks on 15 and 16 June. So the database restart is not the problem. I see some problems with connections in the ‘Advisor’ log:
- 8% of all connections are aborted. This value should be below 1%
- Aborted connections rate is at 23.49 per minute, this value should be less than 1 per hour
- Aborted client rate is at 4.84 per hour, this value should be less than 1 per hour
No idea what this means and what I can do about it…

That’s all for now.

Didier.
Plugin Support wfpeter
(@wfpeter)

2 years, 10 months ago

Thanks for your follow-up and your other topic stating that the 7.10.0 release has somewhat helped with these. As stated there, we will continue to look into any detailed log reports of this issue since that version and if any further improvements can be made from our side, we will do so.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Commands out of sync’ is closed to new replies.