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

Upgrade Moodle dababase while Installing plugin via uploaded ZIP file

June 22, 2020, 10:57 am
$
0
0
by Antonio A.  

Hi all, 

 I am installing the plugin "Profile field based cohort membership" (https://moodle.org/plugins/pluginversions.php?plugin=local_profilecohort) by uploading the zip file to my moodle 3.8...

1. Uploaded the Zip here: .../admin/tool/installaddon/index.php

2. Clicked intall plugin button

3. Got hte messgas "validation susscessful. Installation can continue"

4. clicked "Continue" and got to the screen in the bellow image, Should I click "Upgrade Moodle Database Now"? Is it safe?

↧
Search

Re: Upgrade Moodle dababase while Installing plugin via uploaded ZIP file

June 22, 2020, 11:27 am
↧
↧

Re: Cannot upgrade to 3.9 because of ddl sql error 'wrong create options'

June 22, 2020, 12:10 pm
$
0
0
by Jeff Hopper.  

Ken,

Thank you for your quick reply.

I understand how proper names that cross domains can cause confusion. I'm certain this is a 'database thang' smile Here's info on the page compression I'm referring to: https://mariadb.com/kb/en/innodb-page-compression/

I also confirmed I'm using MariaDB 10.3.7

I don't believe it wise for me to try to compress tables using the referenced script - as that option is incompatible with my existing DB configuration.

Any insight on modifying the 3.8->3.9 database change requests?

Blessings and thanks!
↧

File Permissions after upgrade to 3.9

June 22, 2020, 1:10 pm
$
0
0
by Dennis Fulton.  

I upgraded to Moodle 3.9 at the same time I create a new VPS running CentOS 8 (I know, not the smartest thing to do changing two things at the same time.)  My old system was running Moodle 3.8 on CentOS 7.  I was surprised to see the different requirements for file permissions.  Don't know if anyone ran into this or not:

3.8 on CentOS 7
  -- moodledata  apache:apache 755
  -- moodle root:root 755

3.9 on CentOS8
  -- moodledata apache:apache 777
 -- moodle root:root 755

Moodledata would not run without 777.  I had to change /moodle/mod and /moodle/themes  to 777 to install a theme and some plugins.

Don't like the idea of 777 file permissions; but I am up and running.



↧

Re: Cannot upgrade to 3.9 because of ddl sql error 'wrong create options'

June 22, 2020, 1:34 pm
$
0
0
by Ken Task.  

If you taking about hacking 3.9 code ... beyond me. 

However, once hacked (if one finds a way) to get by this won't you forever be facing the same issues on any update to 3.9 and beyond?

From MariaDB docs:

Enabling InnoDB Page Compression

InnoDB page compression is not enabled by default. However, InnoDB page compression can be enabled for just individual InnoDB tables or it can be enabled for all new InnoDB tables by default.

InnoDB page compression is also only supported if the InnoDB table is in a file per-table tablespace. Therefore, the innodb_file_per_table system variable must be set to ON to use InnoDB page compression.

InnoDB page compression is only supported if the InnoDB table uses the Barracuda file format.Therefore, in MariaDB 10.1 and before, the innodb_file_format system variable must be set to Barracuda to use InnoDB page compression.

InnoDB page compression is also only supported if the InnoDB table's row format is COMPACT or DYNAMIC.

You can use set global commands

SET GLOBAL innodb_compression_default=ON;

This system variable's session value can be changed dynamically with SET SESSION. For example:

SET GLOBAL innodb_file_per_table=ON;

SET GLOBAL innodb_file_format='Barracuda';

SET GLOBAL innodb_default_row_format='dynamic';

*SET GLOBAL innodb_compression_algorithm='lzma';

SET SESSION  innodb_compression_default=ON;

* the one above is something not in any docs for Moodle known to me.

What does:

php mysql_compressed_rows.php -i

show?

as well as

php mysql_compressed_rows.php -l

Neither one of those changes ... but they do inform.

What does:

show variables like '%innodb%';

show?

'SoS', Ken


↧
↧

Re: File Permissions after upgrade to 3.9

June 22, 2020, 1:50 pm
$
0
0
by Ken Task.  

selinux is still present in CentOS 8.

As long as moodledata is in /var/www/ and you do NOT have any apache configuration granting access then it's 'safe' (or as safe as anything can be on the web these days).

As an assurance?   One could use an .htaccess file in moodledata root.  I just installed a fresh 3.9 on  CentOS 7 and that file was present by default.

cat .htaccess
deny from all
AllowOverride None
Note: this file is broken intentionally, we do not want anybody to undo it in subdirectory!

Realize this is hind sight .... and probably 2 cents, but ....

'SoS', Ken


↧

Re: Cannot upgrade to 3.9 because of ddl sql error 'wrong create options'

June 22, 2020, 2:31 pm
$
0
0
by Jeff Hopper.  

Ken,

Thanks for taking your time to offer suggestions.

I'm confident that I have the database configured and tuned for my particular SSD-storage optimized database server (at least as far as I know how to... ;) And regarding 'hacking the code', I'm a software developer by trade, so making a configuration adjustment before running the database upgrade doesn't scare me. I just need to know where it's happening and, more importantly, how the Moodle upgrade process is open to such configuration tweaks. I originally installed Moodle and upgrade it using the git repository strategy, so configuration modifications seem like a viable option. I'm absolutely surprised I couldn't find any existing dialog on this, since page-based table compression appeared to be commonly discussed as an avenue for SSD-based mysql/mariadb database optimization. Maybe someone with experience with this type of configuration will chime in...

However, for completeness, the following is the information you requested. Again thanks for your time.

mysql_compressed_rows.php -i
Database version: 5.5.5-10.3.7-MariaDB
Database name: moodle-some-alt-name
Database engine: InnoDB
innodb_file_per_table: ON
innodb_file_format:

mysql_compressed_rows.php -l
mdl_badge Dynamic
mdl_data Dynamic
mdl_data_fields Dynamic
mdl_enrol_lti_lti2_consumer Dynamic
mdl_enrol_paypal Dynamic
mdl_lti Dynamic
mdl_oauth2_issuer Dynamic
mdl_user Dynamic
mdl_user_info_field Dynamic

show variables like '%innodb%';
+---------------------------------------------+--------------------------------------+
| Variable_name | Value |
+---------------------------------------------+--------------------------------------+
| ignore_builtin_innodb | OFF |
| innodb_adaptive_flushing | ON |
| innodb_adaptive_flushing_lwm | 10.000000 |
| innodb_adaptive_hash_index | ON |
| innodb_adaptive_hash_index_parts | 8 |
| innodb_adaptive_max_sleep_delay | 150000 |
| innodb_autoextend_increment | 64 |
| innodb_autoinc_lock_mode | 1 |
| innodb_background_scrub_data_check_interval | 3600 |
| innodb_background_scrub_data_compressed | OFF |
| innodb_background_scrub_data_interval | 604800 |
| innodb_background_scrub_data_uncompressed | OFF |
| innodb_buf_dump_status_frequency | 0 |
| innodb_buffer_pool_chunk_size | 16777216 |
| innodb_buffer_pool_dump_at_shutdown | ON |
| innodb_buffer_pool_dump_now | OFF |
| innodb_buffer_pool_dump_pct | 25 |
| innodb_buffer_pool_filename | ib_buffer_pool |
| innodb_buffer_pool_instances | 1 |
| innodb_buffer_pool_load_abort | OFF |
| innodb_buffer_pool_load_at_startup | ON |
| innodb_buffer_pool_load_now | OFF |
| innodb_buffer_pool_size | 16777216 |
| innodb_change_buffer_max_size | 25 |
| innodb_change_buffering | all |
| innodb_checksum_algorithm | crc32 |
| innodb_checksums | ON |
| innodb_cmp_per_index_enabled | OFF |
| innodb_commit_concurrency | 0 |
| innodb_compression_algorithm | zlib |
| innodb_compression_default | ON |
| innodb_compression_failure_threshold_pct | 5 |
| innodb_compression_level | 6 |
| innodb_compression_pad_pct_max | 50 |
| innodb_concurrency_tickets | 5000 |
| innodb_data_file_path | ibdata1:10M:autoextend |
| innodb_data_home_dir | /var/packages/MariaDB10/target/mysql |
| innodb_deadlock_detect | ON |
| innodb_default_encryption_key_id | 1 |
| innodb_default_row_format | dynamic |
| innodb_defragment | OFF |
| innodb_defragment_fill_factor | 0.900000 |
| innodb_defragment_fill_factor_n_recs | 20 |
| innodb_defragment_frequency | 40 |
| innodb_defragment_n_pages | 7 |
| innodb_defragment_stats_accuracy | 0 |
| innodb_disable_sort_file_cache | OFF |
| innodb_disallow_writes | OFF |
| innodb_doublewrite | OFF |
| innodb_encrypt_log | OFF |
| innodb_encrypt_tables | OFF |
| innodb_encryption_rotate_key_age | 1 |
| innodb_encryption_rotation_iops | 100 |
| innodb_encryption_threads | 0 |
| innodb_fast_shutdown | 1 |
| innodb_fatal_semaphore_wait_threshold | 600 |
| innodb_file_per_table | ON |
| innodb_fill_factor | 100 |
| innodb_flush_log_at_timeout | 1 |
| innodb_flush_log_at_trx_commit | 1 |
| innodb_flush_method | fsync |
| innodb_flush_neighbors | 1 |
| innodb_flush_sync | ON |
| innodb_flushing_avg_loops | 30 |
| innodb_force_load_corrupted | OFF |
| innodb_force_primary_key | OFF |
| innodb_force_recovery | 0 |
| innodb_ft_aux_table | |
| innodb_ft_cache_size | 8000000 |
| innodb_ft_enable_diag_print | OFF |
| innodb_ft_enable_stopword | ON |
| innodb_ft_max_token_size | 84 |
| innodb_ft_min_token_size | 3 |
| innodb_ft_num_word_optimize | 2000 |
| innodb_ft_result_cache_limit | 2000000000 |
| innodb_ft_server_stopword_table | |
| innodb_ft_sort_pll_degree | 2 |
| innodb_ft_total_cache_size | 640000000 |
| innodb_ft_user_stopword_table | |
| innodb_idle_flush_pct | 100 |
| innodb_immediate_scrub_data_uncompressed | OFF |
| innodb_io_capacity | 10000 |
| innodb_io_capacity_max | 20000 |
| innodb_lock_schedule_algorithm | vats |
| innodb_lock_wait_timeout | 50 |
| innodb_locks_unsafe_for_binlog | OFF |
| innodb_log_buffer_size | 16777216 |
| innodb_log_checksums | ON |
| innodb_log_compressed_pages | ON |
| innodb_log_file_size | 50331648 |
| innodb_log_files_in_group | 2 |
| innodb_log_group_home_dir | /var/packages/MariaDB10/target/mysql |
| innodb_log_write_ahead_size | 8192 |
| innodb_lru_scan_depth | 1024 |
| innodb_max_dirty_pages_pct | 75.000000 |
| innodb_max_dirty_pages_pct_lwm | 0.000000 |
| innodb_max_purge_lag | 0 |
| innodb_max_purge_lag_delay | 0 |
| innodb_max_undo_log_size | 10485760 |
| innodb_monitor_disable | |
| innodb_monitor_enable | |
| innodb_monitor_reset | |
| innodb_monitor_reset_all | |
| innodb_old_blocks_pct | 37 |
| innodb_old_blocks_time | 1000 |
| innodb_online_alter_log_max_size | 134217728 |
| innodb_open_files | 300 |
| innodb_optimize_fulltext_only | OFF |
| innodb_page_cleaners | 1 |
| innodb_page_size | 16384 |
| innodb_prefix_index_cluster_optimization | OFF |
| innodb_print_all_deadlocks | OFF |
| innodb_purge_batch_size | 300 |
| innodb_purge_rseg_truncate_frequency | 128 |
| innodb_purge_threads | 4 |
| innodb_random_read_ahead | OFF |
| innodb_read_ahead_threshold | 56 |
| innodb_read_io_threads | 4 |
| innodb_read_only | OFF |
| innodb_replication_delay | 0 |
| innodb_rollback_on_timeout | OFF |
| innodb_rollback_segments | 128 |
| innodb_scrub_log | OFF |
| innodb_scrub_log_speed | 256 |
| innodb_sort_buffer_size | 1048576 |
| innodb_spin_wait_delay | 4 |
| innodb_stats_auto_recalc | ON |
| innodb_stats_include_delete_marked | OFF |
| innodb_stats_method | nulls_equal |
| innodb_stats_modified_counter | 0 |
| innodb_stats_on_metadata | OFF |
| innodb_stats_persistent | ON |
| innodb_stats_persistent_sample_pages | 20 |
| innodb_stats_sample_pages | 8 |
| innodb_stats_traditional | ON |
| innodb_stats_transient_sample_pages | 8 |
| innodb_status_output | OFF |
| innodb_status_output_locks | OFF |
| innodb_strict_mode | ON |
| innodb_sync_array_size | 1 |
| innodb_sync_spin_loops | 30 |
| innodb_table_locks | ON |
| innodb_temp_data_file_path | ibtmp1:12M:autoextend |
| innodb_thread_concurrency | 0 |
| innodb_thread_sleep_delay | 10000 |
| innodb_tmpdir | |
| innodb_undo_directory | ./ |
| innodb_undo_log_truncate | OFF |
| innodb_undo_logs | 128 |
| innodb_undo_tablespaces | 0 |
| innodb_use_atomic_writes | ON |
| innodb_use_native_aio | ON |
| innodb_version | 10.3.7 |
| innodb_write_io_threads | 4 |
+---------------------------------------------+--------------------------------------+
↧

Re: File Permissions after upgrade to 3.9

June 22, 2020, 2:43 pm
$
0
0
by Dennis Fulton.  

Great idea on the .htaccess file.   Thanks!  3.9 is looking pretty good.

↧
Search

Re: Cannot upgrade to 3.9 because of ddl sql error 'wrong create options'

June 22, 2020, 7:07 pm
$
0
0
by Ken Task.  

I certainly do not have the creds you do.  Am not a programmer nor a true DB admin.  I do 'dig' a lot ... sooo the following is a 'dig' ... nugget or fools gold ... I can't really tell.  Maybe one of the following will help:

https://www.percona.com/blog/2017/11/20/innodb-page-compression/

https://www.percona.com/doc/percona-server/LATEST/flexibility/compressed_columns.html

The error is about tables related to something new in Moodle ... contentbank ... am wondering if one could set tables with characteristics where Moodle upgrade wouldn't complain upon attempts to upgrade.

If it helps:

mysql> show tables like '%content%';
+--------------------------------+
| Tables_in_moodle39 (%content%) |
+--------------------------------+
| mdl_contentbank_content        |
| mdl_data_content               |
| mdl_h5p_contents_libraries     |
+--------------------------------+


explain  mdl_contentbank_content;
+--------------+--------------+------+-----+---------+----------------+
| Field        | Type         | Null | Key | Default | Extra          |
+--------------+--------------+------+-----+---------+----------------+
| id           | bigint(10)   | NO   | PRI | NULL    | auto_increment |
| name         | varchar(255) | NO   | MUL |         |                |
| contenttype  | varchar(100) | NO   |     |         |                |
| contextid    | bigint(10)   | NO   | MUL | NULL    |                |
| instanceid   | bigint(10)   | YES  |     | NULL    |                |
| configdata   | longtext     | YES  |     | NULL    |                |
| usercreated  | bigint(10)   | NO   | MUL | NULL    |                |
| usermodified | bigint(10)   | YES  | MUL | NULL    |                |
| timecreated  | bigint(10)   | NO   |     | 0       |                |
| timemodified | bigint(10)   | YES  |     | 0       |                |
+--------------+--------------+------+-----+---------+----------------+

Hope a true DB admin person comes along soon! smile

'SoS', Ken

↧
↧

Cannot upgrade to 3.9 because of ddl sql error 'wrong create options'

June 22, 2020, 7:46 am
$
0
0
by Jeff Hopper.  

My current 3.8.x instance of Moodle is using MariaDb with page compression.

When trying to upgrade to 3.9, my install fails with a DDL sql execution error - citing errno: 140 "Wrong create options".  I'm fairly confident the issue is related to creation of the mdl_contentbank_content table with the ROW_FORMAT=Compressed option (table compression). The two compression schemes being mutually exclusive.

My question to the community is: Where do I find and modify the upgrade script/code to remove the offending table compression directives before attempting the database update? Is there possibly a config option to select page compression? (I can hope... right?)

Searching the documentation, I see references to such files being called /db/install.xml and/or /db/upgrade.php. But I did not find either in my instance of Moodle.

I would appreciate it if someone could point me in the correct direction on this. Thanks in advance.

↧

PHP apache handler and clamAV upload issue, PHP fast-cgi slowness

June 23, 2020, 2:47 am
$
0
0
by tore erotavlas.  

Hi,
I have latest moodle 3.9 on zentyal 6.2 (ubuntu 18.04.4 64 bit). I have ClamAV 0.102.3/25850, with apache 2.4.43 (default version 2.4.29 does not support latest TLS versions and encryption primitives, so I installed apache from third party repositories) and PHP 7.2.24-0ubuntu0.18.04.6 with Zend OPcache v7.2.24-0ubuntu0.18.04.6.

With PHP apache handler (file /etc/php/7.2/apache2/php.ini configured as described here), whenever there is an upload of a file, clamAV fails:
/tmp/phpys4WKw: lstat() failed: No such file or directory. ERROR
ClamAV user has write access to web server folders and is member of www-data group (similar issue here).

With PHP fast-cgi (file /etc/php/7.2/fpm/php.ini configured as described here), generally it works well. However, sometimes moodle is very slow and get stucks (especially with previous 3.8.2 version) and I have to manually restart apache and php-fpm services.

Do you have hint about how to solve PHP apache handler problem? Is the PHP fast-cgi problem a possible bug?

↧

Re: Integrating automatic users

June 23, 2020, 5:21 am
$
0
0
by Carlos Cadabeira.  

Thank you soo much...

↧

Re: Error DDL sql execution error (mod_h5pactivity)

June 23, 2020, 5:28 am
$
0
0
by Benjamin Waller.  

Thank you Leon,

I logged in to phpMyAdmin to check and i can find those tables but i am a little confused about the 3.7 vs 3.9 database. So when i am in my phpMyAdmin account i should be seeing the 3.9 database which was the 3.7 one because i restored it in the progress of upgrading? Sorry, i am very new to this. Pls see a screenshot of one example table https://www.sugarsync.com/pf/D6922769_683_6154037578?_ga=2.112608964.1122925838.1592914742-1260109309.1592914742
And how would i go about deleting them?
Cheers,
Ben
↧
↧

Re: Installing and Upgrading Moodle on VPS using cPanel Videos

June 23, 2020, 6:15 am
↧

Re: Error DDL sql execution error (mod_h5pactivity)

June 23, 2020, 7:27 am
$
0
0
by Leon Stringer.  

It looks like there's just one database there: bitnami_moodle, the others (information_schema, mysql, performance_schema and sys) are system databases and should be left alone.

So it should be a case of clicking on database bitnami_moodle in the left hand pane, then the tables should be listed in the main pane on the right:

phpMyAdmin showing Moodle tables

You should then be able to find the tables and click ⛔ Drop (which is the database word for delete). Again, ensure there's a database backup before making changes.

↧
Search

Moodle upgrade error - Invalid permissions detected when trying to create a directory.

June 23, 2020, 10:38 am
$
0
0
by Paul L.  

Upgrading moodle 3.5.5 to 3.5.12 and encountered the following error while performing command line update in Windows/IISserver. "Invalid permissions detected when trying to create a directory. " (More detailed errors included below.)

-tried deleted cache folder contents, no luck
-tried adding IUSR with Full access to cache folder, no luck
-tried web interface update, no luck, blank page after a minute
-added myself to cache folder with full access, helped,
-added myself to localcache folder with full access, helped
-added myself to whole moodledata folder, appeared to work then.

Solution: add access permissions to moodledata for the account I was logged into the server with.
The CLI process must be running under my user account, not the web user. To further complicate things my administrator account didnt seem to have enough access rights to the moodledata folder on a network drive, so I added myself, perhaps the network drive was part of the confusion too.

Thought Ild post my solution for Windows 20016 IIS 10 users out there. There's a few forum posts on this issue with apache solutions.


========further details from failed updates:=============

php E:\xxxxxxxxxx\cli\upgrade.php --non-interactive
Default exception handler: Invalid permissions detected when trying to create a directory. Turn debugging on for further details. Debug: [cachedir]/cachestore_file/default_application is not writable, check permissions.
Error code: invaliddatarootpermissions
* line 1566 of \lib\setuplib.php: invalid_dataroot_permissions thrown
* line 1744 of \lib\setuplib.php: call to make_writable_directory()
* line 155 of \cache\stores\file\lib.php: call to make_cache_directory()
* line 528 of \cache\classes\helper.php: call to cachestore_file->__construct()
* line 493 of \cache\classes\helper.php: call to cache_helper::purge_store()
* line 175 of \admin\cli\upgrade.php: call to cache_helper::purge_all()

C:\Users\zzzzzzzzz>php E:\xxxxxxxxx\admin\cli\upgrade.php --non-interactive
PHP Warning:  rmdir(E:\xxxxxxdata/cache/cachestore_file): Directory not empty in E:\xxxxxxxxx\lib\moodlelib.php on line 9443
PHP Warning:  unlink(E:\xxxxxxdata/localcache/.lastpurged): Permission denied in E:\xxxxxxxxx\lib\moodlelib.php on line 9434
PHP Warning:  rmdir(E:\xxxxxxxxx/localcache/htmlpurifier/2018051705.03): Permission denied in E:\xxxxxxxxx\lib\moodlelib.php on line 9443
PHP Warning:  rmdir(E:\xxxxxxxxx/localcache/htmlpurifier): Permission denied in E:\xxxxxxxxx\lib\moodlelib.php on line 9443
PHP Warning:  unlink(E:\xxxxxxxxx/localcache/mustache/1592912537/boost/__Mustache_3428caa03544af11ff6e67391084b68b.php): Permission denied in E:\xxxxxxxxx\lib\moodlelib.php on line 9434
PHP Warning:  unlink(E:\xxxxxxxxx/localcache/mustache/1592912537/boost/__Mustache_5f41112bee7414b7305fa62cbc2d1f13.php): Permission denied in E:\xxxxxxxxx\lib\moodlelib.php on line 9434
PHP Warning:  unlink(E:\xxxxxxxxx/localcache/mustache/1592912537/boost/__Mustache_72541c0a8f02293347e0812e8799ca64.php): Permission denied in E:\xxxxxxxxx\lib\moodlelib.php on line 9434
PHP Warning:  unlink(E:\xxxxxxxxx/localcache/mustache/1592912537/boost/__Mustache_7a43f0495820dce0201da63ee5c35425.php): Permission denied in E:\xxxxxxxxx\lib\moodlelib.php on line 9434
PHP Warning:  unlink(E:\xxxxxxxxx/localcache/mustache/1592912537/boost/__Mustache_7ac6cfa4ad7774790d2aafb799a63dfe.php): Permission denied in E:\xxxxxxxxx\lib\moodlelib.php on line 9434
PHP Warning:  unlink(E:\xxxxxxxxx/localcache/mustache/1592912537/boost/__Mustache_9b0dfa9438111951d1532fded4f28734.php): Permission denied in E:\xxxxxxxxx\lib\moodlelib.php on line 9434
PHP Warning:  unlink(E:\xxxxxxxxx/localcache/mustache/1592912537/boost/__Mustache_e8d8ae873a984614cbb0bd0c2a191036.php): Permission denied in E:\xxxxxxxxx\lib\moodlelib.php on line 9434
PHP Warning:  unlink(E:\xxxxxxxxx/localcache/mustache/1592912537/boost/__Mustache_fe0367092bc18a0ea6dfce2f676bcc18.php): Permission denied in E:\xxxxxxxxx\lib\moodlelib.php on line 9434
PHP Warning:  rmdir(E:\xxxxxxxxx/localcache/mustache/1592912537/boost): Permission denied in E:\xxxxxxxxx\lib\moodlelib.php on line 9443
PHP Warning:  rmdir(E:\xxxxxxxxx/localcache/mustache/1592912537): Permission denied in E:\xxxxxxxxx\lib\moodlelib.php on line 9443
PHP Warning:  rmdir(E:\xxxxxxxxx/localcache/mustache): Permission denied in E:\xxxxxxxxx\lib\moodlelib.php on line 9443
Default exception handler: Invalid permissions detected when trying to create a directory. Turn debugging on for further details. Debug: [localcachedir] is not writable, check permissions.
Error code: invaliddatarootpermissions
* line 1566 of \lib\setuplib.php: invalid_dataroot_permissions thrown
* line 1764 of \lib\setuplib.php: call to make_writable_directory()
* line 1668 of \lib\moodlelib.php: call to make_localcache_directory()
* line 1781 of \lib\upgradelib.php: call to purge_all_caches()
* line 176 of \admin\cli\upgrade.php: call to upgrade_core()

!!! Invalid permissions detected when trying to create a directory. Turn debugging on for further details. !!!
!! [localcachedir] is not writable, check permissions.
Error code: invaliddatarootpermissions !!
!! Stack trace: * line 1566 of \lib\setuplib.php: invalid_dataroot_permissions thrown
* line 1764 of \lib\setuplib.php: call to make_writable_directory()
* line 1668 of \lib\moodlelib.php: call to make_localcache_directory()
* line 1781 of \lib\upgradelib.php: call to purge_all_caches()
* line 176 of \admin\cli\upgrade.php: call to upgrade_core()
 !!
php E:\xxxxxxxxx\admin\cli\upgrade.php --non-interactive
PHP Warning:  rmdir(E:\xxxxxxxxxxxxdata/cache/cachestore_file): Directory not empty in E:\xxxxxxxxx\lib\moodlelib.php on line 9443
-->auth_oauth2
++ 2018051401: Success (0.06 seconds) ++
++ Success (0.16 seconds) ++
-->filter_mathjaxloader
++ 2018051401: Success (0.10 seconds) ++
++ Success (0.14 seconds) ++
Default exception handler: Invalid permissions detected when trying to create a directory. Turn debugging on for further details. Debug: [tempdir]/filestorage is not writable, check permissions.
Error code: invaliddatarootpermissions
* line 1566 of \lib\setuplib.php: invalid_dataroot_permissions thrown
* line 1724 of \lib\setuplib.php: call to make_writable_directory()
* line 59 of \lib\filestorage\file_storage.php: call to make_temp_directory()
* line 6501 of \lib\moodlelib.php: call to file_storage->__construct()
* line 36 of \theme\boost\settings.php: call to get_file_storage()
* line 52 of \admin\settings\appearance.php: call to include()
* line 7997 of \lib\adminlib.php: call to require()
* line 8020 of \lib\adminlib.php: call to admin_get_root()
* line 188 of \admin\cli\upgrade.php: call to admin_apply_default_settings()

!!! Invalid permissions detected when trying to create a directory. Turn debugging on for further details. !!!
!! [tempdir]/filestorage is not writable, check permissions.
Error code: invaliddatarootpermissions !!
!! Stack trace: * line 1566 of \lib\setuplib.php: invalid_dataroot_permissions thrown

↧

Re: Moodle upgrade error - Invalid permissions detected when trying to create a directory.

June 23, 2020, 11:15 am
$
0
0
by Paul L.  

note, next time I will make sure to Right click on the command prompt to 'Run as Administrator'
↧
↧

Re: Error DDL sql execution error (mod_h5pactivity)

June 23, 2020, 4:46 pm
$
0
0
by Benjamin Waller.  

Hello Leon,

Thank you very much for your help. That did the trick! I deleted all those tables and able to update moodle. Once again I am really appreciative.

On the topic of full Unicode support, what is the best method for doing this? When following the instructions from this page https://docs.moodle.org/39/en/MySQL_full_unicode_support do I need to :
1. add the following lines of code to the my.cnf file? See screenshot of file below.
[client]
default-character-set = utf8mb4

[mysqld]
innodb_file_format = Barracuda
innodb_file_per_table = 1
innodb_large_prefix

character-set-server = utf8mb4
collation-server = utf8mb4_unicode_ci
skip-character-set-client-handshake

[mysql]
default-character-set = utf8mb4

2. Then run the follwing scripts?
Restart your MySQL server.
Run the CLI script to convert to the new Character set and Collation (requires Moodle 3.1.5, 3.2.2 or newer):
$ php admin/cli/mysql_collation.php --collation=utf8mb4_unicode_ci
Make sure to repair and optimize all databases and tables.
mysqlcheck -u root -p --auto-repair --optimize --all-databases

Please let me know if this is the best and easiest way.

Best regards,
Ben
↧

Re: Error DDL sql execution error (mod_h5pactivity)

June 23, 2020, 6:11 pm
$
0
0
by Benjamin Waller.  

Hello Leon,

Now I noticed I get an error from the database when trying to access the Content bank option for H5P in my course.. see screenshot below.

so I am guessing after deleting this table "mdl_contentbank_content" I get this error. Should I add back now all these tables I deleted? I would like to use the Contact bank and h5P related content. 

Cheers,
Ben
↧

Re: Upgrading Moodle to 3.9 stable [RESOLVED]

June 23, 2020, 11:33 pm
↧
Viewing all 47003 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>