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

Re: Moodle migration to Oracle

$
0
0
by Howard Miller.  

Don't. 

Although Moodle is in theory compatible with Oracle, you'll be pretty much on your own. Very few optional plugins will ever have been tested with it. It's a bad plan. The best advice I can give is to stick with the server platforms that everybody else uses. For your sanity. 

To make matters worse - migrating from one DB to another is rarely plain sailing. There are some tools out there to do it, though. 


Re: Moodle 0KB downloads after Upgrade

$
0
0
by Howard Miller.  

Ultimately, we have no idea what the Bitnami script you used did so you may have to get your host's support involved. 

However, you should start by turning on Debugging, reproducing the problem and checking your web server's error log. 

Re: Moodle 0KB downloads after Upgrade

$
0
0
by The Haag.  

Where do these file upload to when creating the course? In the moodledata/filesdir directory?

Re: Moodle 0KB downloads after Upgrade

$
0
0
by Ken Task.  

That is correct ... files uploaded to moodle do go to moodledata/filedir/ ... but not by humanly recognizable filenames.

When you upgraded from 2.x to 3.x did Bitnami allow you to upgrade just the code or did you have to re-install bitnami - the php, the apache, the mysql DB included.   Did you make a backup of the site before upgrading?  How about ownerships/permissions on moodledata?

Looks like Bitnami has docs on moodle upgrades:

https://docs.bitnami.com/oci/apps/moodle/administration/upgrade/

Their docs may not mention that one should check the environment in moodle to see if one has correct versions of php and mysql.

Anyhoo, because Bitnami is 'different', you best resource ... 1st resource ... are Bitnami forums and docs.

Any advice you get for free here in these forums or docs you might find probably  have to be translated to 'Bitnamese'. smile

'spirit of sharing', Ken


Re: Moodle 3.6.2+ SSL Certificate Issue - https not working

$
0
0
by Craig Birtwell.  

Hi Luis,

I have taken your advise and re-setup using IIS 10 using PHP 7.3.1, MariaDB 10.3. The wildcard SSL certificate is now installed and Moodle is working fine and the site is secure.  I have also enabled OpCache to improve performance.

Thanks

Craig


Error in database when attempting to browse list of users

$
0
0
by Jeff Kaiser.  

Background: We have migrated a Moodle 2.5+ site from Windows Server 2016 to Linux, which was our first step in updating the site to a current build. The migration went well; so far all end-user functionality appears to be fully operational.

Issue: Error at Site administration/Users/Accounts/Browse list of users. The error message with developer debugging enabled is:

    • Debug info: Unknown column 'wwwroot' in 'field list'
    • SELECT id, wwwroot, name FROM mdl_mnet_host ORDER BY id
    • [array (
    • )]
    • Error code: dmlreadexception
    • Stack trace:
      • line 423 of /lib/dml/moodle_database.php: dml_read_exception thrown
      • line 1005 of /lib/dml/mysqli_native_moodle_database.php: call to moodle_database->query_end()
      • line 1226 of /lib/dml/moodle_database.php: call to mysqli_native_moodle_database->get_records_sql()
      • line 1177 of /lib/dml/moodle_database.php: call to moodle_database->get_records_select()
      • line 133 of /user/filters/lib.php: call to moodle_database->get_records()
      • line 46 of /user/filters/lib.php: call to user_filtering->get_field()
      • line 160 of /admin/user.php: call to user_filtering->user_filtering() 

The mnet_host table contains 2 rows; one contains wwwtpdbusr=http://localhost/moodle, ip_address=127.0.0.1, name=blank, and the other contains wwwtpdbusr=empty, ip_address=empty, name=All Hosts. Other than the id field, these are the only fields with different values between the 2 rows.

Troubleshooting: Verified that the wwwroot setting in config.php is set to the correct url, 'http://mydomain.com'. Updated configuration items that contained Windows file paths to the default value suggested by Moodle.

I'm hoping that there is a configuration setting that was set for Windows, but needs a different value on a Linux host. I've searched through the configuration settings and I was unable to find anything that was obvious to me. The only references to localhost are in the chat_serverhost (value=localhost) and HTTP proxybypass (values=localhost, 127.0.0.1) settings.

Please let me know if you have any guidance or additional questions that may lead me to a resolution for this issue.

Thank you,

