Are there any clients of ifasthosting?
I have a vPS and couldnt connect my SSH or reset my server about 72 hours and they didnt reply my ticket about 24 hours. also server's panels are down so i couldnt get backup.
Are there any person like me? My VPS has problems after they migrate thier node from Softlayer . I want to get my backup folder now but they arent replying me.
I have a vps at ifasthosting and it was having problems for the beginning now they completely disabled my account and vps without ANY NOTICE! This creates a big problem for me as I have many live sites on that vps and they are the cause of it!! I never got one email telling me anything or why or what was going on... I have sent them 2 emails in the last hour... What do you guys think I should do?
I obviously need to first figure out whats going on but what after that will I be able to get a back up of my files?
As i seem unable to get a decent reply to my ticket which is currently open with you (#210268) through your ticketing system. I am afraid i need to resort to posting here.
As i have asked in the ticket numerous times, can you please provide a reason as to why our server was offline? This ticket has been open since 29th April and so far we have only been told that you had "a couple of issues with you system".
I can't not change Keep Alive: on to off
My httpd.conf
User apache
Group apache
KeepAlive Off
MaxKeepAliveRequests 100
KeepAliveTimeout 3
MinSpareServers 5
MaxSpareServers 10
StartServers 5
MaxRequestsPerChild 0
ServerLimit 1024
MaxClients 250
ExtendedStatus On
ServerSignature Off
My php.php info:
Apache Version Apache
Apache API Version 20051115
Server Administrator webmaste@MYDOMAIN.com
Hostname:Port www.MYDOMAIN.com:0
User/Group apache(48)/48
Max Requests Per Child: 0 - Keep Alive: on - Max Per Connection: 100
Timeouts Connection: 60 - Keep-Alive: 1
Virtual Server Yes
Server Root /etc/httpd
Keep Alive still ON in my php page report.
I remember when digits.com was a big deal to me when I first got into web design in the 90's.
Anyways, [url] Do you think they are serious with that deal?
Do you think people still use it? The main site is PR8 but thats possibly due to the free counter-link backs and simplicity of the domain.
if anyone knows the status on vps4less.de? I have a VPS with them that was set to renew on 10/29, but I canceled way before then, or at least I thought it should have. I noticed a couple days after the renew date that it was still online so I sent another one, this time via WHMCS and request account cancellation link. So far, it's been 10 days (now 11/8) and I haven't heard from them, and my VPS is still online. I received an automated invoice overdue notice today, but I know that's just because they haven't closed my account yet.
View 1 Replies View RelatedI have a VPS with 256MB of guaranteed memory, and no burst/swap. Having little memory like this is quite common for a VPS and I want to know how to make the most of it while running websites. By far the biggest culprit for taking my memory is Apache and I'm not convinced that the default setup makes sense on a VPS.
I know there are other daemons out there that use considerably less memory, such as lighttpd, but enough people (myself included) are going to use Apache regardless (they might require some of the advanced features after all) so it is worth knowing how to get the most out of it.
Apache 2 has various mpm options, most notably prefork and worker. As I understand it the prefork method forks processes to handle requests ahead of time, and can fork more on demand if required, each process handles one request at a time. Worker uses threads, again created ahead of time and on demand, each thread handles one request at a time.
With the default configuration and prefork Apache spawned 6 processes each taking about 5MB, so there goes 50MB in total. With workers it wanted to create 50 threads, each with a 10MB stack, this instantly went over the memory limit so wouldn't start at all. Thankfully the stack can be adjusted using the ThreadStackSize setting so it can be made to run, but even after this what do you really have for your memory?
One problem with having one request per process/thread is that, again by default, Apache has a keep alive setting of 15 seconds. This means that once a request has been processed, the process/thread is then kept around for up to 15 seconds in case the client wants to do anything else. With prefork that is 5MB of memory being used, and even with threads with a reasonable 1MB stack size there is still a huge amount of memory wastage on a connection that might not even do anything. Meanwhile other visitors might be getting out-of-memory problems as Apache tries to spawn more handlers to meet demand.
I think it should be fairly obvious that the worker mpm is the best option here, if everything works fine with a 1MB stack then the thread overhead is considerably lower than the process overhead.
The new events mpm should relieve this problem as it uses an event queue to keep an eye on keep alive connections rather than a whole thread. Unfortunately this mpm is not considered stable yet, so in the mean time I am wondering if VPS users should just disable keep alive, or at least adjust it to just a few seconds.
The benefit of keep alive is that it reduces network traffic and CPU load as there is a small amount of overhead in setting up a new TCP connection. When servers had 400MHz chips and massive 256MB of ram this was a good trade off. But now VPS often have access to much more powerful processors, and the same 256MB isn't considered massive any more so a lot of applications are less frugal and less adept at running in this environment.
In the unlikely even that Apache had 200MB to play with, using 1MB threads means that the system can handle 200 idle connections before running out of resources and failing to handle new connections. With a keep alive of 15 seconds you can support 200 connections per 15 seconds. In light of the fact that many newer browsers will open 4 simultaneous connections (up from the previous 2) that is only 3.34 users per second. Drop the keep alive to 1 second and you can handle 50 users per second. These numbers are unrealistic because they assume the request handling itself takes no time at all, but a lot of requests can be handled in split seconds so maybe these numbers aren't so far fetched. If the request handling takes 250ms and you turn keep alive off you could handle 200 users per second.
I am thinking that it would be great to have a reverse proxy sat in front of Apache, one that used an event queue and thus had little memory overhead for maintaining incoming connections, but closed down its connection to Apache after each request. Unfortunately I do not know of one.
I'm running 4 websites on a quad core xeon x3220, with 2gig of ram. It's 4 proxy sites, they are running fine and dandy, except for the fact that even when their is little traffic going to them ram is still just as high. I'm running debian 4.0, and heres a copy of my footer Apache/2.2.3 (Debian) mod_python/3.2.10 Python/2.4.4 PHP/5.2.0-8+etch11 mod_perl/2.0.2 Perl/v5.8.8. I'v modified nothing since I got the server, I installed apache2, and awstats, that's it. I'v read up about optimizing and it hasn't helped much, and I thought maybe their is proxy specific tweaks I could make to the conf.
View 6 Replies View RelatedIt appears some elements of the ICPH webpage have keep-alive and some not.
I want to ask how to achieve all are loaded with keep-alive?
htaccess contains:
<ifModule mod_headers.c>
Header set Connection keep-alive
</ifModule>
recently I have an weird problem and I don't know what might be, I just suspect that this error appeared after we have enabled Keep Alive on apache
I have the same error with randomly Forbidden error. The most time I see it is on 2 websites that are build with Gallery 2 and very rarely on other website, on my end never happent on other websites but some people told me it did.
Bellow is a small part of cPanel's "Last 300 visits" it shows every request so you can see first request was a direct link , I have wrote the galery name .. and the others are aither requests to images either other files ....
How can i remove "Connection and keep-alive" from response headers ? I am using Apache http server to load balance two tomcat nodes
Apache Server- Apache/2.4.2
mod_jk - 1.2.27
Apache tomcat - Apache Tomcat/7.0.23
JDK - 1.6
I have also enabled SSL in the apache http server using mod_ssl. The load balancing works fine, but in all the response headers these connection attributes are added "Connection: keep-alive keep-alive: timeout=5"
Is there a way to remove these headers? I do not want these headers to be added in the response. I have also tried mod_header to unset these headers, but no use. HTTP/1.1 protocol is being used, so eventhough the connection is not present in the header, the connection would should be considered as persistent. Why is apache sending these attributes explicitly in each response. I just want to get rid of these attribute...
