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

Re: Moodle 3.7.1+ Installation

$
0
0
by Lavanya Lav.  

The details show:
Check your Internet connection
Check any cables and reboot any routers, modems, or other network devices you may be using.

Allow Chrome to access the network in your firewall or antivirus settings.
If it is already listed as a program allowed to access the network, try removing it from the list and adding it again.

If you use a proxy server
Check your proxy settings or contact your network administrator to make sure the proxy server is working. If you don't believe you should be using a proxy server: Go to the Chrome menu > Settings > Show advanced settings… > Change proxy settings… > LAN Settings and deselect "Use a proxy server for your LAN".

Re: Moodle 3.7.1+ Installation

$
0
0
by Howard Miller.  

Sorry - need a bit more detail. There's normally no such place as 'localhost'. Is this a server / hosting / local PC? Which operating system? Did you have WAMP of some sort already set up?

Do you know where the web server error log is and can you check it?

Re: After upgrading from 3.5.1 to 3.7.1 cron is not working

$
0
0
by Erik Frangež.  

Hi Ken,

Upgrade? Standard, we have deleted all files in moodle directory, copy new sources and plugins and go through steps in Moodle (WEB). We are using same procedure many years.

today I have change collation in mysqldatabase to utf8mb4_general_ci, situation is same, I have run next command: php mysql_collation.php --collation=utf8mb4_general_ci, situation is same!

What to do next?

Thank you all for help!

tool_dataprivacy DDL sql execution error

$
0
0
by Daniel Luff.  

I tried to upgrade to the Moodle 3.7 but ran into server compatibility issues. I reloaded a backup of version 3.4.8.

But now I can't get past the plugin update page due to a DDL sql execution error.

Any help to resolve this would be appreciated.

