Not signed in (Sign In)
Welcome Guest!
Want to take part in these discussions? If you have an account, sign in now.
If you don't have an account, apply for one now.

Installing Akelos: Could not connect to booklink_tests database

Bottom of Page

1 to 7 of 7

  1.  
    • CommentAuthorsteinitz
    • CommentTimeMar 26th 2008
     
    Hello,

    I'm playing around with Akelos on Mac OS X Leopard.

    For expedience, I decided to use the the sqlite option for the booklink tutorial. I created sqlite database per the naming in the install wizard:

    booklink_dev-T8KGRSUT.sqlite
    booklink_tests-T8KGRSUT.sqlite
    booklink-T8KGRSUT.sqlite

    But when I click continue, I get

    Could not connect to booklink_tests database

    I've set the permissions of everything in sight to 777

    I searched the archives but couldn't see anyone else having this problem.

    I'm going to install MySQL as a workaround but I thought this report might interest someone.

    Best regards,

    Steve
    • CommentAuthorsteinitz
    • CommentTimeMar 26th 2008
     
    Hello again,

    I installed mysql and created an akelos user. I created the three databases and granted privileges to akelos for all three. Using MySQL Administrator, I confirmed that the akelos user can access the three databases. I ran the booklink wizard at localhost/booklink and got the same message as before: Could not connect to booklink_tests database. Is there any way I can get more detailed diagnostic messages?

    I tried restarting mysql to no avail.

    Thanks,

    Steve
    • CommentAuthormvitjiten
    • CommentTimeMar 26th 2008
     
    I also got the same problem as mentioned by steinitz. But then i stopped my server(apache.) and mysql. then i started again. And the problem get solved.
    Again if you r using mysql then check for password.Keep the password field blank and try once.I think you will get the solution.
    Otherwise please notice it in this blog.
    • CommentAuthorThijs
    • CommentTimeMar 26th 2008
     

    Steinitz, are you using MAMP?

    If so, look here

    I had the same problem. Changing the 'socket' setting -as mentioned in the first posts- didn't work. (well, maybe now with a newer trunk version it might work)
    You'll probably have to change the socket for you system. (see the latest posts in the discussion)

    • CommentAuthorsteinitz
    • CommentTimeMar 26th 2008
     
    Thank mvitjiten and Thijs.

    mvitjiten - I restarted apache and mysql and played around with password as suggested.

    Thijs - thanks for the pointer to the other thread -- I set up a symlink as suggested there.

    Its late here in Sydney. I think I'll get a fresh start tomorrow.

    Thanks again for your help.

    Steve
    • CommentAuthorsteinitz
    • CommentTimeMar 26th 2008
     
    Hello,

    I had a closer look at the mamp thread. I'm not using the mamp product so I had to take a slightly different approach. A non-mamp mysql, on Mac OS X Leopard, creates the mysql.sock file at /private/tmp/mysql.sock. That file is deleted after mysql stops. Still, as an experiment based on the mamp thread, I created a mysql directory in /var and in it I created a symlink to the temporary mysql.sock file. That allowed the Akelos wizard to get to the next step.

    I think the MySQL documentation shows a way to have mysql create the socket in a less temporary location. I might look into that later.

    Thanks again for your help,

    Steve
    • CommentAuthork00k
    • CommentTimeMay 2nd 2008
     
    Thanks Steve. That worked for me as well. Just to clarify for anyone else in the same boat:

    1) Create /var/mysql directory
    2) Create a symbolic link to mysql.sock there with the folowing command:

    ln -s /private/tmp/mysql.sock /var/mysql/mysql.sock

1 to 7 of 7

  1.  
Add your comments
    Username Password
  • Format comments as
 
Back to Discussions Top of Page