On May 2, 2007, at 12:25 PM, Michael K wrote:

>
> On May 2, 10:09 am, Mark Phillips <[EMAIL PROTECTED]> wrote:
>> Being a newbie has its challenges...
>
> I know exactly what you mean.
>
>> The server is running mysql, I use phpMyAdmin and a couple of other
>> applications successfully with it.
>> There is an existing database of the same name as the new django
>> project.
>> I didn't find anything interesting in the logs, but then the django
>> logs are empty at the moment.
>> I did not find a file at "/tmp/mysql.sock"
>
> The error involving not being able to open the /tmp/mysql.sock usually
> has to do with host resolution OR the server being down (we've ruled
> that one out).  Simply put, your mysql isn't listening on a UNIX
> socket, but an actually IP address (be it a normal one, or 127.0.0.1),
> but the application is trying to open the UNIX socket, instead of the
> IP socket.
>
> Try setting DATABASE_HOST to 'localhost' instead of blank.  What OS
> are you running this on?
>
> HTH,
>
> Michael

Thank you, Michael. 'localhost' did not work but '127.0.0.1' did.

Happy days,

  - Mark


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to