Screenshots of the plugin update page and error debug info below (I can provide the whole debug info if helpful.



When I click "Upgrade Database" I get the following error:





Re: Is it necessary to use maintenance mode for small updates?

$
0
0
by Przemek Kaszubski.  

This probably should have been obvious for admins but using the CLI script for turning on the maintenance mode blocks the WWW interface even for admins. At least I ran the script with sudo permissions. Perhaps it should have been run using the www-data / apache server as the owner. I have not tested for that.

Re: Exception - Call to member function Moodle 3.7

$
0
0
by Karina Maltez.  

Hello Trish, if you disable it, the problem will always appear, you have to eliminate it completely and it doesn't have to show you new problems. Don't be afraid it's just a plugin that is not compatible with new versions of Moodle.

Re: After upgrading from 3.5.1 to 3.7.1 cron is not working

$
0
0
by Ken Task.  

Leon has explained the error seen in one of what you've shared:

Column count doesn't match value count at row 1

If omit column names and do no specify values for all columns, MySQL will give the "Column count doesn't match value count at row" error will occur, as MySQL doesn't know what to put in the missing columns.

You say not always the same thing ... so the following is for what's been shared ...

Cleaning up stale session data from cache stores
cd moodlecode/admin/tool/task/cli

php schedule_task.php --execute="\core\task\cache_cleanup_task"

php schedule_task.php --execute="\core\task\cache_cron_task"

php schedule_task.php --execute="\core\task\session_cleanup_task"

The mdl_task_log table is a log of actions taken by task.

Also, mind sharing your setup of cron? ... ie, the actual command issued running cron.

'SoS', Ken


Re: After upgrading from 3.5.1 to 3.7.1 cron is not working

$
0
0
by Leon Stringer.  

If you're familiar with working with MariaDB at the shell or using phpMyAdmin you could try running that query manually and seeing if it works, e.g.:

INSERT INTO mdl_task_log (type, component, classname, userid, timestart,
timeend, dbreads, dbwrites, result, output)
VALUES (0, 'logstore_standard', 'logstore_standard\\task\\cleanup_task', 0,
1563856022.3714321, 1563856022.4131601, 2, 999, 0,
'Execute scheduled task: Čiščenje tabele dnevnikov (logstore_standard\\task\\cleanup_task)
Deleted old log records from standard store.
... used 3 dbqueries
... used 0,042447090148926 seconds
Scheduled task complete: Čiščenje tabele dnevnikov (logstore_standard\\task\\cleanup_task)');

I've set dbwrites to 999 so you can hopefully identify the row to remove it. Take a database backup before making any changes to be safe.

The values on the second "Column count doesn't match..." error look correct, i.e. the 10th value (index 9 in the array) has the terminating single quote as expected, the extra comma after is because Moodle is using var_export() to show the array, i.e. it's expected.

Let us know If the above INSERT works or not, and any error you see. Also the output of SHOW CREATE TABLE mdl_task_log would let us check the table definition.


Re: After upgrading from 3.5.1 to 3.7.1 cron is not working

$
0
0
by Ken Task.  

The method of upgrading called for copying back into new code plugins/addons from old code directory to appropriate/same locations in new code.

Those include themes.

In a 3.5.stock, themes directory had boost, bootstrapbase,clean, and more.  Did you have any addiional theme for the 3.5.x?

Themes have changed in 3.7.x.  *ONLY* boost and a new one called 'classic'.

By chance did the copy of old code themes include a theme that isn't compatible with 3.7.x?

The moodle environment check doesn't check plugins for compatiblity with higher version of moodle code.

Just one incompatible plugin can cause some very strange errors and send one off down a rabbit holes! sad

'SoS', Ken

Re: Is it necessary to use maintenance mode for small updates?

$
0
0
by Ben Kahn.  

Przemek, thank you for your great contributions. I tried the SCSS and it works beautifully. Saved me from having to go in and figure out what CSS classes to use smile 



And yes a good note of warning that web access to the site is totally cut off when using CLI maintenance mode. So you need to be comfortable running updates from the command line as well. Since I already use git for updates this is an easy change for me to make. Instead of visiting the admin notifications area I can just run:

##do the upgrade (using the apache user)
 $ sudo -u www-data /usr/bin/php admin/cli/upgrade.php
##turn off maintenance mode
 $ sudo -u www-data /usr/bin/php admin/cli/maintenance.php --disable

How can I update my moodlecloud site to version 3.7?

$
0
0
by donna shell.  

I expected to be updated to 3.7 automatically.  Is there something I should do? (Currently 3.6.4)

Re: After upgrading from 3.5.1 to 3.7.1 cron is not working

$
0
0
by Erik Frangež.  

Hi, I have manually run query and works:
INSERT INTO mdl_task_log (type, component, classname, userid, timestart,
timeend, dbreads, dbwrites, result, output)
VALUES (0, 'logstore_standard', 'logstore_standard\\task\\cleanup_task', 0,
1563856022.3714321, 1563856022.4131601, 2, 999, 0,'')

1 row inserted. [br] Inserted row id: 30 (Query took 0.0189 seconds.)

Show create table mdl_task_log return this
mdl_task_log | CREATE TABLE `mdl_task_log` (
`id` bigint(10) NOT NULL AUTO_INCREMENT,
`type` smallint(4) NOT NULL,
`component` varchar(255) NOT NULL DEFAULT '',
`classname` varchar(255) NOT NULL DEFAULT '',
`userid` bigint(10) NOT NULL,
`timestart` decimal(20,10) NOT NULL,
`timeend` decimal(20,10) NOT NULL,
`dbreads` bigint(10) NOT NULL,
`dbwrites` bigint(10) NOT NULL,
`result` tinyint(2) NOT NULL,
`output` longtext NOT NULL,
PRIMARY KEY (`id`),
KEY `mdl_tasklog_cla_ix` (`classname`),
KEY `mdl_tasklog_tim_ix` (`timestart`)
) ENGINE=InnoDB AUTO_INCREMENT=31 DEFAULT CHARSET=utf8mb4 ROW_FORMAT=COMPRESSED |

Re: After upgrading from 3.5.1 to 3.7.1 cron is not working

$
0
0
by Erik Frangež.  

Hi Ken,

mentioned PHP statements are not working, everywhere same error:

php schedule_task.php --execute="\core\task\cache_cleanup_task"
Execute scheduled task: Odstrani potekle predpomnilniške vnose (core\task\cache_cleanup_task)
... used 1 dbqueries
... used 0,010622978210449 seconds
Scheduled task complete: Odstrani potekle predpomnilniške vnose (core\task\cache_cleanup_task)
... used 2 dbqueries
... used 0,011515140533447 seconds
Scheduled task failed: Odstrani potekle predpomnilniške vnose (core\task\cache_cleanup_task),Napaka pri pisanju v podatkovno bazo
Debug info:
Column count doesn't match value count at row 1
INSERT INTO mdl_task_log (type,component,classname,userid,timestart,timeend,dbreads,dbwrites,result,output) VALUES(?,?,?,?,?,?,?,?,?,?)
[array (
0 => 0,
1 => 'moodle',
2 => 'core\\task\\cache_cleanup_task',
3 => 0,
4 => 1564033013.5786741,
5 => 1564033013.588649,
6 => 0,
7 => 1,
8 => 0,
9 => 'Execute scheduled task: Odstrani potekle predpomnilniške vnose (core\\task\\cache_cleanup_task)
... used 1 dbqueries
... used 0,010622978210449 seconds
Scheduled task complete: Odstrani potekle predpomnilniške vnose (core\\task\\cache_cleanup_task)
',
)]
Backtrace:
* line 1329 of /lib/dml/mysqli_native_moodle_database.php: call to moodle_database->query_end()
* line 1375 of /lib/dml/mysqli_native_moodle_database.php: call to mysqli_native_moodle_database->insert_record_raw()
* line 84 of /lib/classes/task/database_logger.php: call to mysqli_native_moodle_database->insert_record()
* line 299 of /lib/classes/task/logmanager.php: call to core\task\database_logger::store_log_for_task()
* line 718 of /lib/classes/task/manager.php: call to core\task\logmanager::finalise_log()
* line 163 of /admin/tool/task/cli/schedule_task.php: call to core\task\manager::scheduled_task_complete()

php schedule_task.php --execute="\core\task\cache_cron_task"
Execute scheduled task: Obdelava v ozadju za predpomnilnike (core\task\cache_cron_task)
Cleaning up stale session data from cache stores.
... used 0 dbqueries
... used 0,011645078659058 seconds
Scheduled task complete: Obdelava v ozadju za predpomnilnike (core\task\cache_cron_task)
... used 1 dbqueries
... used 0,012732982635498 seconds
Scheduled task failed: Obdelava v ozadju za predpomnilnike (core\task\cache_cron_task),Napaka pri pisanju v podatkovno bazo
Debug info:
Column count doesn't match value count at row 1
INSERT INTO mdl_task_log (type,component,classname,userid,timestart,timeend,dbreads,dbwrites,result,output) VALUES(?,?,?,?,?,?,?,?,?,?)
[array (
0 => 0,
1 => 'moodle',
2 => 'core\\task\\cache_cron_task',
3 => 0,
4 => 1564033021.109978,
5 => 1564033021.120805,
6 => 0,
7 => 0,
8 => 0,
9 => 'Execute scheduled task: Obdelava v ozadju za predpomnilnike (core\\task\\cache_cron_task)
Cleaning up stale session data from cache stores.
... used 0 dbqueries
... used 0,011645078659058 seconds
Scheduled task complete: Obdelava v ozadju za predpomnilnike (core\\task\\cache_cron_task)
',
)]
Backtrace:
* line 1329 of /lib/dml/mysqli_native_moodle_database.php: call to moodle_database->query_end()
* line 1375 of /lib/dml/mysqli_native_moodle_database.php: call to mysqli_native_moodle_database->insert_record_raw()
* line 84 of /lib/classes/task/database_logger.php: call to mysqli_native_moodle_database->insert_record()
* line 299 of /lib/classes/task/logmanager.php: call to core\task\database_logger::store_log_for_task()
* line 718 of /lib/classes/task/manager.php: call to core\task\logmanager::finalise_log()
* line 163 of /admin/tool/task/cli/schedule_task.php: call to core\task\manager::scheduled_task_complete()

php schedule_task.php --execute="\core\task\session_cleanup_task"
Task '\core\task\session_cleanup_task' not found

Re: Moodle 3.7.1+ Installation

$
0
0
by Howard Miller.  

We know what that message says... you need to answer my questions if you want some help wink

Re: This site can't be reached during installation

$
0
0
by Vinod Kumar Aleti.  

Thank you so much...
I also was facing this issue from last few days and adding this in conf file really worked.


Re: Moodle 3.7.1+ Installation

Re: Moodle 3.7.1+ Installation

Moodle 3.7 Mail Send issue

$
0
0
by Emma Richardson.  

I recently upgraded my site to 3.7 which included a php 7.0 to 7.2 upgrade.  All seems fine but I have a strange issue happening and not sure where to look for logs to find the issue.

I have a class with over 200 students in it.  The forum, all of a sudden, since the upgrade, is not sending mail notifications to every student.  I have mail set up through gmail.  I have checked the gmail logs and the people missing notifications are simply not there.  Most of them do get sent, just not all - just found the number 109 of 225 get sent...

I did find that the session limit was set to 20 so I raised that to 200 to match my other moodle site which is happily sending over 800 emails through the general news forum.  No change.

Seeing as I am using smtp through Google, I can't see that the php upgrade could have affected that - or could it?  Is there anywhere I would find logs for that - (running Debian Jesse)?

Is there something that might have changed in Moodle to cap emails sent?

Does anyone have any idea of where I should start?

This site can’t be reached localhost refused to connect.

$
0
0
by Arthur Fridrich.  

I've searched postings regarding this, but they are all old.

Did a clean install of Moodle 3.7 on Tuesday. It was on a Windows server, using 2012. Everything worked fine and was able to log in and do some work.

Today, attempted to access again using http://localhost, page couldn't be reached.

Went to server, shutdown Moodle, saw a message can't find apache\logs\httpd.pid, but appeared to close.

Restarted and no error messages. Tried localhost again, no success.

At some point, I did see a b2e.exe has stopped working server 2012 message. Do find AppCrash_b2e.exe report.wer

Any ideas?

Thanks....

Art

Re: This site can’t be reached localhost refused to connect.

$
0
0
by Arthur Fridrich.  

Not sure if this will add anything to the information above, but the server sys admin said in the event viewer, he received a message "Could not find a valid table space file for PHPmyadmin/PMA_user

Thanks again...
Art
Viewing all 47064 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>