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

Re: Can't get through the installation process! Problem with admin account setup

$
0
0

by Troy Wolf.  

So the reason styles.php can't find theme_get_sub_revision_for_theme() from /lib/outputlib.php is because when setup.py is included from styles.php (by way of config.php), it has this bit:

define('ABORT_AFTER_CONFIG', true);
require('../config.php');

That ABORT_AFTER_CONFIG tells setup.php to abort and load a minified setup of some kind....those require_once() lines don't happen, thus the method is missing.

As a test, I disabled the ABORT_AFTER_CONFIG line in styles.php, but things broke in other ways.

I'm missing something here or the 3.4.1 release is simply broken. I have to assume the former, but...thoughts?


Re: Can't get through the installation process! Problem with admin account setup

Trả lời: Re: installation (version 5.5.31 is required and you are running 5.5.5.10.1.10)

Re: No forum post get send as email ....

$
0
0

by Matteo Scaramuccia.  

Here is the related docs for Exim, https://www.exim.org/exim-html-current/doc/html/spec_html/ch-smtp_authentication.html#SECTauthexiser :

When Exim receives an EHLO command, it advertises the public names of those authenticators that are configured as servers, subject to the following conditions:

  • The client host must match auth_advertise_hosts(default *).
  • It the server_advertise_condition option is set, its expansion must not yield the empty string, “0”, “no”, or “false”.

HTH,
Matteo

error in installing Moodle-Your database has tables using Antelope as the file format

$
0
0

by moodle question.  

Hi, 


I am facing problem in installing new Moodle, 

I am getting this error


  • Your database has tables using Antelope as the file format. Full UTF-8 support in MySQL and MariaDB requires the Barracuda file format. Please convert the tables to the Barracuda file format. See the documentation Administration via command line for details of a tool for converting InnoDB tables to Barracuda.


  • For full support of UTF-8 both MySQL and MariaDB require you to change your MySQL setting 'innodb_large_prefix' to 'ON'. See the documentation for further details.

Moodle (3.1 LTS)

when I created the database I chose the correlation  utf8_unicode_ci. and also tried utf8_general_ci

both options didn't work


I read the help but I here and here but I really didn't understand how to solve the problem

I am using wamp 2.5

mySqL 5.6.17

 I created the database using phpmyadmin

any help appreciated




Re: Can't upgrade from 3.3.1 to 3.3.4 (Barracuda issue)

$
0
0

by Martin Millmore.  

It appears that this regression only hits people who are using the utf8mb4 character set with Antelope. If you are using any other character set, the check passes. So the impact is likely limited.

Re: error in installing Moodle-Your database has tables using Antelope as the file format

$
0
0

by moodle question.  

I spent 2 hours , and when I post the thread I solved it big grin

just run the following in mysql console as in moodle documents.

SET GLOBAL innodb_file_format = barracuda;


SET GLOBAL innodb_file_per_table = 1;


SET GLOBAL innodb_large_prefix = 'on';

Re: Upgrade Moodle 3.1 to 3.4 PHP/SOLr error

$
0
0

by Ron Vitug.  

Hi Ken,

Actually this is the one we build before. I just upgraded it to the PHP 7 and the error show up. Yes we still using SciLinux

$ nano solr.ini 

$ sudo service httpd restart 

Stopping httpd: [ OK ] Starting httpd: [ OK ] 

$ php -m |grep solr

PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib64/php/modules/solr.so' - /usr/lib64/php/modules/solr.so: undefined symbol: zval_used_for_init in Unknown on line 0


Correct that is the tail end after we did the pear install pecl/solr on 3.1



Re: error in installing Moodle-Your database has tables using Antelope as the file format

$
0
0

by Ken Task.  

While the link below is for version 5.7, think it applies to versions
Moodle might be running under as well.

https://dev.mysql.com/doc/refman/5.7/en/using-system-variables.html

"If you change a global system variable, the value is remembered and used for new sessions until you change the variable to a different value or the server exits. The change is visible to any client that accesses the global variable. However, the change affects the corresponding session variable only for clients that connect after the change. The global variable change does not affect the session variable for any current client sessions (not even the session within which the SET GLOBAL statement occurred).

To make a global system variable setting permanent so that it applies across server restarts, you should also set it in an option file
."

And, the 'set global' will only work *IF* the DB user is the 'superuser'.

Suggest you create a text document with those global set commands for safe keeping.

Make a backup of your DB for Moodle.

Then restart your MySQL service as a test to see if your Moodle site remains accessible/usable.

If it doesn't, use your text document global commands again.

'spirit of sharing', Ken

Re: Can't upgrade from 3.3.1 to 3.3.4 (Barracuda issue)

$
0
0

by Ken Task.  

