No Statistics? See Here For The Solution We Use... Options

[Kaan]

Hey all,

I just logged on to report an issue (unrelated) and saw that everyone is having issues with no statistics being generated.

We've had this a couple of times over the past 12 months - it's to do with a table (one of the 'raw' tables) being marked as crashed within MySQL and you need to repair the table. Sure, easy solution once you realise there's a problem but that's probably too late. You can regenerate the stats apparently (see below) but what if your temporary table size is only small and you've restricted the date range to only a few days? That important data is long gone by now...

This is what we run nightly (cron job, run early morning because it locks tables and freezes things up for a minute or two) to make sure the problem never, ever happens on the database server for OpenX:

/usr/bin/mysqlcheck -Aao --auto-repair -u USER --password=PASSWORD | mail -s "mysqlcheck `date`" YOUR@EMAIL.ADDRESS

So what does it do? I'll go step by step so everyone of all levels understands.

From the MySQL manual: "The mysqlcheck client checks, repairs, optimizes, and analyzes tables."

-A Checks all databases

If you want to specify multiple databases use -B or --databases and list them afterwards or if you want to just check the OpenX database use this format:

/usr/bin/mysqlcheck DATABASENAME ... (then same as above, make the first arguement the database name)

-a Analyze the tables for issues

-o Optimize the tables to remove fragmentation, reclaim space, etc.

--auto-repair Should be obvious but automatically fixes a table if it's found to be corrupted or crashed

-u USER Specify the user to execute as (root or some other MySQL user with the relevant permissions)

--password=PASSWORD Specify the password for the user from above

That's all for the mysqlcheck command itself, what we then do is pipe the output from this into mail, set a subject as mysqlcheck followed by the date (`date` executes the date command on the shell) and sends it to an email address so we can have a look each day.

You can run this command daily or even more, we run it daily and haven't had a problem since but if you were really worried you could run it every 6 hours and that should cover you for any possible crashes.

Comments? Works for us but if someone thinks I'm doing it wrong or this could be done better let me know...

Also I've seen in another thread that you can use openx\scripts\maintenance\tools\regenerateAdServerStatistics.php to regenerate statistics from the data in the 'raw' tables if something goes wrong so use this if you've already got issues with a crashed table.

Just remember you need to be vigilant and manage your database server as even though it sits in the background 90% of the time chugging along it still needs to be monitored.

[Mentor]

Hi Kaan,

Thank you for the informative post. You have provided a bunch of useful information. I'm going to pin this topic for a while to see what is other users feedback in this area.

Please keep the ideas coming. Any other descriptive step by step solutions are welcome!

[amanda]

You can also run mysqlcheck without the auto-repair option if you want to look at things first. I've been running openx since phpads so my database is called "phpads":

mysqlcheck phpads -u openads -p betterpassword

[zwartemarkt]

HI,

OpenX v2.8.0 running Apache 2.2.8,
PHP 5.2.6-2ubuntu4 and MySQL 5.0.51a-3ubuntu5.4.

i added the repair cmd to mine cronjobs.

/usr/bin/mysqlcheck -Aao --auto-repair -u USER --password=PASSWORD | mail -s "mysqlcheck `date`" YOUR@EMAIL.ADDRESS

tried also

php /var/www/zwartemarkt.org/openx/scripts/maintenance/tools/statisticsTestAndCorrect.php

now i see the impressions in the stats but i miss AdClicks CTR Rev. CPM
if i look at the stats before the update then i have data in it.
(sorry for the bad english, i am a newbie also)

the strange part is mine debug.log

maintance doesnt get generated after the update, its still empty.
i backuped the old one that i used before the update, made an empty maintance.log with the correct file permissions.

debug.log:

Apr 06 12:34:02 +0200 OX [ warning] Invalid argument supplied for foreach()
Apr 06 12:34:12 +0200 OX [ warning] Invalid argument supplied for foreach()


