On 29 Feb 2012, at 01:13, Daevid Vincent wrote:
>> -Original Message-
>> From: Stuart Dallas [mailto:stu...@3ft9.com]
>>
>> Seriously? Errors like this should not be getting anywhere near your
>> production servers. This is especially true if you're really getting 30k
>> hits/s.
>
> Don'
Hi, Daevid
What you could do to have it quick is to install the plugin xdebug.
Here you can (as described in the documentation linked here) enable to get
some extra information for a E_* message from php.
http://xdebug.org/docs/stack_trace
I would not do that on a live-system where you have 30k
On Tue, Feb 28, 2012 at 3:14 PM, Daevid Vincent wrote:
> My question is, is there a way to enable some PHP configuration that would
> output more verbose information, such as a backtrace or the URL attempted?
>
Have you looked at log4php? [1] It's a log4j (Java based) logging
facility port to PHP
> -Original Message-
> From: Stuart Dallas [mailto:stu...@3ft9.com]
>
> Seriously? Errors like this should not be getting anywhere near your
> production servers. This is especially true if you're really getting 30k
> hits/s.
Don't get me started. I joined here almost a year ago. They did
On 28 Feb 2012, at 23:14, Daevid Vincent wrote:
> My question is, is there a way to enable some PHP configuration that would
> output more verbose information, such as a backtrace or the URL attempted?
>
> In our PHP error log, we have the usual semi-useful information. However
> this is only a p
On Tue, Feb 28, 2012 at 6:14 PM, Daevid Vincent wrote:
> My question is, is there a way to enable some PHP configuration that would
> output more verbose information, such as a backtrace or the URL attempted?
>
> In our PHP error log, we have the usual semi-useful information. However
> this is o
My question is, is there a way to enable some PHP configuration that would
output more verbose information, such as a backtrace or the URL attempted?
In our PHP error log, we have the usual semi-useful information. However
this is only a partial story as it's hard to re-create the URL that caused
Am 18.01.2011 01:33, schrieb Jimmy Stewpot:
Hello,
I currently have a strange issue where we are seeing 'random errors' being
displayed to end users. What I find most interesting is that in the php.ini
file we have the following error settings.
error_reporting = E_ALL& ~E_NOTICE
display_er
On Mon, Jan 17, 2011 at 19:33, Jimmy Stewpot wrote:
> Hello,
>
> I currently have a strange issue where we are seeing 'random errors' being
> displayed to end users. What I find most interesting is that in the php.ini
> file we have the following error settings.
>
> error_reporting = E_ALL & ~
Hello,
I currently have a strange issue where we are seeing 'random errors' being
displayed to end users. What I find most interesting is that in the php.ini
file we have the following error settings.
error_reporting = E_ALL & ~E_NOTICE
display_errors = Off
display_startup_errors = Off
log_er
I suggest each student adds the line
error_reporting(E_ALL);
This will echo the errors and will not affect the php.ini settings.
Hope that will work for you
cheers
On 5/31/07, Clark Alexander <[EMAIL PROTECTED]> wrote:
We have the following php.ini settings:
error_reporting = E_ALL
display
On Thu, May 31, 2007 3:25 pm, Clark Alexander wrote:
> We have the following php.ini settings:
> error_reporting = E_ALL
> display_errors = Off
> display_startup_errors = Off
> log_errors = On
> log_errors_max_len = 1024
> ignore_repeated_errors = Off
> ignore_repeated_source = Off
> report_memle
Upon review, I also discover that fatal error entries are being made as
well.
On 5/31/07 5:14 PM, in article [EMAIL PROTECTED], "Jochem Maas"
<[EMAIL PROTECTED]> wrote:
> Clark Alexander wrote:
>> We have the following php.ini settings:
>> error_reporting = E_ALL
>> display_errors = Off
>> dis
Yes, it does write to the file, but the only things going in there are
notice type entries.
Also, for further information, it is php 5.1.2 using the Suse rpm.
On 5/31/07 5:14 PM, in article [EMAIL PROTECTED], "Jochem Maas"
<[EMAIL PROTECTED]> wrote:
> Clark Alexander wrote:
>> We have the follow
Clark Alexander wrote:
> We have the following php.ini settings:
> error_reporting = E_ALL
> display_errors = Off
> display_startup_errors = Off
> log_errors = On
> log_errors_max_len = 1024
> ignore_repeated_errors = Off
> ignore_repeated_source = Off
> report_memleaks = On
> track_errors = Off
We have the following php.ini settings:
error_reporting = E_ALL
display_errors = Off
display_startup_errors = Off
log_errors = On
log_errors_max_len = 1024
ignore_repeated_errors = Off
ignore_repeated_source = Off
report_memleaks = On
track_errors = Off
on a SuSE 10.1 server and the errors are b
-Original Message-
From: Al [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 10, 2004 9:19 PM
To: [EMAIL PROTECTED]
Subject: [PHP] Error logging problem
My site is on a virtual host and I'd like to log errors to a file while
I'm
debugging. Can't get it to work.
H
My site is on a virtual host and I'd like to log errors to a file while I'm
debugging. Can't get it to work.
Here is the code at the top of my script:
ini_set("display_errors", "on"); //also tried "Off"
ini_set("error_log", "/AutoSch/error.log");
$ini_array= ini_get_all();
error_repor
Greg Donald wrote:
On Wed, 10 Nov 2004 10:49:29 -0500, Al <[EMAIL PROTECTED]> wrote:
ini_set("error_log", "/AutoSch/error.log");
Looks like this might be a path relative to your domain or your vhost
definition? I'd go with a full system path if that's the case.
Hey Greg, that did it.
It's obviou
On Wed, 10 Nov 2004 10:49:29 -0500, Al <[EMAIL PROTECTED]> wrote:
> > ini_set("error_log", "/AutoSch/error.log");
Looks like this might be a path relative to your domain or your vhost
definition? I'd go with a full system path if that's the case.
--
Greg Donald
Zend Certified Engineer
http://
Hey there,
I'm playing around with the logging options in the php.ini file.
I set this:
display_errors = Off
Because I don't want to visitors to see any errors (besides the errors I
define myself in the PHP script, which is exactly what this does... I only
print out things like can't open data
I've an installation of PHP4pl1 running under Apache 1.3.19. Without output
buffering enabled, the error logging is fine (going to Apache's error_log as
expected) The problem is that when I turn on output buffering (to enable me
to send cookies when I feel like it ;) the error logging stops being
22 matches
Mail list logo
