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

Re: Error Message after upgrade - The operation timed out while waiting for a lock

$
0
0
by Howard Miller.  

This is normally an error reported in connection with Scheduled Tasks (i.e. cron jobs), although it's not impossible I suppose. 

Can you do three things...

- enable Debugging by copying the lines from section 7 of config-dist.php to config.php

- completely delete the 'cache/' directory under your moodledata / $CFG->dataroot directory (not your Moodle program code)

- Purge the caches using https://docs.moodle.org/35/en/Administration_via_command_line#Purge_caches


If you're lucky it might fix it. Failing that we should at least find where the error is originating. 


Re: Error when Updating Moodle 3.1 (Build 20160623) to Moodle 3.3 or higher

$
0
0
by Visvanath Ratnaweera.  

Hi

How did you know that (Windows) PHP 7.1 is better than 7.2 for Moodle or were you just lucky.

Your other question: To get more information than "500 Error", you need to switch on https://docs.moodle.org/en/Debugging.

Re: Migrated to new host & now no images showing

$
0
0
by Tina Smith.  

Sorry, I'm not actually answering all questions ...in last post and this one...I'm trying to shoot off quick answers when I can...I WILL get back to both of your posts with more answers as soon as I have more time...probably a little later today...Just want to quickly answer the things that I can quickly address...

I didn't change the URL. URL is the same, I only changed hosts. I went from Host Gator to Site Ground. NOW, I DID get an SSL with the change though.... would I need to do search and replace for that? I did not have https on Host Gator (old) but I DO on Site Ground (new).  That never occurred to me.  See...this is why I need more brains to help me think through these things! LOL!


I already have all the backups from the old host still. Have the moodledata and database...even have the old backup of the install...I just thought that might have been where the problems were so I wasn't going to use that when I tried to reinstall this time...  and I still have access to my Host Gator server...paid for another month until I sort this out. So it's still sitting there. I can't get into the Moodle install via login, but I can via cpanel.


More later.


Re: Problems updating to Moodle 3.5 with MySQL 8.0 and mod_chat

$
0
0
by Debbie Unterseher.  

The following was the information that my IT person sent me:

  1. Started with Moodle version 3.2.6
  2. We did a backup of the database from the MariaDB version 5.5.56
  3. Created a new server with MySQL version 8.0.11
  4. Loaded the backup from MariaDB to MySQL
  5. Created a new server for Moodle.
  6. Used the git method to checkout the 3.5 version of moodle
  7. Used a web browser to go to the moodle site and was presented with the upgrade screen which then eventually led to the screen shot.
  8. I then used MySQL WorkBench to manually change the system column name to find the syntax that should be used.
  9. I then modified the upgrade.php in the chat module to have the accent mark around system.  This then allowed the upgrade script to run correctly.

Re: Migrated to new host & now no images showing

$
0
0
by Ken Task.  

Am not certain that anyone trying to help can actually follow what you've done/tried, etc.   Know this is sort of pressing to you ... at least until end of July ... so let's not go off into yet another direction just yet.

IF the domain was the same and the only thing that changed in the URL was http to https then that's all one needed to do in the search and replace tool ... http://domain/moodle/ to https://domain/moodle/

Notice that /moodle/ was in existence on old site ... and from what I'm able to gather then is still true on new host.

The business about backups ... think the backup of the moodledata directory on old system was botched ... either in backup or transfer of that backup.    Like I said before, moodledata backups on sandboxes I have are in M to Gigs.  You showed KiB (killobytes).   Now if the original moodledata backup file you downloaded is still in your possession, check the size.   The fact you have to upload that again means two transfers ... down then up to new.  Those transfers need to be in binary mode .... not ASCII/Text ... whatever you were using for FTP shoud have a setting for that.   Could be you uploaded the moodledata backup as ASCII/Txt and thus corrupted it ... result ... no images.

Oh, that offer ... is one time and has a 24 hour time limit ... now that it's Monday I too have 'gone back to work'.  (yes, even us 'retired folk') :\

'spirit of sharing', Ken



