[rt-users] [SOLVED] Re: Problemwith rt-crontool: can't get it running

[Patrick G. Stoesser]

As often, just after I wrote to the list, I got a solution.

I just opened the line specified in the error message once again and saw 
the comment "VALUE is a queue id or Name." In the cron line, I specified 
"--search-arg general". And so my idea was that maybe "general" is not 
"a queue id or Name". So I replaced "--search-arg general" with 
"--search-arg Level1" (Level1 is the Name of one of my queues). And what 
can I say: It works.

At least for a Debian system, the wiki documentation is wrong.

Regards, Patrick


Am 18.01.2013 15:35, schrieb Patrick G. Stoesser:
> Hello there,
>
> even after googleing and trying several hours I'm still stuck with
> rt-crontool.
>
> I'm running RT 4.0.7 via Backports on a Debian Squeeze system. RT
> istelfs works ok so far, but rt-crontool not.
>
> According to the manual, I have added a non-privileged system user
> (rtcron).This user is ingroup staff and www-data.
> Iadded a privileged RT user rtcron (setting UNIX login also to rtcron),
> gave this RT user the rights "ShowTicket" and "ModifyTicket".
>
> In cron I added
> @hourly * * * * * rtcron /usr/bin/rt-crontool --search
> RT::Search::ActiveTicketsInQueue --search-arg general --action
> RT::Action::LinearEscalate --verbose
>
> What happens: Nothing. The only thing: In syslog and in RTs log the call
> results in
>
> [warning]: Use of uninitialized value $args{"VALUE"} in join or string
> at /usr/share/request-tracker4/lib/RT/Tickets.pm line 2099.
> (/usr/share/request-tracker4/lib/RT/Tickets.pm:2099)
>
> [warning]: Use of uninitialized value $value in substitution (s///) at
> /usr/share/request-tracker4/lib/RT/Tickets.pm line 3403.
> (/usr/share/request-tracker4/lib/RT/Tickets.pm:3403)
>
> [warning]: Use of uninitialized value in concatenation (.) or string at
> /usr/share/request-tracker4/lib/RT/Tickets_SQL.pm line 262.
> (/usr/share/request-tracker4/lib/RT/Tickets_SQL.pm:262)
>
> At those lines there'snothing I could regognize as appearently broken.
> So at the moment, I'm completely stumped.
>
> Has anyone an idea?
>
> Thanks for all comments.
>
> Regards, Patrick