Quantcast
Channel: Installing and upgrading help
Viewing all 46905 articles
Browse latest View live

Re: Installation Error on php max_input_vars

$
0
0
by noorul arshad.  

Hi Ken,

As you said, I tried php checks.php. it shows the below errors.
Errors in environment php

Re: RFC: Running moodle cron via docker.

$
0
0
by Howard Miller.  

We do see questions about Docker and Moodle and they never seem to get answers.

I don't get the impression that anybody uses it in production. I'll say what I've said before. You're essentially writing an installation script for Moodle and that's quite a personal thing depending on your own needs. I don't think they transfer well.

Re: Installation Error on php max_input_vars

$
0
0
by noorul arshad.  

Hi Leaon,

I tried creating phpinfo.php in /var/www/html/moodle/admin/cli, and tried accessing phpinfo.php in my site. It shows max_input_vars is 1000.
max vars shows 1000

But for confirmation I have searched for php.ini files


 php.ini file search


the I opened the file in etc/php/8.0/apache2/php.ini in that the max_input_vars is set to 10000. 



php.ini file setting

Re: Installation Error on php max_input_vars

$
0
0
by noorul arshad.  

Hey !!!!! Thanks you ken & Leon.

Once again I edited php.ini file and saved it. now its working !!!


Thanks a lot !!!!

Re: Installation Error on php max_input_vars

$
0
0
by Ken Task.  

Congrats on solving!

Comment: sort of unusual to see only PHP 7.0 and PHP 8.x.  That find command helped you locate the correct php.ini to edit ... phpinfo should have shown a line showing what php.ini your web service was using.

Suggest removing those backups of older versions of PHP ... keep your server 'clean of stuff' not using.  Reduces confusion. smile

'SoS', Ken

Re: Could not upgrade or installing plugins from Moodle plugin directory

$
0
0
by Tony Stark.  

Anyone can help?

Re: Could not upgrade or installing plugins from Moodle plugin directory

$
0
0
by Ken Task.  

If you were root user and acquired the BBB plugin via curl and it succeeded there is no wonder in that.   Same if logged on as user via ssh that owns the directory to which you were downloading the .zip.

Via Moodle GUI ... different story.   This sounds like a permissions issue.

So what is:

1. locadtion of moodledata in relation to code.

2. ownership and permissions on directories/files in your moodledata.

3. the zip of the plugin you attempt to install has to be able to be downloaded, unzipped, checked to see if it's a proper archive for installing, then that routine has to arvhive the current plugin folder, and copy the new code/plugin into a proper location for installing ... like a mod plugin to the code/mod/ directory.

Also, your site could be running some sort of web application firewall (WAF) [like mod_security] that is preventing ... same is true of seLinux.

So check your servers web service error logs as well as any WAF log to see what's the problem.

Note: you can manually install plugins.

Please see:

https://docs.moodle.org/311/en/Installing_plugins#Installing_a_plugin

'SoS', Ken

Background processing for assignment module fails to run

$
0
0
by Andy Nicolle.  

Email notifications of assignments being graded delayed in their sending (often several hours later), I have found that the scheduled task 'Background processing for assignment module' failing is what is causing the delay. When the scheduled task is run manually via command line the emails are sent, but with the below error message:

Execute scheduled task: Background processing for assignment module (mod_assign\task\cron_task)
Processing 10 assignment submissions ...
Processing assignment submission 4962 ...
!!! Exception - Cannot access private property cm_info::$uservisible !!!

When viewing the scheduled task logs for the specific task the below message is shown:

Execute scheduled task: Background processing for assignment module (mod_assign\task\cron_task)
... started 15:38:30. Current memory use 18.8MB.
Processing 10 assignment submissions ...
Processing assignment submission 4966 ...
... used 11 dbqueries
... used 0.15214896202087 seconds
Scheduled task failed: Background processing for assignment module (mod_assign\task\cron_task),Cannot access private property cm_info::$uservisible
Each time the task runs the fail delay increases by 60.

Ubuntu 18.04
PHP 7.2

Any help would be appreciated in getting this ask to run regularly again.
Andy

Re: Moodle Messages problem after upgrading to 3.9

$
0
0
by Paul Hale.  

I have managed to correct the error 😊

To start I enabled debugging in the config.php file by adding the following lines at the end of the file:

ini_set ('display_errors', 'on');
ini_set ('log_errors', 'on');
ini_set ('display_startup_errors', 'on');
ini_set ('error_reporting', E_ALL);
$CFG->debug = 30719; // DEBUG_ALL, but that constant is not defined here.

When I went to the message and tried to send a new error appeared:

"unexpected token < in JSON at position 0

Chasing this error lead me to an error in line 135 of /lib/classes/message/manager.php

