[IC] Internal server error...

Glenn McCalley interchange-users@interchange.redhat.com
Mon Nov 5 10:59:01 2001


Thanks for the reply, Joachim.

interchange.cfg has "Variable DEBUG 1"

I also uncommented the "::logDebug" statements in interchange.  The
/tmp/icdebug file shows the activity and it looks OK (AFAIK).  The last
entry in each case is:
    main::debug: arg is
    mail::debug: paht=admin/order

...but still 500 error.  Also, 5 minutes after the failure, the interchange
error.log shows "Spurious PID file for process xxxxx supposedly running 301
seconds".  I suppose this is whatever task was forked and died being killed
for running too long?

Are there other programs where logging should be uncommented?  Or
everywhere?  Or is there a way to enable some logging in the task that's
being left behind?

Thanks!
Glenn.



----- Original Message -----
From: Joachim Leidinger <jojo@blackpoint.de>
To: <interchange-users@interchange.redhat.com>
Sent: Sunday, November 04, 2001 12:38 PM
Subject: Re: [IC] Internal server error...


> Glenn McCalley wrote:
> >
> > OK it's been a week and I still can't find it.  Staring at it  too much
> > maybe...
> >
> > IC 4.8.2
> > Perl 5.6.1
> > FreeBSD 4.0
> > Foundation -- stock install.
> >
> > The "orders" and "merchandising" sections of the administrative UI (and
only
> > these major sections) return "Internal Server Error" -- each time every
> > time.  A perl.core is produced in catalogs/foundation/perl.core.  Also,
with
> > the "items" table displaying, clicking either yes/no in the "promo"
column
> > produced Internal server error.
> >
> > All other functions work great.  We can add/del users, products, change
page
> > layout/content, buy stuff and checkout calculates fine.  Just can't
click
> > orders or merchandising.
> >
> > interchange/error.log and interchange/catalogs/foundation/error.log show
> > nothing.  Apache error_log shows the 500 with "Premature end of script
> > headers.
> >
> > It seems apparent (risky statement I know) that the 500 is the result of
> > Perl issuing an error msg.  Is there a way to get IC to put this message
to
> > the browser (like "fatalstoBrowser" does) or in a log somewhere?
>
> Hmmm...maybe you get more informations and hint, if you use
>
> # Set to 1 to send extra debugging info to file /tmp/icdebug
> # and get a dump of global and catalog data structures.
> Variable  DEBUG  1
>
> in your interchange.cfg file?
>
> Joachim
>
> --
> Hans-Joachim Leidinger | Dipl.-Phys.Ing. Entwicklung eCommerce
> [Hans-Joachim.leidinger@bpanet.de]
> Black Point Arts Internet Solutions GmbH
> http://www.bpanet.de
> _______________________________________________
> interchange-users mailing list
> interchange-users@interchange.redhat.com
> http://interchange.redhat.com/mailman/listinfo/interchange-users
>