Robin,
I can tell you what is wrong, although not for sure how to fix it. The
communication between webwork and your mysql database is still not yet
correctly set up. Instructions for setting permissions are at:
http://devel.webwork.rochester.edu/twiki/bin/view/Webwork/InstallationManualV2pt2#Database_configuration
specifically: $ mysql -u root -p mysql Password: ** ################## CREATE DATABASE webwork; > GRANT SELECT ON webwork.* TO webworkRead@localhost IDENTIFIED BY 'passwordRO'; > GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, ALTER, DROP ON webwork.* TO webworkWrite@localhost IDENTIFIED BY 'passwordRW'; > exit Bye $
You might try doing this again (Don't create the database again -- just
reissue the GRANT commands. ). The passwordRO should be the same as the
one in database.conf and the same for passwordRW. I believe what you
can read in the mysql webwork table will only be the encoded version of
these passwords,
so that might be the problem.
Also check to make sure that the admin course tables have been created in the database webwork:
e.g. webwork.admin_user webwork.admin_set webwork.admin_key and similar tables should exist.
One other trick you can try is to issue the GRANT command above omitting the entire
IDENTIFIED by clause at the end. Then set your passwords in database.conf to be empty
strings "". That might get you connected so that you can check that everything else is ok.
I can tell that you are using a slightly older version of webwork2 since now we only need
to set the password once in global.conf instead of database.conf. however I don't think that makes a difference:
cvs update -r rel-2-2-1 -d gets the latest stable release if you are hooked up to the cvs.
Take care,
Mike
<| Post or View Comments |>
|