Line 135 $processors = array_filter(get_message_processors(false), function($processor) {

I am no programmer and as I could not see any obvious error I tried changing the vale of Line 135 to (True) now my messaging works without errors.

I hope this proves helpful, my next issue is I cant add contacts in the message area, but that is for another day.

Regards
Paul

Re: Updating Moove theme plugin option not available

$
0
0
by Leon Stringer.  

Moove version 3.11.01 is for Moodle 3.11. It won't work with Moodle 3.9.

See the theme's versions page for information on which Moove version works with which Moodle version. Since Moove 3.9.08 is the latest version for Moodle 3.9 and you already have this no update option appears.

Re: RFC: Running moodle cron via docker.

3.8.2+ -> 3.9.7 admin/cli/upgrade.php says no Upgrade necessary

$
0
0
by Martin Eckleben.  

Hi everyone and thank you for your time!

root@xyz:/var/www# sudo -u www-data /usr/bin/php /var/www/moodle/admin/cli/upgrade.php
Für die installierte Version 3.8.2+ (Build: 20200402) (2019111802.04) ist kein Upgrade notwendig. Danke für den Versuch!

Roughly translated:
For the installed version 3.8.2+ (Build: 20200402) (2019111802.04) no upgrade is necessary. Thank you for trying!

3.9.7 is LTS if I'm right?
Why shouldn't I upgrade?

Thank you again!

Re: 3.8.2+ -> 3.9.7 admin/cli/upgrade.php says no Upgrade necessary

$
0
0
by Leon Stringer.  

This message suggests that the current site is 3.8.2+ and the source code in /var/www/moodle is also 3.8.2+.

To upgrade you must replace the source code in /var/www/moodle with the 3.9.7 source code.

If you've already done this run the command tail /var/www/moodle/version.php and tell us what it says. It should be something like:

$version  = 2020061507.02;              // 20200615      = branching date YYYYMMDD - do not modify! 
                                        //         RR    = release increments - 00 in DEV branches.
                                        //           .XX = incremental changes.
$release  = '3.9.7+ (Build: 20210520)'; // Human-friendly version name
$branch   = '39';                       // This version's branch.
$maturity = MATURITY_STABLE;             // This version's maturity level.

Re: 3.8.2+ -> 3.9.7 admin/cli/upgrade.php says no Upgrade necessary

$
0
0
by Martin Eckleben.  

It's working.
Thank you so much!

If I'd have any spare time I'd open a discussion about improving the message and post a PR.
Maybe I will in a free moment smile

Re: 3.8.2+ -> 3.9.7 admin/cli/upgrade.php says no Upgrade necessary


Re: Could not upgrade or installing plugins from Moodle plugin directory

$
0
0
by Tony Stark.  

Hi Ken,

I really appreciate your reply!

Follow the steps you mentioned, I think I may found the problem: I could download the zip file using CURL but couldn't unzip it and this is what I got trying to unzip it:

Archive: mod_bigbluebuttonbn_moodle311_2019101008.zip
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of mod_bigbluebuttonbn_moodle311_2019101008.zip or
mod_bigbluebuttonbn_moodle311_2019101008.zip.zip, and cannot find mod_bigbluebuttonbn_moodle311_2019101008.zip.ZIP, period.

But I tried the same file on my computer and it unzipped no problem.

My OS is Centos 7, do you have any suggestion?

Thank you again,
Tony

Re: Could not upgrade or installing plugins from Moodle plugin directory

$
0
0
by Tony Stark.  

Also when I FILE the zip file I downloaded using CURL, it says it's a HTML document, but not a Zip archive data.

Any idea why?

Re: Could not upgrade or installing plugins from Moodle plugin directory

$
0
0
by Ken Task.  

On Centos 7, you probably don't have 'unzip' installed.

yum install unzip [ENTER] - that might also grab some related libraries ... just say yes! smile

What curl command are you using?

curl -LO urltozipfile

will display something like this:

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 2123k  100 2123k    0     0  1226k      0  0:00:01  0:00:01 --:--:-- 1226k

And to check the zip ...

file -b nameofzipfiles.zip

should show:

Zip archive data, at least v2.0 to extract

Transferring (downloading) from Moodle pluginsserver a plugin zip, one can also use wget .... thusly ... wget https://URL to zip file.  That will save the zip where you are currently located.

'SoS', Ken

Re: Could not upgrade or installing plugins from Moodle plugin directory

$
0
0
by Tony Stark.  

I have UNZIP installed. I used curl -LO downloaded this zip file and when I used FILE, this came up:

# file mod_bigbluebuttonbn_moodle311_2019101008.zip
mod_bigbluebuttonbn_moodle311_2019101008.zip: HTML document, ASCII text, with very long lines

When I used WGET I get this:

# wget https://moodle.org/plugins/download.php/24237/mod_bigbluebuttonbn_moodle311_2019101008.zip
--2021-06-08 13:19:39-- https://moodle.org/plugins/download.php/24237/mod_bigbluebuttonbn_moodle311_2019101008.zip
Resolving moodle.org (moodle.org)... 104.22.65.81, 104.22.64.81, 172.67.26.233, ...
Connecting to moodle.org (moodle.org)|104.22.65.81|:443... connected.
HTTP request sent, awaiting response... 403 Forbidden
2021-06-08 13:19:40 ERROR 403: Forbidden.

Any thoughts?

Thanks,
Tony

Re: Updating Moove theme plugin option not available

$
0
0
by Madelyne de Bruin.  

Thank you for the feedback. Yes, I realise Moove 3.11 won't work with Moodle 3.9. I guess it makes sense that the update option won't reflect in Moodle. 

My next problem is then this: If I first update to the latest Moodle - it breaks my theme and I can't update to latest Moove theme then. How do I go about updating both without causing havoc? In what order should I update and do I do it as normal?

Viewing all 46905 articles
Browse latest View live