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

Re: No forum post get send as email ....

$
0
0

volgens werner cyrmon.  

Happend afte upgrade to 3.4. Here is a mail log:

2018-01-10 07:27:18	Connection: opening to mail2.htlwrn.ac.at:587, timeout=300, options=array()
2018-01-10 07:27:18	Connection: opened
2018-01-10 07:27:23	SERVER -> CLIENT: 220 mail2.htlwrn.ac.at ESMTP Exim 4.80 Wed, 10 Jan 2018 08:27:25 +0100
2018-01-10 07:27:23	CLIENT -> SERVER: EHLO moodle4.htlwrn.ac.at
2018-01-10 07:27:23	SERVER -> CLIENT: 250-mail2.htlwrn.ac.at Hello moodle4.htlwrn.ac.at [195.202.147.120]
                   	                  250-SIZE 52428800
                   	                  250-8BITMIME
                   	                  250-PIPELINING
                   	                  250-STARTTLS
                   	                  250 HELP
2018-01-10 07:27:23	CLIENT -> SERVER: STARTTLS
2018-01-10 07:27:23	SERVER -> CLIENT: 220 TLS go ahead
2018-01-10 07:27:24	CLIENT -> SERVER: EHLO moodle4.htlwrn.ac.at
2018-01-10 07:27:24	SERVER -> CLIENT: 250-mail2.htlwrn.ac.at Hello moodle4.htlwrn.ac.at [195.202.147.120]
                   	                  250-SIZE 52428800
                   	                  250-8BITMIME
                   	                  250-PIPELINING
                   	                  250 HELP
2018-01-10 07:27:24	SMTP Error: Could not authenticate.
2018-01-10 07:27:24	CLIENT -> SERVER: QUIT
2018-01-10 07:27:24	SERVER -> CLIENT: 221 mail2.htlwrn.ac.at closing connection
2018-01-10 07:27:24	Connection: closed
2018-01-10 07:27:24	SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting
So it seems there is a problem with authentication, but I changed nothing freom the previous version where it worked and TLS and the user/pw combination I use to send emails works perfectly fine from my webmailserver ....

Re: Operation : Upgrade PHP

$
0
0

volgens John Pap.  

Million thanks to all of you, I fixed the issue.

It needed to set up a new fresh MAMP installation and to transfer some folders from old MAMP to new, such as data folder etc... 

dmlwriteexception on upgrade from 2.7 to 3.1

$
0
0

volgens EBC TEFLCourse.  

I get the error shown below when trying to upgrade from 2.7 to 3.1

All my plugins are up to date.

I converted my DB to innodb.

I copied the config file.

I did not convert to barracuda because I am on a shared host and they cannot change the DB just for me. The Moodle documentation says that this should not be a problem.

Does anyone know how to get around this problem?

Thanks, Jim




Debug info: Field 'id' doesn't have a default value
INSERT INTO mdl_config (name,value) VALUES(?,?)
[array (
0 => 'upgraderunning',
1 => 1515570886,
)]
Error code: dmlwriteexception
×Stack trace:
  • line 482 of /lib/dml/moodle_database.php: dml_write_exception thrown
  • line 1259 of /lib/dml/mysqli_native_moodle_database.php: call to moodle_database->query_end()
  • line 1305 of /lib/dml/mysqli_native_moodle_database.php: call to mysqli_native_moodle_database->insert_record_raw()
  • line 1379 of /lib/moodlelib.php: call to mysqli_native_moodle_database->insert_record()
  • line 1406 of /lib/upgradelib.php: call to set_config()
  • line 1482 of /lib/upgradelib.php: call to upgrade_started()
  • line 1671 of /lib/upgradelib.php: call to print_upgrade_part_start()
  • line 507 of /admin/index.php: call to upgrade_core()

Upgrade from 1.9.9 or perform a fresh install of current version

$
0
0

volgens Paul Hayes.  

Hello,

I hope I'm not asking something that has already been answered any number of times. If so, please forgive me.

My current installation is 1.9.9 and I'd like to upgrade to the current version (I realize that's quite a leap).

Can that even be done? Or should I just bite the bullet and do a clean install of the current version?

