concrete5 - viewing query / ability
Permalink
Hi There,
I have a c5 setup which has been running without fail for 5 months. It averages 12,000 unique vistors over a month. This morning we sent out a mail shot and 600 people clicked through in the space of 5 minutes.
The website became unresponsive and it would appear that apache failed. I restarted apache and it started working again.
My question is what is c5's capability for users viewing the site at one time. I have built over 80 c5 websites and all he code appears ok with no heavy loading and all cached pages.
Any input appreciated.
I have a c5 setup which has been running without fail for 5 months. It averages 12,000 unique vistors over a month. This morning we sent out a mail shot and 600 people clicked through in the space of 5 minutes.
The website became unresponsive and it would appear that apache failed. I restarted apache and it started working again.
My question is what is c5's capability for users viewing the site at one time. I have built over 80 c5 websites and all he code appears ok with no heavy loading and all cached pages.
Any input appreciated.
Thanks for your response
Its linux: I have pulled the below from the server info tab in cpanel:
(Is there a way i can review the server logs in cpanel to see what may have caused this to stop working..? I can t see any report tabs i can view..?)
Processor Information
Total processors: 2
Processor #1
Vendor
GenuineIntel
Name
Intel(R) Xeon(R) CPU E5-2680 0 @ 2.70GHz
Speed
2700.001 MHz
Cache
20480 KB
Processor #2
Vendor
GenuineIntel
Name
Intel(R) Xeon(R) CPU E5-2680 0 @ 2.70GHz
Speed
2700.001 MHz
Cache
20480 KB
Memory Information
Memory: 3904288k/5242880k available (5325k kernel code, 1049092k absent, 289500k reserved, 7013k data, 1276k init)
Its linux: I have pulled the below from the server info tab in cpanel:
(Is there a way i can review the server logs in cpanel to see what may have caused this to stop working..? I can t see any report tabs i can view..?)
Processor Information
Total processors: 2
Processor #1
Vendor
GenuineIntel
Name
Intel(R) Xeon(R) CPU E5-2680 0 @ 2.70GHz
Speed
2700.001 MHz
Cache
20480 KB
Processor #2
Vendor
GenuineIntel
Name
Intel(R) Xeon(R) CPU E5-2680 0 @ 2.70GHz
Speed
2700.001 MHz
Cache
20480 KB
Memory Information
Memory: 3904288k/5242880k available (5325k kernel code, 1049092k absent, 289500k reserved, 7013k data, 1276k init)
Sorry, I should have been more clear - I was wondering more about whether it was running on a 'shared' server, or not? any idea?
Its a cloud based VPS... I believe we share resources with other sites but we have a private cloud for our account.
Is there any standard reportng in cpanel that will allow we to see what may have caused apache to stop..?
Is there any standard reportng in cpanel that will allow we to see what may have caused apache to stop..?
Go at them from ssh.
Apache General Error and Auditing logs
Exceptions thrown by httpd along with standard error output from CGI applications, normally the first place you look when http crashes or you get errors when visiting a website
Location: /usr/local/apache/logs/error_log
Apache Access Logs
Less important in this case but has all the processed requests, you might use this to try and pinpoint where people started getting errors on pages to further narrow down the exact time this happened if you don't know alread.
/usr/local/apache/logs/access_log
MySQL Logs
This path could vary a bit but most typically is somewhere under /var/lib/mysql/$(hostname).err or another common spot is /var/log/mysqld.log
Good luck troubleshooting!
Apache General Error and Auditing logs
Exceptions thrown by httpd along with standard error output from CGI applications, normally the first place you look when http crashes or you get errors when visiting a website
Location: /usr/local/apache/logs/error_log
Apache Access Logs
Less important in this case but has all the processed requests, you might use this to try and pinpoint where people started getting errors on pages to further narrow down the exact time this happened if you don't know alread.
/usr/local/apache/logs/access_log
MySQL Logs
This path could vary a bit but most typically is somewhere under /var/lib/mysql/$(hostname).err or another common spot is /var/log/mysqld.log
Good luck troubleshooting!
I run several sites that each receive several thousand hits a day with no problem on a variety of Dedicated and VPS setups. Basically, if you have a server with a high spec, a site powered by Concrete5 should be able to deal with that sort of traffic.
What sort of server setup do you have?