-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Is it my imagination, or does RT 3.6.3 do more voluminous ‘debug’ level
logging than, say, 3.4.5 or 3.4.2?
In particular, in 3.6.3, whenever I reference a ticket that consists of a
couple of merged tickets, I get several dozen rapid-fire messages in my
rt.log, like this:
[debug]: We found a merged ticket.566/561
(/users/ist-rt/RT/rt/ist-rt/lib/RT/Ticket_Overlay.pm:271)
The identical message appears consecutively at least a couple of dozen
times and the same same thing occurs for each ticket that was merged into
the selected ticket.
In earlier RT versions, I might see no more than 3 or 5 such consecutive
log messages.
My log is filling up quite fast because of this.
Any ideas?
Thanks.
Mike
Mike Friedman Information Services & Technology
mikef@ack.Berkeley.EDU 2484 Shattuck Avenue
1-510-642-1410 University of California at Berkeley
Socrates and Berkeley Scholars Web Hosting Services Have Been Retired | Web Platform Services http://ist.berkeley.edu
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8
iQA/AwUBRi2Kfq0bf1iNr4mCEQJVfgCcDo6JR0/jspHEtYRvv+cPuf+2inIAnRY/
jCv8a2cQpWZBZhE2eGs73uWa
=O7yt
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Is it my imagination, or does RT 3.6.3 do more voluminous ‘debug’
level logging than, say, 3.4.5 or 3.4.2?
In particular, in 3.6.3, whenever I reference a ticket that
consists of a couple of merged tickets, I get several dozen rapid-
fire messages in my rt.log, like this:
[debug]: We found a merged ticket.566/561
(/users/ist-rt/RT/rt/ist-rt/lib/RT/Ticket_Overlay.pm:271)
The identical message appears consecutively at least a couple of
dozen times and the same same thing occurs for each ticket that was
merged into the selected ticket.
In earlier RT versions, I might see no more than 3 or 5 such
consecutive log messages.
My log is filling up quite fast because of this.
Any ideas?
The ‘debug’ log level is really intended for, well, debugging. In
production, I’d probably turn it down to “warn” or “info”
Best,
Jesse
PGP.sig (186 Bytes)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1On Tue, 24 Apr 2007 at 08:45 (-0400), Jesse Vincent wrote:
On Apr 24, 2007, at 12:41 AM, Mike Friedman wrote:
Is it my imagination, or does RT 3.6.3 do more voluminous ‘debug’ level
logging than, say, 3.4.5 or 3.4.2?
The ‘debug’ log level is really intended for, well, debugging. In
production, I’d probably turn it down to “warn” or “info”
Jesse,
Well, that certainly makes a lot of sense. I was a bit concerned that the
difference between 3.4.2 and 3.6.3 in the amount logged under ‘debug’
might reflect something wrong with my setup of the latter. But I have no
evidence for this, so I’ll just change ‘debug’ to ‘info’ and see how that
goes. I assume I won’t miss any messages that I need to know about in
normal operation.
Thanks.
Mike
Mike Friedman Information Services & Technology
mikef@ack.Berkeley.EDU 2484 Shattuck Avenue
1-510-642-1410 University of California at Berkeley
Socrates and Berkeley Scholars Web Hosting Services Have Been Retired | Web Platform Services http://ist.berkeley.edu
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8
iQA/AwUBRi4iBa0bf1iNr4mCEQLEyQCeJbId3cGz887zFOBnomAaelHcd0sAoLCz
FM3m8gaiAKC4CJhROnNq050I
=4vJt
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Is it my imagination, or does RT 3.6.3 do more voluminous ‘debug’
level logging than, say, 3.4.5 or 3.4.2?
The ‘debug’ log level is really intended for, well, debugging. In
production, I’d probably turn it down to “warn” or “info”
Jesse,
Well, that certainly makes a lot of sense. I was a bit concerned
that the difference between 3.4.2 and 3.6.3 in the amount logged
under ‘debug’ might reflect something wrong with my setup of the
latter. But I have no evidence for this, so I’ll just change
‘debug’ to ‘info’ and see how that goes. I assume I won’t miss any
messages that I need to know about in normal operation.
We tend to add more debugging output when we’re doing more debugging.
We don’t tend to remove new debugging output.
Jesse
PGP.sig (186 Bytes)