In latest git pull of 3.3 the config-dist.php file has a line:

    'dbcollation' => 'utf8mb4_unicode_ci', // MySQL has partial and full UTF-8
                                // support. If you wish to use partial UTF-8
                                // (three bytes) then set this option to
                                // 'utf8_unicode_ci', otherwise this option
                                // can be removed for MySQL (by default it will
                                // use 'utf8mb4_unicode_ci'. This option should
                                // be removed for all other databases.

When one upgrades the config.php file isn't touched - not even when using git.

Always a good idea to check the config-dist.php file to see if there are changes that could affect an update or upgrade.

2 cents and hind sight, I know ... but ...

'spirit of sharing', Ken


Re: Upgrade Moodle 3.1 to 3.4 PHP/SOLr error

$
0
0

by Ken Task.  

Ok, am confused by response .... are you saying you've solved it ... or are you saying you still get the warning?

zval_used_for_init  indicates you are using Zend Guard Loader.

Do you need or are you required to run that?

Is Zend Guard Loader looking in the same directory for .so files?

'spirit of sharing', Ken


Moodle & Dspace

$
0
0

volgens rashad al masry.  

Dear ALl,


hello, I'm new to Moodle and I'm working on integrating Moodle with Dspace as a repository, I followed the below steps:

1- install the SWORd upload repository.

2- I enabled the repository from site Administration -> plugin -> repository

3- I added the sword URL. the repository was displayed only when I need to add a link only.


My question: how to enable/ Display the repository while adding course content.


moodle version used: 3.3 

your help is much appreciated.


Regards,

Moodle Theme Stopped Working After Purge Cache

$
0
0

volgens Linas Peckys.  

Hi everyone,


I have reached inodes limit of 300 000, and I was advised to do a house keeping like clearing the cache. I found in google that I can "Purge All Cache" on moodle, that's what I did. So after this, the theme does not load up... It does load up when I turn on "theme designer mode", but the website then is very very slow...


How can I solve this?

Re: Can't upgrade from 3.3.1 to 3.3.4 (Barracuda issue)

$
0
0

volgens Ken Task.  

It is an issue for admins who haven't made a habit of using the Environment check prior to updates or upgrades or who don't maintain a 'sandbox'.   Shared hosting, a popular choice for many simply due to cost, is the other major factor.   Those seeking an 'easy button' might have problems (more than likely).

Wonder, if on your shared hosting, it were possible to use 'alter' on the DB's for your Moodle.   Wonder if helpdesk of where you host would make sure the DB user for your shared hosting had 'alter' priv's for databases they 'own'?

Two things .... IF site is English only ... no need for the 'extra bites' to support Asian languages, is there?.   And if the site doesn't really care about emoj's usage, then also not needed.   While use of 'emoj's' is 'cooler'/more 'modern', is there any significance or improved instruction/learning because they are used?

But, it is what it is .... for the non-Moodle Association user, not with a Moodle Partner, etc. may as well go with the 'flow' and not try to fight it.   After all it is offered for free.

'spirit of sharing', Ken



Re: Upgrade Moodle 3.1 to 3.4 PHP/SOLr error

$
0
0

volgens Ron Vitug.  

Still getting the warning. Not sure on Zend Guard Loader that just show up after I upgrade the php that is the only changes I did so far. Once  I revert back to the old php I encounter no error

Re: Installing moodle 3.4 on Cloudways with Debian distro

$
0
0

volgens Skeeter Harris.  

Hi Emma,

Thank you for your response and first off please understand I am not familiar with Lunix so were talking complete newbie here.  So following your instructions - I created a PHP server on Cloudways VPS and then checked with the online support team who told me that  LAMP was already installed.  So my thinking is step 1 was complete.

I was able to copy and paste step 2 as you described without issue.

I then downloaded and FTP back up the uniziped moodle 3.4.1 into a directory called moodle and created the moodledata directory. but when I tried to change permissions the commands came back operation failed.

Step 6 was really where I lost it.  At this point you're saying I have to point Apache to the moddle website but no where did I see where or what configuration file (my assumption) I need to change.  So I just had no idea what to do here.

Finally my guess is that step 7 would end up being something like http://moodle.12345-1345.cloudwaysapps.com/moodle  would be then how I would get to the app.

That's where I ended up and finally after many hours yesterday just gave up.


Database Deadlock when upgrading Moodle

$
0
0

volgens Rolf Cper.  

