0.00 MB Transfered In 1368694 Responses. What Does This Mean

Mar 16, 2007

I got the following information in the logwatch report

Quote:

--------------------- httpd Begin ------------------------

0.00 MB transfered in 1368694 responses (1xx 1368686, 2xx 8, 3xx 0, 4xx 0, 5xx 0)
8 Content pages (0.00 MB),
1368686 Other (0.00 MB)

A total of 1 unidentified 'other' records logged
with response code(s)

---------------------- httpd End -------------------------

It didn't happen very often, but appears to be quite often recently. Is this a sign of being abused by some sort of attack to the server?

View 0 Replies


ADVERTISEMENT

Is There Anyway That Has Website Transfered To Another Hosting When Current One Down

Jun 17, 2009

both concerns with programming,hosting and domain as well.

Have we had any solution for a website with multi hosting? I mean how to prevent it from being down by transfering it to another host. I know that it is about A record. If my site down, i should immediately change A record point to another IP of a backup server. However, it still takes time.

View 8 Replies View Related

Apache :: 2.4.3 - Localhost Responses Very Slow

Aug 4, 2013

I've very slow response (from 1-2 seconds to tens of seconds) from http://localhost using Apache 2.4.3/Win32 service on Windows 8/32bit (6.2 build 9200). It doesn't depend on the browser used. Responses from all other sites are much faster.

Because it seemed to me to be a DNS issue, I tried to uncomment "127.0.0.1 localhost" and/or "::1 localhost" line in the hosts file, put "http://127.0.0.1" or "http://[::1]" instead of "http://localhost" into the browser, flushing dns by ipconfig /flushdns, stopping DNS Client by "net stop dnscache", disabling IPV6, etc. but nothing worked.

It seems that hosts file is ignored and "localhost" is passed to external DNS. Ping localhost yields to "Reply from ::1: time<1ms" response, ping 127.0.0.1 yields to expected "Reply from 127.0.0.1: bytes=32 time<1ms TTL=128" response.

Finally, "unplugging the network cable" is the only solution I've found: then the connection to localhost is much faster.

How to get instant response when connected?

View 6 Replies View Related

Apache :: 2.4.4 To Not Send Back Responses

Aug 11, 2014

I'm using Apache 2.4.4 as a part of WAMPSERVER 2.4 under Windows Server 2008 to host a business web application. I recently added a tool that involves users accessing the application from their mobile devices connected through our wifi network.

The issue occurs when a user is connected via our external address(x.x.x.x:8080). This issue does not occur if connected through our local address(192.168.x.x:8080).

First, the user makes a POST request to our server. The server handles the request and redirects the user to a GET version of the same page. Standard stuff.

However, if the user leaves the network while this process is occurring, the entire server will stop sending back responses. Localhost, x.x.x.x:8080, and 192.168.x.x:8080 all fail to receive responses until the Apache service is restarted.

If that isn't bizarre enough, my access.log continues to be filled with requests and my apache_error.log doesn't report any issues and even reports when the server is being restarted.

At first, I thought this might be a routing problem since it only occurs when connected though our external address and it isn't typical as far as I know for ALL Apache childs to become unresponsive. However, not being able to access the application through even localhost made me rethink that. So, I'm thinking it's a Windows or Apache issue, but that's as far as I've gotten.

This makes our application nearly unusable because it's a system for punching in and out of work, so it's likely people will be trying to punch out while leaving the building and network, causing this issue.

View 1 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved