Thanks for the reply William, at first I thought the same thing but as time went on and this only effected 1 virtual host and not the other (and the other had 10x the traffic), I didn't seem like hardware or config related. I've gotten a little further since my last post, but it still doesn't make sense. If I take the DB connection out of the script, it doesn't happen. I've added and removed it a few times just because I couldn't belive it. The DB is on another machine and both virtual hosts call the same machine (each virtual is a different DB on the dedicated DB server). The only difference in the DB connection call between the 2 scripts is that virtual host 1 calls it via a custom package (as other scripts need the same DB) - this is the site that works. Virtual Host 2 makes the connection within "sub handler" and that's the one that doesn't work. No closer to a solution though - any method I try to use to connect to the DB from VH2 results in this problem. Still doesn't make a lot of sense. ________________________________
From: William T [mailto:dietbud...@gmail.com] Sent: Tue 1/12/2010 11:47 AM To: cfaust-dougot Cc: modperl@perl.apache.org Subject: Re: Apache Blank Pages It seems pretty clear the blank pages are from the apache children dieing badly (hence the errors). I would make an educated guess based on the malloc error that your ram is bad. Try running your app on a different box and see if you get the same errors. On Jan 12, 2010 7:19 AM, "cfaust-dougot" <cfa...@doyougot.com> wrote: Hello, I have a bizarre problem I'm hoping someone could give me some suggestions with. I have a couple of MP2 scripts running on a server, they are both similar in use of modules and structure. Without any recent changes, one of the scripts is producing a blank apache page on SOME requests. It's not always the same function, it can happen to any of the function calls contained in the script. When the blank page happens there is nothing in either the access log or the error log of that virtual host (like the request never made it that far). In the default error log I will get something like [notice] child pid 11497 exit signal Aborted (6) Sometimes (but not always), I'll see *** glibc detected *** malloc(): memory corruption: 0x09c120f8 *** There is also no consistency to the blank page, sometimes you hit the URL and you get the content, sometimes you get a blank page, sometimes 1 refresh on the blank page gives you content, other times it can take 3 - 7 refreshes before the content comes. I've been trying to pull apart my script piece by piece in the hopes that I could at least narrow it down to some specific section but I'm not having a lot of luck. Any thoughts on how I could debug this better? TIA!