I think I know the answer (clean install of the current version) but thought I would ask.

Also, on a related topic, my current server is running PHP 5.1.6, though it will soon be upgraded.

The oldest version of PHP available on the new server is 5.6.32, with newer versions also available.

Moodle 1.9.9 is running acceptably well on the current server. Does anyone foresee any cause for concern about trying to run Moodle 1.9.9 with a newer version of PHP?

Thanks.

Re: No forum post get send as email ....

$
0
0

volgens Matteo Scaramuccia.  

Hi Werner,
what version of Moodle and PHP have you updated your instance from? Have you moved to a new server too?

BTW, to debug any mail issue please use https://moodle.org/plugins/local_mailtest : it would be easier for you in any of the next tries knipoog.

HTH,
Matteo

Re: No forum post get send as email ....

$
0
0

volgens werner cyrmon.  

php from 5.6 to 7.1, moodle from 3.3 to 3.4

and the output I posted is from exactly this tool (2nd post)

BTW: in the meantime I tried to reach the smtpserver via telnet, worked, then testet php and openssl/TLS with echo QUIT | openssl s_client -crlf -starttls smtp -connect mail2.htlwrn.ac.at:587 - worked like a charm

so it seems to be a moodle issue ..

Re: Upgrade from 1.9.9 or perform a fresh install of current version

$
0
0

volgens Howard Miller.  

It's technically possible to upgrade... there are a number of steps starting with upgrading to the last version of 1.9, then to 2.2, then to 2.7, then to 3.0 and finally to 3.4. You would need to do this on a copy and to take backups at each stage. You would also have problems with versions of PHP and MySQL to consider (read all the release notes carefully).

I really wouldn't bother - it's much less trouble starting with a clean install and recreating your courses. The end result will use new features, probably have years of clutter removed and is much more likely to be stable in the long run. 

When Moodle 1.9.19 was released PHP 5.6 was still two years in the future. You're lucky it works with 5.6. It will definitely not work with PHP 7. 

Re: How to setup moodle testing environment ?

$
0
0

volgens gurpreet singh.  

thanks to reply .. Howard I need steps to understand the plugin testing process . 

Just like a beginner . If anyone can provide the steps How to start with plugin development specially on plugin code changes  


Re: How to setup moodle testing environment ?

$
0
0

volgens Howard Miller.  

There's loads of documentation for plugin development...

https://docs.moodle.org/dev/Plugin_types

...plus the documentation I have already linked to. I don't think anybody is going to give you 'steps' when it is all documented. The documentation isn't perfect. If there are any parts you don't understand then you should ask (we will happily try to improve parts). However, you ARE going to have to read it. 

Re: No forum post get send as email ....

$
0
0

volgens Matteo Scaramuccia.  

Hi Werner,
OK, you've anticipated the tests (in case of a new server) about network connectivity and certificate validation - granted that you've followed https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting#testing-ssl-outside-php and got the certificate chain (CAs).

Did you change anything in the SMTP server configuration?
At first glance, in the server capabilities no authentication type has been replied to the last EHLO (expected e.g. LOGIN).

HTH,
Matteo

Re: No forum post get send as email ....

$
0
0

volgens werner cyrmon.  

Hi Matteo

I didnt change anything in the email part of the config. There is LOGIN selected, a smtp Username is configured an a password, both tested from the command line ....

Re: upgrade to PHP 7 - Moodle 2.2 client issue

$
0
0

volgens David Le Blanc.  

Thank-you Rick. All my other moodle instances are running moodle 3.2 or higher. This particular instance of moodle is version 2.2. I may need to update their moodle version using ssh if I cannot resolve the issue. I appreciate your suggestions and will try a few things first bedenkelijk

Redirection from apache2 server to nginx reverse proxy server w moodle 3.3

$
0
0

volgens Carolynn Bellavance.  

When I go to https://domain.com/moodle/ it gives me the index page as if I was not logged in but when I click on the links it goes to https://192.168.0.26/whatever_comes_next

If I go to https://domain.com/moodle/login/index.php it works, but the moment I login it goes back to the ip address,

