Re: [gentoo-user] trying to find the cause of an http 500 error

[John Covici]

On Fri, 05 May 2017 10:16:08 -0400,
Mick wrote:
>
> To: gentoo-user@l.g.o
> Subject: Re: [gentoo-user] trying to find the cause of an http 500 error
> From: Mick <michaelkintzios@×××××.com>
> Date: Fri, 05 May 2017 15:16:08 +0100
> Reply-to: gentoo-user@l.g.o
>
> [1  <text/plain; us-ascii (quoted-printable)>]
> On Friday 05 May 2017 08:31:56 John Covici wrote:
> > On Fri, 05 May 2017 07:24:02 -0400,
> >
> > Michael Orlitzky wrote:
> > > On 05/05/2017 07:13 AM, John Covici wrote:
> > > > The php log is not mentioned in the .htaccess file of owncloud.  But
> > > > regardless of owncloud, php fatal errors are not logged anywhere under
> > > > apache, even though I have log_errors and a log file name.
> > >
> > > Apache doesn't know anything about what happens in the PHP code, so the
> > > errors should be logged in that separate PHP error log, if anywhere.
> > >
> > > As a temporary measure, you can try enabling "display_errors" and
> > > "display_startup_errors" in your (Apache) php.ini. That should convince
> > > PHP to spit out the error into your browser when you visit the page,
> > > rather than (or in addition to) logging it.
> >
> > If I put those on, I don't even get the 500, I get nothing at all
> > instead!  Very odd, indeed.  I just get a blank window when I use my
> > php fatal error creator.
> > But if I change it to http, I get the fatal error.
> >
> >
> > For owncloud, changing to http yields the same result.  However, when
> > I finally changed the display_startup_errors to On, I get the
> > following fatal error:
> > [05-May-2017 11:44:21 UTC] PHP Fatal error:  Maximum execution time of
> > 30 seconds exceeded in
> > /var/www/covici.com/htdocs-secure/owncloud/lib/base.php on line 542
> > [05-May-2017 11:44:21 UTC] PHP Stack trace:
> > [05-May-2017 11:44:21 UTC] PHP   1. {main}()
> > /var/www/covici.com/htdocs-secure/owncloud/index.php:0
> > [05-May-2017 11:44:21 UTC] PHP   2. require_once()
> > /var/www/covici.com/htdocs-secure/owncloud/index.php:37
> > [05-May-2017 11:44:21 UTC] PHP   3. OC::init()
> > /var/www/covici.com/htdocs-secure/owncloud/lib/base.php:967
> > [05-May-2017 11:44:21 UTC] PHP   4. set_time_limit()
> > /var/www/covici.com/htdocs-secure/owncloud/lib/base.php:542
> >
> >
> > Any insights would be appreciated.
>
> Have you looked at the lines mentioned above in base.php and index.php?
>
> It may be an issue of correct owneship/access rights and the lines in those
> files may give you a hint.  Some files may need to be owned by the owncloud
> user or the webserver user accounts.

Seems good, everything is owned correctly.  I wonder if its something
more basic on my system, what is set_time_limit actually doing?

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@××××××××××.com