If I were looking for temptables that were not deleted as they should be from the database, what would they be names. (I did not find anything called temptables)
And by the way, if I were to check to see what access privleges have been granted to" moodleuser" in my installation, where would I check that?
If the tar.gz files were transferred via ascii not binary, then it's possible to get 'extra' characters.
What happened when the tar.gz (or tar) files were un-compressed?
Did they report something like:
gzip error: stdin: invalid compressed data - format violated?
There is a tool to fix such issues (have not had first hand experience with it but some folks say it works:
Something to check:
Do a mysql query of mdl_files on the troubled instance DB for the humanly recognized file name and contenthash.
Query: select contenthash, filename from mdl_files;
One row example:
188946b0a15d2d08a72ab3debc6c31e2adeca37d | Verb Practice Quick.docx
The contenthash shows where the file is located:
filedir/18/89/188946b0a15d2d08a72ab3debc6c31e2adeca37d
To see if that file is really messed up, one could copy it out to some location and see if it could open in anything:
From moodledata directory:
cp filedir/18/89/188946b0a15d2d08a72ab3debc6c31e2adeca37d /home/test/Verb Practice Quick.docx
And then in /home/test/
file -b "Verb Practice Quick.docx" should show that it's a zip (a .docx is just that).
Then mv "Verb Practice Quick.docx" test.zip
unzip test.zip
inflating: [Content_Types].xml
inflating: _rels/.rels
inflating: word/_rels/document.xml.rels
inflating: word/document.xml
inflating: word/theme/theme1.xml
inflating: word/settings.xml
inflating: word/webSettings.xml
inflating: word/styles.xml
inflating: docProps/core.xml
inflating: word/numbering.xml
inflating: word/fontTable.xml
inflating: docProps/app.xml
If you can do all that, there might be something strange in the tables related: mdl_files. An extra space at the end of the filename field of the DB?
'spirit of sharing', Ken
I hadn't made a backup but I kept my Moodle, Moodledata, and MySQL folder with the files just in case, but when I placed those files back in after reinstalling I couldn't even get the page to come up for localhost.
thx alot, i solve it
thx alot, i solve it
Barb,
The issue is clear, installing moodle from a script installer, and that is NOT recommended, for script installers do not keep up to date versions of moodle with them, but only base versions, like they will keep 2.9, but not updated versions like 2.9.x, so sometimes there are files missing or corrupted from package installer.
Best thing you would have done is, downloading the package from Moodle site and then upgrading even if your initial install was from script installer, all you have to do is copy over plug-in folders and config.php file to new moodle folder.
Hi Emma,
Thank you for trying to help me out. I cleared the cache folders - but it made no difference.
I have contacted hostgator regarding this issue. Awaiting a reply. For moodle installations, I don't see the .htaccess file. Why is that?
After considerable effort updating to the most recent version of MySql and a subsequent reboot of my system, I'm getting a "The website cannot display the page" message. It may be a silly question, but can someone suggest what the problem may be? Thanks. - Brian
It really depends on your setup with the host. Some hosts use a htaccess file - some use a php.ini file - you might compare your existing installation to your new one and see if there are any files in the old install that are not in the new one - that should give you a clue.
I have a current Moodle installation. I have edited various site settings and capabilities. I am also using the More theme. I have create a new installation of Moodle for another organization. Is there a way to import the site settings and capabilities from my first installation into the new installation?
I recently stumbled over a very useful looking plugin called Admin presets. Depending on the plugins you used it should be able to do the vast majority, if not all, that you need.
Hi Ken,
First of all thanks for the time you've taken to reply to my very first query here at the moodle forums - it is much appreciated.
In fact all transfers were done in binary (I use plain ftp command line where I try to control all file transfer settings).
I will dig in a bit deeper based on the DB hints you've left here. I will share once/if I have some news.
Thanks again,
Gama
Kishore, have you made any changes to the database? as in upgrading it or changing permissions? or even changing PHP?
have you copied over the config.php file to new moodle 2.9 folder?
No Usman, Just I just copied previous config.php file in to my new version of moolde folder (2.9).In database also I am not done any changes. Even i am not changed db name and db user name and db password also.
So essentially before upgrade, everything is working absolutely fine?
if its showing issues then try upgrading to next highest, i.e 2.7 and see if that works, if that showed problems then have a look into permissions.
But you stated at the beginning that you had to enter the database details when you upgraded - this means that that the install did not see your config.php file. I would try recopying over your config.php file and making sure that the permissions are correct on it.
Thanks for quick around.Yes Usman ,previously it's working good. When I tried to upgrade with 2.9 then only I am facing this issues and i tried to upgrade 2.7 but it's working. May I know why it is coming.....
Afternoon all,
I've got an interesting one for you today. I am just upgrading our test Moodle to the latest 2.9+ and during the initial server checks I get the following
unsupported_db_table_row_format if this test fails, it indicates a potential problem
Your database has tables using Antelope as the file format. You are recommended to convert the tables to the Barracuda file format. See the documentation Administration via command line for details of a tool for converting InnoDB tables to Barracuda.
In the Options File of MySQL I changed the InnoDB format settings to Barracuda then tried the upgrade again but still got the same. Does anybody know anything about this and why it's suddenly appeared in 2.9?
This doesn’t stop the upgrade but I I want to make sure by not converting it's not going to have any negative affects further down the line.
Cheers,
Hi Graham,
Did you see this discussion - sounds like the same issue. https://moodle.org/mod/forum/discuss.php?d=314802
If its working on 2.7, then should work on 2.9 as well, considering its a big jump may be something's not working as it should.
upgrade to 2.7 first, and then see if it can be upgraded to 2.9
but before that, are you using Apache or IIS Express?
on windows installation (if done automated through WPI), sometimes it asks for salt password (this may will be removed in future installations), see if your config file has salt password in it.
Also, like Emma mentioned (I must have missed that valid point though), why do you have to enter your database username and password again when updating? just copying over the config.php file inherits all the information that is required by moodle for installation so you dont need to provide information once again, only thing will be environment check and next buttons.