Joomdle 1.0 Installation
System Check Errors
- Keith
-
Topic Author
- Offline
- New Member
-
Less
More
8 years 8 months ago #1
by Keith
System Check Errors was created by Keith
Our client has requested that we upgrade his installation of Moodle and at the same time install an SSL certificate. We started by upgrading their Joomla to 3.7.4 this was not straight forward like on other non Joomdle sites as we had to load the .zip file directly in order for the site to upgrade - all is OK now with that part.
We then installed a new copy of Moodle and set the database to call the old database. We checked the PHP version is set to 7.1 and that XMLRPC is turned on. We have access to EasyApache 4 controls through our cPanel. (We have at no point attempted the SSL certificate - we will not do this until the site is fully tested as working.BTW)
Our Joomdle System Check shows: both Moodle and Joomla HTTP connectivity errors - we have checked folders are set to 0744 and files to 0644. Joomdle Web Services is also showing they are not working.
When checking Users I get this error: XML-RPC Error (26045186):
and the same for Course Requests, Mailing Lists and Forums
If I check myurl/moodle I get this error:
Fatal error: Out of memory (allocated 16777216) (tried to allocate 131072 bytes) in /home/xxx/public_html/xxxx.co.uk/moodle/lang/en/moodle.php on line 546
Any ideas where I should start to repair this Please?
Many thanks
Keith
We then installed a new copy of Moodle and set the database to call the old database. We checked the PHP version is set to 7.1 and that XMLRPC is turned on. We have access to EasyApache 4 controls through our cPanel. (We have at no point attempted the SSL certificate - we will not do this until the site is fully tested as working.BTW)
Our Joomdle System Check shows: both Moodle and Joomla HTTP connectivity errors - we have checked folders are set to 0744 and files to 0644. Joomdle Web Services is also showing they are not working.
When checking Users I get this error: XML-RPC Error (26045186):
and the same for Course Requests, Mailing Lists and Forums
If I check myurl/moodle I get this error:
Fatal error: Out of memory (allocated 16777216) (tried to allocate 131072 bytes) in /home/xxx/public_html/xxxx.co.uk/moodle/lang/en/moodle.php on line 546
Any ideas where I should start to repair this Please?
Many thanks
Keith
Please Log in or Create an account to join the conversation.
- Antonio Durán
-
- Offline
- Moderator
-
Less
More
- Posts: 7909
8 years 8 months ago #2
by Antonio Durán
Replied by Antonio Durán on topic System Check Errors
Hi Keith.
>If I check myurl/moodle I get this error:
>Fatal error: Out of memory (allocated 16777216) (tried to allocate 131072 bytes) in /home/xxx/public_html/xxxx.co.uk/moodle/lang/en/moodle.php on line 546
So, you say you cannot open Moodle after upgrading? Or you did not even upgrade? From this error, it seems you need to allow more memory for PHP.
> upgrading their Joomla to 3.7.4 this was not straight forward like on other non Joomdle sites as we had to load the .zip file directly in order for the site to upgrade
Not sure what you mean: Joomdle does not interfere with Joomla automatic updates.
>If I check myurl/moodle I get this error:
>Fatal error: Out of memory (allocated 16777216) (tried to allocate 131072 bytes) in /home/xxx/public_html/xxxx.co.uk/moodle/lang/en/moodle.php on line 546
So, you say you cannot open Moodle after upgrading? Or you did not even upgrade? From this error, it seems you need to allow more memory for PHP.
> upgrading their Joomla to 3.7.4 this was not straight forward like on other non Joomdle sites as we had to load the .zip file directly in order for the site to upgrade
Not sure what you mean: Joomdle does not interfere with Joomla automatic updates.
Please Log in or Create an account to join the conversation.
- Keith
-
Topic Author
- Offline
- New Member
-
8 years 8 months ago #3
by Keith
Replied by Keith on topic System Check Errors
We then installed a new copy of Moodle and set the database to call the old database. We checked the PHP version is set to 7.1 and that XMLRPC is turned on.
So yes we cannot see noodle after upgrade.
We have set php memory to -1 for Joomla where do we set this for noodle then?
Many thanks
keith
So yes we cannot see noodle after upgrade.
We have set php memory to -1 for Joomla where do we set this for noodle then?
Many thanks
keith
Please Log in or Create an account to join the conversation.
- Antonio Durán
-
- Offline
- Moderator
-
Less
More
- Posts: 7909
8 years 8 months ago #4
by Antonio Durán
Replied by Antonio Durán on topic System Check Errors
It's not moodle, it's a php.ini setting. You need to increase memory_limit so you can open Moodle and complete the upgrade.
Please Log in or Create an account to join the conversation.
- Keith
-
Topic Author
- Offline
- New Member
-
8 years 8 months ago #5
by Keith
Replied by Keith on topic System Check Errors
I can only find one php.ini file associated with the Joomla website that calls moodle, it looks like this:
; cPanel-generated php ini directives, do not edit
; Manual editing of this file may result in unexpected behavior.
; To make changes to this file, use the cPanel MultiPHP INI Editor (Home >> Software >> MultiPHP INI Editor)
; For more information, read our documentation ( go.cpanel.net/EA4ModifyINI )
allow_url_fopen = On
allow_url_include = Off
display_errors = Off
enable_dl = Off
file_uploads = On
max_execution_time = 30
max_input_time = 60
max_input_vars = 1000
memory_limit = -1
session.gc_maxlifetime = 1440
session.save_path = "/var/cpanel/php/sessions/ea-php71"
upload_max_filesize = 100M
So the memory allocation is at it maximum - no?
; cPanel-generated php ini directives, do not edit
; Manual editing of this file may result in unexpected behavior.
; To make changes to this file, use the cPanel MultiPHP INI Editor (Home >> Software >> MultiPHP INI Editor)
; For more information, read our documentation ( go.cpanel.net/EA4ModifyINI )
allow_url_fopen = On
allow_url_include = Off
display_errors = Off
enable_dl = Off
file_uploads = On
max_execution_time = 30
max_input_time = 60
max_input_vars = 1000
memory_limit = -1
session.gc_maxlifetime = 1440
session.save_path = "/var/cpanel/php/sessions/ea-php71"
upload_max_filesize = 100M
So the memory allocation is at it maximum - no?
Please Log in or Create an account to join the conversation.
- Keith
-
Topic Author
- Offline
- New Member
-
8 years 8 months ago #6
by Keith
Replied by Keith on topic System Check Errors
In MultiPHP INI Editor I changed memory_limit from -1 to 512M still no change in moodle error:
Fatal error: Out of memory (allocated 16777216) (tried to allocate 131072 bytes) in /home/xxx/public_html/xxx.co.uk/moodle/lang/en/moodle.php on line 546
Fatal error: Out of memory (allocated 16777216) (tried to allocate 131072 bytes) in /home/xxx/public_html/xxx.co.uk/moodle/lang/en/moodle.php on line 546
Please Log in or Create an account to join the conversation.
- Antonio Durán
-
- Offline
- Moderator
-
Less
More
- Posts: 7909
8 years 8 months ago #7
by Antonio Durán
Replied by Antonio Durán on topic System Check Errors
PHP configuration depends on hosting company. You easiest way is to ask your hosting company how to increase memory limit (attach the error you are getting so they see what problem you are having)
Please Log in or Create an account to join the conversation.
- Keith
-
Topic Author
- Offline
- New Member
-
8 years 8 months ago #8
by Keith
Replied by Keith on topic System Check Errors
I thought it may be helpful to show how this was solved. We tried hard ourselves to rectify the memory issue we had but in the end we spoke to our VPS provider and they increased the Apache RLimits up to 1024M. This then enabled Moodle to work and we completed the upgrade.
The only remaining problem was that Joomdle auth method was disabled in Moodle. After enabling it, system check is all green!
Excellent support as always - thank you
The only remaining problem was that Joomdle auth method was disabled in Moodle. After enabling it, system check is all green!
Excellent support as always - thank you
Please Log in or Create an account to join the conversation.