Quiubu Su, "LAMP" stands for Linux+Apache+MySQL+PHP. So yes, you have a LAMP stack.
Since you say you have created the socket file by hand, it may be that permissions got screwed up. This would not explain why the problem happened in the first place, unless you had done something else before you rebooted that might have changed permissions on one of that file's parent directories. If the socket file is not getting created by the mysql init script then this is a likely cause.
If this doesn't help, Quiubu Su, then your problem is officially out of my league, and I commend your soul to more capable hands. However, I can still suggest that you google the error you're getting, and see if you can find clues from more general sources. At the end of the day this doesn't really appear to be a Drupal issue but a Linux / MySQL one. Sorry I couldn't help you more.
On 11/05/2010 08:38 AM, Shai Gluskin wrote:
I'm late to this issue. What I'm reporting likely has nothing to do with the issue... /but just in case/... and others should know about this anyway:
*backup_migrate module v. 2.3 with table-locking turned on will crash mysql on your server.*
There is a patch, but 2.3 is still the recommended release: http://drupal.org/node/952584
Shai
On Fri, Nov 5, 2010 at 6:13 AM, Qiubo Su (David Su) <qiubosu@gmail.com mailto:qiubosu@gmail.com> wrote:
On Fri, Nov 5, 2010 at 10:36 PM, Victor Kane <victorkane@gmail.com <mailto:victorkane@gmail.com>> wrote: But what mystifies me is that quiuboso says it was running fine before he rebooted. 1. How much memory in the Ubuntu base machine? 2.5G 2. Is the VM Ubuntu too? Yes It has 1 GB? Yes 3. The VM effectively has a LAMP stack installed together with Drupal? No LAMP, I installed PHP, Apache, MySql manually On Fri, Nov 5, 2010 at 12:05 AM, Nick Holden <nick@thewebtailor.co.uk <mailto:nick@thewebtailor.co.uk>> wrote: Some versions of MySQL default to only allowing local connections to the server. It's not clear from what you've written if, when you 'use a VM for this', the drupal install and the MySQL server are both on the VM. If not, you might need to alter the MySQL config to allow connections over the network from another machine. Not only that but you might need to change the GRANT command issued during the drupal set up, because if you grant permissions to a user @ a certain machine or IP those permissions do not apply if the user (in this case the drupal system) connects from a different machine or IP. Hope that helps. I'm away from my desk so can't give exact advice, but that's what struck me when you mentioned using a VM. Nick Sent from my BlackBerry® wireless device -----Original Message----- From: "Qiubo Su \(David Su\)" <qiubosu@gmail.com <mailto:qiubosu@gmail.com>> Sender: support-bounces@drupal.org <mailto:support-bounces@drupal.org> Date: Fri, 5 Nov 2010 09:59:15 To: <support@drupal.org <mailto:support@drupal.org>>; <cjones@partialflow.com <mailto:cjones@partialflow.com>> Reply-To: support@drupal.org <mailto:support@drupal.org> Subject: Re: [support] urgently need help for Site off-line error -- [ Drupal support list | http://lists.drupal.org/ ] -- [ Drupal support list | http://lists.drupal.org/ ] -- [ Drupal support list | http://lists.drupal.org/ ] -- [ Drupal support list | http://lists.drupal.org/ ]