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

Unable to access the files after upgrade from 2.8 to 3.2

$
0
0

by Mahmood Naderan.  

We have successfully updated 2.8 to 3.2 with the following steps:

1- We preserved the old site /var/www/html/courses

2- Created a new folder /var/www/html/courses_3.2

3- In the installation wizard, I used the old mysql username and prefixs and also we used the previous moodle data folder /var/www/moodle


The site works fine, and we can see the courses we setup earlier with 2.8. However, in a course when we want to access the files (slides for example), it says


Cannot read file. Either the file does not exist or there is a permission problem.



Please see


mahmood@ce:~$ ls -l /var/www/
drwxrwxrwx 110 www-data root      4096 Dec 22  2014 moodledata


mahmood@ce:~$ ls -l /var/www/html/
drwxrwxrwx 46 root     root     4096 Feb 24  2016 courses
drwxrwxrwx 49 root     root     4096 Mar 13 10:12 courses_3.2


Re: Unable to access the files after upgrade from 2.8 to 3.2

$
0
0

by Howard Miller.  

"the installation wizard"sad

You shouldn't have done that. You're not installing anything. I'm not sure what install has done to your file area but it probably isn't a good thing.

All you needed to do was to replace the 2.8 Moodle code with the 3.2 and copy across the old config.php file. 

I hope you have a backup. 

Re: Database connection failed - Moodle 3.2.1

$
0
0

by Joao Beca.  

Hello Rick, The service provider replied me that they can't reboot the server because it's used by many others clients.

I don't know what can I do for now.

sad

Re: Unable to access the files after upgrade from 2.8 to 3.2

$
0
0

by Emma Richardson.  

I think they mean that they did not copy over the config.php file so when moodle was opened up, it acted like it was a new installation.

My guess is that your site address changed and you did not run the replace tool to update the database with the new url.  You can find this at yoursite.com/admin/tool/replace/index.php

BTW, just saving the old moodle code folder did not "save a copy" of your site - when you upgraded, you upgraded the database and if you did not backup the database first, there is no reversal at this point.

Re: Database connection failed - Moodle 3.2.1

$
0
0

by Emma Richardson.  

You are using the address for the web interface to the database, not the actual database server.  You should be able to find the correct address from your host.  If not in your control panel somewhere, ask them.

Re: Unable to access the files after upgrade from 2.8 to 3.2

$
0
0

by Mahmood Naderan.  

We went through the installation wizard and used the old database user name and moodle data folder. But as I said, the old website is still available (however it uses php5 and is not compatible with php7).

mahmood@ce:~$ ls -l /var/www/html/
drwxrwxrwx 46 root     root     4096 Feb 24  2016 courses
drwxrwxrwx 49 root     root     4096 Mar 13 10:12 courses_3.2


What should I do now? which folder is the old one (/var/www/html/courses/) contains the slides and other files one upon on time uploaded on the old website?



P.S: What is that replace tool?

Re: Unable to access the files after upgrade from 2.8 to 3.2

$
0
0

by Mahmood Naderan.  

Excuse me, I disabled php7 and enabled php5 in order to access the old website and its replace tool. http://oursite/courses/admin/tool/replace/index.php


But I get

Error reading from database


It seems that the new site changed the mysql in its form and now the old website is not able to read that. Any idea?

Re: Unable to access the files after upgrade from 2.8 to 3.2

$
0
0

by Emma Richardson.  

Yes, as I mentioned, the database is now converted to the new site - if you do not have a backup of the database, you have to get new site running now.

Did you get the location of the database correct?  Did the installation wizard complete?

Try this - in the NEW site, rename config.php to confignew.php - then copy over the config.php from the old site to the new site.  Open it up and just change the location for the moodle code folder, nothing else.

Then see if you can reach the database.


Re: Installing Moodle 3.2.2

$
0
0

by Vivek SM.  

not able to create tracker it shows 

Dear Moodler, before creating a new issue you need to demonstrate that you have searched among the existing issues to see if it's already been filed. Please find a similar issue from among the open issues and either start watching it or vote for it.

Re: Installing Moodle 3.2.2

Upgraded to PHP 7 - existing Moodle site down!

$
0
0

by Daniel Williams.  

I am in the process of upgrading to a later version of Moodle (I have been using Moodle 2.8 with PHP 5). I removed PHP 5 and added PHP 7. I re-enabled the necessary extensions (php_intl, php_pgsql, and php_opcache), restarted IIS, and now my old Moodle site is unreachable: 500 - Internal Server Error. Please assist!

Re: Upgraded to PHP 7 - existing Moodle site down!

Re: Upgraded to PHP 7 - existing Moodle site down!

$
0
0

by Daniel Williams.  

