catbreadbat Posted March 21, 2022 Share Posted March 21, 2022 Our log table is growing out of control, even with the pruning set to 1 week. Here's the message: Quote The log table core_log within the database is 179.71 GB in size. There is a repeated error (500 times) that seems to be the cause: Array ( [query] => Array ( [bool] => Array ( [must] => Array ( ) [must_not] => Array ( ) [filter] => Array ( [0] => Array ( [bool] => Array ( [should] => Array ( [0] => Array ( [terms] => Array ( [index_class] => Array ( [0] => IPS\core\Statuses\Status [1] => IPS\core\Statuses\Reply ) ) ) [1] => Array ( [terms] => Array ( [index_class] => Array ( [0] => IPS\forums\Topic\Post ) ) ) [2] => Array ( [terms] => Array ( [index_class] => Array ( [0] => IPS\downloads\File [1] => IPS\downloads\File\Comment [2] => IPS\downloads\File\Review ) ) ) [3] => Array ( [terms] => Array ( [index_class] => Array ( [0] => IPS\cms\Pages\PageItem ) ) ) [4] => Array ( [terms] => Array ( [index_class] => Array ( [0] => IPS\gallery\Image [1] => IPS\gallery\Image\Comment [2] => IPS\gallery\Image\Review ) ) ) [5] => Array ( [terms] => Array ( [index_class] => Array ( [0] => IPS\gallery\Album\Item [1] => IPS\gallery\Album\Comment [2] => IPS\gallery\Album\Review ) ) ) ) ) ) [1] => Array ( [bool] => Array ( [should] => Array ( [0] => Array ( [terms] => Array ( [index_class] => Array ( [0] => IPS\core\Statuses\Status ) ) ) [1] => Array ( [bool] => Array ( [must] => Array ( [0] => Array ( [terms] => Array ( [index_class] => Array ( [0] => IPS\forums\Topic\Post ) ) ) [1] => Array ( [term] => Array ( [index_is_last_comment] => 1 ) ) ) ) ) [2] => Array ( [terms] => Array ( [index_class] => Array ( [0] => IPS\downloads\File ) ) ) [3] => Array ( [terms] => Array ( [index_class] => Array ( [0] => IPS\cms\Pages\PageItem ) ) ) [4] => Array ( [terms] => Array ( [index_class] => Array ( [0] => IPS\gallery\Image ) ) ) [5] => Array ( [terms] => Array ( [index_class] => Array ( [0] => IPS\gallery\Album\Item ) ) ) ) ) ) [2] => Array ( [term] => Array ( [index_item_author] => ) ) [3] => Array ( [range] => Array ( [index_date_created] => Array ( [gt] => 0 ) ) ) [4] => Array ( [terms] => Array ( [index_permissions] => Array ( [0] => 3 [1] => m1252776 [2] => * ) ) ) [5] => Array ( [term] => Array ( [index_hidden] => 0 ) ) ) ) ) [sort] => Array ( [0] => Array ( [index_date_commented] => desc ) ) [from] => 0 [size] => 11 [error] => Array ( [root_cause] => Array ( [0] => Array ( [type] => illegal_argument_exception [reason] => field name is null or empty ) ) [type] => illegal_argument_exception [reason] => field name is null or empty ) ) Link to comment Share on other sites More sharing options...
catbreadbat Posted March 21, 2022 Author Share Posted March 21, 2022 The error was of type Elasticsearch. I cleared caches from admin CP and it seems to have stopped logging this error now. Will update if it spams the log again. Is it possible to clear these entries from the DB to reduce it's size in our backups? Link to comment Share on other sites More sharing options...
catbreadbat Posted March 21, 2022 Author Share Posted March 21, 2022 Clearing cache didn't fix the issue. I also tried rebuilding the search index and that hasn't fixed the error spam either. Link to comment Share on other sites More sharing options...
Luuuk Posted March 21, 2022 Share Posted March 21, 2022 Hi, 8 hours ago, catbreadbat said: Is it possible to clear these entries from the DB to reduce it's size in our backups? You can truncate the core_log table. I always do the operation when lots of errors are recorded. Link to comment Share on other sites More sharing options...
Marc Stridgen Posted March 21, 2022 Share Posted March 21, 2022 We would need to look further into this for you, however the access details on file appear to be incorrect or missing. Could you please update these details by visiting your client area, selecting the relevant purchase, then clicking "Review/Update Access Information" under the "Stored Access Information" section. We look forward to further assisting you. Link to comment Share on other sites More sharing options...
catbreadbat Posted March 21, 2022 Author Share Posted March 21, 2022 5 hours ago, Luuuk said: Hi, You can truncate the core_log table. I always do the operation when lots of errors are recorded. How to do this? 4 hours ago, Marc Stridgen said: We would need to look further into this for you, however the access details on file appear to be incorrect or missing. Could you please update these details by visiting your client area, selecting the relevant purchase, then clicking "Review/Update Access Information" under the "Stored Access Information" section. We look forward to further assisting you. I’ve updated the information. Link to comment Share on other sites More sharing options...
Luuuk Posted March 21, 2022 Share Posted March 21, 2022 1 hour ago, catbreadbat said: How to do this? You need to go to your SQL manager and deploy the command. Link to comment Share on other sites More sharing options...
Jim M Posted March 21, 2022 Share Posted March 21, 2022 I would suggest first starting off by updating all your third party applications/plugins there are some there too which are far outdated, like the Rules application. Please then check your ElasticSearch connection in ACP -> System -> Search. Then rebuild the search index on the same page. If you're still having this error logged, please let us know. If it is resolved, please have your hosting provider truncate the table. Link to comment Share on other sites More sharing options...
catbreadbat Posted March 21, 2022 Author Share Posted March 21, 2022 1 hour ago, Jim M said: I would suggest first starting off by updating all your third party applications/plugins there are some there too which are far outdated, like the Rules application. Please then check your ElasticSearch connection in ACP -> System -> Search. Then rebuild the search index on the same page. If you're still having this error logged, please let us know. If it is resolved, please have your hosting provider truncate the table. The rules application is disabled and not in use. I’ve disabled all hooks loaded by the error, and rebuilt the search index yet again. Issue persists Link to comment Share on other sites More sharing options...
Jim M Posted March 21, 2022 Share Posted March 21, 2022 2 hours ago, catbreadbat said: The rules application is disabled and not in use. I’ve disabled all hooks loaded by the error, and rebuilt the search index yet again. Issue persists While I understand that, some background processes may still be influenced by disabled applications which is why uninstalling unused or outdated applications may be in your favor here. Link to comment Share on other sites More sharing options...
catbreadbat Posted March 21, 2022 Author Share Posted March 21, 2022 (edited) 16 minutes ago, Jim M said: While I understand that, some background processes may still be influenced by disabled applications which is why uninstalling unused or outdated applications may be in your favor here. I have removed that application and all other unused ones and the issue persists. Edited March 21, 2022 by catbreadbat Link to comment Share on other sites More sharing options...
Jim M Posted March 21, 2022 Share Posted March 21, 2022 Thank you. I have moved this to a ticket so that we can investigate this more in depth. You will receive further correspondence by email. Link to comment Share on other sites More sharing options...
Recommended Posts