Apr 06 12:45:06 +0200 OX-maintenance [ info] Running Maintenance Engine
Apr 06 12:45:06 +0200 OX-maintenance [ info] Running Maintenance Statistics Engine
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Maintenance start run time is 2009-04-06 10:45:06 UTC
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Getting the details of when maintenance statistics last ran on the basis of the operation interval
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Maintenance statistics last updated intermediate table statistics to 2009-04-06 09:59:59 UTC
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Current time must be after 2009-04-06 10:59:59 UTC for the next intermediate table update to happen
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - At least 60 minutes have not passed since the last operation interval update
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Getting the details of when maintenance statistics last ran on the basis of the hour
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Maintenance statistics last updated final table statistics to 2009-04-06 09:59:59 UTC
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Current time must be after 2009-04-06 10:59:59 UTC for the next intermediate table update to happen
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - At least 60 minutes have NOT passed since the last final table update
Apr 06 12:45:06 +0200 OX-maintenance [ info] - Maintenance statistics will NOT be run for the
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Logging the completion of the maintenance statistics run
Apr 06 12:45:06 +0200 OX-maintenance [ info] Started oxMarket_ImportMarketStatistics
Apr 06 12:45:06 +0200 OX-maintenance [ info] Following exception occured: [0] There is no association between PC and OXP accounts
Apr 06 12:45:06 +0200 OX-maintenance [ info] Finished oxMarket_ImportMarketStatistics
Apr 06 12:45:06 +0200 OX-maintenance [ info] Started oxMarket_UpdateWebsites
Apr 06 12:45:06 +0200 OX-maintenance [ info] Finished oxMarket_UpdateWebsites
Apr 06 12:45:06 +0200 OX-maintenance [ info] Maintenance Statistics Engine Completed (Started at 2009-04-06 10:45:06 UTC)
Apr 06 12:45:06 +0200 OX-maintenance [ info] Running Maintenance Priority Engine
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Obtaining maintenance process run information from ox_log_maintenance_statistics
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Obtaining maintenance process run information from ox_log_maintenance_priority
Apr 06 12:45:06 +0200 OX-maintenance [ debug] Running Maintenance Priority Engine: Zone Impression Forecast Update
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Calculating range of operation intervals which require ZIF update
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Found OI range to update
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 0
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 2
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 3
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 4
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 5
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 6
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on past average only
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on previous OI value
Apr 06 12:45:06 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 7
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 8
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 9
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 10
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 11
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on previous OI value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 12
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on previous OI value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 13
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 14
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 15
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 16
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 17
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 18
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 19
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 20
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 21
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 22
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 23
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 24
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 25
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 26
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 27
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 28
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 29
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 30
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 31
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 32
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on previous OI value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 33
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 34
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 35
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 36
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 37
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 38
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 33 (starting '2009-04-06 09:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Forecasting for OI 34 (starting '2009-04-06 10:00:00 UTC') based on default value
Apr 06 12:45:07 +0200 OX-maintenance [ debug] - Saving zone impression forecasts
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Updating past zone impression forecasts
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Recording completion of the Forecast Zone Impressions task
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Logging maintenance process run information into ox_log_maintenance_priority
Apr 06 12:45:08 +0200 OX-maintenance [ debug] Running Maintenance Priority Engine: Get Required Ad Impressions for High Priority Campaigns
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Where campaign lifetime target(s) and end date are set
Apr 06 12:45:08 +0200 OX-maintenance [ debug] Running Maintenance Priority Engine: Get Required Ad Impressions for High Priority Campaigns
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Where a daily target is set
Apr 06 12:45:08 +0200 OX-maintenance [ debug] Running Maintenance Priority Engine: Allocate Zone Impressions
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Creating the tmp_ad_zone_impression table
Apr 06 12:45:08 +0200 OX-maintenance [ debug] Running Maintenance Priority Engine: Priority Compensation
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Obtaining maintenance process run information from ox_log_maintenance_priority
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Building zone and advert objects
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting all of the zones impression inventory data
Apr 06 12:45:08 +0200 OX-maintenance [ debug] Getting all of the zones with ad impressions allocated.
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting all ads where delivery limitations have changed
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting details of previous ad/zone delivery
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting details of ad/zone pairs that delivered last OI
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-06 09:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-06 08:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-06 07:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-06 06:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-06 05:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-06 04:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-06 03:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-06 02:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-06 01:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-06 00:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-05 23:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-05 22:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-05 21:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-05 20:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-05 19:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-05 18:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-05 17:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-05 16:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-05 15:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-05 14:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-05 13:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-05 12:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-05 11:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-05 10:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-05 09:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-05 08:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-05 07:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-05 06:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-05 05:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-05 04:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-05 03:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-05 02:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-05 01:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-05 00:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-04 23:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-04 22:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-04 21:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-04 20:00:00
Apr 06 12:45:08 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-04 19:00:00
Apr 06 12:45:09 +0200 OX-maintenance [ debug] - Getting past details of ad/zone pairs for OI starting at 2009-04-04 18:00:00
Apr 06 12:45:09 +0200 OX-maintenance [ debug] - Getting details of ad/zone pairs that did not deliver last OI (but should have)
Apr 06 12:45:09 +0200 OX-maintenance [ debug] - Getting past details of the non-delivering ad/zone pairs
Apr 06 12:45:09 +0200 OX-maintenance [ debug] - Finding ad/zone pairs set to deliver, but with no past data yet
Apr 06 12:45:09 +0200 OX-maintenance [ debug] - Updating priorities
Apr 06 12:45:09 +0200 OX-maintenance [ debug] - Zeroing category-based priorities
Apr 06 12:45:09 +0200 OX-maintenance [ debug] - Saving calculated priorities WITHOUT transaction support
Apr 06 12:45:09 +0200 OX-maintenance [ debug] - Getting all existing ad/zone pairs with priorities
Apr 06 12:45:09 +0200 OX-maintenance [ debug] - Calculating which existing ad/zone pair priorities need to be zeroed
Apr 06 12:45:09 +0200 OX-maintenance [ debug] - Zeroing required existing ad/zone pair priorities
Apr 06 12:45:09 +0200 OX-maintenance [ debug] - Updating required existing ad/zone pair priorities
Apr 06 12:45:09 +0200 OX-maintenance [ debug] - Epiring old priority values in data_summary_ad_zone_assoc
Apr 06 12:45:09 +0200 OX-maintenance [ debug] - Adding new priority values to data_summary_ad_zone_assoc
Apr 06 12:45:09 +0200 OX-maintenance [ debug] - Recording completion of the Priority Compensation task
Apr 06 12:45:09 +0200 OX-maintenance [ debug] - Logging maintenance process run information into ox_log_maintenance_priority
Apr 06 12:45:09 +0200 OX-maintenance [ debug] Running Maintenance Priority Engine: ECPM
Apr 06 12:45:09 +0200 OX-maintenance [ debug] - Obtaining maintenance process run information from ox_log_maintenance_priority
Apr 06 12:45:09 +0200 OX-maintenance [ debug] - Recording completion of the ECPM task
Apr 06 12:45:09 +0200 OX-maintenance [ debug] - Logging maintenance process run information into ox_log_maintenance_priority
Apr 06 12:45:09 +0200 OX-maintenance [ info] Maintenance Priority Engine Completed (Started at 2009-04-06 10:45:06 UTC)
Apr 06 12:45:09 +0200 OX-maintenance [ info] Maintenance Engine Completed (Started at 2009-04-06 10:45:06 UTC, taking 00:00:03)

grts,

Chris

[zwartemarkt]

nvm.

it seems that 2.8.0 doesnt generate any maintance logs anymore it combines them with the debug.log.

as stated in a diff post

[zwartemarkt]

but still after running a few weeks now on the 2.8.0.
well mine advice is when your older version running smooth dont UPGRADE.
i really have big doubts about 2.8.0
sinds the upgrade i must continuely look at the openx server, then this not work and after that something else isnt working.
well please "dont put out crappy upgrades"!!!
i really freaking out about this dumn upgrade.

i did all workarounds and 2.8.0.works for a while but then the probs are just coming back.

i repair mine database every 6hours (this is an insane workaround, works but still totally gay)
Why? does it corrupt mine database every time?
why plublish workarounds like this magnitude in a forum?
just make a fix for the mainstream and test your software better before releasing it.

example 1:
i have every time that rpc error.
OA_XML_RPC_Client: RPC server did not send response before timeout.

did the workaround, resulting that mine server gets very slow cuz the timeouts are just building up.

strange cuz i have a vps with other software that uses the rpc protocol but i have no probs there.
installed the right extensions etc ...

Well i sit this buggy software out for a few days, if its still crap i delete openx and gonna buy a payed version of a an ad-server and it wont be openx.

at least this buggy software is free, so i wont complain about the support.


succes and good luck

[davidwhthomas]

I still get no statistics with scheduled maintenance enabled ( via cron ) on OpenX 2.8.1 with PostgreSQL 8.1
As it's PostgreSQL, there are not crashed tables to repair and the DB is running normally.
Checking the logs it appears the maintenance script attempts to summarize the data but halts prematurely.
It then restarts at the same place and halts again on the next run.
There's no erroneous data, it appears it just halts arbitrarily.
The result is no ad statistics, with scheduled maintenance enabled.
It's a bit of a show-stopper.

SOLVED!

This problem was that there were too many old raw stats to get through and it needed to run once to churn through and clear the raw data tables.

STEPS:

1. Set the debug logging to verbose in OpenX admin setting
2. Disable the automatic scheduled maintenance. ( coz we're running manually )
3. Set the timeLimitScripts variable in the OpenX config file to 6800 (2 hours)
4. Run the mainteance cron job manually
5. Re-enabled the scheduled maintenance cron job / scheduled task.

CODE

wget /path/to/site/maintenance/maintenance.php

It took about 1.2 hours to get through all the old stats but when it finished all the statistics were summarized properly!

I could also view the log in /var/maintenance.log ( or /var/debug.log for 2.8 )

hope it helps someone else too.

p.s loving the PostgreSQL support

[nzimas]

SOLVED!

This problem was that there were too many old raw stats to get through and it needed to run once to churn through and clear the raw data tables.

STEPS:

1. Set the debug logging to verbose in OpenX admin setting
2. Disable the automatic scheduled maintenance. ( coz we're running manually )
3. Set the timeLimitScripts variable in the OpenX config file to 6800 (2 hours)
4. Run the mainteance cron job manually
5. Re-enabled the scheduled maintenance cron job / scheduled task.

It took about 1.2 hours to get through all the old stats but when it finished all the statistics were summarized properly!

I could also view the log in /var/maintenance.log ( or /var/debug.log for 2.8 )

Did your log look like:

Jul 30 22:16:18 +0000 OX-maintenance [ debug] - Recording completion of the Priority Compensation task
Jul 30 22:16:18 +0000 OX-maintenance [ debug] - Logging maintenance process run information into ox_log_maintenance_priority
Jul 30 22:16:18 +0000 OX-maintenance [ debug] Running Maintenance Priority Engine: ECPM
Jul 30 22:16:18 +0000 OX-maintenance [ debug] - Obtaining maintenance process run information from ox_log_maintenance_priority
Jul 30 22:16:18 +0000 OX-maintenance [ debug] - Recording completion of the ECPM task
Jul 30 22:16:18 +0000 OX-maintenance [ debug] - Logging maintenance process run information into ox_log_maintenance_priority
Jul 30 22:16:18 +0000 OX-maintenance [ info] Maintenance Priority Engine Completed (Started at 2009-07-30 22:16:09 UTC)
Jul 30 22:16:18 +0000 OX-maintenance [ info] Maintenance Engine Completed (Started at 2009-07-30 22:16:09 UTC, taking 00:00:09)
Jul 30 22:16:18 +0000 OX [ info] calling on Plugin_deliveryCacheStore_oxCacheFile_oxCacheFile_Delivery_cacheStore
Jul 30 22:16:18 +0000 OX [ info] calling on Plugin_deliveryCacheStore_oxMemcached_oxMemcached_Delivery_cacheStore

I'm not quite sure if the task has completed.
On the OX admin interface, under Configuration > Maintenance, it says Scheduled maintenance is running correctly.
I'm not sure if it is running in the background right now or if it only means that the scheduiled maintenance is on, which is not true (i did not set up any cronjob yet).
My question is, when do we know that the maintenance work is done and where does maintenance.php fetch data from?

Thanks,
Nuno.

[davidwhthomas]

I'm not quite sure if the task has completed.
On the OX admin interface, under Configuration > Maintenance, it says Scheduled maintenance is running correctly.
I'm not sure if it is running in the background right now or if it only means that the scheduiled maintenance is on, which is not true (i did not set up any cronjob yet).
My question is, when do we know that the maintenance work is done and where does maintenance.php fetch data from?

Thanks,
Nuno.

You'll need to enable the cron job / scheduled task for maintenance / stats summary.
If you enable debug logging, the log file in openx/var/debug.log or maintenance.log will state the relevant info, including when the job is finished.

[nzimas]

I'm not quite sure if the task has completed.
On the OX admin interface, under Configuration > Maintenance, it says Scheduled maintenance is running correctly.
I'm not sure if it is running in the background right now or if it only means that the scheduiled maintenance is on, which is not true (i did not set up any cronjob yet).
My question is, when do we know that the maintenance work is done and where does maintenance.php fetch data from?

Thanks,
Nuno.

You'll need to enable the cron job / scheduled task for maintenance / stats summary.
If you enable debug logging, the log file in openx/var/debug.log or maintenance.log will state the relevant info, including when the job is finished.

Thanks for the quick reply, David.

I have followed your steps, manually ran php /path/to/manage/scripts/maintenance/maintenance.php my.domain.com from the commandline, tailed and then open debug.log for analysis.

debug.log shows what appears to be a successful operation, except that no stats after May 23 2009 are shown as of now.
I'll set a cronjob to run maintenance.php every hour.
What i am wondering is how can i retrieved thye stats from May 23rd to July 31st 2009. That's the real bummer.

Here's full maintenance operation as found in debug.log

Jul 30 23:05:00 +0000 OX-maintenance [ info] Running Maintenance Engine
Jul 30 23:05:00 +0000 OX-maintenance [ info] calling on Plugin_deliveryCacheStore_oxCacheFile_oxCacheFile_Delivery_cacheStore
Jul 30 23:05:00 +0000 OX-maintenance [ info] calling on Plugin_deliveryCacheStore_oxMemcached_oxMemcached_Delivery_cacheStore
Jul 30 23:05:00 +0000 OX-maintenance [ info] Running Maintenance Statistics Engine
Jul 30 23:05:00 +0000 OX-maintenance [ debug] - Maintenance start run time is 2009-07-30 23:05:00 UTC
Jul 30 23:05:00 +0000 OX-maintenance [ debug] - Getting the details of when maintenance statistics last ran on the basis of the operation interval
Jul 30 23:05:00 +0000 OX-maintenance [ debug] - Maintenance statistics last updated intermediate table statistics to 2009-07-30 21:59:59 UTC
Jul 30 23:05:00 +0000 OX-maintenance [ debug] - Current time must be after 2009-07-30 22:59:59 UTC for the next intermediate table update to happen
Jul 30 23:05:00 +0000 OX-maintenance [ debug] - Getting the details of when maintenance statistics last ran on the basis of the hour
Jul 30 23:05:00 +0000 OX-maintenance [ debug] - Maintenance statistics last updated final table statistics to 2009-07-30 21:59:59 UTC
Jul 30 23:05:00 +0000 OX-maintenance [ debug] - Current time must be after 2009-07-30 22:59:59 UTC for the next intermediate table update to happen
Jul 30 23:05:00 +0000 OX-maintenance [ info] - Maintenance statistics will be run
Jul 30 23:05:00 +0000 OX-maintenance [ info] - The intermediate table statistics will be updated
Jul 30 23:05:00 +0000 OX-maintenance [ info] - The final table statistics will be updated
Jul 30 23:05:00 +0000 OX-maintenance [ debug] There are no installed plugins that require data migration
Jul 30 23:05:00 +0000 OX-maintenance [ debug] - Deduplicating conversions between 2009-07-30 22:00:00 UTC and 2009-07-30 22:59:59 UTC
Jul 30 23:05:00 +0000 OX-maintenance [ debug] - Rejecting conversions with empty required variables between 2009-07-30 22:00:00 UTC and 2009-07-30 22:59:59 UTC
Jul 30 23:05:00 +0000 OX-maintenance [ debug] - Selecting conversion data for migration to the "old style" intermediate table for
Jul 30 23:05:00 +0000 OX-maintenance [ debug] conversion in the range 2009-07-30 22:00:00 UTC to 2009-07-30 22:59:59 UTC
Jul 30 23:05:00 +0000 OX-maintenance [ debug] - Saving request, impression, click and conversion data into the final tables.
Jul 30 23:05:00 +0000 OX-maintenance [ debug] - Updating the data_summary_zone_impression_history table for data after 2009-07-30 22:00:00 UTC
Jul 30 23:05:00 +0000 OX-maintenance [ debug] - Selecting total zone impressions from the ox_data_intermediate_ad table where the
Jul 30 23:05:00 +0000 OX-maintenance [ debug] impressions are between 2009-07-30 22:00:00 UTC and 2009-07-30 22:59:59 UTC
Jul 30 23:05:00 +0000 OX-maintenance [ debug] - Updating the data_summary_ad_hourly table for data after 2009-07-30 22:00:00 UTC
Jul 30 23:05:00 +0000 OX-maintenance [ debug] - Summarising the ad requests, impressions, clicks and conversions from the ox_data_intermediate_ad table
Jul 30 23:05:00 +0000 OX-maintenance [ debug] into the ox_data_summary_ad_hourly table, for data between 2009-07-30 22:00:00 UTC and 2009-07-30 22:59:59 UTC.
Jul 30 23:05:00 +0000 OX-maintenance [ debug] - Summarised 0 rows of requests, impressions, clicks and conversions.
Jul 30 23:05:00 +0000 OX-maintenance [ debug] - Logging the completion of the maintenance statistics run
Jul 30 23:05:00 +0000 OX-maintenance [ debug] Logging the maintenance statistics run report
Jul 30 23:05:00 +0000 OX-maintenance [ info] - Managing (activating/deactivating) campaigns
Jul 30 23:05:00 +0000 OX-maintenance [ debug] - Found 0 campaigns to test for activation/deactivation
Jul 30 23:05:00 +0000 OX-maintenance [ info] Started oxMarket_ImportMarketStatistics
Jul 30 23:05:00 +0000 OX-maintenance [ info] Following exception occured: [0] There is no association between PC and OXP accounts
Jul 30 23:05:00 +0000 OX-maintenance [ info] Finished oxMarket_ImportMarketStatistics
Jul 30 23:05:00 +0000 OX-maintenance [ info] Started oxMarket_UpdateWebsites
Jul 30 23:05:00 +0000 OX-maintenance [ info] Finished oxMarket_UpdateWebsites
Jul 30 23:05:00 +0000 OX-maintenance [ info] Maintenance Statistics Engine Completed (Started at 2009-07-30 23:05:00 UTC)
Jul 30 23:05:00 +0000 OX-maintenance [ info] Running Maintenance Priority Engine
Jul 30 23:05:00 +0000 OX-maintenance [ debug] - Obtaining maintenance process run information from ox_log_maintenance_statistics
Jul 30 23:05:00 +0000 OX-maintenance [ debug] - Obtaining maintenance process run information from ox_log_maintenance_priority
Jul 30 23:05:00 +0000 OX-maintenance [ debug] Running Maintenance Priority Engine: Zone Impression Forecast Update
Jul 30 23:05:00 +0000 OX-maintenance [ debug] - Calculating range of operation intervals which require ZIF update
Jul 30 23:05:00 +0000 OX-maintenance [ debug] - Found OI range to update
Jul 30 23:05:01 +0000 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 0
Jul 30 23:05:01 +0000 OX-maintenance [ debug] - Forecasting for OI 119 (starting '2009-07-30 23:00:00 UTC') based on default value
Jul 30 23:05:01 +0000 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 1
Jul 30 23:05:01 +0000 OX-maintenance [ debug] - Forecasting for OI 119 (starting '2009-07-30 23:00:00 UTC') based on default value
Jul 30 23:05:01 +0000 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 2
Jul 30 23:05:01 +0000 OX-maintenance [ debug] - Forecasting for OI 119 (starting '2009-07-30 23:00:00 UTC') based on default value
Jul 30 23:05:01 +0000 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 3
Jul 30 23:05:01 +0000 OX-maintenance [ debug] - Forecasting for OI 119 (starting '2009-07-30 23:00:00 UTC') based on default value
Jul 30 23:05:01 +0000 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 4
Jul 30 23:05:02 +0000 OX-maintenance [ debug] - Forecasting for OI 119 (starting '2009-07-30 23:00:00 UTC') based on default value
Jul 30 23:05:02 +0000 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 5
Jul 30 23:05:02 +0000 OX-maintenance [ debug] - Forecasting for OI 119 (starting '2009-07-30 23:00:00 UTC') based on default value
Jul 30 23:05:02 +0000 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 6
Jul 30 23:05:03 +0000 OX-maintenance [ debug] - Forecasting for OI 119 (starting '2009-07-30 23:00:00 UTC') based on default value
Jul 30 23:05:03 +0000 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 9
Jul 30 23:05:03 +0000 OX-maintenance [ debug] - Forecasting for OI 119 (starting '2009-07-30 23:00:00 UTC') based on default value
Jul 30 23:05:03 +0000 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 10
Jul 30 23:05:03 +0000 OX-maintenance [ debug] - Forecasting for OI 119 (starting '2009-07-30 23:00:00 UTC') based on default value
Jul 30 23:05:04 +0000 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 11
Jul 30 23:05:04 +0000 OX-maintenance [ debug] - Forecasting for OI 119 (starting '2009-07-30 23:00:00 UTC') based on default value
Jul 30 23:05:04 +0000 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 12
Jul 30 23:05:04 +0000 OX-maintenance [ debug] - Forecasting for OI 119 (starting '2009-07-30 23:00:00 UTC') based on default value
Jul 30 23:05:04 +0000 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 14
Jul 30 23:05:05 +0000 OX-maintenance [ debug] - Forecasting for OI 119 (starting '2009-07-30 23:00:00 UTC') based on default value
Jul 30 23:05:05 +0000 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 18
Jul 30 23:05:05 +0000 OX-maintenance [ debug] - Forecasting for OI 119 (starting '2009-07-30 23:00:00 UTC') based on default value
Jul 30 23:05:06 +0000 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 22
Jul 30 23:05:06 +0000 OX-maintenance [ debug] - Forecasting for OI 119 (starting '2009-07-30 23:00:00 UTC') based on default value
Jul 30 23:05:06 +0000 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 30
Jul 30 23:05:06 +0000 OX-maintenance [ debug] - Forecasting for OI 119 (starting '2009-07-30 23:00:00 UTC') based on default value
Jul 30 23:05:06 +0000 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 32
Jul 30 23:05:06 +0000 OX-maintenance [ debug] - Forecasting for OI 119 (starting '2009-07-30 23:00:00 UTC') based on default value
Jul 30 23:05:06 +0000 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 33
Jul 30 23:05:06 +0000 OX-maintenance [ debug] - Forecasting for OI 119 (starting '2009-07-30 23:00:00 UTC') based on default value
Jul 30 23:05:07 +0000 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 36
Jul 30 23:05:07 +0000 OX-maintenance [ debug] - Forecasting for OI 119 (starting '2009-07-30 23:00:00 UTC') based on default value
Jul 30 23:05:07 +0000 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 37
Jul 30 23:05:07 +0000 OX-maintenance [ debug] - Forecasting for OI 119 (starting '2009-07-30 23:00:00 UTC') based on default value
Jul 30 23:05:07 +0000 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 39
Jul 30 23:05:07 +0000 OX-maintenance [ debug] - Forecasting for OI 119 (starting '2009-07-30 23:00:00 UTC') based on default value
Jul 30 23:05:07 +0000 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 48
Jul 30 23:05:07 +0000 OX-maintenance [ debug] - Forecasting for OI 119 (starting '2009-07-30 23:00:00 UTC') based on default value
Jul 30 23:05:07 +0000 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 52
Jul 30 23:05:08 +0000 OX-maintenance [ debug] - Forecasting for OI 119 (starting '2009-07-30 23:00:00 UTC') based on default value
Jul 30 23:05:08 +0000 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 57
Jul 30 23:05:08 +0000 OX-maintenance [ debug] - Forecasting for OI 119 (starting '2009-07-30 23:00:00 UTC') based on default value
Jul 30 23:05:08 +0000 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 60
Jul 30 23:05:08 +0000 OX-maintenance [ debug] - Forecasting for OI 119 (starting '2009-07-30 23:00:00 UTC') based on default value
Jul 30 23:05:08 +0000 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 61
Jul 30 23:05:09 +0000 OX-maintenance [ debug] - Forecasting for OI 119 (starting '2009-07-30 23:00:00 UTC') based on default value
Jul 30 23:05:09 +0000 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 62
Jul 30 23:05:09 +0000 OX-maintenance [ debug] - Forecasting for OI 119 (starting '2009-07-30 23:00:00 UTC') based on default value
Jul 30 23:05:09 +0000 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 63
Jul 30 23:05:10 +0000 OX-maintenance [ debug] - Forecasting for OI 119 (starting '2009-07-30 23:00:00 UTC') based on default value
Jul 30 23:05:10 +0000 OX-maintenance [ debug] - Calculating the ZIF data for Zone ID 64
Jul 30 23:05:10 +0000 OX-maintenance [ debug] - Forecasting for OI 119 (starting '2009-07-30 23:00:00 UTC') based on default value
Jul 30 23:05:10 +0000 OX-maintenance [ debug] - Saving zone impression forecasts
Jul 30 23:05:12 +0000 OX-maintenance [ debug] - Updating past zone impression forecasts
Jul 30 23:05:14 +0000 OX-maintenance [ debug] - Recording completion of the Forecast Zone Impressions task
Jul 30 23:05:14 +0000 OX-maintenance [ debug] - Logging maintenance process run information into ox_log_maintenance_priority
Jul 30 23:05:14 +0000 OX-maintenance [ debug] Running Maintenance Priority Engine: Get Required Ad Impressions for High Priority Campaigns
Jul 30 23:05:14 +0000 OX-maintenance [ debug] - Where campaign lifetime target(s) and end date are set
Jul 30 23:05:14 +0000 OX-maintenance [ debug] Running Maintenance Priority Engine: Get Required Ad Impressions for High Priority Campaigns
Jul 30 23:05:14 +0000 OX-maintenance [ debug] - Where a daily target is set
Jul 30 23:05:14 +0000 OX-maintenance [ debug] Running Maintenance Priority Engine: Allocate Zone Impressions
Jul 30 23:05:15 +0000 OX-maintenance [ debug] - Creating the tmp_ad_zone_impression table
Jul 30 23:05:16 +0000 OX-maintenance [ debug] Running Maintenance Priority Engine: Priority Compensation
Jul 30 23:05:16 +0000 OX-maintenance [ debug] - Obtaining maintenance process run information from ox_log_maintenance_priority
Jul 30 23:05:16 +0000 OX-maintenance [ debug] - Building zone and advert objects
Jul 30 23:05:16 +0000 OX-maintenance [ debug] - Getting all of the zones impression inventory data
Jul 30 23:05:16 +0000 OX-maintenance [ debug] Getting all of the zones with ad impressions allocated.
Jul 30 23:05:18 +0000 OX-maintenance [ debug] - Getting all ads where delivery limitations have changed
Jul 30 23:05:18 +0000 OX-maintenance [ debug] - Getting details of previous ad/zone delivery
Jul 30 23:05:18 +0000 OX-maintenance [ debug] - Getting details of ad/zone pairs that delivered last OI
Jul 30 23:05:18 +0000 OX-maintenance [ debug] - Getting details of ad/zone pairs that did not deliver last OI (but should have)
Jul 30 23:05:18 +0000 OX-maintenance [ debug] - Getting past details of the non-delivering ad/zone pairs
Jul 30 23:05:18 +0000 OX-maintenance [ debug] - Finding ad/zone pairs set to deliver, but with no past data yet
Jul 30 23:05:18 +0000 OX-maintenance [ debug] - Updating priorities
Jul 30 23:05:18 +0000 OX-maintenance [ debug] - Zeroing category-based priorities
Jul 30 23:05:18 +0000 OX-maintenance [ debug] - Saving calculated priorities WITHOUT transaction support
Jul 30 23:05:18 +0000 OX-maintenance [ debug] - Getting all existing ad/zone pairs with priorities
Jul 30 23:05:18 +0000 OX-maintenance [ debug] - Calculating which existing ad/zone pair priorities need to be zeroed
Jul 30 23:05:18 +0000 OX-maintenance [ debug] - Zeroing required existing ad/zone pair priorities
Jul 30 23:05:18 +0000 OX-maintenance [ debug] - Updating required existing ad/zone pair priorities
Jul 30 23:05:18 +0000 OX-maintenance [ debug] - Epiring old priority values in data_summary_ad_zone_assoc
Jul 30 23:05:18 +0000 OX-maintenance [ debug] - Adding new priority values to data_summary_ad_zone_assoc
Jul 30 23:05:18 +0000 OX-maintenance [ debug] - Recording completion of the Priority Compensation task
Jul 30 23:05:18 +0000 OX-maintenance [ debug] - Logging maintenance process run information into ox_log_maintenance_priority
Jul 30 23:05:18 +0000 OX-maintenance [ debug] Running Maintenance Priority Engine: ECPM
Jul 30 23:05:18 +0000 OX-maintenance [ debug] - Obtaining maintenance process run information from ox_log_maintenance_priority
Jul 30 23:05:18 +0000 OX-maintenance [ debug] - Recording completion of the ECPM task
Jul 30 23:05:18 +0000 OX-maintenance [ debug] - Logging maintenance process run information into ox_log_maintenance_priority
Jul 30 23:05:18 +0000 OX-maintenance [ info] Maintenance Priority Engine Completed (Started at 2009-07-30 23:05:00 UTC)
Jul 30 23:05:18 +0000 OX-maintenance [ info] Maintenance Engine Completed (Started at 2009-07-30 23:05:00 UTC, taking 00:00:18)
Jul 30 23:05:18 +0000 OX [ info] calling on Plugin_deliveryCacheStore_oxCacheFile_oxCacheFile_Delivery_cacheStore
Jul 30 23:05:18 +0000 OX [ info] calling on Plugin_deliveryCacheStore_oxMemcached_oxMemcached_Delivery_cacheStore

[nzimas]

You'll need to enable the cron job / scheduled task for maintenance / stats summary.

Mind to elaborate on this procedure?

Shouldn't it be enough to run php /path/to/manage/scripts/maintenance/maintenance.php?
On the other hand, are stats recoverable at all? (provided that OX has logged them somewhere om the DB)

Thanks a bunch.

Nuno.

[peopleofdesign]

my maintance.php is work properly, but i can't see any stats (( in MySQL table - all impressions are collected (sorry for my english i'm from russia)...

Please help me. How can i see statistics ? (

[Corinthians]

This is so much frustrating...I alredy done two entire instalations , did all that is said inthis orum and still not working. No one impressions had been included im my dam empty stats. All in a website with 1500 vitis all days.

If I install a old openads version can this work? Sorry for my english...Im brazilian and I realy pissed with this dam thing

[REEP]

I am seeing this error when I click on the Statistics tab.

I tried the solution presented here. It worked but did not solve this problem

I am not sure if it is related to this post.

Any help would be greatly appreciated.


PEAR Error

MDB2 Error: no such table
_doQuery: [Error message: Could not execute statement]
(deleted to save space)
[Native code: 1146]
[Native message: Table 'DATABASENAME_ext_market_stats' doesn't exist

[jd2media]

We tried this fix for our current blank statistics problem and it did not work.

Attached thumbnail(s)