Thank you. So I will revert back to PHP 5 and try to shock Moodle back to life.

I saw a link earlier on running multiple versions of PHP. I thought, "Who would do that?" smile Apparently I will be doing that. We want to get the latest version - a sandbox to start building a new training site while maintaining the old one until we have time to move stuff over.

I could probably run the latest Moodle on PHP 5 (5.6.5), but I'm wondering if PHP 7 offers a better overall experience (better performance over PHP 5).

Re: Upgraded to PHP 7 - existing Moodle site down!

$
0
0

by Howard Miller.  

Rumour has it that - all else being equal - PHP7 gives a noticeable performance boost. 

Consider that any optional plugins you have installed are likely to be an unknown quantity with PHP7. The conservative choice would be 5.6.

Re: Upgraded to PHP 7 - existing Moodle site down!

$
0
0

by Daniel Williams.  

Great tip, Howard. I'll consider that.


I have the old PHP 5.5 files back in their home and re-copied over the extensions from the Microsoft Driver for SQL. I enabled pdo_sqlsrv_54.nts and sqlsrv_54_nts.

Then I restarted IIS and now I'm troubleshooting this lovely error...


Error: database driver problem detected

The site administrator should verify server configuration

Microsoft Drivers for SQL Server for PHP are not installed or not configured properly.


Re: Upgraded to PHP 7 - existing Moodle site down!

$
0
0

by Howard Miller.  

I've zero experience of IIS and SQLServer but I would start by creating a 'phpinfo()' test file and see what is installed/configured in your PHP. 

Re: Upgraded to PHP 7 - existing Moodle site down!

$
0
0

by Daniel Williams.  

Do you use Apache or Nginx?


And although these extensions worked before, I found and grabbed the drivers for PHP 5.5. That led to a different error:


Error: Database connection failed

It is possible that the database is overloaded or otherwise not running properly.

The site administrator should also check that the database details have been correctly specified in config.php


Ironically, Howard, I found you in another post about that topic. smile

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

I didn't change the config file though. So that's what I'm troubleshooting now.

Re: Upgraded to PHP 7 - existing Moodle site down!

$
0
0

by Howard Miller.  

I'm an Apache user - although I've tried Nginx

On the face of it, it now sounds like the driver is in place but authentication/permission isn't. 

And yes, I get around a bit in these forums smile

Re: 3.2.2 upgrade

$
0
0

by Rick Jerz.  

Ken, interesting.

First, no, I have not created a tracker item because it hasn't been bothersome enough to me.

Second, you might be on to something with a "tour" bug.  I do not ever recall seeing these popups with pre-3.2 versions of Moodle.  I am running the MORE theme, and as far as I know, I am not allowing tours to be used (because it is not within MORE).  However, this is not to say that there is some code running in the background that is trying to run tours.

Ken, are you running BOOST or a different theme.  I wonder if when running BOOST, if one ever gets these error messages?  I am not exactly sure how we might test this, because I cannot force these undefined boxes to appear.  I guess what I might be able to do is to run BOOST on my experimental Moodle and see if I ever get these errors.  And to also run MORE on my experimental server to see if I get these.  You might be able to do the same, or you might have another way of testing your idea about this problem being "tour" related.

I am also not sure if my students are getting these errors on my production Moodle (which is still using MORE).  None of my students have reported any problems.  How about yours?

Your thoughts?

Re: 3.2.2 upgrade

$
0
0

by Lee Hensley.  

ok Update I have been running in maintenance mode with debugging set to developer and I got a very long list of errors all doing with get string identifiers and email. nothing else. Could this have to do with the new email system? I would post them but it is a really long list. Here is a single entry.

PHP Notice:  Invalid get_string() identifier: 'noreplyaddress' or component 'message_email'. Perhaps you are missing $string['noreplyaddress'] = ''; in /my/ moodle/site/moodle30/message/output/email/lang/en/message_email.php?<ul style="text-align: left" data-rel="backtrace"><li>line 349 of /lib/classes/string_manager_standard.php: call to debugging()</li><li>line 7078 of /lib/moodlelib.php: call to core_string_manager_standard->get_string()</li><li>line 34 of /message/output/email/settings.php: call to get_string()</li><li>line 68 of /lib/classes/plugininfo/message.php: call to include()</li><li>line 80 of /admin/settings/plugins.php: call to core\plugininfo\message->load_settings()</li><li>line 7703 of /lib/adminlib.php: call to require()</li><li>line 7805 of /lib/adminlib.php: call to admin_get_root()</li><li>line 42 of /admin/settings.php: call to admin_write_settings()</li></ul> in /my/moodle/site/moodle30/lib/weblib.php on line 3110

Viewing all 46868 articles
Browse latest View live


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