Re: Error when Updating Moodle 3.1 (Build 20160623) to Moodle 3.3 or higher

$
0
0
by Andy Hamm.  

I was just lucky.  I couldn't get PHP 7.2 to work but 7.1.19 worked fine.  So yes, just lucky.

Thanks for the info on debugging.  I will remember for the future!

Fortunately, all is working extremely well now!

Andy from Boyceville, WI

Re: Migrated to new host & now no images showing

$
0
0
by Tina Smith.  

It's ok, I totally appreciate the offer...I think I'm going to keep trying to poke around myself and see if the stuff you are teaching me is going to help me figure this out....I usually eventually hit on a solution with help from forums like these....it just sometimes takes awhile. But I don't give up! smile

I'm not actually in a big time crunch. (Other than the host...but I can buy another month if need be.) No one is waiting for these classes. It's a side project right now. I have other projects I'm working on as well... which keep taking priority, so I've yet to make time to get fully back to this... but I'm going to see what I can squeeze in this week because this has gone on long enough.

So if what you are saying proves true... perhaps its as simple as redownloading/uploading that moodledata file (I'll check the size on the original server), and doing search/replace for the https...cross my fingers and see what happens. If it doesn't work, I'll go back to trying a fresh install. Worth a shot!

Oh and I'm not using FTP, takes too long...I just zip within CPanel and download and upload and extract through that. I read somewhere that that can be more efficient and faster? Seems to work for me. Most of the time.  FTP was just taking AGES.

Going to poke around and see what happens! Hopefully I'll have some promising info when I get back!


Thanks again SO MUCH for taking time to help me!

Re: Migrated to new host & now no images showing

$
0
0
by Ken Task.  

Well, all I can say is ... you are my kinda teacher!!!!  .... 'Never Give Up' is a mantra I would hope most teachers have ... with teaching and with tech!

Just 'thimk, before click!' (nope, spelled it right).  And one additional, take the time to jot down in notepad what you did. smile

'spirit of sharing', Ken



Re: Migrated to new host & now no images showing

$
0
0
by Rich Debonair.  

Thank you, i am now using another theme and its working plus i was doing something else terribly wrong ie letting 2 different versions share the same database!!!!!

Re: Problem after upgrading to Moodle 3.4+ or 3.5+

Re: Problems updating to Moodle 3.5 with MySQL 8.0 and mod_chat

$
0
0
by Matteo Scaramuccia.  

TNX Debbie!
I'll file the issue into the Tracker.

Moodle addressed all the known issues - both in the modules code and in the unit tests testing some edge cases in the DB API - around MySQL 8 since 3.3.7/3.4.4/3.5.1, even if MDL-59098 is still open for some feedback.

HTH,
Matteo

Apache server fails with the ERROR - at MoodleWindowsInstaller-latest-35.zip

$
0
0
by Kahraman Bulut.  

I have downloaded the latest 3.5.1 version for Windows from  https://download.moodle.org/download.php/windows/MoodleWindowsInstaller-latest-35.zip

During the installation when I clicked the CONTINUE button on the module installation page (see screenshot) the ApacheServer has crashed. I tried 2 times with the same result at the same step. These are the lines from the APACHE logs:

[Tue Jul 10 11:46:28.019403 2018] [ssl:warn] [pid 7256:tid 164] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name

[Tue Jul 10 11:46:28.204403 2018] [ssl:warn] [pid 7256:tid 164] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name

[Tue Jul 10 11:46:28.238403 2018] [mpm_winnt:notice] [pid 7256:tid 164] AH00455: Apache/2.4.28 (Win32) OpenSSL/1.0.2l PHP/7.1.10 configured -- resuming normal operations

[Tue Jul 10 11:46:28.238403 2018] [mpm_winnt:notice] [pid 7256:tid 164] AH00456: Apache Lounge VC14 Server built: Oct  4 2017 11:36:32

It seems it needs a SSL certificate ? Can you please help how to move forward from here ?

Thanks!




Re: Help with Redis cache

$
0
0
by Tony H.  

Hi Alan,

Did you get this to work? We just upgraded to 3.5.1 and I've not seen a slow admin interface. We are using NGINX, but as a reverse proxy to the standard Apache/PHP setup. Our Redis server and moodledata are on the same VPS,

Here are some things to try:

  1. Site administration -> Plugins -> Cache stores -> Redis
    1. Enter the test server information, such as your Redis server in the Test server field. (mine is 127.0.0.1:6379)
  2. Site administration -> Plugins -> Caching -> Configuration
    1. Honestly, I don't know if you need this...
    2. Add a store instance to Redis
    3. It should be ready (with a green check) and have at least one store
    4. You can view the store instance information under Configured store instances 
  3. Site administration -> Plugins -> Caching -> Test performance
    1. Run a test set
    2. If Redis is working, you should see the information there.
    3. Run the largest test set. Perhaps you can't do this on your setup, but you might be able to monitor the processor status through htop on your caching instance. If so, you should see redis show up in the process list as it processes the large request set.
    4. Here are my values (for comparison)
      1. 500 requests: 0.02020.01620.01720.0142
      2. 10000 requests: 0.30550.30170.29460.3084
      3. 100000 requests: 3.20922.91873.04523.1045
  4. Verify Redis is properly handling the requests using redis-cli monitor 
    1. https://redis.io/commands/monitor
    2. This is from our VPS:
1531191276.803634 [0 127.0.0.1:38460] "PING"
1531191276.803894 [0 127.0.0.1:38460] "SETNX""bm_moodlean1nng1eq5a49kqhctil830gn4.lock""s:1:\"1\";"
1531191276.804052 [0 127.0.0.1:38460] "EXPIRE""bm_moodlean1nng1eq5a49kqhctil830gn4.lock""7200"
1531191276.804179 [0 127.0.0.1:38460] "GET""bm_moodlean1nng1eq5a49kqhctil830gn4"
1531191276.804351 [0 127.0.0.1:38460] "EXPIRE""bm_moodlean1nng1eq5a49kqhctil830gn4""7280"
1531191276.810255 [0 127.0.0.1:38460] "SETEX""bm_moodlean1nng1eq5a49kqhctil830gn4""7280""s:228:\"USER|O:8:\"stdClass\":2:{s:2:\"id\";i:0;s:10:\"mnethostid\";s:1:\"1\";}SESSION|O:8:\"stdClass\":3:{s:4:\"lang\";s:2:\"en\";s:8:\"wantsurl\";s:29:\"https://moodle.my-instance.com/\";s:7:\"fromurl\";s:44:\"https://moodle.my-instance.com/cache/admin.php\";}\";"
1531191276.810391 [0 127.0.0.1:38460] "DEL""bm_moodlean1nng1eq5a49kqhctil830gn4.lock"

When I logged in, it set (and cached) a very code containing all of the admin user information:

"s:3485:\"USER|O:8:\"stdClass\":60:{s:2:\"id\";s:1:\"2\";s:4:\"auth\";s:6:\"manual\";s:9:\"confirmed\";s:1:\"1\";s:12:\"policyagreed\";s:1:\"0\";s:7:\"deleted\";s:1:\"0\";s:9:\"suspended\";s:1:\"0\";s:10:\"mnethostid\";s:1:\"1\";s:8:\"username\";s:11:\"bm_admin\";s:8:\"idnumber\";s:0:\"\";s:9:\"firstname\";s:11:\"bm_admin\";s:8:\"lastname\";s:5:\"Admin\";s:5:\"email\";s:21:\"admin@my-instance.com\";s:9:\"emailstop\";s:1:\"0\";s:3:\"icq\";s:0:\"\";s:5:\"skype\";s:0:\"\";s:5:\"yahoo\";s:0:\"\";s:3:\"aim\";s:0:\"\";s:3:\"msn\";s:0:
.
.
.
:16:\"contexthasrepos5\";a:3:{i:0;i:1531191348;i:1;s:1:\"2\";i:2;s:4:\"b:0;\";}}}s:21:\"load_navigation_admin\";i:1;}\";"
1531191351.701704 [0 127.0.0.1:38526] "DEL""bm_moodledvd4lh4j0cq98qi6g18aaikmv5.lock"

Finally, here are the settings in the config.php file (mostly default):

//   Redis session handler (requires redis server and redis extension):
$CFG->session_handler_class = '\core\session\redis';
$CFG->session_redis_host = '127.0.0.1';
$CFG->session_redis_port = 6379;  // Optional.
$CFG->session_redis_database = 0;  // Optional, default is db 0.
$CFG->session_redis_auth = ''; // Optional, default is don't set one.
$CFG->session_redis_prefix = 'bm_moodle'; // Optional, default is don't set one.
$CFG->session_redis_acquire_lock_timeout = 120;
$CFG->session_redis_lock_expire = 7200;

I hope this helps!

Re: Help with Redis cache

$
0
0
by Alan CF.  

Hi Tony,

Thanks for your detailed explanation!

I solved my problem a while ago. Turns out I hadn't configured the Redis store properly in Moodle.

Re: Error Message after upgrade - The operation timed out while waiting for a lock

$
0
0
by Stephan Häberle.  

After Deleting the cache/ directory the site works again.


Thank you for your help.


Error 403 displaying images when installing moodle onto cpanel witrh softalicious

$
0
0
by James Scott.  

Hello when i create a new moodle platform on cpanel with softalicous using a domain i am getting error 403 when i upload a logo to the moove theme, the image seems to upload but not display. does anyone know what the problem is?

Re: Error 403 displaying images when installing moodle onto cpanel witrh softalicious

$
0
0
by Howard Miller.  

I wouldn't use these one-click installers at all. 

Does it work properly with a core theme? For example Boost? If it does then the problem is with the optional theme. I've never heard of that one before. You'd be better contacting the developer. In this case, https://github.com/willianmano/moodle-theme_moove/issues

If it doesn't work at all... the problem is that we have no idea what this script is doing. Only get Moodle from moodle.org.   As this script is provided by your hosting company and it doesn't seem to work, you'd be better (to start with anyway) contacting their support people. 


Plugins Management

$
0
0
volgens Albert Ramsbottom.  

Is there any excepted system or way of managing plugins on multi-node Moodle application

There process seems a little outdated, insofar as we have to check that a particular plugin is compatible with a version of Moodle and then download the plugin from the moodle site and replace the current plugin with the new updated version

I normally just manage the server infrastructure and leave the plugins to developers


Cheers

Re: Plugins Management

$
0
0
volgens Howard Miller.  

I would suggest that you should do that anyway. I'm not a big fan of the web version of plugin management as it means you have to leave your Moodle site incredibly insecure. 

I assume you are also going to test prospective plugins before they get anywhere near the live server

What I'm coming round to is that this is easy if you use Git for deployment. Load your plugin on the test system (use the web interface if you like). Test it. Push the changes to your git repo. Then on the live system just run 'git pull' on each front end. Then run the update. Easy grote grijns

Re: Problems after upgrading to Moodle 3.4

$
0
0
volgens Karishma Tiwari.  

I've got another problem here since the upgrade - this is pertaining to educator site experience.


We enter a course and try to list the participants and get this error:

get_related_contexts_string() is removed, please use $context->get_parent_context_ids(true) instead


I checked the lib/accesslib.php is using the correct get_parent_context_ids(true):

$contexts = $context->get_parent_context_ids(true);


I realised that user/index.php was still calling the old get_related_context_string at line 365, so I changed it to:

$contextlist = get_parent_context_ids(true);


However I am still getting some error:

$contextlist = get_parent_context_ids(true);


Is the parameter 'true' correct or should be something else?

I tried turning the debugging on, this is what I get:

Exception - Call to undefined function get_parent_context_ids()

More information about this error

Debug info: 
Error code: generalexceptionmessage
Stack trace:

Exception - Call to undefined function get_parent_context_ids()

More information about this error

Debug info: 
Error code: generalexceptionmessage
Stack trace:
  • line 365 of /user/index.php: Error thrown

Viewing all 47362 articles
Browse latest View live


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