I have an apache server with 2 sites on it. When I load the IP of the server, it loads up one site, but I'd like it to load the other. I am not running cpanel or plesk, just a basic redhat box with apache and virtual servers.
I can't seem to recall how I can control what configuration to change in order to change where the IP points to when I access it.
Can you help?
There has been a lot of talk about SSL creating excess CPU/memory load on websites. What I want to do is test this on my VPS/my brothers dedicated server. Will I be missing something important if I use apache JMeter and skipfish to create http/https server loads while monitoring/logging with htop?
Hi,
I just got new server from iweb with following configuration
Dual Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz (24 cpus)
16GB RAM
2x SAS2 15K RPM 300GB on RAID1
I think this server can handle 3000+ concurrent online visitors at a time. But dont know what went wrong.
I'm part way through setting up a Railo server, running alongside Apache on a Ubuntu Rackpspace cloud server.
I've got Apache working fine, it will server PHP pages, I've got subdomains set up as well, that's all fine.
I have a basic CentOS server running Apache that I use for website development and testing.
Whenever I make changes to a file, like a 'javascript' file, and then reload my webpage, usually the server takes about 15+ seconds to load the page, even though it should load immediately (it's on a very small local network).
Looking at Chrome dev tools, I can see that it's the recently changed file that
We have WebLogic installed on two separate RHEL 5.6 servers. An Apache web server instance will be installed on each of those servers which will be configured to listen on 80 and 443 and redirect any requests from 80 to 443. SSL will terminate at the Apache web server and traffic between the Apache web server and the WebLogic servers will not need to be encrypted.
This has happened twice now and it's a little bit concerning to me. I have a Fedora 12 server with 5GB of RAM that I use to host a few small web sites of mine. As I mentioned, this happened once before. I tried to load one of my web sites today and it took FOREVER (as in the 10s of minutes) to load. I SSHed into the box and found the load average around 100 (dual core machine).
I have a question. Over time, should an apache process's memory consumption grow? I am wondering if this is normal apache behavior or we may be causing this somehow in code?
Basically, we have a simple LAMP stack running Drupal. On an apache restart the processes fire up @ 120MB and eventually all the processes climb to 500-1GB of memory(resident aka physical-non-swap).
Is there a lighter alternative (runs in shell, in one process, can be started and stopped easily by the user) to Apache that supports .htaccess files? If not, how could Apache be run in a "lighter" way?
In fact, I'm looking to setup a development environment to mimic an Apache server, so I can then push my code on the production server and get the same behavior.