by Ernie Havermale.
We are running under the default Unix OS standard on the AS400.
The server log doesn't say anything was wrong, the php server log shows:
Can not read response from /usr/local/ZendSvr6/bin/php-cgi.bin (0.0) - [0] There is no error.
Which without a program or line to work with is pretty useless.
by Emma Richardson.
1. Did you create the database?
2. If this is hosted, are you you using the correct location for the database?
3. Does the user specified in config.php have sufficient access to the database?
by Timothy Buell.
I am running Moodle on a few different domains. Purchasing SSL certificates can get expensive -- so can you tell me if it is possible to install the Moodle database for several different installations on a single domain, while maintaining separate domains for the individual installations?
by Manuel Antonio Rivera Socarras.
Hello Tim, I had the same problem as Richard Lian and I followed this post to the letter, only that when I debuge at the developer level the system shows me these lines:by Manuel Antonio Rivera Socarras.
Enma Richardson , I had the same problem as Richard Lian and I followed this post to the letter, only
that when I debuge at the developer level the system shows me these
lines:
Debug info: SELECT * FROM {modules} WHERE name =?
[Array (
0 => 'fm',
)]
Error code: invalidrecord
Stack trace:
Line 1502 of /lib/dml/moodle_database.php: dml_missing_record_exception thrown
Line 1478 of /lib/dml/moodle_database.php: call to moodle_database-> get_record_select ()
Line 425 of /course/modlib.php: call to moodle_database-> get_record ()
Line 63 of /course/modedit.php: call to can_add_moduleinfo ()
What can I do or what does this mean?
by Howard Miller.
I think you might be out there in weird operating system land unfortunately. That is, on your own.
I don't recall any mention of AS400 (I know it's not actually called that now - officially) in recent times.
Having said that Googling, "Can not read response...." has quite a lot of vaguely useful looking hits.
by Daniel S.
Thank you all so much for your support!
@Ken: I really appreciate all your hints and your time! Never came across that the order is so necessary. It'll take some time but I won't give up 'till I got it running (I also have no other option...)! I'll work through these steps.
Version of the db is: 2013111802.09
According to installation process it's 2.6.2+ (Build: 20140424) now updated to 2.6.11+
by . ..
LDAP-module cannot connect to any servers: Server: ''ldap://ipaddr'', Connection: '', Bind result: ''
I have search through the documentation, but have yet to find a solution to the problem. I have also tried to change it to 'ldap://myad.domain.com' but I still get the same message. I have checked the firewalls on the moodle and AD server. No problem there. I changed the bind from cn to ou to account@domain.com. Still nothing. Thoughts.
by Ken Task.
Sigh ... well, have to hand it to you ... you are determined ... and learning what doesn't work ... but that's good.
You are at a huge dis-advantage and given a job that requires some in-depth understanding of Moodle (something that really requires years ... not days)
Keep this concept in mind ... DB must match code ... moodledata must match what's in DB.
Work with a copy of the sql dump you have. Keep the original in case
you have to start over.
Hint provided ... MariaDB ... so am gonna guess you have CentOS.
Install nano editor ...
Work with a copy of the sql dump you have. Keep the original in case
you have to start over.
sql dump you have is 'moodle.sql' ... copy that file to another file by a different name:
cp moodle.sql moodletoedit.sql
Using nano (has search and replace) load up the .sql dump you have copied.
nano moodletoedit.sql
Search for: http://oldsite/ Replace with http://newsite/
Save.
Import the edited sql dump into MariaDB.
Using some tool to query/view the DB,
Look in mdl_config table.
In the name column there is one labels 'version'.
It will show a number ***like***: 2014111012 (I no longer have a 2.6 to look at)
That indicates the date the moodle software being used was released.
There is also a label for backup_release ... which will show 2.6
What you really need to find is the exact version that's in the DB.
**That requires the use of git** ... which is presently beyond your understanding
of Moodle code, the relationship to DB and to moodledata directory.
(Not that you couldn't get there, eventually, its just not needed right now)
Go to the true source of Moodle code ... that's not source forge ...
It's the git hub for Moodle ...
link:
https://github.com/moodle/moodle/archive/MOODLE_26_STABLE.zip
That will acquire the highest version of 2.6.
Use that code ... cause it's closest to what you have in the DB but it is
the highest subversion of 2.6. One of the recommendations in upgrading is to
always *update* the version you have to it's highest/most secure version first,
before upgrading to the next in the series ... in this case 2.7.highest
Install that code.
You have to manually create the config.php file for it.
Use config-dost.php as a guide ... copy config-dist.php to config.php
and then fill in values ... just the basics
DB user, DB password, DB, location of data directory, wwwroot URL, etc..
This **will/might result** in an **update** ... NOT an upgrade - to the version 2.6 to the highest/most secure/working version in that series. Now there might be
issues related to addons and plugins ... you have a base 2.6.x code but the database has references to addons/plugins that you don't have in the code directory.
You could find and download the zips for those and manually restore them.
Before doing that, however, I would research IF those addons have a version
for the desired end version ... that of 3.2.highest ... your goal.
IF the plugins/addons don't, some where along the march you will have to remove those
addons/plugins as they might stop an upgrade. No way round that either.
Now the moodledata directory matching should be closer ... but still might
have errors ... hopefully not as many. Can't do anything about that cept
to edit those links (each one) manually.
Am not aware of anyhing one could look at in moodledata that would be a clue as to the version of Moodle ... soooo.
FIX the 2.6 as best you can before upgrading to 2.7.
Before you attempt an upgrade do a full site backup ... code, DB, and data directory ... that becomes a fall back point just in case the next step fails.
'spirit of sharing', Ken
by Suzie Ama.
I have a new instance of Moodle 3.2 (not upgraded from a previous version). When attempting to install themes in the Plugin Installer, I get the following error:
Validating theme_eduhub ... Error [Error] Write access check [/home/educ/public_html/mod] Installation aborted due to validation failureI have tried five different 3.2 themes with the same result.
As an aside, when I first installed the instance, the config.php file could not be created automatically. I had to copy and paste code provided into a document and manually upload the config.php file. Is that related?
Suzie Ama
by Ken Task.
Welcome. So I take it that you now have a functioning 2.6.11+ site running, right?
Now the next step ... the hard way is the old way ftp files, copy plugins config.php etc. etc. ... leaves to much room for human error.
The *BEST* way is to use git. Assumes CentOS
skip this part ... go to **HERE** below cause you already have git.
Install git:
yum -y install git
Once it's installed ... whereis git ... will show the path to git ... probably in /usr/bin/git Perfect!
Now the tricky part ... can't update/upgrade a moodle code directory without the hidden .git diretory in the code directory.
So we side load a moodle 2.6.11+ directory using git, then copy the hidden .git directory from the sideload to the active code directory.
Let's say the code is in /var/www/html/
As root user, in /var/www/
issue the following command:
git clone git://git.moodle.org/moodle.git htmlgit
That will create a directory called htmlgit ... it's the one that will have the hidden .git directory in it.
Next cd htmlgit ... issue the following commands in the order shown:
git branch --track MOODLE_26_STABLE origin/MOODLE_26_STABLE
git checkout MOODLE_26_STABLE
to see what git has set:
fgrep '$release' version.php
should show you 2.6.11+
Great ... now the copy
You are still in /var/www/htmlgit
cp -rp .git ../html/.git
that's copy, recursively preserving permissions .git to ../html/.git which is up on level from htmlgit
When it's finished .... cd ../html/
Now check to see git works.
git pull [ENTER].
It shouldn't pull anything of core code ... it's already there and the highest version of that series.
** AFTER ** you have checked out the site ... everything works, ** MAKE A FULL SITE BACKUP **
** HERE **
mkdir /home/backup ... reason for creating location ... home is probably largest partition
from /var/www/ which should be the location of moodledata, issue the following commands
tar -cvf /home/backup/moodledata2611+.tar ./moodledata
tar -cvf /home/backup/moodlecode2611+.tar ./html/ that should get the code.
mysqldump -u [UPSERUSER] -p[password] [MDLDBNAME] > /home/backup/moodledb2611+.sql
Now to upgrade to 2.7 ... the easy way.
Back to using git.
git branch --track MOODLE_27_STABLE origin/MOODLE_27_STABLE
git checkout MOODLE_27_STABLE
git pull
(git will acquire 27 code and replace/add/delete whatever it needs ... but only core ... will NOT touch the addons/plugins)
php admin/cli/upgrade.php --non-interactive
The DB will be updated ... script uses the DB information in config.php of the site.
When that finishes:
fgrep '$release' version.php to see if it now says it's 2.7.highest.
** important **
You've been doing this as root ... all files/diretories that were changed below to root user and root group. Need to change them all for apache user and apache group. ... Uhhhh ... will harden later ... after the march.
while in /var/www/html/
chown apache:apache * -R
Check config.php ...
ls -l config.php ... that file needs to have at least read access by all - that's the last 'r' in the output of the ls -l config.php command.
Now hit site with browser.
Check things out ... get plugin updates.
Everything OK?
**BACKUP** changing the backup file names so they contain 27 version number.
Then we repeat the process ... changing only the numbers for the version we desire.
27 to 28
Here's one bash shell script you could use to either update or upgrade ... depending upon what's commented out. ** EDIT FOR YOUR SYSTEM ** If you don't have shell access .. get it.
put into /var/www/html/ to make the march easier
# 2.7.18 (Build: 20170109)
tar -cvf /home/backup/moodles/moodle2718-code-$(date +%Y%m%d%-H%M%S).tar ../moodle27;
tar -cvf /home/backup/moodles/moodle-data-2718-$(date +%Y%m%d%-H%M%S).tar /var/www/moodle27data;
mysqldump -u root -p[PASSWORD] moodle27 > /home/backup/moodles/moodle2718-db-$(date +%Y%m%d%-H%M%S).sql;
git branch -a
php admin/cli/cron.php;
php admin/cli/maintenance.php --enable;
git pull;
php admin/cli/upgrade.php --non-interactive;
# git branch --track MOODLE_28_STABLE origin/MOODLE_28_STABLE;
# git checkout MOODLE_28_STABLE;
# php admin/cli/upgrade.php non-interactive;
# php admin/cli/cron.php;
php admin/cli/maintenance.php --disable;
chown apache:apache * -R
fgrep '$release' version.php
Can 'march' a moodle up through each version 2.7->2.8->2.9->3.0->3.1->3.2 in one day's time
That includes backups and checking and acquiring updates to plugins via mdeploy via the Moodle UI as admin level user ... but not any config of additional features added in 3.1> of core.
'spirit of sharing', Ken
by Mary Evans.
Hi,
All this is related to your server. So it would all depend on how you have set up the server in the first place. If you are on a hosting package using a shared server, then yes it is possible Moodle cannot set up the config.php so you will need to do this manually. It also means that you will need to make sure your Moodle site directories are set up correctly. This is why you are having problems installing your theme too. Moodle cannot install the theme because of the read/write/execute permissions of your Moodle directories.
I will move this to the Installing help forum.
Hope this helps?
Mary
by Иван Харитонов.
Just yesterday I tried to install Moodle 3.2.1+ on a hosting server. I followed all the instructions but every time the outcome was the same: after the installation process ended and I was asked to configure administrator account (at moodle/user/editadvanced.php) I got stuck. The text box for user password just doesn't open, the link goes nowhere. I checked many possible reasons that I could find on FAQs and forums but none of them worked. PHP version and every other technical aspect seems to be OK. My database is fine and running but even manually creating a user wouldn't let me through. What else should I try?
Attached is the screenshot of that configuration page.
by Brijesh Yadav.
I have install a question type plugin. plugin was install success full massage. when i go back all the screen goes white. Nothing is working. site not open any pages. When i goes with block page url. it is working .but not open any admin file.. I have delete plugin manually. but nothing happen. Please help asap. Thanks in advance.
by Howard Miller.
Can you try the page again, this time with your 'Javascript Console' running (on Chrome it's View > Developer > JavaScript console). Do any errors appear?
Alternatively, you could use the command line installer (see Administration_via_command_line), although I would not be surprised if you still had problems in normal use.
Also, are you sure you don't have any software installed on your computer (extra firewall / security software) that might be causing this. Try disabling any such software.
by Howard Miller.
Sounds like a permissions error but we don't have much to go on. What sort of server or hosting is it? What instructions did you follow to install Moodle?I've said it before etc... but it pays you to spend a little time finding out and understanding how file permissions and ownership works on your chosen server or operating system. It will save you a lot of time in the end.
by Howard Miller.
Moving to Installation forum.......but, switch on Debugging. You will need to do it by copying lines from debugging section of config-dist.php to config.php. Check for messages displayed and check your error logs.
by Ken Task.
See if you can't purge caches ... via direct URL in browser
http://yoursite/admin/purgecaches.php
See if you can't go directly to:
http://yoursite/admin/qtypes.php
On that page, one has 'un-install' link. Try the un-install link - that not only removes files but removes records in the DB for the plugin.
Other wise,, turn on debugging via direct URL:
http://yoursite/admin/settings.php?section=debugging
logout
then hit main page again.
If you can't hit the debugging page, then set debugging manually by copying the debug lines from config-dist.php into config.php.
'spirit of sharing', Ken
