Processor overloaded
Permalink
Hi All
We have installed concrete5 recently around 3 months ago and it was working smoothly until we encountered this problem of website going down. It started last week and I have checked with the server admin regarding the issue, apparently the processor was getting overloaded for some reason. We had to resit it every time the problem occurs.
I checked in the dashboard in maintenance section and found that there was one job (indexing) which was running for a long time. i have deleted that job, and things were normal again, i got the same problem today morning as well.
I can't seem to trace the cause of this problem, could anyone help me please ..
We have installed concrete5 recently around 3 months ago and it was working smoothly until we encountered this problem of website going down. It started last week and I have checked with the server admin regarding the issue, apparently the processor was getting overloaded for some reason. We had to resit it every time the problem occurs.
I checked in the dashboard in maintenance section and found that there was one job (indexing) which was running for a long time. i have deleted that job, and things were normal again, i got the same problem today morning as well.
I can't seem to trace the cause of this problem, could anyone help me please ..
Hi frz :)
yes, even after stopping the indexing job, the problem is occurring.
is there any configuration or parameter in concrete that i have to change, for example to handle more connections or more processes. Because the sever hosts two other websites and both are functioning really well .. so it cannot be global server configuration that we need to check for php , it must be local php configuration in concrete ..
yes, even after stopping the indexing job, the problem is occurring.
is there any configuration or parameter in concrete that i have to change, for example to handle more connections or more processes. Because the sever hosts two other websites and both are functioning really well .. so it cannot be global server configuration that we need to check for php , it must be local php configuration in concrete ..
If that keeps the error from coming up, that's great - but I'm kinda dubious. Could be any number of things that are consuming the CPU time on your server. Can you figure out if its php/apache or mysql that is eating the resources?