This only happens with moodle, all the other servers are available so I do not know where else I can ask for help. I am now running in circle editing config after config trying to figure out which one is missing.... 

This as worked in the past as the site was available before a failure of all the servers. I had to reboot everything and remake the the nginx server. Everything was copy/pasta of the last config but it still does not work as it did before.


Moodle config.php :

<?php  // Moodle configuration file

unset($CFG);
global $CFG;
$CFG = new stdClass();

$CFG->dbtype    = 'mysqli';
$CFG->upgradekey = 'stuff';
$CFG->dblibrary = 'native';
$CFG->dbhost    = 'localhost';
$CFG->dbname    = 'moodle';
$CFG->dbuser    = 'user';
$CFG->dbpass    = 'password';
$CFG->prefix    = 'mdl_';
$CFG->dboptions = array (
  'dbpersist' => 0,
  'dbport' => '',
  'dbsocket' => '',
);

$CFG->wwwroot   = 'https://192.168.0.26';
$CFG->dirroot = '/var/www/moodle';
$CFG->dataroot  = '/var/moodledata';
$CFG->admin     = 'admin';

$CFG->directorypermissions = 02777;
require_once(dirname(__FILE__) . '/lib/setup.php');
$CFG->reverseproxy = true;
//$CFG->sslproxy = true;


Nginx conf :

server {
        listen 80;
        server_name domain.com;
        return 301 https://$host$request_uri;
}

