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

Re: Migrated to new host & now no images showing

$
0
0
by Rick Jerz.  

I am thinking the same way, Howard.  A fresh install might be the way to go.  Once a brand new moodle is installed, plugins added to match the old install, and a course and a few students added to build some confidence that Moodle can indeed run on this new server, then the migration can be done.

The migration involves replacing your new moodledata folder contents with the old, and replacing the MySQL new data with the old.  (Tina, how "big" are your moodledata folder, when compressed or "zipped," and the size of your MySQL backup file?)


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

$
0
0
by Visvanath Ratnaweera.  

Hi

You can not avoid PHP 7 for ever. As you have already found out, PHP 7 is mandatory starting from Moodle 3.4. What was you problem with PHP 7. Did you discuss it in this forum? (I have no clue managing Windows servers, but there are others.)

Instead I saw that you had Trouble Installing Stack on Moodle 3.1 Windows Server 2008r2. Could you resolve it?

Study the Upgrading documentation carefully before you do anything.

Re: Migrated to new host & now no images showing

$
0
0
by Ken Task.  

Adding what might be two cents and thus adding to confusion ... not the intent ... however ...

ERR_SPDY_PROTOCOL_ERROR

That error is Google's PageSpeed ... which is great for static pages created
by some web page editor, but not good for dynamic web sites ... use DB ... and that's Moodle.

The domain has a WordPress at document root (probably public_html) of the site.

** In that directory, are there a bunch of folders/directories that begin with wp_?

** What plugins do you have installed in the WordPress?

** Any plugin that controls redirects?

Reason asked ... many links in the WP that show what is typically a directory
location ... like the following:

https://homeschoolrealm.com/book-of-the-week-i-wonder-whats-under-there/

This part of the URL:
/book-of-the-week-i-wonder-whats-under-there/
looks like a long directory name, doesn't it?  It's not.

Different than this:
https://sos.tcea.org/blog/index.php/2017/07/09/git-for-moodle-admins/

Note the WP blog on the second link goes to a blog directory.  WP rules apply
only to /blog/ and not / nor to /moodle35/ on that site.

In the OP's setup, WP is at the document root of the domain and OP is trying
a typical migration to /moodle/ which probably was performed exactly as described
and correctly as well.   But, WP setup/plugin is controlling images .. thus images
in Moodle are broken.

Then there is the hosting plan OP has with SiteGround.
https://www.siteground.com/shared-hosting-features.htm

** Do you have the GoGeek?

IF OP, eventually learns CLI and the value of Git for Moodle installs/updates/upgrades
he GoGeek is the only one that provides Git.

In the link to the plans/features I see this:
"We Allocate the Resources You Need"
What the heck does 'Geeky' mean?

In reading their FAQ's and searching for 'Moodle'
https://www.siteground.com/kb/detailed_moodle_requirements/
"SiteGround servers are fully optimized to meet all Moodle requirements and to provide the best hosting environment for it."

it claims to be one of the best
hosting sites for Moodle.
https://www.siteground.com/lms-hosting.htm

And the page points to the same 3 hosting plans.
Nothing special there.

How to install Moodle on my account?
https://www.siteground.com/kb/how_to_install_moodle_on_my_account/
Alternatively, you can install Moodle manually by following the steps from our tutorial here.
https://www.siteground.com/tutorials/
but one cannot find the tutorial for installing Moodle manually!!!

Think OP needs to check out a new offering ... they call it Hosting Plus

https://www.siteground.com/blog/hosting-plus-is-here/

Please respond to the questions (**) above.

'spirit of sharing', Ken


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

$
0
0
by Andy Hamm.  

Hello,

In terms of stack, I gave up and moved a different direction.  I am using WIRIS and, though it does cost, they have cut me a great discount and the tool is amazing!

I haven't discussed the PHP 7 issue in this forum, but it is coming up at the same time.  When I change to PHP 7.2 I can read the test.php file fine but the moodle site (regardless of version, but 3.1 for example) comes up with an immediate 500 Internal Server Error...I don't even get to the language screen I get to with the PHP 5.6.  Any ideas?

I have spent hours going over the upgrading documentation but I will do it again.  I have spent in upwards of 10-15 hours doing research and trying different solutions before I posted to the forum.

Thanks.

Andy

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

$
0
0
by Visvanath Ratnaweera.  

OK. Then you could start a new discussion on your problem of getting Moodle 3.5(?) to run with PHP 7. As an initial step I would install a new Moodle (not upgrade) on the same server in a different domain, example.com/moodle35 for example.

