On Fri, Oct 29, 2010 at 8:53 AM, Jordan Aberle wrote: > I have tried to visit the website last night as well as this morning but > there seems to be a database problem. It is saying 'mysql: too many > connections' but I tried accessing the website early this morning - I doubt > it was getting bombarded by millions of plug members. :) > > Any eta? > > Thanks, > Jordan > > --------------------------------------------------- > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us > To subscribe, unsubscribe, or to change your mail settings: > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss > Exact Error is: Failure to connect to your MySQL database server. MySQL reports the following message: *Too many connections*. - Are you sure you have the correct username and password? - Are you sure that you have typed the correct database hostname? - Are you sure that the database server is running? For more help, see the Installation and upgrading handbook. If you are unsure what these terms mean you should probably contact your hosting provider. I doubt that this was due to Hans upgrading it! There were also unauthorized ssh access from Russia; I recommended the server be rebuilt, after full forensics on the logs and server and replacing the old debian insecure SSL. I rebuilt an old 1 U server that they had for the purposes of replacing the web server/installation, but the ball was dropped somewhere with a human bandwidth issue with Hans. That CMS had a great many Drupal security updates that I recommended we update, but Hans did not authorize the work then, wanting to keep legacy functions in some of the tools that were obsolete in 6.0. The Drupal version was an upgraded 4 with a core patch and many modules that would not be compatible. A complete plan was created, and I installed the replacement Drupal in another directory running concurrently on another port 81. The balll was dropped on that cut-over as well, because Hans didn't want to lose all those years of content. I often found the site with the databases curiously rolled back to old edits and reported those errors. I am not on the disaster recovery team; and my bandwidth is limited (especially after already doing all this work/engineering), but if you need any help give me a call. It might just be a database overrun issue with the repeat date functions (which were dropped with that code module due to thrashing like this). If that's so, one simply has to roll back to the last dump and it should continue to run until next time. I don't think anything but the best, most state of art Drupal installation should be in place for a Linux group, but that's just me. -- Skype: 6022393392 ATT: 5037544452 GV: 6236883392 http://www.it-clowns.com Politicians should read science fiction, not westerns and detective stories. -Arthur C. Clark