Thank you, I just realized, that the changes should be only new files that were not in git previously. All the other changes, actually change files that are part of the moodle git. So that is already wrong. I will discuss what happened on the server and who put which files where and why.
Started seeing more fatal errors (see below) regarding memory exhausted after recently upgrading moodle and php. Currently using php memory_limit of 512mb which I thought was on the high end.
We are at a slow time of the year so I am was concerned this may become a larger issue in the fall when the load is 5-10x more. We also have a number of courses >1GB.
Our environment is windows2008/IIS7.5/php7.1 64bit and similar separate server with mysql, which is also used for sessions. We recently upgraded from php5.6->7.1 and moodle 3.1->3.3
The error logs mention session\manager.php and session\database.php so I thought it might be related to sessions, which I get the impression Moodle suggests using redis > disk > database .
Would anyone recommend switching sessions storage to File or just making the memory_limit larger first? Is there any potential downside of raising this memory limit value to 1G? Any downside to using File over Database for session storage?
Thanks
====fatal php errors======
PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in \cache\stores\static\lib.php on
PHP Fatal error:
Allowed memory size of 536870912 bytes exhausted (tried to allocate
20480 bytes) in \cache\stores\static\lib.php on line 261
PHP Fatal error:
Allowed memory size of 536870912 bytes exhausted (tried to allocate
40960 bytes) in \lib\classes\session\manager.php on line 530
PHP Fatal error:
Allowed memory size of 536870912 bytes exhausted (tried to allocate
28672 bytes) in \lib\classes\session\database.php on line
PHP Fatal error:
Allowed memory size of 536870912 bytes exhausted (tried to allocate
262144 bytes) in \m23\lib\classes\component.php on line 1040
Fatal error:
Allowed memory size of 536870912 bytes exhausted (tried to allocate
262144 bytes) in Unknown on line 0
PHP Fatal error:
Allowed memory size of 536870912 bytes exhausted (tried to allocate
20480 bytes) in \cache\stores\static\lib.php on line 261
PHP Fatal error:
Allowed memory size of 536870912 bytes exhausted (tried to allocate
40960 bytes) in \lib\classes\session\manager.php on line 530
PHP Fatal error:
Allowed memory size of 536870912 bytes exhausted (tried to allocate
28672 bytes) in \lib\classes\session\database.php on line
I definitely wouldn't recommend using the database for session storage.
I would encourage you to look into Redis, but failing that switch to file sessions.
Thanks for all the great info on wincache.
Since we are on moodle 3.3 and the caching plugin doesnt appear to be supported beyond v3.0 I wasnt planning on pursuing this.
I am looking into other caching options though. Just reviewed Redis for sessions but it appears that is not fully supported on windows although developers have made some workarounds, Windows not getting a lot of love these days ! Any recommendations for a moderately busy (400 simultaneously logged in) Windows environment?
Thanks for this information. It worked good on my website
Cheers, María
Sorry, I have no idea, but hopefully someone else does.
OK, I contacted support about my Putty issue and found that I have to load the key every time I use it...ok, now that I know that, no problem.
So I got that working again.
But I was so tired from beating my head against a wall over this for about 3 days straight of doing nothing but Moodle, that I've yet to get back to this.
I have one other thing I'm working on for something else that I need to get set up pronto so I can start taking orders on it...then I'm coming back to this Moodle issue, which I still haven't solved.
I did try to go back to my old install (I paid for another month at old host so I still have access, and pointed the nameservers back over there again) and for some reason THAT is broken now....no idea... 404 error there. I just gave up on that, I don't have time to troubleshoot something new. When I left it, it worked just fine and I've not touched it since.
Now I'm back to thinking I'll just do a fresh install of Moodle on the new host (instead of copying old Moodle install) and get that working first...and then copy the old moodledata folder and import the old database into the new? But I'm trying to figure out the best order to do this, if it's even possible... I haven't completely understood how this works... so if anyone can tell me if this is even possible, or if there's a way to make it possible, I'd love to hear it!
Since I'm not sure what's breaking my install, I'm really just trying things out to see what will work...
The following was sent from my IT person, and might be helpful to others:
We had problems updating to Moodle 3.5 using MySQL 8.0 because the word system is a reserved word. Had to make the following changes:
Hi Debbie,
TNX for sharing your issue and solution too: when working at MDL-60793 we believed people would jump to 3.5 via 3.3 or 3.4 - by updating first to the latest 3.3.x/3.4.y available and still working w/ MySQL 5.7 and then moving to MySQL 8 being then Moodle compatible with it -, but eventually we were wrong .
Could you give us more details on how you moved to MySQL 8.x running what version of Moodle before upgrading?
The more the better : I'm going to file an issue into the Tracker, including proposing a fix compatible with all the DB supported by Moodle.
HTH,
Matteo
I would normally say - and I think I have - that doing a fresh install is pointless because you're just going to overwrite it with your backed-up data. And that's true. However, given all the trouble you have been having, I would just go and try it. If it works, it's a win for you and you've also proved that Moodle actually runs on your system.
I'm feeling a bit guilty about the ssh thing. Although I still recommend getting to grips with the command line do remember that you can get just the same results with cPanel. If you feel more comfortable with cPanel then use that. Once you get your head around the command line you won't go back but I'm worried that I've just thrown another variable at you to confuse things.
You should really start a new thread - I don't think your problem is related at all.
However - the answer to your *specific* question is simple. The optional theme you are using is not compatible with Moodle 3.5.
Thank you.
We definitely need to look at balancing I think. I think we have addressed disk speeds this time, fingers crossed at least.
We are moving to Microsoft SQL and away from MySQL so hopefully that will be an area we gain speed on, at least we have more in house expertise with that to fine tune it, so I'm optomistic.
I think at this point I shall knock the wincache on the head and just keep my eye on developments for the future.
Heather
hi ... maybe more explanation
that means:
if you have an auto increment field, like user is you will get on insert on master1:
1,3,5,7
and if you switch to master2:
2,4,6,8
some applications have problems, when the increment field is not a following number.
like select 3 rows from the table.
hope, someone can help me,
thanks,
ronny
Hi Ronny,
you don't need to bother about how auto increment fields are managed in the database server: when Moodle will create new entities, they will be properly referenced without the need to know base offset and increment step.
HTH,
Matteo
Tinkered with master-slave before but didn't run any site that I thought would justify the time spent. Having said that, did a little digging (revisiting) and discovered (am not a certified DB admin):
Master-master setups might be old technology now. There is now 'Group Replication' which might address the issue you've raised.
Master-master
https://www.digitalocean.com/community/tutorials/how-to-set-up-mysql-master-master-replication
note what it says on that page ... link to new method ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication.html
above is version 8 of MySQL
https://dev.mysql.com/doc/refman/5.7/en/group-replication.html
Think others would be interested in how you get along with this, so please share back your discoveries! ;)
'spirit of sharing', Ken
Paul, just OpCache would work fine on its own as it's recommended by moodle developers as well, rest depends on your own server configuration, if you have SSD drives then raw PHP 7 would even suffice. if you have combination of drives (mechanical and SSD), then prefer keeping temp files directory on SSD drives.
Hello, everyone!!
Please help me out with this:
2018-07-06 11:30:11 Connection: opening to webmail.mdkgcollege.edu.in:25, timeout=300, options=array() 2018-07-06 11:30:12 Connection: opened 2018-07-06 11:30:12 SERVER -> CLIENT: 220-srv10.iiwhosting.com ESMTP Exim 4.91 #1 Fri, 06 Jul 2018 17:00:12 +0530 220-We do not authorize the use of this system to transport unsolicited, 220 and/or bulk e-mail. 2018-07-06 11:30:12 CLIENT -> SERVER: EHLO moodle.mdkgcollege.edu.in 2018-07-06 11:30:12 SERVER -> CLIENT: 250-srv10.iiwhosting.com Hello moodle.mdkgcollege.edu.in [45.127.102.163] 250-SIZE 52428800 250-8BITMIME 250-PIPELINING 250-AUTH PLAIN LOGIN 250-STARTTLS 250 HELP 2018-07-06 11:30:12 CLIENT -> SERVER: AUTH LOGIN 2018-07-06 11:30:12 SERVER -> CLIENT: 334 VXNlcm5hbWU6 2018-07-06 11:30:12 CLIENT -> SERVER: bW9vZGxlQG1ka2djb2xsZWdlLmVkdS5pbg== 2018-07-06 11:30:12 SERVER -> CLIENT: 334 UGFzc3dvcmQ6 2018-07-06 11:30:12 CLIENT -> SERVER: TWRrZ0FkbWluQDIwMTc= 2018-07-06 11:30:14 SERVER -> CLIENT: 535 Incorrect authentication data 2018-07-06 11:30:14 SMTP ERROR: Password command failed: 535 Incorrect authentication data 2018-07-06 11:30:14 SMTP Error: Could not authenticate. 2018-07-06 11:30:14 CLIENT -> SERVER: QUIT 2018-07-06 11:30:14 SERVER -> CLIENT: 221 srv10.iiwhosting.com closing connection 2018-07-06 11:30:14 Connection: closed 2018-07-06 11:30:14 SMTP connect()I've tried changing the port, smtp auth type, smtp security but nothing seems to work. the attachments are screenshots of the outgoing mail settings page.
my moodle site has SSL and so does the mail server but when I change the port to 465 the server simply refuses connection. The web hosting service providers say this problem is beyond their scope and have declined to offer any help/assistance.
my moodle site's version is 3.3.1
Hello,
First, pardon my ignorance. I am a high school math and science teacher who got sick and tired of grading thousands of pages of papers and waiting for my rural, small school district to get access to a Moodle server so I built one myself with our IT person, who is also very green on all of this.
I have been running this version of Moodle 3.1 (Build 20160623) very well for two years and am looking to upgrade during the summer to keep on top of things. My website is:
http://www.boycevillemoodle.com/moodle
I have already checked and got the OK for everything in the Server > Environment window. Everything is OK.
I have download the files for the Moodle 3.3 build (which works with my PHP 5.6...another story, I can't get any PHP 7 versions to work) and dumped them into a new folder called Moodle (I kept the old Moodle 3.1 build and just renamed it Moodle_OLD). I can go through the start to installation, but I get a 500 Internal Server Error on the page immediately after I put in my username/password/etc. for my MySQLdatabase, which works fine with Moodle 3.1 In the meantime I have switched back to Moodle 3.1 and I have tried dozens of ideas, with no luck.
Ideally I want to move to Moodle 3.5 but I can't get PHP 7 working at all with any version of Moodle.
I have a Windows Server 2008 r2 with IIS 7.5
MySQL Version 5.7
Any help would be greatly appreciated.
Thanks.
Andy Hamm
Boyceville Community School District
Boyceville, WI
ok will do, thx!