Hello expert,
Three months ago I had Moodle 3.0 running, but something went wrong when trying to update Poodll.
Ever since, I cannot get Moodle to run anymore because of 'Error reading from database'.
I have tried two ways to get a new Moodle environment working with all my old courses running properly:
a) I tried to use the newest version of Moodle (v3.4.0.) and connect it to my old database (of Moodle v3.0 in MySQL v5.7) in order to get access to all my course content (It took me years of effort creating them).
b) I tried to extract the content (and layout/makeup) of my courses (from Moodle 3.0 in MySQL) and import them into a clean Moodle database (from Moodle 3.4.0.) in order to avoid previous persistent database errors.
Both a) and b) lead to many errors:

ad a)
I start in my Test-environment with http://localhost:83/install.php . (I can login as administrator.)
At the beginning of upgrading procedure (http://localhost:83/admin/index.php?lang=en), I will see that:
1) 411 plugins need to be updated ('plugins acquiring attention').
Every time I click on the button 'Upgrade Moodle database now' the procedure crashes with 'Error reading from database', for example qtype_essay, with some debug_info and stack trace.
I go back to the previous page (http://localhost:83/admin/index.php?lang=en) and one less 'plugin acquires attention'.
Should I do these steps 411 times, and then eventually end with the same 'Error reading from database' ?

2) Several plugins are missing ('Additional Missing from disk!') in my Test-environment, such as:
groupselect 2017061302
user_bookmarks 2016100800
poodllz 2014102100 (crippled version of Poodll, mentioned in the old database that I cannot get rid of/erase).
wordcount 2014051200
analytics 2017031300
mobile 2015111114 (see item 3).
Should I download each separate zip-file of these plugins and copy the unzipped folder to the local-directory of Moodle, before I upgrade?

3) 1 update available needs to be installed: mobile 2015111114 Additional Missing from disk! There is a new version 2017111300 available! Release 3.4.340 .
After I click on 'Install this update' it
How do I get rid of the plugins that seem to cause errors, at the beginning of the upgrading procedure (to Moodle 3.4.0)?

4) 11 plugins have the status 'To be deleted'.
5) 43 plugins have the status 'To be installed'.

Summary: The plugins Mobile and Poodllz seem to cause trouble. The error 'Error reading from database' keeps on returning.

ad b) Extract existing courses from old, crippled database:
I do not know which are all the correct tables.
How do I use the tool HeidiSQL to extract (all) the correct tables within Moodle 3.0 database, so I can import them in Moodle 3.4.0. DB?
Which tables should I at least export/import (how many tables)?
If I succeed in extracting/exporting the correct data, can I overwrite the similar file (.frm) in the new database?

Does anyone have any advice on how to go about?

Friendly regards,
Rolf Snijders

PHP 7.0.9 on WIMP

Re: Moodle Theme Stopped Working After Purge Cache

$
0
0

volgens Emma Richardson.  

Go into your moodleDATA folder and manually delete cache and local cache folders.  That should fix it.

Re: Moodle Theme Stopped Working After Purge Cache

$
0
0

volgens Ken Task.  

Preface for this response .... you might eventually need to find another hosting provider.  I have seen a hosting provider that had inode limits which did provide a 'special package' for installing a Moodle to get under their inode limit.   That package removed behat testing and some other meant-for-developer tools that come with the typical moodle code.

*BEFORE* thinking about that (one seriously cripples Moodle), look else where first.

Example: got any courses not active (hidden)?   Might consider attempting backup of those, download those backups, then remove them.

How many backups of courses do you have?

Are you running Autobackups?   Might have to turn that off and find an alternative to backups of courses.

Are you using videos/audios in courses where the videos/audios are stored in Moodle?   Might look into hosting those in a repository outside of Moodle where one could simply link to them.

Bascially, you are looking for anything that adds to the inode (which is everything really), that could possibly be hosted else where and linked to.

But .... think your 'best' option is to seek a hosting povider that is more 'moodle friendly'! ;)   Moodle, now-a-days, only grows .... it doesn't get smaller.

'spirit of sharing', Ken


Re: Upgrade Moodle 3.1 to 3.4 PHP/SOLr error

$
0
0

volgens Ken Task.  

So when you revert back to older PHP, is the Zend Loader still present?

php -m

at the bottom shows.

Now if you are using yum to upgrade the PHP, how are you doing that?  and the repo from which you are pulling PHP is?

If using a yum command with a global .... something like yum install php-*, whatever is available from the repo using will be installed (cept conflicts).   That's where one grabs an extension not really needed.

Might need to be more exacting with yum ... ie, long command, but getting only the extensions needed ... not extra ... or use the --exclude= switch to omit.   Just don't do the command with a -y ... that way you get a chance to see what yum is gonna do .... a y/n prompt pauses the update/upgrade process.

After upgrading the PHP extensions with a global, one could turn around and remove extensions not needed *IF* that doesn't pick up extensions via dependencies you need to run the Moodle.

'spirit of sharing', Ken

Viewing all 47191 articles
Browse latest View live


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