I am so frustrated

it's not any type of "solution" though. The problem is pretty much in the db as far as I can tell there just isn't the resources available or there are some queries that are killing the app. The problem is I haven't figured out how to see what queries are being run on the db when it tailspins or I would fix them and/or whatever indexing problems there might be. I have a headache already today LOL...
 
it's not any type of "solution" though. The problem is pretty much in the db as far as I can tell there just isn't the resources available or there are some queries that are killing the app. The problem is I haven't figured out how to see what queries are being run on the db when it tailspins or I would fix them and/or whatever indexing problems there might be. I have a headache already today LOL...
But DB queries should not make it return 500 or 404 errors either.

This is a production environment, we cannot run in full debug mode for all services, it just is not possible.
I am trying to help here, but there are some places that it isn't working right at all, and no real errors coming.
 
it was returning the 500 404 errors from IIS because of the way the error handling is in the moodle application. Basically the errors from http were not being passed back to the moodle app properly and moodle was redirecting into it's own error handling which was being chocked out by IIS which then returned it's own page not found error page.

as far as the debugging goes yeah I understand what you are saying. The behavior I see I believe the db is getting overloaded domino theory kind of thing...I just have no idea what to do I have spent so much time and grief on this issue at this point....every day I make changes and hope for the best and it just is not efficient enough...and I'm standing there with a bunch of middle school kids who think their computer is slow LOL
 
I just sent you what I think is the issue, wasn't realizing that many users there, and I think hitting the mysql per db login limit.
 
That's what I think too...because it's not processing fast enough then there are times too many connections are open and things grind to a stand still.
 
That's what I think too...because it's not processing fast enough then there are times too many connections are open and things grind to a stand still.
Maybe try it on linux? It processes a bit faster on unix than windows...
Could do it on a demo/test domain to see if it was any better.
 
yeah I was in the process of doing that but found that I need zip.so library and was told it's not available so I was stuck there...
 
Maybe try it on linux? It processes a bit faster on unix than windows...
Could do it on a demo/test domain to see if it was any better.

I'm attempting to set up a Moodle app as well, on Win17. Support, however, has informed me that PHP 5.3.2 (required for all v2.x Moodle apps) is not available on Linux servers, only on Windows. Please confirm that this is the case and advise (if known) if the issues reported in this thread have been resolved on Windows servers.
 
I could never get moodle to run on jodo servers and changed hosting providers because of it. The application got bogged down and there wasn't any way to tune it up on these servers. I was happy with Jodo for years but needed Moodle and I am very happy where I am at now too.
 
Yes, for a now php 5.3 is not available on Linux server and it is only available on one windows server which is in
cluster one . We have most of the user on same server , those are running moddle, due to availability of php 5.3.
 
Yes, for a now php 5.3 is not available on Linux server and it is only available on one windows server which is in
cluster one . We have most of the user on same server , those are running moddle, due to availability of php 5.3.

Thanks, Ashwani. I'll watch this thread and the forum in general for any announcements re: php 5.3 on Linux. Moodle really needs Chron jobs to work they way we need it to...
 
Back
Top