pixeldude Posted January 10, 2023 Share Posted January 10, 2023 Hello, I'm getting this background task error after the upgrade to 4.7.5:Â 1S111/1 BIGINT UNSIGNED value is out of range in '`schq_prd`.`core_solved_index`.`solved_date` - `schq_prd`.`forums_topics`.`start_date`' Seems a substraction is causing this error, what can I do to solve this? Thanks! Link to comment Share on other sites More sharing options...
Marc Posted January 11, 2023 Share Posted January 11, 2023 You have an issue with a 3rd party item there. The column in question is actually not one of ours. Link to comment Share on other sites More sharing options...
pixeldude Posted January 11, 2023 Author Share Posted January 11, 2023 Hi Marc, Do you mean solved_date in table core_solved_index has been added by a 3rd party item? The error persists even when disabling all 3rd party items and a background task is stuck on one specific forum with "Rebuilding solved statistics for forum [name]" Error log is flooded with : SELECT AVG(core_solved_index.solved_date-forums_topics.start_date) FROM `forums_topics` LEFT JOIN `core_solved_index` ON core_solved_index.app='forums' AND core_solved_index.item_id=forums_topics.tid WHERE ( state NOT IN('link','merged') ) AND ( approved NOT IN(-2,-3) ) AND forum_id=25 AND start_date > 1390911377 AND start_date < 1396051140 AND core_solved_index.id IS NOT NULL BIGINT UNSIGNED value is out of range in '`schq_prd`.`core_solved_index`.`solved_date` - `schq_prd`.`forums_topics`.`start_date`' The forum in question is of type "discussion", so why is the system even querying for solved dates? Link to comment Share on other sites More sharing options...
Marc Posted January 12, 2023 Share Posted January 12, 2023 Sorry, that was actually my mistake. Taking a look at this now for you, and may well need to get this escalated. Link to comment Share on other sites More sharing options...
Marc Posted January 12, 2023 Share Posted January 12, 2023 I have created a ticket so that we can look into this further for you pixeldude 1 Link to comment Share on other sites More sharing options...
Solution pixeldude Posted February 7, 2023 Author Solution Share Posted February 7, 2023 It was a small glitch in the database, which was corrected by invision support. Thanks! Link to comment Share on other sites More sharing options...
Jim M Posted February 7, 2023 Share Posted February 7, 2023 Glad to hear your issue is resolved 🙂 Link to comment Share on other sites More sharing options...
Recommended Posts