Re: [rt-users] RT CLI CF query operators
Loos,
Thank you for the help but after I rectified the typo. I still getting a
different errors.
rt list -i 'CF.{Modtrak} > 0 AND Created >= "2015-07-01" AND Created <=
"2015-07-31"'
rt: Invalid query: 'Wrong query, expecting a AGGREGATOR in 'CF.{Modtrak} >
0 AND Created >='"2015-07-01'>" AND Created <='"<--here2015-07-31'"' at
/opt/rt4/sbin/../lib/RT/SQL.pm line 130.
Stack:
[/opt/rt4/sbin/../lib/RT/SQL.pm:130]
[/opt/rt4/sbin/../lib/RT/Tickets.pm:2979]
[/opt/rt4/sbin/../lib/RT/Tickets.pm:2997]
[/opt/rt4/share/html/REST/1.0/search/ticket:89]
[/opt/rt4/share/html/REST/1.0/autohandler:54]
[/opt/rt4/sbin/../lib/RT/Interface/Web.pm:680]
[/opt/rt4/sbin/../lib/RT/Interface/Web.pm:368]
[/opt/rt4/share/html/autohandler:53]
'.
Invalid query: 'Wrong query, expecting a AGGREGATOR in 'CF.{Modtrak} > 0
AND Created >='"2015-07-01'>" AND Created <='"<--here2015-07-31'"' at
/opt/rt4/sbin/../lib/RT/SQL.pm line 130.
Stack:
[/opt/rt4/sbin/../lib/RT/SQL.pm:130]
[/opt/rt4/sbin/../lib/RT/Tickets.pm:2979]
[/opt/rt4/sbin/../lib/RT/Tickets.pm:2997]
[/opt/rt4/share/html/REST/1.0/search/ticket:89]
[/opt/rt4/share/html/REST/1.0/autohandler:54]
[/opt/rt4/sbin/../lib/RT/Interface/Web.pm:680]
[/opt/rt4/sbin/../lib/RT/Interface/Web.pm:368]
[/opt/rt4/share/html/autohandler:53]
> Am 26.08.2015 um 21:25 schrieb supp...@pureview.com:
>> rt list -i "'CF.{Modtrak}' > 0 AND Created >= '2015-07-01' AND Create <=
>> '2015-07-31'"
>> rt: Invalid query: 'Unknown field 'Create' in ''CF.{Modtrak}' > 0 AND
>> Created >= '2015-07-01' AND Create <= '2015-07-31'' at
>> /opt/rt4/sbin/../lib/RT/Tickets.pm line 2943.
>
> The error message says all.
> It's just a typo, the ticket field is called Created and not Create.
>
> Chris
>
Re: [rt-users] rt cluster using postgres
I think your solution is going to come from postgres, rather than RT. I believe Ticket ID's come from tickets_id_seq. You could set them to increment by 2, with one starting at an even number and another starting at an odd number. See: http://www.postgresql.org/docs/9.4/static/sql-createsequence.html However, I don't have enough experience with clustering to know if that's a good idea. Here's some info on postgres that could be useful to your situation: https://wiki.postgresql.org/wiki/Replication,_Clustering,_and_Connection_Pooling Joseph Wagner On 08/28/2015 03:35 PM, Jeff Mundine wrote: I had an idea to cluster RT, using postgres to synchronize the different RT servers. The only issue I have, is if the DB's stop talking to eachother, then there would be a problem with the ticket sequencing. (you would get duplicate tickets for the same id). I've tried to look around for something like modifying the ticket id. I know it's numeric only, but haven't found much to do something like have one server do odd numbers, the other even or some such.. Any ideas of a way to do this, or is it simply not possible at this time. Also, any other reasons or possible problems anyone could see with this? My secondary step, is just to run 1 instance, but use the postgres replication and probably rsync for a hot standby.
[rt-users] rt cluster using postgres
I had an idea to cluster RT, using postgres to synchronize the different RT servers. The only issue I have, is if the DB's stop talking to eachother, then there would be a problem with the ticket sequencing. (you would get duplicate tickets for the same id). I've tried to look around for something like modifying the ticket id. I know it's numeric only, but haven't found much to do something like have one server do odd numbers, the other even or some such.. Any ideas of a way to do this, or is it simply not possible at this time. Also, any other reasons or possible problems anyone could see with this? My secondary step, is just to run 1 instance, but use the postgres replication and probably rsync for a hot standby.
Re: [rt-users] procmail call to rt-mailgate fails
On Fri, Aug 28, 2015 at 1:52 PM, Asif Iqbal wrote: > > MAILDIR=$HOME/Maildir > DEFAULT=$MAILDIR/mbox > LOGFILE=$HOME/procmail.log > LOCKFILE=$HOME/lockmail > VERBOSE=on > :0 > |/usr/sbin/rt-mailgate --queue IPANEMA --action correspond --url > https://ticket.example.net > > procmail: [15376] Fri Aug 28 13:19:04 2015 > procmail: Assigning "LASTFOLDER=/usr/sbin/rt-mailgate --queue IPANEMA > --action correspond --url https://ticket.example.net"; > procmail: [15376] Fri Aug 28 13:19:04 2015 > procmail: Executing > "/usr/sbin/rt-mailgate,--queue,IPANEMA,--action,correspond,--url, > https://ticket.example.net"; > procmail: Notified comsat: "ipanema@:/usr/sbin/rt-mailgate --queue > IPANEMA --action correspond --url https://ticket.example.net"; > From axisys Fri Aug 28 13:19:04 2015 > Folder: /usr/sbin/rt-mailgate --queue IPANEMA --action correspo660 > procmail: Unlocking "/home/ipanema/lockmail" > /usr/sbin/rt-mailgate: Couldn't create temp file, using memory > error: Error in tempdir() using /tmp/XX: Could not create > directory /tmp/Rf_FTTAo4f: Permission denied at /usr/sbin/rt-mailgate line > 273 > > An Error Occurred > = > > 500 Can't connect to ticket.example.net:443 (connect: Permission denied) > > Any suggestion why rt-mailgate is failing? > > This works just fine > > foo: "|/usr/sbin/rt-mailgate --queue IPANEMA --action correspond --url > https://ticket.example.net"; > > I am using rt-mailgate from rt4-mailgate-4.0.19-2.sdl6.noarch on centos 6.7 > > It was selinux issue. Now all good. -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?
[rt-users] RT 4.2 query; RequestorGroup != 'admin'
Hello, I have an RT query created with the query builder that RequestorGroup. Status = '@owner' returns 163 tickets Status = '@owner' AND RequestorGroup = 'admin' returns 101 tickets This lists all issues where the Requestor is a member of the admin group. I would like to list all tickets where the Requestor is not a member of the admin group. I expected this query to work. Status = '@owner' AND RequestorGroup != 'admin' I also tried NOT LIKE 'admin' These give the error: There was an error parsing your search query: Invalid RequestorGroup Op: !=. Your RT admin can find more information in the error logs. This looks like a bug to me. regards Richard
[rt-users] procmail call to rt-mailgate fails
MAILDIR=$HOME/Maildir DEFAULT=$MAILDIR/mbox LOGFILE=$HOME/procmail.log LOCKFILE=$HOME/lockmail VERBOSE=on :0 |/usr/sbin/rt-mailgate --queue IPANEMA --action correspond --url https://ticket.example.net procmail: [15376] Fri Aug 28 13:19:04 2015 procmail: Assigning "LASTFOLDER=/usr/sbin/rt-mailgate --queue IPANEMA --action correspond --url https://ticket.example.net"; procmail: [15376] Fri Aug 28 13:19:04 2015 procmail: Executing "/usr/sbin/rt-mailgate,--queue,IPANEMA,--action,correspond,--url, https://ticket.example.net"; procmail: Notified comsat: "ipanema@:/usr/sbin/rt-mailgate --queue IPANEMA --action correspond --url https://ticket.example.net"; >From axisys Fri Aug 28 13:19:04 2015 Folder: /usr/sbin/rt-mailgate --queue IPANEMA --action correspo660 procmail: Unlocking "/home/ipanema/lockmail" /usr/sbin/rt-mailgate: Couldn't create temp file, using memory error: Error in tempdir() using /tmp/XX: Could not create directory /tmp/Rf_FTTAo4f: Permission denied at /usr/sbin/rt-mailgate line 273 An Error Occurred = 500 Can't connect to ticket.example.net:443 (connect: Permission denied) Any suggestion why rt-mailgate is failing? This works just fine foo: "|/usr/sbin/rt-mailgate --queue IPANEMA --action correspond --url https://ticket.example.net"; I am using rt-mailgate from rt4-mailgate-4.0.19-2.sdl6.noarch on centos 6.7 -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?
[rt-users] Antwort: Re: Including latest transactions in RSS-Feed
Hi Christian! Thanks for your input. Now I managed to change the RSS content, so that it outputs the latest transaction (Comment/Correspond) for each ticket in the search result. Maybe someone updates this in the release version, because I think, that this content is of a bigger interest than just the contents of the initially created tickets. Patch file is attached... Greetings, Markus P.S.: Danke nochmal für die Unterstützung - hat mir sehr geholfen! ResultsRSSView.patch Description: Binary data
Re: [rt-users] How to add last comment to ticket query results?
Am 28.08.2015 um 13:03 schrieb Ewan Meadows: > I've been asked to add another column to a query which shows the last > comment added to a ticket, any ideas how I can do this? > > Thanks, > > Ewan > Hi, there is an extension for this: https://github.com/bestpractical/rtx-ticketlisttransactions Chris
[rt-users] How to add last comment to ticket query results?
I've been asked to add another column to a query which shows the last comment added to a ticket, any ideas how I can do this? Thanks, Ewan