Jeff


Re: Error in database when attempting to browse list of users

$
0
0
by Ken Task.  

The table causing the issue is mdl_mnet_host

What do the following queries show;

mysql> select id,deleted,wwwroot from mdl_mnet_host;

and related ...

mysql> select id,username,firstname,lastname,email,mnethostid from mdl_user;

A server not using any Moodle Networking has the mnethostid as '1' for all users in mdl_user.

Not all url's may have been converted when using the hidden /admin/tool/replace/ tool so you might have to manipulate the mdl_mnet_host table via mysql client on DB server.

'spirit of sharing', Ken


Database error

$
0
0
by Joshua Kingston.  

Ok I was trying to upload questions in Aiken Format but it would only upload one question and then it didn't even do it right so when i click on the question I get this error 


Any ideas I am not adept at the server side of things i tried going to the forum posted about it but got lost. I'm also not sure how to force run Chrons. 

Please help!



Moodle 0KB downloads after Upgrade

$
0
0
by The Haag.  

Hi All,

Following on from a previously ask Question however, this was from bitnami build 2.9 to 3.5, All files within a course are downloading 0KB files. Is there a solution to what could be the possible cause of this??

https://moodle.org/mod/forum/discuss.php?d=357981

Hoping someone can help.

Re: Error in database when attempting to browse list of users

$
0
0
by Jeff Kaiser.  

Hi Ken, 

Thank you for the quick response. 

For mysql> select id,deleted,wwwroot from mdl_mnet_host; , I get:
        #1054 - Unknown column 'wwwroot' in 'field list'

For mysql> select id,username,firstname,lastname,email,mnethostid from mdl_user;, I get:
        A list of users

If I run select * from mdl_mnet_host; , see the attached image.

It looks like the "wwwroot" field was somehow renamed to "wwwtpdbusr" during migration. I have renamed the field to "wwwroot" and now I can see the list of users. 

Thanks for having me look at this another way,

Jeff




Re: Error in database when attempting to browse list of users

$
0
0
by Ken Task.  

Good!  Glad to hear it!   Strange though that a column name changed on xfer.   Let's hope that was the only one.  If you run into any other weirdness, might want to 'explain' the table shown in the error to see it's  structure and column names.

Have rated your fix useful in hopes that others who make the move from Windows to Linux (me thinks a very wise move) and have the same issues might find this thread and be able to fix their own.

'spirit of sharing', Ken


Upgrading to 3.4 mysql Barracuda blocker

$
0
0
by rob davis.  

Hi,

I have a Moodle 3.3.1 instance hosted by 1and1 (now IONOS) and back in Jan 2018 I tried to upgrade it to 3.4.


This failed because of the mysql innodb file requirement to be Barracuda and I had to do a complete roll back.


I am now trying this again. This time I have created a VM with all the standard settings from the https://docs.moodle.org/33/en/Step-by-step_Installation_Guide_for_Ubuntu 


I have then set the mysql innodb to Antelope expecting the upgrade to 3.4.7 to fail. 

SET GLOBAL innodb_file_format = antelope;
SET GLOBAL innodb_file_format_max = antelope;
SET GLOBAL innodb_large_prefix = off;

But it did not fail and when I checked the innodb settings afterwards I found it had set them back to Barracuda.


Because of the shared hosting I am unable to change the innodb settings for my live instance. I am guessing the Moodle upgrade process will also be unable to make the change.


How can I set up my VM so the Moodle upgrade fails? 

The whole point of all this was I wanted to try an bypass the check using https://stackoverflow.com/questions/51838089/moodle-baracuda-check-bypass-or-highest-antelope-version


Has anyone got this upgrade working on a 1and1 shared hosting?


Or has Moodle 3.4.7 resolved the Barracuda requirement?

We do  not need Unicode support


Top 120+ Google Adsense High Cpc Keywords List 2019

$
0
0
by lokesh vijay.  

If you are getting very high traffic on your website and still not generating much revenue from Google Adsense and it is not because you are not getting clicks but because of your CPC (Cost Per Click) is very low then you are at the right place because here I am going to tell you here about the Highest Paying Keywords of adsense and if you will work on them then you will easily earn thousands of dollars from very low traffic.




 Hey guys, My Name is Lokesh from Tech With Logic and here I am going to share with you about Top 120+ Google Adsense High Cpc Keywords List 2019 and if you work on them then you will earn alot money in 2019 with Google Adsense.
