I have set the sessioncookie prefix in the first install, deleted all cookies in my browser but still the same problem.
Any suggestions?
Paz y Bien.
Jennison Grey:
Sugiero lo siguiente:
Si la priomera versión está correcta, entonces de nombre las carpetas nuevas:
1. Para el archivo de datos: moodlebase2
In the Command Console made database. Name: moodlebase2
2. Para los archivos de instalación: moodle2.
In your local host (root) httpdocs/moodle2
3. Para la base de datos: moodledata2
In your local host (root) httpdocs/moodledata2
De esta manera todo está en congruencia, sin afectar o comper otros directorios.
http://www.myhost.com/moodle2 (for example) Y sólo procederá la instalación.
I would like to receive feedback.
Saludos desde México.
José de Jesús
I'm not sure I undestand you well but:
I have 2 installations exactly the same in the same locations, the first being my production site called moodle the second a site for users to practice on named doodle (it is for use in a school where many of the teachers are not particularly IT comfortable - hence the humorous name).
To install the first I created a database moodle, a folder for that moodle's data called moodledata on another drive (d:\moodledata) and then moodle in www_root/moodle. That installation works fine.
After changing the cookie prefix in the first installation I installed the second installation exactly the same. Created a database doodle alonside the original moodle, created a data folder doodledata alongside the moodledata folder and installed the moodle at www_root/doodle.
This second install completes only as far as the "Checking your environment .."screen and then comes up with the error message but no details.
Both installs use the same Moodle version 1.8.2 so I can't see why they don't work exactly the same.
Thanks Jennison
Peace and Well.
Jennison:
It must remember that the names of them data base must be different: it moodlebase - for that already moodlebase2 for the new installation is working. He remembers that the directories of data (of moodle) also must be called different: moodledata (for already works; moodledata2 (for the new installation). My English in poor man, I must resort to my wife, she lived in the USA. But, I can understand what you say to me.
José de Jesús
JdJEQ,
I would only add that I believe one can use the same database for two Moodle installations if one uses a different prefix for each.
RLE
Peace and Well. Richard:
Ah. I do not know how to do it. But you I do not recommend it, if they are more than three courses and more than 150 students. It remembers that the data base goes to be shared and that area code RLE can cause that the data transfer is slow.
Greetings from México.
José de Jesús.
JdJEQ,
You may be right. I am not an expert on database server efficiency. But as for how to do it, that I can tell you. When you run the Moodle install script install.php, and it asks for your database type, username, password, database name, and table prefix, you just type the same database name for each installation, but a different prefix. The default prefix is MDL_. It is added on the left to the name of each table Moodle creates. That way, each Moodle will have its own set of tables within the same database.
At what point sharing a database with the tables of another Moodle installation would cause slower data transfer than having its tables in a separate database from the other installation, but both handled by the same database server, I do not know. The only thing I can think of that would be slower would be backing up the database, because it would be bigger. But you would still eventually have to back up both databases anyway.
RLE
I'd be inclined not to share a database, as each of my database folders contains four files which don't have the chosen prefix for that Moodle (adodb_logsql.frm, adodb_logsql.MYD, adodb_logsql.MYI, and db.opt).
I don't know what these files do, but if you try to make two Moodles share the same database they might end up fighting over these four files.
For safety I'd have a separate database for each Moodle.
Chris
CL,
You might be right. But if you are, it raises some questions:
- What is the purpose of having table prefixes at all, if Moodle databases are not shared with anything else, including other Moodle installations?
- I know that three of the four files you named are the table adodb_logsql. I suspect that if Moodle installations would fight over that table, the designer(s) of Moodle would have applied the prefix to it. I therefore suspect that their intension was for multiple Moodle installations to share that table.
- I don't know what the fourth file is, but the name suggests it contains option settings that apply to the database as a whole.
- I recently installed Moodle 1.8 on my PC for testing, etc. I haven't been able to do much with it yet (that's a separate issue), which might be why the adodb_logsql table on mine is empty. But for whatever it's worth, this is what it looks like:
mysql> select * from adodb_logsql;
Empty set (0.59 sec)
mysql> describe adodb_logsql;
+---------+---------------------+------+-----+----------+----------------+
| Field | Type | Null | Key | Default | Extra |
+---------+---------------------+------+-----+----------+----------------+
| id | bigint(10) unsigned | NO | PRI | NULL | auto_increment |
| created | datetime | NO | | | |
| sql0 | varchar(250) | NO | | | |
| sql1 | text | YES | | NULL | |
| params | text | YES | | NULL | |
| tracer | text | YES | | NULL | |
| timer | decimal(16,6) | NO | | 0.000000 | |
+---------+---------------------+------+-----+----------+----------------+
7 rows in set (0.16 sec)
RLE
Peace and Well.
Jennison Congregation:
I suggest the following thing:
If the first version is correct, then of name the new folders:
1. For the data file: moodlebase2 In the Console Command made database. Name: moodlebase2
2. For the installation archives: moodle2. In your local host (root) httpdocs/moodle2
3. For the base of data: moodledata2 In your local host (root) httpdocs/moodledata2 This way everything is in congruency, without affecting or to cobreak the archives o directories. http://www.myhost.com/moodle2 (for example) and will only come the installation.
I would like to receive feedback.
Greetings from Mexico. Jose de Jesus
Jose de Jesus, thanks for your help.
I did manage to get it to work by deleting the second Moodle installation and reinstalling it. I made no changes to the database nor the moodle documents folder. Somewhere during the Moodle setup process something must have been currupted which would not allow it to proceed.
Thanks again
and greetings from Oxford - UK.