server {
       listen 443 ssl http2;
        server_name domain.com;

        root   /var/www/domain;
        index index.php index.html index.htm;

        ssl on;
        ssl_certificate                 /etc/ssl/certs/www.domain.com.crt;
        ssl_certificate_key             /etc/ssl/private/www.domain.com.key;
        ssl_session_cache               builtin:1000    shared:SSL:10m;
        ssl_protocols                   TLSv1 TLSv1.1 TLSv1.2;
        ssl_ciphers                     HIGH:!aNULL:!eNULL:!EXPORT:!CAMELLIA:!DES:!MD5:!PSK:!RC4;>
        ssl_prefer_server_ciphers       on;

        access_log      /var/log/nginx/domain.access.log;
        error_log       /var/log/nginx/domain.error.log;

        error_page 404 /custom_404.html;
        location = /custom_404.html {
                root /var/www/domain/;
                internal;
        }

        error_page 500 502 503 504 /custom_50x.html;
        location = /custom_50x.html {
                root /var/www/domain/;
                internal;
        }

        location /.well-known/acme-challenge/ {
                alias /var/www/domain/;
                try_files $uri =404;
        }

        location / {
                try_files $uri $uri/ =404;
        }

        location ~ /\. {
                deny all;
        }

        location /moodle/ {
                proxy_pass              https://192.168.0.26/;
                proxy_set_header        X-Real-IP               $remote_addr;
                proxy_set_header        X-Forwarded-For         $proxy_add_x_forwarded_for;
                proxy_set_header        X-Forwarded-Proto       $scheme;
                proxy_read_timeout      90;
                }


Moodle log file : 

==> /var/log/apache2/access.log <==

192.168.1.201 - - [10/Jan/2018:10:07:25 -0500] "GET / HTTP/1.0" 200 7583 "-""Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36"

192.168.0.160 - - [10/Jan/2018:10:07:25 -0500] "GET /theme/yui_combo.php?rollup/3.17.2/yui-moodlesimple-min.css HTTP/1.1" 200 1758 "https://domain.com/moodle/""Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36"

192.168.0.160 - - [10/Jan/2018:10:07:25 -0500] "GET /theme/styles.php/boost/1499973071/all HTTP/1.1" 200 110212 "https://domain.com/moodle/""Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36"

192.168.0.160 - - [10/Jan/2018:10:07:25 -0500] "GET /theme/styles.php/boost/blocks/configurable_reports/js/codemirror/lib/codemirror.css HTTP/1.1" 404 257 "https://domain.com/moodle/""Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36"

192.168..0.160 - - [10/Jan/2018:10:07:25 -0500] "GET /theme/styles.php/boost/blocks/configurable_reports/js/datatables/media/css/jquery.dataTables.css HTTP/1.1" 404 257 "https://domain.com/moodle/""Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36"

192.168.0.160 - - [10/Jan/2018:10:07:25 -0500] "GET /theme/styles.php/boost/blocks/configurable_reports/js/codemirror/addon/display/fullscreen.css HTTP/1.1" 404 409 "https://domain.com/moodle/""Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36"

192.168.0.160 - - [10/Jan/2018:10:07:25 -0500] "GET /moodle/theme/image.php/boost/core/1499973071/t/collapsed_empty HTTP/1.1" 404 765 "https://192.168.0.26/theme/styles.php/boost/1499973071/all""Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36"

192.168.0.160 - - [10/Jan/2018:10:07:25 -0500] "GET /moodle/theme/image.php/boost/core/1499973071/t/collapsed HTTP/1.1" 404 759 "https://192.168.0.26/theme/styles.php/boost/1499973071/all""Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36"

192.168.0.160 - - [10/Jan/2018:10:07:25 -0500] "GET /moodle/theme/image.php/boost/core/1499973071/i/course HTTP/1.1" 404 756 "https://192.168.0.26/theme/styles.php/boost/1499973071/all""Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36"

192.168.0.160 - - [10/Jan/2018:10:07:25 -0500] "GET /theme/yui_combo.php?m/1499973071/core/event/event-min.js&m/1499973071/filter_mathjaxloader/loader/loader-min.js HTTP/1.1" 200 1398 "https://domain.com/moodle/""Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36"

192.168.0.160 - - [10/Jan/2018:10:07:25 -0500] "GET /theme/yui_combo.php?m/1499973071/course/categoryexpander/categoryexpander-min.js HTTP/1.1" 200 2479 "https://domain.com/moodle/""Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36"

192.168.0.160 - - [10/Jan/2018:10:07:25 -0500] "GET /lib/requirejs.php/1499973071/core/first.js HTTP/1.1" 200 111696 "https://domain.com/moodle/""Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36"

192.168.0.160 - - [10/Jan/2018:10:07:25 -0500] "GET /lib/javascript.php/1499973071/lib/requirejs/jquery-private.js HTTP/1.1" 200 670 "https://domain.com/moodle/""Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36"

192.168.0.160 - - [10/Jan/2018:10:07:25 -0500] "GET /lib/javascript.php/1499973071/lib/jquery/jquery-3.1.0.min.js HTTP/1.1" 200 30756 "https://domain.com/moodle/""Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36"

192.168.0.160 - - [10/Jan/2018:10:07:25 -0500] "GET /theme/yui_combo.php?3.17.2/event-mousewheel/event-mousewheel-min.js&3.17.2/event-resize/event-resize-min.js&3.17.2/event-hover/event-hover-min.js&3.17.2/event-touch/event-touch-min.js&3.17.2/event-move/event-move-min.js&3.17.2/event-flick/event-flick-min.js&3.17.2/event-valuechange/event-valuechange-min.js&3.17.2/event-tap/event-tap-min.js HTTP/1.1" 200 5382 "https://domain.com/moodle/""Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36"


==> /var/log/apache2/error.log <==

[Wed Jan 10 10:07:25.570442 2018] [:error] [pid 27188] [client 192.168.0.160:39224] Default exception handler: Erreur de programmation d\xc3\xa9tect\xc3\xa9e. Ceci doit \xc3\xaatre corrig\xc3\xa9 par un programmeur\xc2\xa0: Invalid json in request: Syntax error Debug: \nError code: codingerror\n* line 42 of /lib/ajax/service.php: coding_exception thrown\n


==> /var/log/apache2/access.log <==

192.168.0.160 - - [10/Jan/2018:10:07:25 -0500] "OPTIONS /lib/ajax/service.php?sesskey=2mw4FF7tAe&info=core_fetch_notifications HTTP/1.1" 404 24237 "-""Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36"


Nginx log file : 

192.168.0.160 - - [10/Jan/2018:10:06:53 -0500] "GET /moodle/ HTTP/2.0" 200 7193 "-""Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36"



If I change $CFG->wwwroot to https://domain.com/moodle it gives me error :

ERR_TOO_MANY_REDIRECTS


Nginx log file : 

192.168.0.160 - - [10/Jan/2018:10:13:26 -0500] "GET /moodle/ HTTP/2.0" 303 636 "-""Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36"


Moodle log file : 
192.168.1.201 - - [10/Jan/2018:10:13:26 -0500] "GET / HTTP/1.0" 303 872 "-""Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36"

Re: Operation : Upgrade PHP

$
0
0

volgens Rick Jerz.  

Great!  Thanks for the update.  Now you can continue with your Moodle.

Re: upgrade to PHP 7 - Moodle 2.2 client issue

$
0
0

volgens Ken Task.  

Well, since my 'tree has been rattled' ... taking a stab.

The error says a file is missing ... ie, cannot be found.   Are all files there?

When attempting upgrade via command line mind describing how you plan to do that?   Not that I do not know, I do, and is my preferred method just in your server setup following 'normal' directions may need to be adjusted.

For the 2.2 instance using command line update/upgrade would have to use the lower PHP version.   The command line php environment then becomes a factor.

So what do you get in an ssh access to server and in the user space where the 2.2 version exist?

which php

or/and php -v as well as php -m

While command line updates and upgrades take apache out of the loop if the command line environment is not pointed to the lower version of php, the update/upgrade will fail at command line as well.

While it's nice to have the ability to run multple versions of PHP, right about now, might consider running only ONE ... IF not running other apps but Moodle.

Alternative to the issue ... means more work on your part, but doable ...

Make a full site backup of the 2.2.

Download the full site backups.

Spin up a Virtual box instance of your server OS, install the lower version of PHP, + whatever to setup an environment as close to server as possible.   Restore the site backup and get it running first - as is.   Will have to cheat with host file to use the same fully qualified domain name on local VB/other until site has been upgraded.

Use git to 'march' the 2.2 to a 3.x. All command line ... that process much quicker than FTP or any other method.

Once the site is marched.   Full site backup.    Change host file.  Upload the full site backup pieces to server (wiping out the site on the server).  Once setup test.

Yeah, I know too much work, but ... like  I said ... doable without messing anymore with a production environment.

'spirit of sharing', Ken




Re: upgrade to PHP 7 - Moodle 2.2 client issue

$
0
0

volgens Rick Jerz.  

Since you are acting as the moodle and server admin for these instructors, aren't you going crazy by not keeping everyone at the same version of moodle?  Don't you set the rules?  If it was me, I would do upgrades to all Moodles at the same time.  glimlach

Re: upgrade to PHP 7 - Moodle 2.2 client issue

$
0
0

by David Le Blanc.  

Thank you Ken. Weird thing happened; nothing was working last night but when I tried this morning, everything was working. I cannot account for what caused it to start working again. I wonder if it has something to do with the security certificates. In any case, I appreciate your help. I continue to use your instructions on how to update to newer moodle versions that you once posted several years ago, to this day. approve Very much appreciated.

Re: upgrade to PHP 7 - Moodle 2.2 client issue

$
0
0

by David Le Blanc.  

Yes, it does drive me a little nuts. The account is for a public, non-profit online program which I host free of charge. The teachers have been resisting upgrading due to some of the old plug-ins they have become accustomed to using. I need to assume some responsibility here, since when I upgraded the server, I wasn't thinking it would affect their moodle.

I will impress the need that they upgrade now. I know that being down these last few days will convince them. Thanks again for your help Rick. smile

Re: upgrade to PHP 7 - Moodle 2.2 client issue

$
0
0

by Ken Task.  

First, thanks for your thanks! ;)

Suddenly started working .... strange!  Probably not worth discovering why at this point as you are going to impress upon the teachers involved in the site the need to upgrade.  IF, however, there is any 'group' that should be accustomed to change (good or bad), it should be teachers!

'spirit of sharing', Ken



Re: Upgrade from 1.9.9 or perform a fresh install of current version

$
0
0

by Paul Hayes.  

Thanks for your quick and concise reply.

I agree completely with what you said about a clean install. That is definitely what I will do. And I'll make it a priority in the future to install all upgrades as they are released.

Also, thanks for the insight into staying with PHP 5.6 until I install the current version of Moodle.

Viewing all 47059 articles
Browse latest View live


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