In one of your currently working Moodles, check out the php info link to show settings for PHP on SiteGround. If max time to execute is set to 30 seconds need to increase that. Initial installs also require more memory. Didn't say if you are on a shared plan or dedicated. Shared plan may not be a good environment for 2.7-> of Moodle.
I think you are correct. It was a time to execute issue.
However, I tried to do it again and it worked. The sixth time was a charm. Maybe the server or Internet connection
was a little faster this time and it worked as it should.
I could not find anything on that error code so I decided to
try a forum post.
It seems everything I do with moodle is in the spirit of
thinkering...
I've got Moodle 2.71 from Hostgator. Don't bother with the control panels one click install, even if you get it, it will be a dated 2.5 Moodle. Ensure your php is set to the latest version, it's in the control panel.
Follow this tutorial installing Moodle with HOSTGATOR, and if you still have a problem, send a ticket to Hostgator and they will fix it for you just as they have done for me. It's always a good idea to contact your host, as they normally know what to do. In fact they often don't just explain, more often than not they fix it for you. But beware, not all hosts are good, some are useless, and not helpful at all.
Hostgator is using a third party member called quick install, which I do believe you used. Hostgater is boasting that quick install keeps their software up to date. This is not true, and you could ask Hostgator to get this sorted with an up to date Moodle.
But best option is to follow the video instructions, get your mysql database sorted, download and upload to your file manager with the latest Moodle from here. It's the best way.
The problem I was having was resolved by setting the Hostgator PHP setting to "CURRENT." This is a menu choice under PHP administration resulting in PHP file processing by the most current PHP version available on Hostgator. Before the reset I was using a version earlier than 5.4.4
Hi Howard,really thanxs for giving this solution and it works but again i had problem the following error come while upgrading so what should i do please help
; If something does not work in Moodle ;opcache.revalidate_path = 1 ; May fix problems with include paths ;opcache.mmap_base = 0x20000000 ; (Windows only) fix OPcache crashes with event id 487
; Experimental for Moodle 2.6 and later ;opcache.fast_shutdown = 1 ;opcache.enable_cli = 1 ; Speeds up CLI cron ;opcache.load_comments = 0 ; May lower memory use, might not be compatible with add-ons and other apps.
Reload apache and it still doesn't work. I also try to comment out part *; If something does not work in Moodle* and error still occurs. Any idea what might be wrong?
I also read that might be a problem with themes. Before I upgrade I switch theme to Clean which is default theme in 2.7.
I have ubuntu 14.04 with PHP 5.5.9-1ubuntu4.3 (cli) (built: Jul 7 2014 16:36:58)
Not sure what came over me, but I finally decided to switch from MySQL 5.5 to MariaDB 5.5 (maybe too much reading and talking about performance optimizations)
The "migration" was smooth like "they" say it is. (uninstall mysql-server ... install mariadb-server)
After a few days of everything works fine (I am running 15 various Moodle versions servers on that development machine) came that weekly day where I do git pull on moodle.org master (dev) branch.
Running through the upgrade I got:
Debug info: Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging. InnoDB is limited to row-logging when transaction isolation level is READ COMMITTED or READ UNCOMMITTED.
INSERT INTO mdl_context (contextlevel, instanceid)
SELECT 30, u.id
FROM mdl_user u
WHERE u.deleted = 0
AND NOT EXISTS (SELECT 'x'
FROM mdl_context cx
WHERE u.id = cx.instanceid AND cx.contextlevel=30)
[array (
)]
Error code: dmlwriteexception
Stack trace:
line 446 of /lib/dml/moodle_database.php: dml_write_exception thrown
line 908 of /lib/dml/mysqli_native_moodle_database.php: call to moodle_database->query_end()
line 6432 of /lib/accesslib.php: call to mysqli_native_moodle_database->execute()
line 5922 of /lib/accesslib.php: call to context_user::create_level_instances()
line 1586 of /lib/upgradelib.php: call to context_helper::create_instances()
line 361 of /admin/index.php: call to upgrade_core()
My server currently
runs two separate versions of Moodle on two different websites.
One website runs
version 2.3.11 and the other runs 1.9.12
Both versions of Moodle
works as expected... NO PROBLEMS.
I have attempted all
of the following with no success.
Upgrade from 1.9.12
to to 2.0.10, I get as far as the plugins check, then on clicking the"upgrade" button I get a blank screen. No errors, no apache errors,
no nothing errors...
I have attempted a
fresh install of 2.0.10 with the same results.
I have attempted a
fresh install of version 2.5.7 as well as 2.6.4 - nothing works, all
installs or upgrade attempts indicate that my server has all the right PHP, MySQL
versions, etc... I have experimented to various tweaks in the config.php and
many other hacks.
I have searched Moodle
forums for solution and read and attempted every logical suggestion or similar suggestion
fix - nothing works.
This is beyond
frustrating - my server is running two versions of Moodle just fine...
Suggestions? Are there any advanced server configuration capability checks
available for Moodle?
PHP 5.5.X does require the Visual C++ Redistributable for Visual Studio 2012. You also need to make sure you get the right version of these files. If you are running 64bit PHP you need the 64bit VC11 files. You also need to make sure you get the correct files for either Apache or IIS. You can go here to get them http://windows.php.net/download/ just look in the left column for the file information.
Just a note about the 64bit builds of PHP, they are currently experimental and I would not recommend using them on any production environment.
You are indeed running Linux Debian ... at least that's what X-Powered shows.
Verify before doing what is suggested below ... ie, check your apache2.conf.
DOCUMENT_ROOT /var/www/ - this found in apache2.conf so moodledata can be in /var/ but must be owned by apache2 user or www-data (don't remember which Debian boxen uses). If you have WP at your site in front of Moodle, check the ownerships of those files.
In the config.php file for Moodle give the full path to moodledata ... which would be /var/moodledata
Thanks! I have tried with /var/moodledata without success.
Being incompetent in Linux/PHP (I am here just using a FTP tool), I asked my webmaster for a copy apache2.conf. Or you have a way to help me retrieve it?
