Mickey - showmedo runs at WebFaction (thumbs up for WF!), on Linux.
I've not seen what Kevin's seen with mis-configured logging, but if
indeed a bad config sends stuff to stdout and there's no stdout to
catch it...it'll probably break just like my Broken Pipe experiences.
I'd suggest taking a look there first - maybe remove all the logging
so that nothing is written out anywhere, then build it back up?
You could also try editing your start-prj.py (or autostart.cgi which,
at WF, does some process checking and then calls start-prj.py) and
redirecting stdout to a file? Something like:
import sys
stdout_to_file=file('stdout.txt', 'w')
sys.stdout=stdout_to_file
then when anything is written to stdout, it instead goes to the
file...you then inspect the file for printed output and backtrack to
the source from there? I haven't tried this so YMMV...if you try it,
I'd love a report back on how/if it helps?
ian.
On Jan 11, 12:15 am, Mickey <[EMAIL PROTECTED]> wrote:
> Oh heck. The production version is on Linux, on WebFaction to be
> exact. I develop on Xubuntu.
>
> I don't have any prints, but that at least gives me a hint. Thanks.
>
> On Jan 10, 7:57 am, "[EMAIL PROTECTED]"
>
> <[EMAIL PROTECTED]> wrote:
> > Hi Mickey. You haven't said which platform (win/linux?) you're
> > running on, or whether this is a debug or production setup?
>
> > When I deploy our site using linux it runs in production mode which
> > means there's no stdout. If we've left print statements in the code
> > then on occasion we get 'Broken Pipe' errors. I believe that stdout's
> > buffer isn't being flushed as, under production mode, the output
> > doesn't go to screen (or indeed anywhere) so the buffer just fills up
> > and then barfs. The site keeps going and the error gets logged.
>
> > Not that we tend to leave print stmts on deployed code (!), but it has
> > been known to happen. The broken pipes have only ever appeared due to
> > print stmts. On our dev environments we print stdout to screen so we
> > never see these 'broken pipe' errors.
>
> > Hope that helps?
> > Ian.
>
> > On Jan 10, 12:21 pm, Mickey <[EMAIL PROTECTED]> wrote:
>
> > > My TurboGears based app (still somewhat under development) throws this
> > > error, "exceptions.IOError [Errno 32] Broken pipe". My app uses TG
> > > 1.0.2 and Kid templates, along with the identity module for TG.
>
> > > I've peppered my code with log.debug statements, and it's failing at a
> > > point when I return a multi-valued function:
>
> > > def foo()
> > > return 1, 2, 3, 4, 5
>
> > > a, b, c, d, e = foo()
>
> > > Restarting TG was making it go away, but now it fails every time. It
> > > happens to be the main page of the app, so I'm really confused on this
> > > one.
>
> > > Any ideas?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---