to read more click here

Re: moodledata directory ownership

Re: Upgrading to 3.4 mysql Barracuda blocker

$
0
0
by Ken Task.  

First, let me introduce to you another 1and1 user ... found @

https://moodle.org/mod/forum/discuss.php?d=381788

You and he might need to talk about experiences with hosting provider.

When you set up another VM ... it wasn't a shared system ... thus not really a fair environment comparison.

The commands you used to set globals are good only for the session ... the CLI session ... not the Web based client (another session) install session.

As far as needing Barracuda and the 'extra character support' .... yes, your site might not offer courses in an Asian language, but the 'modern expection' of users is 'emoj's' - regardless if there is any educational value in emoj's or not, sites might be judged by users as ancient/archaic if users can't use emoj's.  And factor into that .... devices ... smart phones/tablets.  Users today might actually choose some other online education/training if they cannot use their smartphone or 'fablet'!

Can't use emoj's with Antelope and older character sets/collations.

Question ... was your current 3.3 site (the one you want to upgrade on shared hosting), installed with 1&1's "Click and Build"?

The  user at above link opted to do that some time ago and now is having issues with core files that should be there, but are not.   Now how did that happen?.

Suggestion ... since you know it works in a VM with 1&1 why not move your production instance to that environment ... where you are the only customer and 'relatively' in 'control' of that environment?

Also suggest using the current sites Environment check.  Update the component.  Use the pick list for higher Moodle versions to see what the environment check says.

No offense, but trying to hack thus allow upgrade to 3.4.highest me thinks is kinda futile ... even if you succeed.   Why?   Can't stay a 3.4.highest much longer.

https://docs.moodle.org/dev/Releases#Moodle_3.4
Bug fixes for general core bugs in 3.4.x ended 12 November 2018 (12 months).
Bug fixes for security issues in 3.4.x will end 13 May 2019 (18 months).

Again ... no offense ... kinda like trying to continue to use Window XP or MacOS 9 ...

Yes, the VM will cost more than cheapo shared ... but  is it worth the extra cost if you don't have to contend with finding ways to hack?   What of your students/clients experiences, etc.?

No one likes change ... but it's the only constant.   Why fight it?

My 2 cents of course.

'spirit of sharing', Ken


Re: Upgrading to 3.4 mysql Barracuda blocker

$
0
0
by Howard Miller.  

Just to be clear. Barracuda is NOT a requirement. It's only advised. 

It only becomes a requirement if you change your DB's character set to utf8mb4. Which you also don't have to. 

What you loose is the ability to store emojis.

Re: Upgrading to 3.4 mysql Barracuda blocker

$
0
0
by Ken Task.  

Yes, that is 'technically' correct.   But ... why does the user report an attempt to upgrade on shared hosting at 1to1 and it failed?

The directions for upgrading the 'old way' say to copy the config.php file out to a safe place, acquire the new code from moodle.org ... and so on and so forth ... at the end, move/copy that archived config.php file back into the new code directory.   Should trigger and upgrade.

But ... but ... there's something new in the download code for moodle 34 config-dist.php ... there is another line in the array for the DB.

    '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.

Directions for 3.4 at Moodle.org don't mention that - or if they do/did, haven't seen it.  Should users add that line to their config.php?

Something else on **shared systems** ... for hosting providers that do allow ssh into shared accounts, not all of the cli scripts in moodlecode/admin/cli/ will work as expected.

Those scripts use config.php for DB user ... DB user in shared database systems don't have priv's high enough to make changes to customers own databases.  Especially those that are global changes to the DB server - not just the DB's for the customer.

Besides that ... changes to a database involve three levels ... database, tables, and the columns in those tables.

All in all, don't think the poster would intentionally 'fib' ... poster said it failed ... and from what I've seen when granted access via ssh to such accounts as the user (no two providers are the same) have come to the conclusion that the days of Moodle hosted on shared systems is almost over.

Another poster on different shared system ... a 'click and build' install ... which we don't know anything about ... has worked for a couple of years without error ... until recently ... poster is stuck in infinite loop attempting to install something that is core and no way to do that.

So right about now, moodle hosting on shared host will have some strange results - like 'perfect storm'?

