JoeJoe Posted July 25 Report Share Posted July 25 Hi, I am currently using Revive Adserver v. 5.5.2 running on Apache, PHP 8.1.29 and MySQL 10.6.18 MariaDB I have changed from automatic maintenance to using a cron job. I read the documentation and am using the following line: /usr/local/bin/php /home/example/public_html/scripts/maintenance/maintenance.php example.com example and example.com are not the actual values being used. I see this "www.example.com" after maintenance.php in the documentation (https://revive-adserver.atlassian.net/wiki/spaces/DOCS/pages/721205/Running+Maintenance) but am not sure exactly what domain this is supposed to be or what it does. If I run this cron job without that domain at the end it doesn't work at all. I currently use the root domain that revive is installed on, and it does run the maintenance script, just doesn't update the stats. My primary issue is that I run this ever 5 minutes (for now, for testing) and it does not update the statistics. It seems to update them only once an hour still (and I'm yet to fully verify that is even the case). I get the following issue in my debug.log file: Jul 25 09:15:02 +0000 OX-maintenance-66a21795b6305 [ info] Running Maintenance Engine Jul 25 09:15:02 +0000 OX-maintenance-66a21795b6305 [ info] Running Maintenance Statistics Engine Jul 25 09:15:02 +0000 OX-maintenance-66a21795b6305 [ info] OX_Maintenance->run: MaxMind GeoIP2 license key missing, skipping auto-update Jul 25 09:15:02 +0000 OX-maintenance-66a21795b6305 [ info] OX_Maintenance->run: Task begin: OX_Maintenance_Statistics_Task_SetUpdateRequirements Jul 25 09:15:02 +0000 OX-maintenance-66a21795b6305 [ info] OX_Maintenance->_runMSE: - Maintenance statistics will NOT be run I see the part that says "Maintenance statistics will NOT be run" Why is this? Why can't it run? I have opened pages with the banners and clicked on them for testing, and still it wont update the stats here. It randomly did in a new hour that happened to pass though. I assume it is checking OX_Maintenance_Statistics_Task_SetUpdateRequirements. Is there some way to change these requirements to make this work? Any help here would be greatly appreciated. Waiting an hour when doing testing is quite time consuming. Thank you Quote Link to comment Share on other sites More sharing options...
JoeJoe Posted July 25 Author Report Share Posted July 25 Just an update to this. I set the Maintenance Interval to 5m to match the Cron Job and this seemed to half work. The debug.log now says the stats are being updated, however, I get the following messages: Jul 25 09:45:02 +0000 OX-maintenance-66a21e9dd3c76 [ info] OA_Task_Runner->runTasks: - The rv_data_bkt_a table is a raw data table. Data logged in real-time, not operation intervals. Jul 25 09:45:02 +0000 OX-maintenance-66a21e9dd3c76 [ info] OA_Task_Runner->runTasks: - Accordingly, pruning of the rv_data_bkt_a table will be performed based on data that has a logged date between Jul 25 09:45:02 +0000 OX-maintenance-66a21e9dd3c76 [ info] OA_Task_Runner->runTasks: 2024-07-25 09:00:00 UTC and 2024-07-25 09:04:59 UTC Jul 25 09:45:02 +0000 OX-maintenance-66a21e9dd3c76 [ info] OA_Task_Runner->runTasks: - The rv_data_bkt_a table is a raw data table. Data logged in real-time, not operation intervals. Jul 25 09:45:02 +0000 OX-maintenance-66a21e9dd3c76 [ info] OA_Task_Runner->runTasks: - Accordingly, pruning of the rv_data_bkt_a table will be performed based on data that has a logged date between Jul 25 09:45:02 +0000 OX-maintenance-66a21e9dd3c76 [ info] OA_Task_Runner->runTasks: 2024-07-25 09:05:00 UTC and 2024-07-25 09:09:59 UTC I notice that the impressions/clicks most recently done before this "maintenance" updated the stats are not being updated at all. I wonder if those are stuck to the hourly regiment. I hope there is some way to reconfigure this to run at a requested interval. Quote Link to comment Share on other sites More sharing options...
Matteo Beccati Posted July 26 Report Share Posted July 26 For best performance Operation Interval should be left at 1 hour and maintenance should be scheduled to run hourly. Doing it more often is unnecessary. TL;DR You can't have statistics updated more often than 1 hour anyway Quote Link to comment Share on other sites More sharing options...
JoeJoe Posted July 26 Author Report Share Posted July 26 Hi Matteo, Thanks for your reply. I understand that for a live environment the current interval of 1 hour is acceptable and less may be unnecessary. I am, however, referring to a testing environment, where I would like to be able to view the results of my testing immediately. If you say it is not possible at all, then that is a different issue. I was hoping it would be possible without having to change the source code myself. It would be nice, considering there is the option to run general maintenance at lesser intervals, for the statistics to be included in that setting. Quote Link to comment Share on other sites More sharing options...
Matteo Beccati Posted July 29 Report Share Posted July 29 I understand it would be nice, but unfortunately the core design of the product that was made decades ago doesn't allow it. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.