ON DUPLICATE KEY UPDATE errors
-
Every visit is resulting in WP db errors in nginx error logs. An example:
2018/01/24 23:56:49 [error] 28343#0: *670105 FastCGI sent in stderr: “PHP message: WordPress database error Unknown column ‘entry_id’ in ‘where
clause’ for query SELECT allowed_entry + blocked_entry as cnt
FROMwp_spbc_firewall_logs
WHERE entry_id = ‘5ee3dbc141771099fc6c8a01cf57de47’; made by require(‘wp-blog-header.php’), require_once
(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), include_once(‘/plugins/security-malware-firewall/security-malwa
re-firewall.php’), SpbcFireWall->check_ip
PHP message: WordPress database error Unknown column ‘entry_id’ in ‘field list’ for query INSERT INTOwp_spbc_firewall_logs
(entry_id
,ip_entry
,entry_timestamp
,allowed_entry
,blocked_entry
,status
,page_url
,http_user_agent
, `
request_method,
x_forwarded_for`)
VALUES
(‘5ee3dbc141771099fc6c8a01cf57de47’, ‘174.78.249.18’, 1516838208, 1, 0, ‘PASS’, ‘https://www.neptunesystems.com/
?wc-ajax=get_refreshed_fragments’, ‘Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari
/537.36’, ‘POST’, ‘174.78.249.18’)
ON DUPLICATE KEY UPDATE
ip_entry = ip_entry,
entry_timestamp = 1516838208,
allowed_entry = allowed_entry + 1,
blocked_entry = blocked_entry + 0,
status = ‘PASS’,
page_url = ‘https://www.neptunesystems.com/?wc-ajax=get_refreshed_fragments’,
http_user_agent = http_user_agent,
request_method = ‘POST’,
x_forwarded_for = ‘174.78.249.18’ made by require(‘wp-blog-header.php’), require_once(‘wp” while reading respons
e header from upstream, client: 174.78.249.18, server: https://www.neptunesystems.com, request: “POST /?wc-ajax=get_refreshed_fragments HTTP/1.1”, upstr
eam: “fastcgi://unix:/var/run/php-fpm/php-fpm.sock:”, host: “www.neptunesystems.com”, referrer: “https://www.neptunesystems.com/products/apex-controllers/apex-controller-system/”WP/4.9.2
Security by CleanTalk/2.3
nginx/1.13.6
PHP-FPM/5.6Please assist/advise…
The page I need help with: [log in to see the link]
- The topic ‘ON DUPLICATE KEY UPDATE errors’ is closed to new replies.