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

Re: Moodle Upgrading options - what do you think?

$
0
0

by Ken Task.  

moodledata is unique to each implementation of Moodle ... be it production or dev.

Git should deal only with code. (while you could setup a github and your moodledata could be included in a git clone I wouldn't - dynamic nature of cache/localcache/muc etc.   Think it would have potential to confuse your efforts to clone again and test upgrades.

While Emma is right ... one could copy moodledata to the dev implementation, think I'd setup an rsync script (production moodledata to dev moodledata) and have the rsync update (which means add new files but remove old files no longer on production in filedir on the dev moodledata).

Why?   Once having tested an upgrade on dev, then replicating actions/commands, etc. on production, dev sites have a tendency to languish.   Production server is used therefore database has grown, files uploaded to moodle have changed, students come and gone, couses added and removed.   So before doing the next major upgrade, I'd replicate the production server to dev site again.

Git will handle the update to code.   There is an experimental utility now in (3.2 and 3.3) for 'Database Migration'.   Have tried it and it did work.   That would have to create a new database ... let's call it moodledev2017 ... if you name it with a year then just by looking at the DB name one can tell when dev was last migrated and how current dev was when first created.    This then allows you to skip the conversion of the FQDN ... production.yoursite.net to dev.yoursite.net - thus being able to get a dev site setup much more quickly to test the upgrade.

Have a 'customer' that contacts me about once every 2 years - they are upgrading. They have a Quality Assurance mind set.   They spend much of their QA $'s just getting the QA servers up to par ... before they can begin on testing an upgrade because they insist on keeping the QA as it was rather than cloning what they have as production again before upgrading.   Database requirements now much larger than when dev was first setup.   And because they setup servers with different partitioning, work-arounds exist on production that don't exist on production .... like a partition for /var/mysql/ where the databases live.

Bottom line ... make the dev a clone ... no work-arounds need come into play on upgrading production.   The idea is to make your admin life easier ... as close to 'no-brainer' as possible.

My 2 'sense' of course ... nope, spelled it right! ;)

'spirit of sharing', Ken


$CFG->tempdir

$
0
0

by Rikard E.  

We recently upgraded from 2.8.5 to 3.1.6 and everything went fine.

We are running a Moodle cluster with several moodle nodes and we use sticky session.

We have configured all our moodle nodes to use a local tempdir and a local localcachedir. This was recommended before Moodle 3+.

Now the configuration file says $CFG->tempdir MUST be shared between all nodes.

Is that really necessary when we use sticky session? One logged in user stays on his node throughout his whole session.

I would like someone to explain why $CFG->tempdir MUST be shared between all nodes in our installation.

As far as I can see I must say that everything runs just fine with our current settings where tempdir is local on each node.


Re: trouble updating to 3.3.2

$
0
0

by Rick Jerz.  

I tend to have this same problem from time to time.  Here is what is going on, in my best judgement.

I use the following code to get the latest version:

wget http://downloads.sourceforge.net/project/moodle/Moodle/stable33/moodle-latest-33.tgz

For example, yesterday I was planning to start my upgrade (on my experimental moodle) and I issued this code.  However, just as what happened to you, I did not get the latest version.  For whatever reason, sometimes the latest copy of moodle, as shown on the moodle.org webpage (where Howard directed you) does not immediately make it into the sourceforge system.  It seems to eventually make it there, but can take a little while.

When I download moodle from souceforge and check the version.php information, and see that it is not the latest moodle, I simply download the latest moodle from moodle.org and FTP it to my server in order to continue with my upgrades.  The copy of the latest moodle on moodle.org is always accurate.

3.3.2 Installation Broken

$
0
0

by Jason Sypolt.  

After downloading and installing 3.3.2 via the zip archive at the /user/editadvanced.php?id=2 page where an initial user is set up, there seems to be something with with the HTML files as the theme is not working and JS is broken as well. It prevents creation of the admin user and I am unable to continue.

developer console errors

maintenance.html missing

$
0
0

by Verity Web Services.  

Whenever I try to put Moodle  3.3.2 in Maintenance Mode, non-logged in users get a 404 error message.

The error logs indicate that maintanance.html is missing:

2017/09/13 19:55:22 [error] 23151#23151: *3047 open() "/home/mysite/moodle/maintenance.html" failed (2: No such file or directory) while sending to client, client: 2601:3c4:201:658f:383d:352c:e7e2:1ae3, server: edu.mysite.xyz, request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "edu.mshealthcarealliance.org", referrer: "https://edu.mysite.xyz/"

That file does not exist in the moodle folder or sub-folders in any version I have had.

Any idea why this is happening and what I can do to resolve it?

Re: $CFG->tempdir

Re: Separate data directory(moodledata) to web address

$
0
0

volgens Arnel Jr. Rubiano.  

Thanks for your reply!

I'd already got the setup.

I setup a high availability server with 1 load balancer, 2 web server and 1 database and data server.I just got confuse on how to point the moodledata to the data server.

Re: How to install moodle in window pc

$
0
0

volgens Csaba Gloner.  

I have been using MAMP for testing Moodle sites locally for a while on my Windows machine. I had a good experience as I could easily switch between php versions, etc. so even though I was not very familiar with server settings, I could install several different versions.

