I am using Fedora14_x64, apache2.2 and after installing webwork and creating a testCourse and a homeWork set I get these error messages when trying to display the homework set:
Any help greatly appreciated !!!
Hi Silvio,
This is the relevant part of your error message.
DBD::mysql::db selectall_arrayref failed: Table 'webwork.depths' doesn't exist at /opt/webwork/pg/lib/WeBWorK/PG/ImageGenerator.pm line 435.
I think the easiest fix will be for you to do
svn update
which should download the fix for your problem.
I believe that the version of webwork you installed is
automatically connected to the "trunk" version of the svn repository.
In case it is not there are "quick" instructions on using Subversion (svn) are at
http://webwork.maa.org/wiki/Subversion
There is an excellent online book (pdf) linked to at the end of that
wiki page if you wish to have the complete story.
--Mike
Revision: 6670
http://webwork.maa.org/viewvc/system?view=rev&revision=6670
Author: gage
Date: 2011-01-19 23:06:21 -0500 (Wed, 19 Jan 2011)
Log Message:
-----------
Add code to initialize depths, location and location_addresses when admin starts up
commented out utilities for dbExport and dbImport -- we aren't using those anymore.
This is the relevant part of your error message.
DBD::mysql::db selectall_arrayref failed: Table 'webwork.depths' doesn't exist at /opt/webwork/pg/lib/WeBWorK/PG/ImageGenerator.pm line 435.
I think the easiest fix will be for you to do
svn update
which should download the fix for your problem.
I believe that the version of webwork you installed is
automatically connected to the "trunk" version of the svn repository.
In case it is not there are "quick" instructions on using Subversion (svn) are at
http://webwork.maa.org/wiki/Subversion
There is an excellent online book (pdf) linked to at the end of that
wiki page if you wish to have the complete story.
--Mike
Revision: 6670
http://webwork.maa.org/viewvc/system?view=rev&revision=6670
Author: gage
Date: 2011-01-19 23:06:21 -0500 (Wed, 19 Jan 2011)
Log Message:
-----------
Add code to initialize depths, location and location_addresses when admin starts up
commented out utilities for dbExport and dbImport -- we aren't using those anymore.
Hi Silvio,
Mike's solution is the best one.
Another solution is the following. From the command line run the script wwdb_init. You must have downloaded WeBWorK when we were using this script. However when we changed things so that it was no longer needed (only a few weeks ago), we removed the instructions telling people to run it. You should find in in the directory /opt/webwork/webwork2/bin or /opt/webwork/webwork2/bin/old_scripts
Arnie
Mike's solution is the best one.
Another solution is the following. From the command line run the script wwdb_init. You must have downloaded WeBWorK when we were using this script. However when we changed things so that it was no longer needed (only a few weeks ago), we removed the instructions telling people to run it. You should find in in the directory /opt/webwork/webwork2/bin or /opt/webwork/webwork2/bin/old_scripts
Arnie
Arnold: I did not find the file wwdb_init.
I decide to download the stable version again, using svn, and reinstalled from scratch.
These are the messages I get.
I decide to download the stable version again, using svn, and reinstalled from scratch.
These are the messages I get.
Hi Silvio,
Have you updated your pg directory from the svn recently (and restarted the server)? I believe the last of the %hash errors was fixed around revision 6504 last november. (It won't be noticed by older perl compilers -- just the latest versions object to that construction.)
http://webwork.maa.org/viewvc/system?view=rev&revision=6504
I wonder if the error about WWPlot is also due to some files in PG being out of date or not being updated properly.
-- Mike
Have you updated your pg directory from the svn recently (and restarted the server)? I believe the last of the %hash errors was fixed around revision 6504 last november. (It won't be noticed by older perl compilers -- just the latest versions object to that construction.)
http://webwork.maa.org/viewvc/system?view=rev&revision=6504
I wonder if the error about WWPlot is also due to some files in PG being out of date or not being updated properly.
-- Mike
Hi Silvio,
You should find the file WWPlot.pm in the directory
/opt/webwork/pg/lib
It should be readable, e.g
-rw-r--r-- 1 wwadmin wwadmin 18659 2011-01-18 22:27 WWPlot.pm
Is this how it is on your system?
What OS are you using? Did you install WeBWorK from the SVN distribution or from the LiveDVD or ?.
Arnie
You should find the file WWPlot.pm in the directory
/opt/webwork/pg/lib
It should be readable, e.g
-rw-r--r-- 1 wwadmin wwadmin 18659 2011-01-18 22:27 WWPlot.pm
Is this how it is on your system?
What OS are you using? Did you install WeBWorK from the SVN distribution or from the LiveDVD or ?.
Arnie
Hi Arnie,
This is how it is in my system:
-rw-r--r-- 1 root root 16735 Feb 18 16:19 WWPlot.pm
I installed from SVN on a Fedora14-x64bits, apache 2.2, and I think perl-5.12.3.
This is how it is in my system:
-rw-r--r-- 1 root root 16735 Feb 18 16:19 WWPlot.pm
I installed from SVN on a Fedora14-x64bits, apache 2.2, and I think perl-5.12.3.
Hi Silvio,
Have you disabled Selinux. It's out of date, but take a look at http://webwork.maa.org/wiki/Installation_Manual_for_2.4_on_Fedora_11, especially:
Check That You Have Access To The Internet And Continue The Installation
Click on the FireFox icon and you should be connected to the world. If not, go back and check that all your entries are correct
Select System, Administration, Firewall. You will have to enter the . The Firewall Configuration window will open
Under Service check Secure WWW (HTTPS), SSH and WWW (HTTP). Then click File,Apply and click Yes to confirm. Then Quit
Select System, Administration, SELinux Management. The SELinux Administration window will open
Under System Default Enforcing Mode select Disabled. Then Quit
On newer versions of Fedora, the SELinux Management menu may not exist, and you may need to edit the file /etc/selinux/config and change one line to read SELINUX=disabled (instead of SELINUX=enforcing) while root
Don't skip the step of disabling SELinux or you will have a rat's nest of permission problems.
Arnie
Have you disabled Selinux. It's out of date, but take a look at http://webwork.maa.org/wiki/Installation_Manual_for_2.4_on_Fedora_11, especially:
Check That You Have Access To The Internet And Continue The Installation
Click on the FireFox icon and you should be connected to the world. If not, go back and check that all your entries are correct
Select System, Administration, Firewall. You will have to enter the . The Firewall Configuration window will open
Under Service check Secure WWW (HTTPS), SSH and WWW (HTTP). Then click File,Apply and click Yes to confirm. Then Quit
Select System, Administration, SELinux Management. The SELinux Administration window will open
Under System Default Enforcing Mode select Disabled. Then Quit
On newer versions of Fedora, the SELinux Management menu may not exist, and you may need to edit the file /etc/selinux/config and change one line to read SELINUX=disabled (instead of SELINUX=enforcing) while root
Don't skip the step of disabling SELinux or you will have a rat's nest of permission problems.
Arnie
Arnie,
selinux was disabled.
That's one of the first things I do after installing Fedora.
I installed Webwork following the installation instructions you have for Fedora11.
The only step I skipped was the one that commented out modules from the httpd.conf files.
The reason I skipped that step was that I might need those apache2 modules running for other virtual sites.
The question is: Can that be the reason why my WW is not working?
Thanks so much for your prompt responses,
Silvio
The attached file lists the module section of my httpd.conf file.
selinux was disabled.
That's one of the first things I do after installing Fedora.
I installed Webwork following the installation instructions you have for Fedora11.
The only step I skipped was the one that commented out modules from the httpd.conf files.
The reason I skipped that step was that I might need those apache2 modules running for other virtual sites.
The question is: Can that be the reason why my WW is not working?
Thanks so much for your prompt responses,
Silvio
The attached file lists the module section of my httpd.conf file.