Hi,
Seeing the error in the event log I think your most immediate problem may be the persistent mysql connections. This is a frequent cause of too many mysql connections errors. If I recall correctly MODx itself doesn’t by default
I agree here, the errors you see are most likely related to persistent mysql connections and the # of connections being maxed out. OpenX (the ad serving software) doesn’t use this by default, but you can check your setting in the OpenX admin panel’s Settings->Database settings
You’ll want to check the settings of the other web-software being used, too
Your hardware specs are quite good, so definitely tuning of the actual software (apache, mysql, php) being used is highly suggested. It can make a very large difference - MySQL settings often should change depend on the hardware available and how much of the available memory, etc, you want MySQL to use.
Some OpenX suggestions:
https://developer.openx.org/wiki/display/DOCS/Performance+Tuning
See the Children of the page for other general tips, like server monitoring and MySQL tuning
with 200k views a day your openads DB is probably around 20gb already and if you set everything up by their instructions you probably have a maintenance script running every hour or so - this kills the server.
With this case it sounds like something was wrong. 20GB is way too large for a 200k/day site -- hourly Maintenance shouldn’t kill the server but anytime the DB is 20gb the maintenance script will take quite a while to run, as will most other tasks.
I would suggest first to upgrade to the newest version of OpenX to ensure you have the newest bug fixes, including some which do help DB size, but also to follow the OpenX tuning tips above - a main setting is in the Statistics and Maintenance Settings page which lets you change how long raw statistics should be kept once they have been summarised -- if you lower this value then your database size can be much less.
Hope this helps,
Arlen Coupland
OpenX