Also note that "500 Internal error" is not informative at all. It is just generic error from the web server for any number of reasons.

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

$
0
0
by Andy Hamm.  

OK, will do, it would be Moodle 3.1 that I have now running with PHP 7.  

I know the 500 internal error is not informative at all...is there any way I can find out more information about this error in the server?  Sorry for my ignorance...

Andy

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

$
0
0
by Andy Hamm.  

OK, I have some new information.

I was able to get PHP 7.1.19 working with my moodle site.  So that is no longer the problem.  Now the only problem seems to be the 500 internal error when trying to upgrade moodle to 3.5.

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

$
0
0
by Andy Hamm.  

OK, now it seems to be spontaneously working since I got PHP 7.1.19 installed.  Moodle 3.5 is currently upgrading the database.  For whatever reason my server didn't like PHP 7.2 but 7.1.19 is working fine now.

Thank you for your help!

Andy


Re: Migrated to new host & now no images showing

$
0
0
by Tina Smith.  

Moodledata compressed is 219kb

MySQL backup is 41.1 MB

Re: Migrated to new host & now no images showing

$
0
0
by Tina Smith.  

** In that directory, are there a bunch of folders/directories that begin with wp_?

Yes, HomeschoolRealm.com is a Wordpress install.  Moodle is installed in a subdirectory on HomeschoolRealm.com.


** What plugins do you have installed in the WordPress?  A bunch...

** Any plugin that controls redirects? Yes, I have "Redirection" by John Godley


The reason for the URL structure is that I have permalinks set to  "post name". (vs the options that use dates.)


** Do you have the GoGeek?

I do not. I have GrowBig





Re: Migrated to new host & now no images showing

$
0
0
by Ken Task.  

Now one follow up question and something to try.

Follow up: does the 'redirection' plugin have rules?  or a configuration screen that would allow you to 'exclude' a directory from it's control?

And something to try ...

I think this is now in every install ... in moodledata, there is an .htaccess file created by the install script.

It contains:

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

Are you sure the moodledata directory compressed is '219kb' ... that's really small for a moodledata directory from a site that's been used!

Example of some sandbox sites probably not used as much as a homeschool moodle:

65M    ./moodle35data

3.1G    ./moodle30data

86M     ./moodle33data

The largest directory in moodle??data is filedir.

If old site is still up or the server where it was hosted still accessible, re-compress the moodledata directory and see if it's not larger.

If you followed the directions from https://docs.moodle.org/35/en/Moodle_migration#Recommended_method that said to make a compressed file of only filedir of moodledata.   The other directories on a restore of the site would be rebuilt by moodle.

Now before you start to restore the site, you must manually create a 'moodledata' directory with the correct ownerships and permissions ... same ownerships/permissions of that you see on wp- files.  The zip/tar ball of filedir from old site should create a 'filedir' directory in moodledata.

Re-read the section of the above url entitled:

"Copy moodledata from the old server to the new server"

What was your original Moodles version?

In your moodledata directory, create a hidden .htaccess file with the above contents.

Then move moodledata to the same location as your 'moodle' code directory - which is also where you see all those wp- directories.

Edit the config.php file of the moodle site to reflect the new path to moodledata.

Also, the theme may not be compatible for upgrading.  So you can add a line to config.php of Moodle that sets the theme to be a stock theme from the Moodle code you have.   Look in moodlecode/theme/ and you'll see the names of the stock themes.

Example: you see a 'clean' and a 'more'... in config.php file add a line:

$CFG->theme='clean';

Yes, that will hard set theme ... we can deal with that later after getting the site accessible and you can see/log into it consistently ... with no errors.

Try to hit your site.

Do the images that didn't show before show now?

Also test security of the moodledata directory:

https://yoursite/moodledata/  should not list any directories.

https://yoursite/moodledata/filedir/ should not also.

'spirit of sharing', Ken


Re: Migrated to new host & now no images showing

$
0
0
by Tina Smith.  

Woah, a lot there. I totally appreciate you taking time out of your weekend to try to help me out!!

I am not fully understanding everything you wrote so I will address the things I do, and I'll go from there...

First of all you said something about maybe the theme might not be compatible for upgrading. Before I tried a second shot at migrating, I pointed nameservers back to old host and fully upgraded everything on old host. So everything was peachy. Actually I even picked a new theme. Hadn't even had a chance to customize it yet...figured I'd play with it once I finished migrating it. But it worked fine on the old host, with the updated version of Moodle before I tried migrating again.

