DB Error “Column ‘date’ cannot be null”
-
My feeds are showing up and working just fine, but…
I’m getting occasional HTTP 500 errors, and lots of errors like this in the debug log (which I assume are connected to the 500s? That’s what my host’s support suggested):
[19-Jun-2019 02:44:20 UTC] WordPress database error Column ‘date’ cannot be null for query INSERT INTO
wp_x3b2c2_wprss_logs(id,date,level,message,feed_id) VALUES (NULL, NULL, ‘info’, ‘Imported completed!’, ‘110’) made by do_action_ref_array(‘wprss_fetch_single_feed_hook’), WP_Hook->do_action, WP_Hook->apply_filters, wprss_fetch_insert_single_feed_items, Psr\Log\AbstractLogger->info, RebelCode\Wpra\Core\Logger\WpdbLogger->log, RebelCode\Wpra\Core\Database\WpdbTable->offsetSetAny help is greatly appreciated!!
-
Okay it’s actually tons of this error over and over again. And also some of this–
[22-Jun-2019 00:44:43 UTC] PHP Warning: A non-numeric value encountered in /home/rojavs/rojavs.dreamhosters.com/wp-includes/SimplePie/Parse/Date.php on line 694
These are my feed sources–
https://www.tandfonline.com/feed/rss/rfse20
https://www.tandfonline.com/feed/rss/rrse20Thanks!
Hi @markdigidigi,
The first error you are encountering is caused by our logging system when trying to save logs in the database. This error should not happen, but we can patch the plugin to mitigate any potential causes. What is the version of MySQL or MariaDB for your database?
The second error you are encountering harmless. It is unfortunately a bug in SimplePie, which is code that we use that comes bundled with WordPress. Unfortunately we cannot fix the issue, but we can at least catch the warnings to make sure they do not flood your error logs. We will include a patch for this in the next update of the plugin.
Hi Miguel, thanks for the reply. Here’s the info–
PHP 7.2.19 | Apache | MySQL 5.7.25-log
Do these errors explain why I was getting occasional HTTP 500 errors? Those stopped happening when I deactivated RSS Aggregator.
Hi @markdigidigi,
The database errors could be cause, but it’s hard to say. HTTP 500 errors are best diagnosed from your server’s error log (not to be confused with the request/access log). The other errors are very benign and harmless.
Your PHP, Apache and MySQL versions look fine, so we’re not sure why you are getting those database errors. If you know how, you can try deleting the table that our plugin uses for logging – it might solve your problem. The table is called “wp_wprss_logs”, but the “wp_” prefix might be different for you.
Hi Miguel,
Thanks.
I don’t know how to delete the table that the plugin uses for logging. How do I do that?
My server’s error log doesn’t show any errors.
Also, using the RSS validator, I do see that there may be some setup issues on the feeds I’m using.
*Realistically*, could these issues shown in the validator be causing those errors I sent above? And in turn causing the 500 error on my site?
Validator checks–
https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Fwww.tandfonline.com%2Ffeed%2Frss%2Frfse20
https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Fwww.tandfonline.com%2Ffeed%2Frss%2Frrse20Thanks!
Mark@markdigidigi I don’t think the RSS feeds not validating would cause 500 server errors. It’s most likely to do with the log table not being created correctly.
Can you try using the latest versions of the plugin? We’ve added options in the latest version to disable the plugin’s logging, which might solve your problem.
@mekku
Hi Miguel,Thanks, it seems to be a lot better!
I’m still having site performance issues though, and using Query Monitor a couple things are coming up as “Slow Queries” from WP RSS.
See this image — https://www.dropbox.com/s/mak7721apgc8m3l/Screen%20Shot%202019-07-21%20at%202.40.03%20PM.png?dl=0
And copying the text from that image below, with the “Caller” boxes expanded, in case you need that info.
Thank you!
Mark——–
SELECT option_value
FROM wp_g6xdeq_options
WHERE option_name = ‘wprss_settings_license_keys’
LIMIT 1
–
do_action(‘plugins_loaded’)
wp-includes/plugin.php:465
wpra_run()
wp-content/plugins/wp-rss-aggregator/wp-rss-aggregator.php:345
RebelCode\W\C\ModularModule->run()
wp-content/plugins/wp-rss-aggregator/src/ModularModule.php:89
RebelCode\W\C\M\LicensingModule->run()
wp-content/plugins/wp-rss-aggregator/src/Modules/LicensingModule.php:24
RebelCode\W\C\C\WpFilterContainer->get()
wp-content/plugins/wp-rss-aggregator/src/Container/WpFilterContainer.php:43
RebelCode\W\C\C\ModuleContainer->get()
wp-content/plugins/wp-rss-aggregator/src/Container/ModuleContainer.php:75
RebelCode\W\C\M\LicensingModule->RebelCode\W\C\M\{closure}()
wp-content/plugins/wp-rss-aggregator/src/Modules/LicensingModule.php:73
wprss_licensing_get_manager()
wp-content/plugins/wp-rss-aggregator/includes/licensing.php:27
Aventura\W\C\L\Manager->__construct()
wp-content/plugins/wp-rss-aggregator/includes/Aventura/Wprss/Core/Licensing/Manager.php:69
Aventura\W\C\L\Manager->_loadLicenses()
wp-content/plugins/wp-rss-aggregator/includes/Aventura/Wprss/Core/Licensing/Manager.php:691
Aventura\W\C\L\Manager->getLicenseKeysDbOption()
wp-content/plugins/wp-rss-aggregator/includes/Aventura/Wprss/Core/Licensing/Manager.php:749
get_option()
wp-includes/option.php:100CREATE TABLE IF NOT EXISTS
wp_g6xdeq_wprss_logs(idBIGINT NOT NULL AUTO_INCREMENT,dateTIMESTAMP DEFAULT CURRENT_TIMESTAMP,levelvarchar(30) NOT NULL,messagetext NOT NULL,feed_idvarchar(100), PRIMARY KEY (id) ) DEFAULT CHARACTER
SET utf8mb4 COLLATE utf8mb4_unicode_520_ci;
–
do_action(‘plugins_loaded’)
wp-includes/plugin.php:465
wpra_run()
wp-content/plugins/wp-rss-aggregator/wp-rss-aggregator.php:345
RebelCode\W\C\ModularModule->run()
wp-content/plugins/wp-rss-aggregator/src/ModularModule.php:89
RebelCode\W\C\M\LoggerModule->run()
wp-content/plugins/wp-rss-aggregator/src/Modules/LoggerModule.php:347
RebelCode\W\C\C\WpFilterContainer->get()
wp-content/plugins/wp-rss-aggregator/src/Container/WpFilterContainer.php:43
RebelCode\W\C\C\ModuleContainer->get()
wp-content/plugins/wp-rss-aggregator/src/Container/ModuleContainer.php:75
RebelCode\W\C\M\LoggerModule->RebelCode\W\C\M\{closure}()
wp-content/plugins/wp-rss-aggregator/src/Modules/LoggerModule.php:252
RebelCode\W\C\C\WpFilterContainer->get()
wp-content/plugins/wp-rss-aggregator/src/Container/WpFilterContainer.php:43
RebelCode\W\C\C\ModuleContainer->get()
wp-content/plugins/wp-rss-aggregator/src/Container/ModuleContainer.php:75
RebelCode\W\C\M\LoggerModule->RebelCode\W\C\M\{closure}()
wp-content/plugins/wp-rss-aggregator/src/Modules/LoggerModule.php:78
RebelCode\W\C\C\WpFilterContainer->get()
wp-content/plugins/wp-rss-aggregator/src/Container/WpFilterContainer.php:43
RebelCode\W\C\C\ModuleContainer->get()
wp-content/plugins/wp-rss-aggregator/src/Container/ModuleContainer.php:75
RebelCode\W\C\M\LoggerModule->RebelCode\W\C\M\{closure}()
wp-content/plugins/wp-rss-aggregator/src/Modules/LoggerModule.php:61
RebelCode\W\C\L\WpdbLogger->__construct()
wp-content/plugins/wp-rss-aggregator/src/Logger/WpdbLogger.php:98
RebelCode\W\C\D\WpdbTable->create()
The topic ‘DB Error “Column ‘date’ cannot be null”’ is closed to new replies.