Simple Search Suddenly Fails

Using RT 3.8.1 on a Fedora Core 6 Linux box …
Simple Search had been working fine, now suddenly returns “0” tickets
(where a full search for the same Requestor email returns multiple
tickets) with the following errors in the logs:

Feb 9 12:44:03 Blackhole RT: Couldn’t get principal for not loaded
object (/opt/rt381/bin/…/lib/RT/User_Overlay.pm:1113)

Feb 9 12:44:03 Blackhole RT: Group::HasMember was called with an
argument that isn’t an RT::Principal or id. It’s (undefined)
(/opt/rt381/bin/…/lib/RT/Group_Overlay.pm:1031)

Only recent changes that spring to mind was to disable several existing
queues and modify a few custom statuses in RTSiteConfig.pm

Rebooting the server made no difference. Any pointers or suggestions
greatly appreciated.

Bill Davis

(baffled & confused … more than normal :o) )

Additional information:

If I check “Edit Query” for the failed Simple Search I see:

( Requestor LIKE ‘daviswj@comcast.net’ ) AND ( Status = ‘HOLD’ OR
Status = ‘TstBenchP1’ OR Status = ‘TstBenchP2’ OR Status = ‘new’ OR
Status = ‘open’ OR Status = ‘resolved’ OR Status = ‘stalled’ ) AND (
Subject LIKE ‘Pending-BD’ )

… the reason it is coming back with “0” tickets is the final "… AND
(Subject LIKE ‘Pending-BD’). This will never be true, “Pending-BD” was
a user added status that has now been removed. I’ve no idea why it is
popping up in this query (or why it is being searched for within the
Subject field).

Bill Davis

Bill Davis wrote:

Using RT 3.8.1 on a Fedora Core 6 Linux box ... Simple Search had been working fine, now suddenly returns "0" tickets (where a full search for the same Requestor email returns multiple tickets) with the following errors in the logs:

Feb 9 12:44:03 Blackhole RT: Couldn’t get principal for not loaded
object (/opt/rt381/bin/…/lib/RT/User_Overlay.pm:1113)

Feb 9 12:44:03 Blackhole RT: Group::HasMember was called with an
argument that isn’t an RT::Principal or id. It’s (undefined)
(/opt/rt381/bin/…/lib/RT/Group_Overlay.pm:1031)

Only recent changes that spring to mind was to disable several existing
queues and modify a few custom statuses in RTSiteConfig.pm

Rebooting the server made no difference. Any pointers or suggestions
greatly appreciated.

Bill Davis

(baffled & confused … more than normal :o) )


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users 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

(Que Homer Simpson) DuH!!

… I’m an idiot. Found the cause … had a callback in place to
modify the statuses included in Simple Search, one of which was
"Pending-BD". Removing that status obviously confused RT … removed
"Pending-BD" from the callback & problem is solved.

Please return to your regularly scheduled programming …

Bill Davis