Now, I am wondering if maybe I should try to figure out how to get back into that old install again...because maybe it would be easier...I tried to go back AGAIN and for some reason (I didn't do ANYTHING differently, that I can think of), I got a 404 message and cannot get back into the old install in the old host anymore. No idea why. If I could get inside, I'd just export the courses...there's not much there. It's mostly unused. But I don't want to have to recreate what I did create, of course. That was a LOT of hours of work to create!

I just don't have a whole lot to move really.  But I will try to recompress and move the moodledata again since you think that's too small. Certainly won't hurt to try.


I would like to also point out that it's not just broken images that is the issue I was having with the migration...the internal links seemed to be wonky as well...all the links to the site admin menus went nowhere when I was in my newly migrated Moodle. So it was pretty dang messed up. Not just images.


So many issues here and I don't know what I'm doing, so I'm just trying to figure out the best way to move forward.  I appreciate all the input y'all are giving me....it's very much helpful to try things and see what works. 

Ok, I'm going to go back and look at your post again and see if there's any questions I can answer.... will start a new post since this got long.


Thanks again! smile

Re: Migrated to new host & now no images showing

$
0
0
by Ken Task.  

Ok, sounds like no issue with theme.

Old server ... where is that hosted?   May not be able to get the site up and running by an internet fully qualified domain name, but the DB, the moodledata directory, and the moodle code are accessible via cPanel/Other and one could make a backup of those.

As far as wonky looking after you got it restored ... well, yes that will happen to anyone migrating from one domain to another server IF the URL has changed.

There is a tool in moodle admin called search and replace ... where one searches for old site URL and replaces with new site URL ... http or https.

That does fix images not found as moodle uses the wwwroot variable in the config.php file to build full URL's to *all* internal resources.

So you could have been really close to getting the site migrated and working ... but didn't know it.

Now if you can get a backup of moodledata, moodle code, and a DB dump off of the old site, I'll make a one time offer ... I'll setup access to another server where you can upload those backups - so I can inspect ... not only that, but I'll attempt an install on that other server to see what issues there might be with a site restore.

If interested ... PM me for more info.

'spirit of sharing', Ken


Problem after upgrading to Moodle 3.4+ or 3.5+

$
0
0
by Dejan Mikik.  

Hi,

I have Moodle 3.3.6 and I want to upgrade it to 3.4+ or 3.5

Before upgrade I check requirements and now I have PHP v.7

So I proceed to upgrade, (first I tried 3.4 and after that 3.5) I get Blank front page without any error messages.

I also try upgrade to v.3.5 but same problem.

Can you help be to do upgrade, what I need to do?


Thanks

Dejan

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

$
0
0
by Stephan Häberle.  

Hi,

I've upgraded Moodle from Version 3.3 to 3.5 and now I recieve the error message "The operation timed out while waiting for a lock." when accessing any site of moodle.

For the upgrade I've followed the instructions of this article: https://docs.moodle.org/35/en/Upgrading

Befor upgrading the site which causes Problems, I've upgraded an other, similar site. No problem showed up on the other site.
I've already restored the Server ro re-run the upgrade. But I recieve the error "The operation timed out while waiting for a lock." again and can't access moodle at all.

The only further error message I've found is when I try to access https://my.moodle.site/admin/settings.php. On this page I can see the error message "Required parameter 'section' is missing" and "The operation timed out while waiting for a lock".

Any idea how to solve this error? I currently can't access moodle at all.


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

$
0
0
by Howard Miller.  

How are your sessions set up?

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

$
0
0
by Howard Miller.  

What's in your web server's error log?

You may (should!) also enable Debugging. You will need to do this in your config.php file by copying (and uncommenting) the lines from Section 7 of config-dist.php

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

$
0
0
by Andrew O'Brien.  

Try setting your theme to Boost before doing the upgrade.

Re: Big Blue Button hosting

$
0
0
by Javier Tejera.  

Thanks for the info. If you don 't mind, I will pm you. 

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

$
0
0
by Stephan Häberle.  

I didn't adjust anything regarding the session handling. I'm using the default settings of moodle.

As I'm quite new to moodle, I don't know which information you need exactly. Can I deliver you any outputs from the Database or config files? Please let me know.

Thanks!

Viewing all 46829 articles
Browse latest View live