Hi,
I am trying to run rt-crontool but fails to set the priority value.
The coomand promt error is given below:
[r...@localhost sbin]# rt-crontool --search RT::Search::ActiveTicketsInQueue
--search-arg CI new --condition RT::Condition::UntouchedInHours
--condition-arg 4 --action
Have you installed GraphViz from CPAN`?
2009/11/24 TONY JOHN - ERS, HCL Tech tonyj...@hcl.in
Hi,
I am trying to run rt-crontool but fails to set the priority value.
The coomand promt error is given below:
[r...@localhost sbin]# rt-crontool --search
RT::Search::ActiveTicketsInQueue
Hi ,
Now I'm getting a different error:
[r...@localhost sbin]# rt-crontool --search RT::Search::ActiveTicketsInQueue
--search-arg CI new --condition RT::Condition::UntouchedInHours
--condition-arg 4 --action RT::Action::SetPriority --action-arg 5 --verbose
[Tue Nov 24 09:59:59 2009]
Hi,
PFA UntouchedInHours.pm
Regards,
Tony
From: TONY JOHN - ERS, HCL Tech
Sent: Tuesday, November 24, 2009 3:31 PM
To: 'Torsten Brumm'
Cc: rt-users@lists.bestpractical.com
Subject: RE: [rt-users] rt-crontool error
Hi ,
Now I'm getting a different error:
Looks like you copied not all needed information from wiki into the
UntouchedInHours.pm:
Yours:
package RT::Condition::UntouchedInHours;
require RT::Condition::Generic;
use RT::Date;
@ISA = qw(RT::Condition::Generic);
use strict;
use vars qw/@ISA/;
sub IsApplicable {
my $self =
Hi,
I changed the UntouchedInHours.pm to the exact code as from rt wiki.But I got
this error:
[Tue Nov 24 10:42:18 2009] [warning]: Use of uninitialized value in
concatenation (.) or string at
/usr/lib/perl5/vendor_perl/5.10.0/RT/Tickets_Overlay_SQL.pm line 261.
What is in Line 261 of
/usr/lib/perl5/vendor_perl/5.10.0/RT/Tickets_Overlay_SQL.pm
and why is a RT Module installed in Vendor Perl tree?
Tob
2009/11/24 TONY JOHN - ERS, HCL Tech tonyj...@hcl.in
Hi,
I changed the UntouchedInHours.pm to the exact code as from rt wiki.But I
got this error:
Hi Max,
now i found the time to try it out.
Btw: i'm under RT 3.6.5 with RTx-Shredder, but there the Logger Entry is
also set. Here the Results first from my test box (only RT running on it, no
users)
Empty DB
created 1000 tickets with rt-filler scrip
1. Tickets shreddered without any index
Gordon,
That's where the comment comes in.
Kenn
LBNL
On 11/23/2009 3:35 PM, gor...@cryologic.com wrote:
Thanks Ken,
I use this feature for some fields but others require information
specific to a ticket (eg description of product design change). Also,
reviewers of historical tickets can
On Mon, Nov 23, 2009 at 10:51:46PM -0600, Arends, John wrote:
When upgrading from 3.8.4 to 3.8.6 I'm getting this error when running
bin/rt-setup-database --dba rt_user --prompt-for-dba-password --action
upgrade
Try running
/opt/rt3/sbin/rt-setup-database --dba rt_user \
On Mon, Nov 23, 2009 at 01:19:02PM -0500, Maxwell A. Rathbone wrote:
Look for this line:
$RT::Logger-warning( $msg );
Comment it so it looks like this:
#$RT::Logger-warning( $msg );
If you raise your LogLevel above warning (something like error) this
won't trigger and you can avoid
2009/11/24 Todd Chapman t...@chaka.net:
On Mon, Nov 23, 2009 at 10:35 PM, Jesse Vincent je...@bestpractical.com
wrote:
On Mon, Nov 23, 2009 at 10:33:16PM -0500, Todd Chapman wrote:
I just checked RT out of git and ran:
./configure --enable-layout=inplace --with-my-user-group
Hi All,
I'm definitely an RT novice, and could use some assistance. I have a ticket
Custom Field (Progress). It is a Select One Value field. When someone
selects the value Sent, I want a new ticket created that is 'depended on
by' the original ticket. Can anyone help me with this please?
Slightly offtopic - is there some best practice limit saying when
SQLite stops being efficient and it's time to use something bigger? Or
in other words, how large are average SQLite installations in terms of
users, tickets, etc.?
In my opinion, I would say that SQLite is appropriate for
-Original Message-
From: rt-users-boun...@lists.bestpractical.com [mailto:rt-users-
boun...@lists.bestpractical.com] On Behalf Of Tom Lahti
Sent: Wednesday, 25 November 2009 10:55
To: Ivan Voras
Cc: rt-users
Subject: Re: [rt-users] Is SQLite no longer supported?
Slightly
Slightly offtopic - is there some best practice limit saying when
SQLite stops being efficient and it's time to use something bigger? Or
in other words, how large are average SQLite installations in terms of
users, tickets, etc.?
We don't recommend that you use RT on SQLite in production,
Slightly offtopic - is there some best practice limit saying when
SQLite stops being efficient and it's time to use something bigger? Or
in other words, how large are average SQLite installations in terms of
users, tickets, etc.?
In my opinion, I would say that SQLite is appropriate for
SQLite's complete lack of threading model means responding to a single
request at a time.
Simply put, if you have enough users that the possibility of multiple people
requesting information at the same time, or a user request happening when an
external ticket comes in (email via
18 matches
Mail list logo
