Problem with RT::Logger

I had a working RT system up until this morning when it appears that
RT::Logger stopped functioning. Last week I upgraded from 3.6.4 to 3.6.5
and everything appeared to work fine. I shutdown the system for the weekend
and this morning I’m receiving a “500 Internal Server Error” when trying to
logon.

My apache2/errorlog entry is:
Can’t call method “debug” on an undefined value at
/opt/rt3/local/lib/RT/CurrentUser_Local.pm line 59

The relevant perl line is"

$RT::Logger->debug( "CreateFromExternalUserInfo: entered with args: ",
@lookupargs, “\n”);

If I comment this line from the program, it proceeds to fail on the next
RT::Logger statement including RT::Logger->info calls. If I comment out all
of the RT::Logger calls from this program, the system appears to function
normally.

Any help would be greatly appreciated!

Thanks,

Dan

DISCLAIMER: The information in this message is confidential and may be
legally privileged. It is intended solely for the addressee. Access to this
message by anyone else is unauthorized. If you are not the intended
recipient, any disclosure, copying, or distribution of the message, or any
action or omission taken by you in reliance on it, is prohibited and may be
unlawful. Please immediately contact the sender if you have received this
message in error. Thank you.

Most probably you’re calling methods on $RT::Logger when it’s not
initialized, for example during loading of modules.On 10/22/07, Lamers, Dan dlamers@elcan.com wrote:

I had a working RT system up until this morning when it appears that
RT::Logger stopped functioning. Last week I upgraded from 3.6.4 to 3.6.5
and everything appeared to work fine. I shutdown the system for the weekend
and this morning I’m receiving a “500 Internal Server Error” when trying to
logon.

My apache2/errorlog entry is:
Can’t call method “debug” on an undefined value at
/opt/rt3/local/lib/RT/CurrentUser_Local.pm line 59

The relevant perl line is"

$RT::Logger->debug( "CreateFromExternalUserInfo: entered with args: ",
@lookupargs, “\n”);

If I comment this line from the program, it proceeds to fail on the next
RT::Logger statement including RT::Logger->info calls. If I comment out all
of the RT::Logger calls from this program, the system appears to function
normally.

Any help would be greatly appreciated!

Thanks,

Dan

DISCLAIMER: The information in this message is confidential and may be
legally privileged. It is intended solely for the addressee. Access to this
message by anyone else is unauthorized. If you are not the intended
recipient, any disclosure, copying, or distribution of the message, or any
action or omission taken by you in reliance on it, is prohibited and may be
unlawful. Please immediately contact the sender if you have received this
message in error. Thank you.


The rt-users Archives

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Best regards, Ruslan.

Hello,

I have a problem with logo customization. I followed this instructions (ChangeLogo - Request Tracker Wiki) and paid much attention to the latest mails about logos (after each & every changes I use a cleanmason.sh that makes a apache stop / clean cache / apache start)

But when access the login page I get this :

error: Error during compilation of /opt/rt3/local/html/Elements/Logo:
Bareword “RT::LogoLinkURL” not allowed while “strict subs” in use at /opt/rt3/local/html/Elements/Logo line 49.

context: …
45: %# those contributions and any derivatives thereof.
46: %#
47: %# END BPS TAGGED BLOCK }}}
48:


49: <img src=“<%$RT::WebImagesURL%>/bplogo.gif” alt=“<%loc(“Best Practical Solutions, LLC corporate logo”)%>” width=“177” height=“33” />
50: % if ($show_name) {
51:
<% loc(“RT for [_1]”, $RT::rtname) %>

52: % }
53:


The problem seems to be onlyfor RT::variables in the href=
If I put plain text in there, it’s ok
If I put any other RT variables (just a copy & paste of the following <%$RT::WebImagesURL%> or any other properly defined and substituted variables for instance) I get an error.
But all other RT variables are properly substituted in the line. I only have a problem with the href.

I tried to google around for “bareword” and “strict subs” but did not grasp where to look for or what would be the effect of remove such a “strict subs” command wherever it may be.

I don’t mind coding the URL in plain text in my local Logo file but it would be better if this variable could work properly.

Any idea ?

David

missing $

Shame on me. Not even able to do a copy/paste properly

You can flame me all you want and I deserve it :frowning:

I have solved this problem by adding the following line to my
CurrentUser_Local.pm

Package RT::Interface::Web;

I still don’t understand why it worked before without the added line?
Perhaps this is related to the 3.6.4 to 3.6.5 upgrade?

Hopefully this will help anyone else who runs into similar issues running
CurrentUser_Local.pm ldap overlay.

DanFrom: rt-users-bounces@lists.bestpractical.com
[mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Lamers, Dan
Sent: Monday, October 22, 2007 3:38 PM
To: rt-users@lists.bestpractical.com
Subject: [rt-users] Problem with RT::Logger

I had a working RT system up until this morning when it appears that
RT::Logger stopped functioning. Last week I upgraded from 3.6.4 to 3.6.5
and everything appeared to work fine. I shutdown the system for the weekend
and this morning I’m receiving a “500 Internal Server Error” when trying to
logon.

My apache2/errorlog entry is:
Can’t call method “debug” on an undefined value at
/opt/rt3/local/lib/RT/CurrentUser_Local.pm line 59

The relevant perl line is"

$RT::Logger->debug( "CreateFromExternalUserInfo: entered with args: ",
@lookupargs, “\n”);

If I comment this line from the program, it proceeds to fail on the next
RT::Logger statement including RT::Logger->info calls. If I comment out all
of the RT::Logger calls from this program, the system appears to function
normally.

Any help would be greatly appreciated!

Thanks,

Dan

DISCLAIMER: The information in this message is confidential and may be
legally privileged. It is intended solely for the addressee. Access to this
message by anyone else is unauthorized. If you are not the intended
recipient, any disclosure, copying, or distribution of the message, or any
action or omission taken by you in reliance on it, is prohibited and may be
unlawful. Please immediately contact the sender if you have received this
message in error. Thank you.

DISCLAIMER: The information in this message is confidential and may be
legally privileged. It is intended solely for the addressee. Access to this
message by anyone else is unauthorized. If you are not the intended
recipient, any disclosure, copying, or distribution of the message, or any
action or omission taken by you in reliance on it, is prohibited and may be
unlawful. Please immediately contact the sender if you have received this
message in error. Thank you.