Why The Hell Is Mod_mem_cache..

Aug 6, 2007

NOT packaged with the freebsd port for lighttpd? Any clue?

Also, anyone ever get these errors after turning on mod_expire?

Code:
2007-08-06 11:51:33: (server.c.1149) NOTE: a request for /2007/80514-6713.wmv timed out after writing 37147 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2007-08-06 11:51:43: (server.c.1149) NOTE: a request for /2007/96373-6576.wmv timed out after writing 1470807 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2007-08-06 11:51:47: (server.c.1149) NOTE: a request for /uploads/76248f45a6.jpg timed out after writing 37139 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2007-08-06 11:51:51: (server.c.1149) NOTE: a request for /2007/80449-6083.wmv timed out after writing 37146 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2007-08-06 11:51:54: (server.c.1149) NOTE: a request for /2007/80449-6083.wmv timed out after writing 41242 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2007-08-06 11:51:56: (server.c.1149) NOTE: a request for /2007/22195-6305.wmv timed out after writing 37144 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2007-08-06 11:52:00: (server.c.1149) NOTE: a request for /2007/22195-6305.wmv timed out after writing 33048 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2007-08-06 11:52:05: (server.c.1149) NOTE: a request for /2007/23338-6071.mpg timed out after writing 101260 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2007-08-06 11:52:14: (server.c.1149) NOTE: a request for /2007/96373-6576.wmv timed out after writing 305448 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2007-08-06 11:52:17: (network_freebsd_sendfile.c.175) sendfile: Broken pipe 32
2007-08-06 11:52:17: (connections.c.587) connection closed: write failed on fd 13
2007-08-06 11:52:22: (server.c.1149) NOTE: a request for /2007/80514-6769.wmv timed out after writing 41242 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2007-08-06 11:52:22: (server.c.1149) NOTE: a request for /2007/118308-6944.mpeg timed out after writing 61685 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2007-08-06 11:52:27: (server.c.1149) NOTE: a request for /2007/80514-6707.wmv timed out after writing 37146 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
2007-08-06 11:52:31: (server.c.1149) NOTE: a request for /2007/12434-6925.wmv timed out after writing 33048 bytes. We waited 360 seconds. If this a problem increase server.max-write-idle
Increasing server.max-write-idle does nothing to resolve this.

View 1 Replies


ADVERTISEMENT

Mod_mem_cache V1.2 For Lighttpd Released

Jul 12, 2007

I;m running lighttpd-1.4.15 and I have installed many mods which already comes packed with default install

but I want to install this particular mod and I cant seem to find any way to use this .patch file.

how this is done, only if you done it in the best and worked.

More details on this mod.
[url]

View 0 Replies View Related

Rackspace Hell The Saga Continues

Oct 20, 2008

Rackspace Ticket Number: 080904-05942:

On 2008-09-03 my dedicated server which is hosted by rackspace suddenly went down. It was down for OVER 2 days which was a complete nightmare! Rackspace seemed not to even care. My partner was on the phone with rackspace constantly during that time period and they didn't know what the issue was. Rackspace was saying it was third party "software" issue and not a hardware problem.
My partner who is an experienced programmer, knew it wasn't sofware related so he decided to move the website to a different hosting company calpop. He moved the website to the other hosting company WITHOUT modifying any of the code and the website worked perfectly fine.

Since moving to calpop there have been no downtimes or any other errors like we expeirenced at Rackspace. To make matters worse Rackspace is trying to continue to charge us for the server because we have a 2 year contract with them even though the server was not working properly. I told them I no longer want them as a host and they won't dissolve the contract. To move back to Rackspace would be disaster...we can't trust them again since they already let us down so many times.
My company feels Rackspace violated the TOS by not providing us with a working server and causing 2 days of down time. What do you think?

View 13 Replies View Related

Intel Core2 "buggy As Hell"

Jul 1, 2007

WOW interesting interview with kerneltrap check it out!

I was just starting to move to some of these core2 based models.

[url]

(note its not an AMD piece either as he says AMD is getting worse in this regard as well)

View 5 Replies View Related







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