Re[2]: [EMAIL PROTECTED] Corrupted source files

Hi Joshua, You're right. EnableSendfile Off makes the trick. :-/ Now what could it be with my FreeBSD installation to cause such a mess? Until now I didn't notice any problems with any other applications. I have FreeBSD 6.0 here. Not sure if 6.1 would make a difference... You've got me

Re[3]: [EMAIL PROTECTED] Corrupted source files

Hi Victor, I'm in the process of upgrading to 6.1 right now. Will see if it changes anything. If not I guess I'll post it in freebsd forum and we'll see if we can dig something out. Thanks again for your help! I don't know what it was, but upgrade to 6.1 fixed it. Running no problems

Re: [EMAIL PROTECTED] Corrupted source files

I'm new to Apache. I've just installed Apache 2.2.3 on FreeBSD 6.0. Configured it and got it running. But I'm having something that looks like quite a weird problem. I've done my research on Google, read FAQ and docs but couldn't find anything even closely resembling my situation.

Re: [EMAIL PROTECTED] Corrupted source files

Hi Joshua, And you are sure that the file on the server itself becomes corrupted? Yes, absolutely. That's the first thing I've checked. It is the file on server. Try running strace apachectl -X and see if you can track down where stuff is getting written to disk. In the default config, the

Re: [EMAIL PROTECTED] Corrupted source files

Hi Joshua, I tried it with no luck. I'm far from being a debugger expert, but what's happening doesn't look normal to me. strace starts fine and writes tons of stuff when the server starts. I wait until it's done and make a request to that web page. Page is displayed but nothing is

Re: [EMAIL PROTECTED] Corrupted source files

Ok, I've been able to get some tracing info by running strace -u www -p httpd PID (attaching to the running process). Here's what I got: - 8 -=== getsockname(16, {sa_family=AF_INET6, sin6_port=htons(80), inet_pton(AF_INET6, :::10.10.10.60,

Re: [EMAIL PROTECTED] Corrupted source files

Hi Joshua, Change your Listen directive to a port over 1024 and then strace after starting from a non-root account. I've tried this one as well, finally made it work after fiddling with permissions. Here is the log (looks the same as the previous one): - 8

Re: [EMAIL PROTECTED] Corrupted source files

Hi Joshua, On 9/24/06, Victor Star [EMAIL PROTECTED] wrote: write(7, [EMAIL PROTECTED]..., 156) = 156 writev(16, [{NULL, 135209656}, {@*\26\10\0\0\0\0\0\0\0\0\0\0\0\0\2\0\0\0\1\0\0\0LoadMo..., 135211888}], 2) = 463 Looks pretty ordinary except for the above two lines. Can you try

Re: [EMAIL PROTECTED] Corrupted source files

write(7, [EMAIL PROTECTED]..., 156) = 156 writev(16, [{NULL, 135209656}, {@*\26\10\0\0\0\0\0\0\0\0\0\0\0\0\2\0\0\0\1\0\0\0LoadMo..., 135211888}], 2) = 463 Looks pretty ordinary except for the above two lines. Can you try to figure out what the descriptor 7 is pointing to, and when it is

Re: [EMAIL PROTECTED] Corrupted source files

And completely manual request (file gets corrupted): - 8 -=== accept(4, {sa_family=AF_INET, sin_port=htons(2305), sin_addr=inet_addr(10.10.10.10)}, [16]) = 15 getsockname(15, {sa_family=AF_INET, sin_port=htons(1024),

Re: [EMAIL PROTECTED] Corrupted source files

Hi Joshua, There are only two writing actions there: syscall_393 which is (I believe) sendfile and the log write. Neither of those should have any effect on your file. Just on a whim, I would try EnableSendfile Off in httpd.conf. But even if that works, the only explanation I would have