Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I had an instance where I think my stats were too much and an error was showing in logs saying
"Last cron run did not complete."
So I flushed out the logs by changing the logs duration in settings - running cron again without the browscap then reapplied everything - and then that worked.
Comments
Comment #1
mikeryanIs there a specific browscap issue here? The logs don't really have anything to do with updating the browscap data... If garykeith.com is unavailable or slow, then the attempted browscap update might fail to complete, but there's not a lot the browscap module can do about that.
Comment #2
Marco Palmero commentedI think it timed out - it could be due to the server config settings... and when a php operation goes for too long to save memory it cuts it short.
I'm not really a coder so i was thinking that - perhaps the code could be written - if the past data is so large to recommend the user flush out the old cache. Or if the old data is important - process the data in batches?
Or probably this is too much trouble to bother?
Comment #3
deekayen commentedSounds to me like this is really a feature request to be able to process logs in chunks like the core search cron does.
Comment #4
mikeryanBut the browscap cron hook doesn't have anything to do with any logs. As I said, if garykeith.com is down or slow that would impact the cron hook, but there's nothing that the browscap module can do about that.