<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Message: 6<br>
Date: Thu, 13 Mar 2008 14:37:59 -0400<br>
From: Fairlight <<a href="mailto:fairlite@fairlite.com" target="_blank">fairlite@fairlite.com</a>><br>
Subject: Re: Re: fpCGI failure<br>
To: <a href="mailto:filepro-list@lists.celestial.com" target="_blank">filepro-list@lists.celestial.com</a><br>
Message-ID: <<a href="mailto:20080313143759.C21228@iglou.com" target="_blank">20080313143759.C21228@iglou.com</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>Erm...SCO system? I assume it's probably SCO's build, so it's likely under<br>
/usr/local/apache or /usr/local/lib/apache (possibly suffixed with a<br>
2...it's been a while). Under whichever it is, there should be a logs<br>
directory.<br>
</blockquote><div><br>Found 'em. Up at <a href="http://kinotox.net/2bDELETED/access_log" target="_blank">http://kinotox.net/2bDELETED/access_log</a> and <a href="http://kinotox.net/2bDELETED/error_log" target="_blank">http://kinotox.net/2bDELETED/error_log</a>. The problems start at Wed Mar 5 11:17:15 2008. I can see where the pattern is breaking there, but I don't *really* know what it means.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">A redirect of stderr is 0 bytes? Then it's not kicking up something it<br>
considers an error worth beeping over.</blockquote><div><br>Apparently it's not even creating the files at all, suggesting that fpcgi isn't running rreport.<br></div><div> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The problem with throwing up a lot of dirt is that it obscures the vision.<br>
:)</blockquote><div><br>Things are already mightily obscured, I doubt that more people helping to dig would cloud the air more at all :P<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
You've made reference to other reports running just fine. What happens if<br>
you replicate the necessary parts of the environment at the shell level,<br>
throw your processing for the fpcgi-based stuff into debug mode, and run it<br>
from the command line without fpcgi in the mix at all? Same table, either<br>
with or without debug, but will it run -outside- the context of fpcgi?<br>
Just create the flat ASCII file fpcgi would, fake the environment, and see<br>
what happens. It's the sanest idea at this point.</blockquote><div><br>And was in fact that very first thing I did, lo those many moons ago, when I first encountered the problem. It runs just peachy manually with exactly the same data as when it bombs out. I did discover the DLEN bug this way, but that's been eliminated as the problem here.<br>
<br></div></div>Tyler<br>