by Reece Jones.
FIX:
Deleted the mdata/muc/config.php file
Purge All Caches.
by Reece Jones.
FIX:
Deleted the mdata/muc/config.php file
Purge All Caches.
by Mikel Ortueta.
Forgive me for my typos :S ... It is like I am dyslexic or maybe tired of trying to solve the problem without success.
Yes It is: /etc/php5/apache2 .As you said the other directory it does not exist.
Yep I searched in the suggested directory (/etc/php5/apache2/conf.d) but there is nothing that
The files in that directory are this ones:
05-opcache.ini 20-gd.ini 20-mysqli.ini 20-readline.ini
10-pdo.ini 20-intl.ini 20-mysql.ini 20-xmlrpc.ini
20-curl.ini 20-json.ini 20-pdo_mysql.ini
this files reference to extensions in /usr/lib/php5/20131226/
Itryed purging the cache of moodle also the browser's cache without success... Even changin the browser from Mozilla to Chrome.
Any leads on how to solve this... I am getting mad.
@Emma Richardson Sinceerely thank yo for your help
by Carlo Grandi.
Hello,
my Moodle version is Moodle 3.1.1+ (Build: 20160728).
In settings I have max_upload: 128Mb but...I can't upload a 20 Mb file.
Steps in a course: 'Add an activity or resource' -> File -> add -> 'Select Files' -> 'Upload a file'.
In Chrome the file is loaded up to 100%, then stops; the wheel keeps turning; looking at the Chromeconsole, appears the message:
Failed to load resource: the server responded with a status of 503 (Service Unavailable)
Uncaught TypeError: Cannot read property 'msg' of null
at FilePickerHelper.complete (filepicker.js:1)
at e.Subscriber._notify (yui_combo.php:40)
at e.Subscriber.notify (yui_combo.php:40)
at e.CustomEvent._notify (yui_combo.php:39)
at e.CustomEvent._procSubs (yui_combo.php:39)
at e.CustomEvent.fireSimple (yui_combo.php:39)
at e.CustomEvent._fire (yui_combo.php:39)
at o.fire (yui_combo.php:40)
at o._evt (yui_combo.php:206)
at o.complete (yui_combo.php:206)
complete @ filepicker.js:1
_notify @ yui_combo.php:40
notify @ yui_combo.php:40
_notify @ yui_combo.php:39
_procSubs @ yui_combo.php:39
fireSimple @ yui_combo.php:39
_fire @ yui_combo.php:39
fire @ yui_combo.php:40
_evt @ yui_combo.php:206
complete @ yui_combo.php:206
_uploadComplete @ /elearning/theme/yui_combo.php?3.17.2/datatype-xml-parse/datatype-xml-parse…bold/button/button-min.js&m/1484088153/atto_italic/button/button-min.js:32
(anonymous) @ /elearning/theme/yui_combo.php?3.17.2/datatype-xml-parse/datatype-xml-parse…bold/button/button-min.js&m/1484088153/atto_italic/button/button-min.js:32
_notify @ yui_combo.php:40
notify @ yui_combo.php:40
_notify @ yui_combo.php:39
_procSubs @ yui_combo.php:39
fireSimple @ yui_combo.php:39
_fire @ yui_combo.php:39
fire @ yui_combo.php:39
a.fn @ yui_combo.php:115
In CPANEL:
max_execution_time 50000
max_input_time 50000
max_input_vars 5000
post_max_size 128M
upload_max_filesize 128M
What can I do?
Thanks, regards
volgens Annie Price.
Hi Ken,
Thanks so much for responding.
I am on heart internet shared hosting so I presume I cannot do what you suggest.
Any other ideas? Or do I need to start the upgrade again from scratch?
volgens Emma Richardson.
Can you post or send me a copy of your php.ini file? Also, I guess you could check the permissions on this file - is it possible that apache cannot read it and is just using default settings? Doesn't seem likely but I am running out of ideas...
volgens Ken Task.
Well, with shared hosting, that's probably true then. Shared hosting is cheap and restricted as far as being able to admin a Moodle ... which many times now does involve command line.
The only thing I could suggest is to contact the provider help desk ... they do have ssh access to your server and request they execute the script for you, provide it a password, send you email with that changed password.
Think I'd do that/try that first rather than start over!!!
Do you have access to the database for your Moodle? That's the other way ... not recommended really and considered to be a last resort.
Or consider upgrading from shared hosting to a VPS ... which, of course is more expensive, but then you do have ssh access to your server.
'spirit of sharing', Ken
volgens Mikel Ortueta.
I am out of ideas too, I am thinking on deploying a new server and migrating moodle instance... But i think that is the last option...volgens Ken Task.
In your Moodle, go to Site Admin -> Server -> PHP Info. In that screen there is a variable for 'Loaded Configuration File' ... then it shows the path to the php.ini file your server is using to set global settings for your server. In the output it also shows what the setting are for uploading files ... under 'Core' section ... post_max_size and upload_max_filesize - whose settings actually come from the main php.ini file controlling your service.
If you cannot reach/edit that php.ini, then you are on a Jailed system ... hint/clue is cPanel. You then need to consult hosting providers documentation as to what they are allowing customers to do ... such as the size of file to upload, etc.. and find out what they have determine those maxes are according to the package you purchased from them. If you can upload 20M files, you might have to use either .htaccess files or other php.ini files in certain locations to set those limits higher.
Any change to the main php.ini file requires restart of apache service for it to know of the changes.
Any .htaccess file addition should not require restart ... those are checked by apache all the time by default. If addional php.ini files are being used, that might require restart of apache service.
Once the server is set to allow higher, you need to check the config/settings of various things in Moodle to see what is available in config ... there is a setting for courses, for exampe, where Moodle admin can choose to allow the max as allowed by server config or something lower. Settings to some mods as well.
'spirit of sharing', Ken
volgens Ken Task.
Pardon intrusion ...
in the php.ini file you've shared:
Data Handling section ...
post_max_size = 50wdwd
po
What's that? Means nothing to apache thus defaults to 8M and 2M
upload_max_filesize = 500M
There is also an apache setting that comes into play, but I suspect it's the above.
post max size and upload max size are typically set to slightly above what max is needed.
Uploding a 523M file then needs to 'fit' ... both variables then set to at least 530M gives a little wiggle room.
'spirit of sharing', Ken
volgens Emma Richardson.
You have an errant W at the beginning of your php.ini file - let's start by removing that, restart apache, check PHP info on moodle site. Report back.
Oh, and fix the POST_MAX_SIZE - it has gobbledygook in it!!
volgens Carlo Grandi.
Tnx, very appreciated your reply.volgens Emma Richardson.
This is the reason I thoroughly dislike Vi as an editor!!
volgens Mikel Ortueta.
Thank you for your inputs @Ken Task and @Emma Richardson
I shared the wrong one... Sorry I was trying to do an error in the config file to check if the config was imported from that file
Even with error in the file or without them alwys "charges" the same parameters...
Attached the running-file and still not working...
Enviroment of the server attached.
How can I chech that that is the running config?
Maybe unistalling php and installing? or it brokes moodle installation?
@Ken Task, Yes my needed maximun size is 450 so with 500 it fits. But thank you for the tip!
by Ken Task.
In this most recent php.ini
post_max_size = 500M
In File Uploads
upload_max_filesize = 500M
So those match/should allow.
However, is that php.ini file the one your server loads.
In Modle - Site Admin -> Server -> PHP Info
Loaded Configuration File points to the path and the php.ini it's loading.
Edit that php.ini
Apahe also might be involved ... maybe .... look at it's config for:
LimitRequestBody
https://www.safaribooksonline.com/library/view/apache-the-definitive/0596002033/re28.html
If the php.ini you edited and shared here, did you restart apache service?
What else is running on that server that might prevent config changes?
'spirit of sharing', Ken
by Emma Richardson.
That file has a space before [PHP] first line. Not sure if that is an issue or not. Try removing it.
Your server is fine - I suspect that you have been messing with the config files and not refreshing each time so probably jumped over the correct version at some point.
Remove space, restart apache, and then screenshot the relevant parts of PHP info screen from moodle, specifically the parts you are trying to change and the config file paths.
by Usman Asar.
are you getting password error or is is showing blank page?
also, how you installed your first Moodle (that may be 2.4) using script installer or manually downloading the package from moodle.org?
by Usman Asar.
Jailani,
follow this link
https://download.moodle.org/releases/latest/
download moodle installer package for windows, and it will do everything for you, nice and easy
by Shivam Endez.
Thanks Derek - still on the fence on upgrading vs. fresh install...
by Shivam Endez.
Thanks Howard, definitely considering this strategy
by Shivam Endez.
Thanks for this information Emma!