But now I have a problem with the newest versions from 3.1, as during the installation there are several checks that prevent the installation. I have looked up the solutuions for them and I could solve some of them but could not do it for the following two:


Is there an easy solution as I do only application testing and

- I don't have enough experience to run php scripts, etc.

- As some testings are time sensitive, it would be good if I could just install the sites without any messing around the same way as I can still do with versions up to 3.0 .

I have installed the latest MAMP version as I assumed that the developrs of MAMP would solve this but no luck.

Has someone a good idea or is someone using a different software that works similar and can deal with the newest Moodle versions?

Thanks
Csaba


error configure moodle authentication via RADIUS

$
0
0

volgens tran van dao.  

i configure moodle 3.1 authentication via radius server (on winserver 2012)

i can't login user via radius, my error in image attach

Re: $CFG->tempdir

$
0
0

volgens Rikard E.  

Thank you Matteo!

I have now read your post and as far as I understand you should be safe with having tempdir locally on all nodes as long as you have a sticky session setup in your cluster.
I.e. your user session persist on the same node and therefore all requests goes to that node.

Upgrading from 3.0.3 to 3.3.2

$
0
0

volgens EaD EMARF.  

Hi, Folks,


Our version is 3.0.3 and we intend to upgrade Moodle to 3.3.2. Must we install all the versions between them or can we go straight to 3.3.2?


Thank you very much.

Luiz

Re: Error reading from database during install Moodle 2.9.2

$
0
0

volgens Andrew Normore.  

Confirmed working on 2.6, thank you. 

LDAP Authinticaiton Problem 3.3

$
0
0

volgens himel siraji.  

I am facing some Problem after upgrade my moodle site 3.2.2 to 3.3 also domain name changed. now my site LDAP not working,  LDAP enable and i already  configured it Properly but it not working.

Re: Upgrading from 3.0.3 to 3.3.2

$
0
0

volgens Ken Task.  

According to:

https://docs.moodle.org/33/en/Upgrading_FAQ

it says you can.

However, if at all possible, clone production to a test server and test the hyperjump upgrade there first.

Things to research: any addons/additional plugins?   Check to see if there is a compat version for 3.3.x.   Those include themes.   Database changes ... file formats and collations:

https://docs.moodle.org/33/en/MySQL_full_unicode_support

Make a full site backup ... that's code, DB dump, and moodledata *before* the attempt to upgrade.    Also know how to restore that full backup should, for some un-foreseen reason, the upgrade fails.

In your current version, check environment and update the component.   Then, in the drop down list, choose 3.3 to see what the check says - may as well check 3.4 and beyond as well.

'spirit of sharing', Ken


Re: Upgrading from 3.0.3 to 3.3.2

$
0
0

by EaD EMARF.  

Hi, Ken,


You answered very well. Thank you very much. I really appreciate.


Regards,

Luiz


Installing without SSH/command line

$
0
0

by Michael Coyne.  

We're currently running 2.6.7 and were looking to install a more recent version. On reading the instructions at https://docs.moodle.org/33/en/Installing_Moodle#Create_the_.28moodledata.29_data_directory, we contacted the ISP webmaster about running the commands - e.g. # find /path/to/moodle -type f -exec chmod 0644 {} \;

We received the following reply:

"As you know we do not allow SSH access to our Shared Hosting plans; in addition to this we will not running scripts for third party purposes on those systems.

While the article you linked suggests command line access, in reality you can accomplish virtually all required update process via the website itself and/or manually uploading updated files to the sever; you will need to consult the Moodle support forums and documentation to determine how to accomplish your overall upgrade goal."

Would anyone be able to point us in the right direction to a guide that might help us out? The hosting provider meets the technical requirements for Moodle 3.3 and we can't really afford a more comprehensive hosting package.

Re: Installing without SSH/command line

$
0
0

by Rick Jerz.  

Maybe so.  What hosted server tools might you have?  For example, do you have cPanel?  Do you know what I am talking about?  Do you have FTP access?

Re: Installing without SSH/command line

$
0
0

by Michael Coyne.  

Thanks for the reply Rick. It's not branded as cPanel but it looks very much like it. We've FTP access also.

Can't send emails

$
0
0

by James Steerpike.  

On my hosted site last semester, email just worked.  I then looked around for a VPS and  registered a new domain on a server. Now I have just found e-mails are not working. Email change requests give an error/moodle/cannotmailconfirm.

The Moodle version is 3.3 running on debian, installed manually. I switched the A host to my new site but the mx host has not been changed in the domain zone. Googling through the internet I think I need to install a mail server on my server. Options are Postfix or possibly exim. The mx must then be pointed to the new server.

Before I charge into this, am I heading in the right direction or is there a simpler solution?



Re: maintenance.html missing

$
0
0

by Howard Miller.  

There's no such file (correctly) in Moodle. 

The only reference I can think of to maintenance.html is that you can add it as a file in your 'moodledata' area as one option for setting maintenance mode. See - https://docs.moodle.org/33/en/Maintenance_mode.

My best guess is that something other than (core) Moodle is causing this but I'm not sure what.

Viewing all 47572 articles
Browse latest View live


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