Jump to content

DanM2

Approved members
  • Content Count

    5
  • Joined

  • Last visited

  1. Thanks for the response! It was certainly an oddity, and unfortunately I don't have any detailed server logs from before October to determine if the CPU usage was occurring as I described before moving it to a fresh AWS instance at that point. I agree about the asynchronous tags causing a change to the performance level which made it noticeable, however it does seem like the irregular CPU usage was happening at a smaller scale prior. In any case, I'm just glad that it's gone now, with the server seeming to operate closer to what I would expect (CPU system usage is a bit higher than other servers, but the CPU steal time is practically zero which was the big worry). It could've just been that the usage we get needed a bit more power, we'll probably never know sadly. Hopefully I'm the only one who has this weird issue, but if not, then maybe this can help someone in the future. Thanks again!
  2. It looks like there is a hidden/unknown requirement for this software to run on at least two CPU cores. My issues described above became so great they were killing the server. Launched an instance with higher resources, and since then, CPU steal time has stayed at 0 for the first time since October. Granted more time will tell if this is true or not, but I just went from server essentially crash to no issues with no traffic change. Leaving this here in case someone tries to Google this in the future.
  3. Earlier this week, I upgraded to 3.2.0 with no issues, however since then, I have noticed performance issues on the server that hosts this program. It appears that in moments of higher usage, somehow the CPU steal time and CPU system time raise dramatically. I saw that this could possibly be attributed to the physical machine the server is on, so I moved it to a different one last night. However there appears to be no change in this behavior. It also seems that this has been occurring every day on the server, the 3.2.0 update just made me more aware of it. The reason I believe Revive Adserver has something to do with this, is because none of the other servers I manage show this sort of resource usage, this server only powers Revive Adserver and nothing else, and this is the second time I've moved the virtual server. I'm not really sure what more I can look into at this point. A lot of PHP processes under the user account are spawned and usually stick for some time before eventually quelling themselves. If anyone can provide any assistance or guidance, it would be greatly appreciated. Thanks!
  4. In an update to this situation, I ran a check and auto-repair on the database itself in case of any issues, where a few row counts were altered slightly. Manual maintenance didn't seem to help much after, but it appears that I had success with the republish.php script which I saw referenced in another thread, used as follows: php /home/xxxxxxx/live/scripts/maintenance/tools/republish.php hostname '2014-11-26 00:00:00' '2014-12-02 23:59:59' For a period of time, yesterday's stats weren't coming up nor were today's save for what appears to have been an hour's worth. But as I ran scripts one more time before posting, they all came as well. This appears like it can be chalked up to a database table issue that likely occurred after the reboot. I just wanted to update this with what happened in case anyone comes across this in the future, as well as bring the above script to light since save the post I came across randomly from a few years ago on a Google search, there doesn't appear to be any information on it outside of that post.
  5. Hello! My employer has been using Revive Adserver for a long time (well before I started early in the year), where over the past couple of months I have been able to successfully migrate it to a new server and perform an upgrade to the latest version with no issues (at least, no issues with the software). A few weeks ago, we came across an issue where stats hadn't migrated for a couple of weeks, which was quickly fixed by running maintenance manually and adjusting its settings. Things were running with no issues until this past Thursday, where it looks like the server it resides on was rebooted in the evening (which I am trying to see why this had happened). Since that reboot, the ox_data_bkt_m table has been recording values as expected, however maintenance runs following that have not migrated data. The debug.log shows "Automatic Maintenance Task not run: could not acquire lock" around that time, which makes sense if that was being run before MySQL was fully running. Here is a set of the debug.log outputs following the reboot: Nov 26 21:05:00 -0500 OX-547686ccc9a95 [ info] Running Automatic Maintenance Task Nov 26 21:05:01 -0500 OX-maintenance-547686ccc9a95 [ info] Running Maintenance Engine Nov 26 21:05:01 -0500 OX-maintenance-547686ccc9a95 [ info] Running Maintenance Statistics Engine Nov 26 21:05:01 -0500 OX-maintenance-547686ccc9a95 [ info] Task begin: OX_Maintenance_Statistics_Task_SetUpdateRequirements Nov 26 21:05:01 -0500 OX-maintenance-547686ccc9a95 [ info] - Maintenance statistics will be run Nov 26 21:05:01 -0500 OX-maintenance-547686ccc9a95 [ info] - The intermediate table statistics will be updated Nov 26 21:05:01 -0500 OX-maintenance-547686ccc9a95 [ info] - The final table statistics will be updated Nov 26 21:05:01 -0500 OX-maintenance-547686ccc9a95 [ info] Task complete: OX_Maintenance_Statistics_Task_SetUpdateRequirements Nov 26 21:05:01 -0500 OX-maintenance-547686ccc9a95 [ info] Task begin: OX_Maintenance_Statistics_Task_MigrateBucketData Nov 26 21:05:01 -0500 OX-maintenance-547686ccc9a95 [ info] - The ox_data_bkt_a table is a raw data table. Data logged in real-time, not operation intervals. Nov 26 21:05:01 -0500 OX-maintenance-547686ccc9a95 [ info] - Accordingly, pruning of the ox_data_bkt_a table will be performed based on data that has a logged date between Nov 26 21:05:01 -0500 OX-maintenance-547686ccc9a95 [ info] 2014-11-27 01:00:00 UTC and 2014-11-27 01:59:59 UTC Nov 26 21:05:01 -0500 OX-maintenance-547686ccc9a95 [ info] - The ox_data_bkt_a_var table is a raw data table. Data logged in real-time, not operation intervals. Nov 26 21:05:01 -0500 OX-maintenance-547686ccc9a95 [ info] - Accordingly, pruning of the ox_data_bkt_a_var table will be performed based on data that has a logged date between Nov 26 21:05:01 -0500 OX-maintenance-547686ccc9a95 [ info] 2014-11-27 01:00:00 UTC and 2014-11-27 01:59:59 UTC Nov 26 21:05:01 -0500 OX-maintenance-547686ccc9a95 [ error] ERROR: Could not migrate aggregate bucket data from the 'ox_data_bkt_c', 'ox_data_bkt_m', 'ox_data_bkt_r' bucket table(s) Nov 26 21:05:01 -0500 OX-maintenance-547686ccc9a95 [ error] Error message was: MDB2 Error: Array Nov 26 21:05:01 -0500 OX-maintenance-547686ccc9a95 [ info] Task complete: OX_Maintenance_Statistics_Task_MigrateBucketData Nov 26 21:05:01 -0500 OX-maintenance-547686ccc9a95 [ info] Task begin: OX_Maintenance_Statistics_Task_DeDuplicateConversions Nov 26 21:05:01 -0500 OX-maintenance-547686ccc9a95 [ info] Task complete: OX_Maintenance_Statistics_Task_DeDuplicateConversions Nov 26 21:05:01 -0500 OX-maintenance-547686ccc9a95 [ info] Task begin: OX_Maintenance_Statistics_Task_ManageConversions Nov 26 21:05:01 -0500 OX-maintenance-547686ccc9a95 [ info] Task complete: OX_Maintenance_Statistics_Task_ManageConversions Nov 26 21:05:01 -0500 OX-maintenance-547686ccc9a95 [ info] Task begin: OX_Maintenance_Statistics_Task_SummariseFinal Nov 26 21:05:01 -0500 OX-maintenance-547686ccc9a95 [ info] Task complete: OX_Maintenance_Statistics_Task_SummariseFinal Nov 26 21:05:01 -0500 OX-maintenance-547686ccc9a95 [ info] Task begin: OX_Maintenance_Statistics_Task_LogCompletion Nov 26 21:05:01 -0500 OX-maintenance-547686ccc9a95 [ info] Task complete: OX_Maintenance_Statistics_Task_LogCompletion Nov 26 21:05:01 -0500 OX-maintenance-547686ccc9a95 [ info] Task begin: OX_Maintenance_Statistics_Task_ManageCampaigns Nov 26 21:05:01 -0500 OX-maintenance-547686ccc9a95 [ info] - Managing (activating/deactivating) campaigns Nov 26 21:05:18 -0500 OX-maintenance-547686ccc9a95 [ info] Task complete: OX_Maintenance_Statistics_Task_ManageCampaigns Nov 26 21:05:18 -0500 OX-maintenance-547686ccc9a95 [ info] Maintenance Statistics Engine Completed (Started at 2014-11-27 02:05:01 UTC) Nov 26 21:05:18 -0500 OX-maintenance-547686ccc9a95 [ info] Running Maintenance Priority Engine Nov 26 21:05:18 -0500 OX-maintenance-547686ccc9a95 [ info] Task begin: OA_Maintenance_Priority_AdServer_Task_GetRequiredAdImpressionsLifetime Nov 26 21:05:18 -0500 OX-maintenance-547686ccc9a95 [ info] Task complete: OA_Maintenance_Priority_AdServer_Task_GetRequiredAdImpressionsLifetime Nov 26 21:05:18 -0500 OX-maintenance-547686ccc9a95 [ info] Task begin: OA_Maintenance_Priority_AdServer_Task_GetRequiredAdImpressionsDaily Nov 26 21:05:18 -0500 OX-maintenance-547686ccc9a95 [ info] Task complete: OA_Maintenance_Priority_AdServer_Task_GetRequiredAdImpressionsDaily Nov 26 21:05:18 -0500 OX-maintenance-547686ccc9a95 [ info] Task begin: OA_Maintenance_Priority_AdServer_Task_AllocateZoneImpressions Nov 26 21:05:18 -0500 OX-maintenance-547686ccc9a95 [ info] - Selecting Zones forecasts for all managers for OI from 2014-11-27 02:00:00 to 2014-11-27 02:59:59 Nov 26 21:05:23 -0500 OX-maintenance-547686ccc9a95 [ info] Inserted 10362 rows in the table tmp_ad_zone_impression Nov 26 21:05:23 -0500 OX-maintenance-547686ccc9a95 [ info] Task complete: OA_Maintenance_Priority_AdServer_Task_AllocateZoneImpressions Nov 26 21:05:23 -0500 OX-maintenance-547686ccc9a95 [ info] Task begin: OA_Maintenance_Priority_AdServer_Task_PriorityCompensation Nov 26 21:05:23 -0500 OX-maintenance-547686ccc9a95 [ info] - Selecting Zones forecasts for all managers for OI from 2014-11-27 02:00:00 to 2014-11-27 02:59:59 Nov 26 21:05:23 -0500 OX-maintenance-547686ccc9a95 [ info] Task complete: OA_Maintenance_Priority_AdServer_Task_PriorityCompensation Nov 26 21:05:23 -0500 OX-maintenance-547686ccc9a95 [ info] Task begin: OA_Maintenance_Priority_AdServer_Task_ECPMforContract Nov 26 21:05:23 -0500 OX-maintenance-547686ccc9a95 [ info] - Selecting All Managers Nov 26 21:05:23 -0500 OX-maintenance-547686ccc9a95 [ info] - Selecting active campaigns with priority = '9' for manager 4 Nov 26 21:05:23 -0500 OX-maintenance-547686ccc9a95 [ info] - Selecting active campaigns with priority = '8' for manager 4 Nov 26 21:05:23 -0500 OX-maintenance-547686ccc9a95 [ info] - Selecting active campaigns with priority = '7' for manager 4 Nov 26 21:05:23 -0500 OX-maintenance-547686ccc9a95 [ info] - Selecting active campaigns with priority = '6' for manager 4 Nov 26 21:05:23 -0500 OX-maintenance-547686ccc9a95 [ info] - Selecting active campaigns with priority = '9' for manager 3 Nov 26 21:05:23 -0500 OX-maintenance-547686ccc9a95 [ info] - Selecting active campaigns with priority = '8' for manager 3 Nov 26 21:05:23 -0500 OX-maintenance-547686ccc9a95 [ info] - Selecting active campaigns with priority = '7' for manager 3 Nov 26 21:05:23 -0500 OX-maintenance-547686ccc9a95 [ info] - Selecting active campaigns with priority = '6' for manager 3 Nov 26 21:05:23 -0500 OX-maintenance-547686ccc9a95 [ info] - Selecting active campaigns with priority = '9' for manager 6 Nov 26 21:05:23 -0500 OX-maintenance-547686ccc9a95 [ info] - Selecting active campaigns with priority = '8' for manager 6 Nov 26 21:05:23 -0500 OX-maintenance-547686ccc9a95 [ info] - Selecting active campaigns with priority = '7' for manager 6 Nov 26 21:05:23 -0500 OX-maintenance-547686ccc9a95 [ info] - Selecting active campaigns with priority = '6' for manager 6 Nov 26 21:05:23 -0500 OX-maintenance-547686ccc9a95 [ info] - Selecting active campaigns with priority = '9' for manager 7 Nov 26 21:05:23 -0500 OX-maintenance-547686ccc9a95 [ info] - Selecting active campaigns with priority = '8' for manager 7 Nov 26 21:05:23 -0500 OX-maintenance-547686ccc9a95 [ info] - Selecting active campaigns with priority = '7' for manager 7 Nov 26 21:05:23 -0500 OX-maintenance-547686ccc9a95 [ info] - Selecting active campaigns with priority = '6' for manager 7 Nov 26 21:05:23 -0500 OX-maintenance-547686ccc9a95 [ info] Task complete: OA_Maintenance_Priority_AdServer_Task_ECPMforContract Nov 26 21:05:23 -0500 OX-maintenance-547686ccc9a95 [ info] Task begin: OA_Maintenance_Priority_AdServer_Task_ECPMforRemnant Nov 26 21:05:23 -0500 OX-maintenance-547686ccc9a95 [ info] - Selecting Managers with ECPM priority campaigns running Nov 26 21:05:23 -0500 OX-maintenance-547686ccc9a95 [ info] Task complete: OA_Maintenance_Priority_AdServer_Task_ECPMforRemnant Nov 26 21:05:23 -0500 OX-maintenance-547686ccc9a95 [ info] Maintenance Priority Engine Completed (Started at 2014-11-27 02:05:01 UTC) Nov 26 21:05:23 -0500 OX-maintenance-547686ccc9a95 [ info] Maintenance Engine Completed (Started at 2014-11-27 02:05:01 UTC, taking 00:00:22) Nov 26 21:05:23 -0500 OX-547686ccc9a95 [ info] Automatic Maintenance Task Completed With anything I've looked up, I haven't been able to find any further information past running maintenance manually, which has not helped. Any assistance or direction would be greatly appreciated. Thank you!
×
×
  • Create New...