Still stand on advice given then though ... move from shared hosting to a dedicated VM so that one can at least have the appearance in being in control. :|

'spirit of sharing', Ken

Re: Upgrading to 3.4 mysql Barracuda blocker

$
0
0
by Howard Miller.  

The collation line needs to be correct (in config.php). If you're have that set to mb4 and you're not actually using that then the OP's problem will be the outcome. 

While we advise copying over the config.php from the old version to the new version, it's always worth having a look at config-dist.php to ensure that there are no significant changes. 

I'll go and (again) double check the truth of all this and add it to the documentation somewhere. (not tonight! The dog is glaring at me!!)

I might sound a bit sniffy about it but, yes, it's exceedingly unclear.

Re: Upgrading to 3.4 mysql Barracuda blocker

$
0
0
by rob davis.  

thanks for advice. I had a look at moving from 1and1 and at the moment that is not going to possible.


What I did do is create a new database on the same hosting and restore the DB. Then I got Moodle 3.5.4 (did not realise 3.4 was so long in the tooth) copied the config.php and updated the user and path information.


Got the upgrade process and got the issue.

screen shot of error


Then I ran the mysql_compressed_rows.php and was surprised to see only 9 results.

isef_block_exacompexamples      Compact (needs fixing)

isef_data                       Compact (needs fixing)

isef_data_fields                Compact (needs fixing)

isef_enrol_lti_lti2_consumer    Compact (needs fixing)

isef_enrol_paypal               Compact (needs fixing)

isef_lti                        Compact (needs fixing)

isef_oauth2_issuer              Compact (needs fixing)

isef_user                       Compact (needs fixing)

isef_user_info_field            Compact (needs fixing)



mysql_compressed_rows.php --fix

gave an error

Cannot change GLOBAL innodb_file_format setting, use --showsql option and execute the statements manually.!!! Error writing to database !!!


so I ran with --showsql and got


USE mydb;

SET SESSION sql_mode=STRICT_ALL_TABLES;

SET GLOBAL innodb_file_per_table=1;

SET GLOBAL innodb_file_format=Barracuda;

ALTER TABLE isef_block_exacompexamples ROW_FORMAT=Compressed;

ALTER TABLE isef_data ROW_FORMAT=Compressed;

ALTER TABLE isef_data_fields ROW_FORMAT=Compressed;

ALTER TABLE isef_enrol_lti_lti2_consumer ROW_FORMAT=Compressed;

ALTER TABLE isef_enrol_paypal ROW_FORMAT=Compressed;

ALTER TABLE isef_lti ROW_FORMAT=Compressed;

ALTER TABLE isef_oauth2_issuer ROW_FORMAT=Compressed;

ALTER TABLE isef_user ROW_FORMAT=Compressed;

ALTER TABLE isef_user_info_field ROW_FORMAT=Compressed;


and running that in phpmyadmin SQL got

SQL query:

SET GLOBAL innodb_file_per_table=1

MySQL said: Documentation

#1227 - Access denied; you need (at least one of) the SUPER privilege(s) for this operation


I have now passed those SQL statements to 1and1 support, not sure if they can action them or not.


Re: Upgrading to 3.4 mysql Barracuda blocker

$
0
0
by Ken Task.  

Would be surprised if they would do that for one shared instance.  Sorta opens pandora's box.

However, having said that ... a little leg work for you.  Might not have to move to some other hosting provider but move internally, but ...

https://www.ionos.co.uk/pro/cloud-apps/a/moodle
Version: 3.6.2-1
This application runs on Linux CentOS 7
Minimum requirements: Cloud Server M

Our cloud server recommendation:
1 vCore CPU
1 GB RAM
50 GB SSD

£ 10.00 / mo.

Tip!
You can use any number of free apps as part of your contract. All you need for each app is a separate VM.


Looks under-powered for anything but a tinker Moodle site to me. Am almost willing to bet attempting to migrate from shared hosting to the above would be difficult *IF* going with recommendations as above.

OP would have to take stock of existing site space/usage, etc.  and then calculate if existing would 'fit' and/or work.  No tool in Moodle of which am aware that would give OP that data in a easy one click kinda thing.

There cloud M server does have options ... higher - specs which means $->

'spirit of sharing', Ken


Viewing all 46810 articles
Browse latest View live


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