David Tingen Posted May 22 Share Posted May 22 In my panel I get a notification of an error: Repeated log entries. Our hosting service has already repaired the database, but the error continues to appear. Can you help me solve this problem please. This is the error that the notification shows: Reoccurring system log entries may be indicative of a problem that should be addressed. A summary of the top reoccurring recent log entries are shown below. Review the system log for further details. Message Count INSERT INTO `iBBS_core_view_updates` ( `classname`, `id` ) VALUES ( 'IPS\forums\Forum', 1 ) IPS\Db\Exception: Duplicate entry 'IPS\forums\Forum-1' for key 'classname_and_id' (1062) #0 /home/chapala/public_html/webboard/system/Db/Db.php(941): IPS\_Db->preparedQuery('/*chapala_chapa...', Array) #1 /home/chapala/public_html/webboard/system/Content/ViewUpdates.php(50): IPS\_Db->insert('core_view_updat...', Array) #2 /home/chapala/public_html/webboard/applications/forums/modules/front/forums/forums.php(113): IPS\forums\_Forum->updateViews() #3 /home/chapala/public_html/webboard/applications/forums/modules/front/forums/forums.php(38): IPS\forums\modules\front\forums\_forums->_forum(Object(IPS\forums\Forum)) #4 /home/chapala/public_html/webboard/system/Dispatcher/Controller.php(118): IPS\forums\modules\front\forums\_forums->manage() #5 /home/chapala/public_html/webboard/system/Dispatcher/Dispatcher.php(153): IPS\Dispatcher\_Controller->execute() #6 /home/chapala/public_html/webboard/index.php(13): IPS\_Dispatcher->run() #7 {main} 112 SELECT classname, id, count(*) AS count FROM `iBBS_core_view_updates` AS `core_view_updates` GROUP BY `classname`,`id` LIMIT 20 Table './chapala_chapala_com_new/iBBS_core_view_updates' is marked as crashed and should be repaired 62 Link to comment Share on other sites More sharing options...
Jim M Posted May 22 Share Posted May 22 Your hosting provider will need to review why the table keeps crashing if they keep repairing it and it keeps crashing. A duplicate entry error would not cause the table to crash. Link to comment Share on other sites More sharing options...
David Tingen Posted May 22 Author Share Posted May 22 Hi Jim: This is what our hosting answered: “To avoid this from happening, it would be the best to optimize the database : https://www.hostgator.com/help/article/how-to-optimize-a-mysql-database-using-phpmyadmin And for these tables (if applicable/possible) you might consider creating indexes for because they're over 100,000 rows: 104435 iBBS_core_statistics MyISAM 115772 iBBS_forums_posts MyISAM 127764 iBBS_core_search_index MyISAM 130392 iBBS_core_moderator_logs MyISAM 152086 iBBS_core_members_logins InnoDB 157279 iBBS_core_reputation_index MyISAM 285939 iBBS_core_members_known_ip_addresses MyISAM 296175 iBBS_forums_archive_posts MyISAM Please know that this is not part of our scope of support and you will need an expert to do this on your behalf if not familiar” We have already optimized the database. From the other suggestion, would it help if we deleted the content from past years? And if so, How could we do it? If deleting content doesn't help, Do you have someone you recommend to do this job? Link to comment Share on other sites More sharing options...
Jim M Posted May 22 Share Posted May 22 It's worth noting that around 100,000 rows is not a lot. We have clients in the millions for these tables and they function perfectly fine with with our same table configuration that you have. You may wish to move all tables from MyISAM to InnoDB. However, if the table keeps crashing, this is something the hosting provider will need to analyze with their MySQL server configuration on why that is. Link to comment Share on other sites More sharing options...
David Tingen Posted May 22 Author Share Posted May 22 30 minutes ago, Jim M said: It's worth noting that around 100,000 rows is not a lot. We have clients in the millions for these tables and they function perfectly fine with with our same table configuration that you have. You may wish to move all tables from MyISAM to InnoDB. However, if the table keeps crashing, this is something the hosting provider will need to analyze with their MySQL server configuration on why that is. How can I move all the tables from MyISAM to InnoDB? Link to comment Share on other sites More sharing options...
Jim M Posted May 22 Share Posted May 22 1 minute ago, David Tingen said: How can I move all the tables from MyISAM to InnoDB? You would want to ask your hosting provider. This is a server administrator task rather than a software task. Link to comment Share on other sites More sharing options...
Stuart Silvester Posted May 22 Share Posted May 22 It's also worth noting that the core_view_updates table should not have a unique index or primary key on it (the cause of that duplicate entry error). If you go to admin > support, you may get some database issues flagged up. Link to comment Share on other sites More sharing options...
David Tingen Posted May 25 Author Share Posted May 25 On 5/22/2024 at 3:04 PM, Stuart Silvester said: It's also worth noting that the core_view_updates table should not have a unique index or primary key on it (the cause of that duplicate entry error). If you go to admin > support, you may get some database issues flagged up. Hi Stuart Our Hosting service has already repaired the database, but the error notification continues to appear. Can you go to our forum and see what the problem is, please? Attached I send the images of the support section of our panel. Link to comment Share on other sites More sharing options...
David Tingen Posted May 25 Author Share Posted May 25 11 minutes ago, David Tingen said: Hi Stuart Our Hosting service has already repaired the database, but the error notification continues to appear. Can you go to our forum and see what the problem is, please? Attached I send the images of the support section of our panel. This is the error from today in the system logs: System Logs 403 invalid_api_key Array 2 hours ago The URL of page the error occurred on was Not available #0 /home/chapala/public_html/webboard/applications/core/sources/IndexNow/IndexNow.php(117): IPS\_Log::log('403 invalid_api...', 'IndexNow') #1 /home/chapala/public_html/webboard/applications/core/extensions/core/Queue/IndexNow.php(57): IPS\core\_IndexNow->send(Array) #2 /home/chapala/public_html/webboard/system/Task/Task.php(54): IPS\core\extensions\core\Queue\_IndexNow->run(Array, 0) #3 /home/chapala/public_html/webboard/applications/core/tasks/queue.php(43): IPS\_Task::runQueue() #4 /home/chapala/public_html/webboard/system/Task/Task.php(382): IPS\core\tasks\_queue->IPS\core\tasks\{closure}() #5 /home/chapala/public_html/webboard/applications/core/tasks/queue.php(55): IPS\_Task->runUntilTimeout(Object(Closure)) #6 /home/chapala/public_html/webboard/system/Task/Task.php(281): IPS\core\tasks\_queue->execute() #7 /home/chapala/public_html/webboard/system/Task/Task.php(244): IPS\_Task->run() #8 /home/chapala/public_html/webboard/applications/core/interface/task/task.php(72): IPS\_Task->runAndLog() #9 {main} Link to comment Share on other sites More sharing options...
Marc Posted May 28 Share Posted May 28 Please ensure you perform the actions mentioned on the mysql section, then test this again Link to comment Share on other sites More sharing options...
David Tingen Posted June 7 Author Share Posted June 7 Hi Marc We already updated the database to version 8, we also already changed the database tables to InnoDB, but the error notifications continue to appear in our administration panel. Can you check what the problem is, please? Link to comment Share on other sites More sharing options...
Jim M Posted June 7 Share Posted June 7 You would need to click the “Fix This” button to see what else it is seeing as non-Innodb Link to comment Share on other sites More sharing options...
David Tingen Posted June 7 Author Share Posted June 7 30 minutes ago, Jim M said: You would need to click the “Fix This” button to see what else it is seeing as non-Innodb Sorry it was the wrong image. There is only the Logs error. We already checked and there are no damaged tables in the database. Can you check our forum please? Link to comment Share on other sites More sharing options...
Jim M Posted June 7 Share Posted June 7 If there are no logs in the System Logs from recently then you can ignore that warning telling you that there are repeating entries. Link to comment Share on other sites More sharing options...
David Tingen Posted June 7 Author Share Posted June 7 17 minutes ago, Jim M said: If there are no logs in the System Logs from recently then you can ignore that warning telling you that there are repeating entries. We have some errors in the System Logs. I send you the screenshot with today's errors. Link to comment Share on other sites More sharing options...
Jim M Posted June 8 Share Posted June 8 That too seems to have subsided now that you are on the recent release and IndexNow API key has been updated (that error shouldn't cause issues on the frontend). There are now system errors as of now. Link to comment Share on other sites More sharing options...
Recommended Posts