Re: [rt-users] Don't close tickets (or re-open) if a specific custom field is not a specific value
Am 24.10.2012 16:15, schrieb Holger Haase:
Hi all,
I searched (Google/wiki/nabble/...) and tried for several hours now. Nothing
worked.
I have to make sure tha a ticket can only be closed if a custom field (or
maybe transaction custom field) has a specific value.
I have more than one queue and this should not happen globaly but in several
queues.
Is there any way to do this?
Thank you so much for your help in advance,
Holger
Final RT training for 2012 in Atlanta, GA - October 23 24
http://bestpractical.com/training
We're hiring! http://bestpractical.com/jobs
Hi Holger,
You can use a global scrip with an queue filter like this (scrip not
tested):
Condition: On Resolve
Action: User Defined
Template: Global template: Blank
Stage: TransactionCreate
Custom action preparation code:
my @queue_list = qw(Queue1 Queue2);
my $ticket = $self-TicketObj;
my $queue = $ticket-QueueObj;
my $queue_name = $queue-Name;
return 0 unless grep /$queue_name/, @queue_list ;
return 0 if $ticket-FirstCustomFieldValue('YourCfName');
return 1;
Custom action cleanup code:
$self-TicketObj-SetStatus('open');
return 1;
Chris
Final RT training for 2012 in Atlanta, GA - October 23 24
http://bestpractical.com/training
We're hiring! http://bestpractical.com/jobs
Re: [rt-users] Don't close tickets (or re-open) if a specific custom field is not a specific value
Or you can use html callbacks to dismiss changes before sending them to scrips - just after user click Submit - you can check CF value and in case of error trigger Abort(Error message). This will show notification to client that his changes were discarded. On Wed, Oct 24, 2012 at 4:15 PM, Holger Haase holger.ha...@stepstone.dewrote: Hi all, I searched (Google/wiki/nabble/...) and tried for several hours now. Nothing worked. I have to make sure tha a ticket can only be closed if a custom field (or maybe transaction custom field) has a specific value. I have more than one queue and this should not happen globaly but in several queues. Is there any way to do this? Thank you so much for your help in advance, Holger Final RT training for 2012 in Atlanta, GA - October 23 24 http://bestpractical.com/training We're hiring! http://bestpractical.com/jobs -- Jack Zabolotnyi Arces Network, LLC e: jzabolot...@arces.net w: http://www.arces.net PGP key: 2048R/7F2AB658 2012-07-02 PGP fingerprint: 4C7E 00A8 5210 F3D9 0509 C70E 87C8 666E 7F2A B658 Final RT training for 2012 in Atlanta, GA - October 23 24 http://bestpractical.com/training We're hiring! http://bestpractical.com/jobs
Re: [rt-users] Don't close tickets (or re-open) if a specific custom field is not a specific value
Great, this did the trick! Many thanks to Christian Loos!
Best regards,
Holger
-Ursprüngliche Nachricht-
Von: Loos, Christian [mailto:cl...@netcologne.de]
Gesendet: Donnerstag, 25. Oktober 2012 12:01
An: Holger Haase
Cc: rt-users@lists.bestpractical.com
Betreff: AW: Don't close tickets (or re-open) if a specific custom field is not
a specific value
Hi Holger,
your Custom action preparation code must look like this:
my @queue_list = qw(second_level);
my $ticket = $self-TicketObj;
my $queue = $ticket-QueueObj;
my $queue_name = $queue-Name;
return 0 unless grep /$queue_name/, @queue_list ; return 0 if
$ticket-FirstCustomFieldValue('AssetTag');
return 1;
This *must* be an global script. It only runs if the ticket queue is in the
@queue_list array.
Chris
Christian Loos
Network Documentation Fibre Management
_
NETCOLOGNE Gesellschaft für Telekommunikation mbH
Am Coloneum 9 | 50829 Köln
Tel: 0221 -276 | Fax: 0221 -7276 | Mobil: 0177 276
www.netcologne.de
Geschäftsführer:
Dr. Hans Konle (Sprecher)
Dipl.-Ing. Karl-Heinz Zankel
Vorsitzender des Aufsichtsrates:
Dr. Andreas Cerbe
HRB 25580, AG Köln
Diese Nachricht (inklusive aller Anhänge) ist vertraulich. Sollten Sie diese
Nachricht versehentlich erhalten haben, bitten wir, den Absender (durch
Antwort-E-Mail) hiervon unverzüglich zu informieren und die Nachricht zu
löschen. Die E-Mail darf in diesem Fall weder vervielfältigt noch in anderer
Weise verwendet werden.
-Ursprüngliche Nachricht-
Von: Holger Haase [mailto:holger.ha...@stepstone.de]
Gesendet: Donnerstag, 25. Oktober 2012 11:21
An: Loos, Christian
Betreff: AW: Don't close tickets (or re-open) if a specific custom field is not
a specific value
Hi Christian,
Many thanks for your fast answer!
It must be a global scrip?
So if the queue where it should happen is named second_level it should look
like this, right?
___
Condition: On Resolve
Action: User Defined
Template: Global template: Blank
Stage: TransactionCreate
Custom action preparation code:
my @queue_list = qw(first level second_level third_level); my $ticket =
$self-TicketObj; my $queue = $ticket-QueueObj; my $queue_name = $queue-Name;
return 0 unless grep /$second_level/, @queue_list ; return 0 if
$ticket-FirstCustomFieldValue('AssetTag');
return 1;
Custom action cleanup code:
$self-TicketObj-SetStatus('re-opened');
return 1;
Thanks/Danke
Holger
Final RT training for 2012 in Atlanta, GA - October 23 24
http://bestpractical.com/training
We're hiring! http://bestpractical.com/jobs
[rt-users] RES: Strange CLI Date Output
Folow: root@rt:~# locale LANG=pt_BR.ISO-88591 LANGUAGE= LC_CTYPE=pt_BR.ISO-88591 LC_NUMERIC=pt_BR.ISO-88591 LC_TIME=pt_BR.ISO-88591 LC_COLLATE=pt_BR.ISO-88591 LC_MONETARY=pt_BR.ISO-88591 LC_MESSAGES=pt_BR.ISO-88591 LC_PAPER=pt_BR.ISO-88591 LC_NAME=pt_BR.ISO-88591 LC_ADDRESS=pt_BR.ISO-88591 LC_TELEPHONE=pt_BR.ISO-88591 LC_MEASUREMENT=pt_BR.ISO-88591 LC_IDENTIFICATION=pt_BR.ISO-88591 LC_ALL=pt_BR.ISO-88591 About user date format: Use system default (Thu Oct 25 13:59:03 2012) About RT_SiteConfig.pm No DateTimeFormat. -Mensagem original- De: rt-users-boun...@lists.bestpractical.com [mailto:rt-users-boun...@lists.bestpractical.com] Em nome de Kevin Falcone Enviada em: quinta-feira, 25 de outubro de 2012 01:15 Para: rt-users@lists.bestpractical.com Assunto: Re: [rt-users] Strange CLI Date Output On Tue, Oct 23, 2012 at 05:24:19PM +, Diaulas Castro wrote: Hello RT friends, I got this problem and cant resolve, i cant even locate when started. My CLI started to output errors about ParseDate, but just some tickets, see below: Tickets 770,1070 and 3070 are OK, displaying relative date (7mth, 3mth) Ticket 2070 with error, displaying parsedate error. I'd be curious to know if you have LC_DATE set to something and what you've chosen as your DateTimeFormat in RT_SiteConfig.pm or in your user preferences. -kevin root@rt:~# rt ls 770 Query:id=770 Ticket Owner QueueAge Told Status Requestor Subject 770 jose. hsr 7 mth 7 mth resolv leandro.v Ativação de Job root@rt:~# rt ls 2070 Query:id=2070 Ticket Owner QueueAge Told Status Requestor Subject -- -- Unknown date format in parsedate: Sex Maio 11 15:54:49 2012 Unknown date format in parsedate: Ter Maio 15 17:55:18 2012 2070 hugo. h9j?????? resolv luciano.c Exclusão de host SIGMon root@rt:~# rt ls 1070 Query:id=1070 Ticket Owner QueueAge Told Status Requestor Subject 1070 diaul saude 7 mth 7 mth resolv mirley.ti Verificacao de download e link root@rt:~# rt ls 3070 Query:id=3070 Ticket Owner QueueAge Told Status Requestor Subject 3070 nelso cardi 3 mth 3 mth resolv sistemas@ Dump Final RT training for 2012 in Atlanta, GA - October 23 24 http://bestpractical.com/training We're hiring! http://bestpractical.com/jobs
Re: [rt-users] Error When Upgrade-Database from 3.8.1 to 3.8.2
Hi I ran the upgrade the first time as you indicated just let it run from 3.2.2 to 4.0.7, and that failed as well. So I went back through the docs and the was a step that stated to stop after 3.8.7. Cynthia Roe CRoe Photography (732) 882-6079 http://croephotography.com On Oct 24, 2012, at 10:58 PM, Kevin Falcone falc...@bestpractical.com wrote: On Mon, Oct 22, 2012 at 05:13:57PM -0400, Cynthia Roe wrote: I am in the process of upgrade our RT environment from 3.2.2 to 4.0.7. So far I have been able to upgrade successfully from 3.2.2 to 3.8.1. However, when I run the $ make upgrade-database from 3.8.1 to 3.8.2 I received the following error: Is there a particular reason that you're going one upgrade at a time? We wrote the make upgrade-database command to make running them all much easier than it ever was in older versions. In this case, the problem is that RT's code expects the ACL table to have a Creator field, but the 3.8.2 upgrade is run before the schema change. We actually have code to handle this and if you let it just run from 3.8.1 - 4.0.6 instead of taking single steps, it will complete correctly. There's a bug that it only looks for our special backcompat file in the versions of the upgrade you specified, and we should fix that, but I'm not sure why you're running the upgrade in single steps instead of just letting it go and only revisiting it if something fails? I've filed a bug about this http://issues.bestpractical.com/Ticket/Display.html?id=21317 -kevin $ make upgrade-database Enter RT version you're upgrading from: 3.8.1 Going to apply following upgrades: * 3.8.2 * 3.8.3 * 3.8.4 * 3.8.6 * 3.8.8 * 3.8.9 * 3.9.1 * 3.9.2 * 3.9.3 * 3.9.5 * 3.9.6 * 3.9.7 * 3.9.8 * 4.0.0rc2 * 4.0.0rc4 * 4.0.0rc7 * 4.0.1 * 4.0.3 * 4.0.4 * 4.0.6 Enter RT version if you want to stop upgrade at some point, or leave it blank if you want apply above upgrades: 3.8.2 Going to apply following upgrades: * 3.8.2 IT'S VERY IMPORTANT TO BACK UP BEFORE THIS STEP Proceed [y/N]:y Processing 3.8.2 Now inserting data. [Mon Oct 22 20:54:57 2012] [warning]: Going to add [OLD] prefix to all templates in approvals queue. If you have never used approvals, you can safely delete all the templates with the [OLD] prefix. Leave the new Approval templates because you may eventually want to start using approvals. (./etc/upgrade/3.8.2/content:3) [Mon Oct 22 20:54:58 2012] [warning]: DBD::mysql::st execute failed: Unknown column 'Creator' in 'field list' at /usr/local/share/perl5/DBIx/SearchBuilder/Handle.pm line 587. (/usr/local/share/perl5/DBIx/SearchBuilder/Handle.pm:587) Final RT training for 2012 in Atlanta, GA - October 23 24 http://bestpractical.com/training We're hiring! http://bestpractical.com/jobs Final RT training for 2012 in Atlanta, GA - October 23 24 http://bestpractical.com/training We're hiring! http://bestpractical.com/jobs
Re: [rt-users] Error When Upgrade-Database from 3.8.1 to 3.8.2
On Thu, Oct 25, 2012 at 10:03:51AM -0400, Rutgers Marine wrote: I ran the upgrade the first time as you indicated just let it run from 3.2.2 to 4.0.7, and that failed as well. So I went back through the docs and the was a step that stated to stop after 3.8.7. How did it fail? 3.8.2 isn't after 3.8.7 3.8.2 wouldn't fail if it had the backcompat files available. Please show the failure when you let it run. -kevin pgpVuKenjiBSM.pgp Description: PGP signature Final RT training for 2012 in Atlanta, GA - October 23 24 http://bestpractical.com/training We're hiring! http://bestpractical.com/jobs
[rt-users] Delete articles via CLI?
Hi all, Is there a way to delete articles (i.e. RTFM) via the command line? I couldn't find a way to do it with rt-shredder. I'm at 4.0.7 (just upgraded from 3.8.8 + RTFM). Thanks. -- Roy McMorran Systems Administrator MDI Biological Laboratory mcmor...@mdibl.org Final RT training for 2012 in Atlanta, GA - October 23 24 http://bestpractical.com/training We're hiring! http://bestpractical.com/jobs
[rt-users] RES: Strange CLI Date Output
Another item i checked, Made sql search on database and the fields are equal, justo on CLI I got parsedate error, on web interface all tickets display ok. -Mensagem original- De: Diaulas Castro Enviada em: quinta-feira, 25 de outubro de 2012 12:01 Para: rt-users@lists.bestpractical.com Assunto: RES: [rt-users] Strange CLI Date Output Folow: root@rt:~# locale LANG=pt_BR.ISO-88591 LANGUAGE= LC_CTYPE=pt_BR.ISO-88591 LC_NUMERIC=pt_BR.ISO-88591 LC_TIME=pt_BR.ISO-88591 LC_COLLATE=pt_BR.ISO-88591 LC_MONETARY=pt_BR.ISO-88591 LC_MESSAGES=pt_BR.ISO-88591 LC_PAPER=pt_BR.ISO-88591 LC_NAME=pt_BR.ISO-88591 LC_ADDRESS=pt_BR.ISO-88591 LC_TELEPHONE=pt_BR.ISO-88591 LC_MEASUREMENT=pt_BR.ISO-88591 LC_IDENTIFICATION=pt_BR.ISO-88591 LC_ALL=pt_BR.ISO-88591 About user date format: Use system default (Thu Oct 25 13:59:03 2012) About RT_SiteConfig.pm No DateTimeFormat. -Mensagem original- De: rt-users-boun...@lists.bestpractical.com [mailto:rt-users-boun...@lists.bestpractical.com] Em nome de Kevin Falcone Enviada em: quinta-feira, 25 de outubro de 2012 01:15 Para: rt-users@lists.bestpractical.com Assunto: Re: [rt-users] Strange CLI Date Output On Tue, Oct 23, 2012 at 05:24:19PM +, Diaulas Castro wrote: Hello RT friends, I got this problem and cant resolve, i cant even locate when started. My CLI started to output errors about ParseDate, but just some tickets, see below: Tickets 770,1070 and 3070 are OK, displaying relative date (7mth, 3mth) Ticket 2070 with error, displaying parsedate error. I'd be curious to know if you have LC_DATE set to something and what you've chosen as your DateTimeFormat in RT_SiteConfig.pm or in your user preferences. -kevin root@rt:~# rt ls 770 Query:id=770 Ticket Owner QueueAge Told Status Requestor Subject 770 jose. hsr 7 mth 7 mth resolv leandro.v Ativação de Job root@rt:~# rt ls 2070 Query:id=2070 Ticket Owner QueueAge Told Status Requestor Subject -- -- Unknown date format in parsedate: Sex Maio 11 15:54:49 2012 Unknown date format in parsedate: Ter Maio 15 17:55:18 2012 2070 hugo. h9j?????? resolv luciano.c Exclusão de host SIGMon root@rt:~# rt ls 1070 Query:id=1070 Ticket Owner QueueAge Told Status Requestor Subject 1070 diaul saude 7 mth 7 mth resolv mirley.ti Verificacao de download e link root@rt:~# rt ls 3070 Query:id=3070 Ticket Owner QueueAge Told Status Requestor Subject 3070 nelso cardi 3 mth 3 mth resolv sistemas@ Dump Final RT training for 2012 in Atlanta, GA - October 23 24 http://bestpractical.com/training We're hiring! http://bestpractical.com/jobs
[rt-users] /bin/mail instead of sendmail?
Hello list, Is it possible to use /bin/mail instead of sendmail? I already have a working authentication going with our exchange server using mail.rc, would prefer to just use /bin/mail for outgoing mail. Not having luck getting sendmail to route through the exchange server - everything bounces back. Thanks, William Final RT training for 2012 in Atlanta, GA - October 23 24 http://bestpractical.com/training We're hiring! http://bestpractical.com/jobs
Re: [rt-users] RES: Strange CLI Date Output
On Thu, Oct 25, 2012 at 04:12:27PM +, Diaulas Castro wrote: Another item i checked, Made sql search on database and the fields are equal, justo on CLI I got parsedate error, on web interface all tickets display ok. There's unlikely to be anything wrong in the database. root@rt:~# locale LANG=pt_BR.ISO-88591 LANGUAGE= LC_CTYPE=pt_BR.ISO-88591 LC_NUMERIC=pt_BR.ISO-88591 LC_TIME=pt_BR.ISO-88591 LC_COLLATE=pt_BR.ISO-88591 LC_MONETARY=pt_BR.ISO-88591 LC_MESSAGES=pt_BR.ISO-88591 LC_PAPER=pt_BR.ISO-88591 LC_NAME=pt_BR.ISO-88591 LC_ADDRESS=pt_BR.ISO-88591 LC_TELEPHONE=pt_BR.ISO-88591 LC_MEASUREMENT=pt_BR.ISO-88591 LC_IDENTIFICATION=pt_BR.ISO-88591 LC_ALL=pt_BR.ISO-88591 I asked about your locale settings because they're likely the source of the problem. bin/rt would have to know how to parse dates formatted in pt_BR and it does not. If you unset your LCs or set them all to C I bet you don't see the problem. Fixing this looks quite hard without bloating bin/rt -kevin pgpk5iMtnw4Gg.pgp Description: PGP signature Final RT training for 2012 in Atlanta, GA - October 23 24 http://bestpractical.com/training We're hiring! http://bestpractical.com/jobs
Re: [rt-users] Spreadsheet-esq Web Input
I just realized that there is a table button in the WYSIWYG. was thinking I could set a default ticket description as a table and do it that way. but it looks like the format isn't maintained (the email is plain text with each table cell as it's own line or mashed all on one line for history) so that won't work... had a few hits searching for request tracker grid but that looks like an output, not an input method. hmm... Final RT training for 2012 in Atlanta, GA - October 23 24 http://bestpractical.com/training We're hiring! http://bestpractical.com/jobs
[rt-users] [rt-announce] Security vulnerabilities in RT
We have determined a number of security vulnerabilities which affect both RT 3.8.x and RT 4.0.x. We are releasing RT versions 3.8.15 and 4.0.8, and RTFM version 2.4.5, to resolve these vulnerabilities, as well as patches which apply atop all released versions of 3.8 and 4.0. The vulnerabilities addressed by 3.8.15, 4.0.8, and the below patches include the following: All versions of RT are vulnerable to an email header injection attack. Users with ModifySelf or AdminUser can cause RT to add arbitrary headers or content to outgoing mail. Depending on the scrips that are configured, this may be be leveraged for information leakage or phishing. We have been assigned CVE-2012-4730 for this vulnerability; we would like to thank Scott MacVicar for bringing this matter to our attention. RT 4.0.0 and above and RTFM 2.0.0 and above contain a vulnerability due to lack of proper rights checking, allowing any privileged user to create Articles in any class. We have been assigned CVE-2012-4731 for this vulnerability. All versions of RT with cross-site-request forgery (CSRF) protection (RT 3.8.12 and above, RT 4.0.6 and above, and any instances running the security patches released 2012-05-22) contain a vulnerability which incorrectly allows though CSRF requests which toggle ticket bookmarks. We have been assigned CVE-2012-4732 for this vulnerability; we would like to thank Matthew Astley for bringing this to our attention. Additionally, all versions of RT are vulnerable to a confused deputy attack on the user. While not strictly a CSRF attack, users who are not logged in who are tricked into following a malicious link may, after supplying their credentials, be subject to an attack which leverages their credentials to modify arbitrary state. While users who were logged in would have observed the CSRF protection page, users who were not logged in receive no such warning due to the intervening login process. RT has been extended to notify users of pending actions during the login process. We have been assigned CVE-2012-4734 for this vulnerability; we would like to thank Matthew Astley for bringing this to our attention. RT 3.8.0 and above are susceptible to a number of vulnerabilities concerning improper signing or encryption of messages using GnuPG; if GnuPG is not enabled, none of the following affect you. We have been assigned CVE-2012-4735 for the following related vulnerabilities: * When using GnuPG, RT now clarifies the concepts of signing for _integrity_ and signing for _authentication_, which are separate (and exclusive) concepts. Previously, enabling the Sign by default queue configuration began signing automatically-generated messages with the queue's key, in addition to defaulting emails sent from the web UI to being signed. This provides integrity, but causes emails signed with that key to no longer possess authenticity; no individual email is guaranteed to have come from an actor designated to act for that key, in the case of automatically-generated emails. RT has now changed the Sign by default checkbox to merely provide a default in the web UI when composing messages; it no longer affects automatically-generated outgoing messages. Thus the Sign by default option helps to provide _authenticity_. A separate queue configuration option, Sign all auto-generated mail (defaulting to off) now controls the signing of automatically- generated emails, which (when used in combination with the previous option) helps provide _integrity_ of all outgoing messages. Users who had previously checked Sign by default and who wish to maintain the previous effect of integrity but not authenticity will need to enable the new option as well. We would like to thank Matthijs Melissen (University of Luxembourg) for bringing this matter to our attention. * RT 3.8.0 and above contain a vulnerability which allows incoming emails to force all triggered outgoing mail to be signed and/or encrypted. * RT 3.8.0 and above contain a vulnerability which allows incoming emails to incorrectly appear in the UI to have been encrypted when they had not been. This vulnerability only applies to encryption, not signing. * RT 3.8.0 and above contain a vulnerability which allows any user who is capable of sending signed email in the UI to do so using any secret key stored in RT's keyring. Additionally, RT 3.8.0 and above contain a vulnerability which allows a user to pass arbitrary arguments to the command-line GnuPG client, which could be leveraged to create arbitrary files on disk with the permissions of the webserver. This vulnerability only applies if GnuPG is enabled, and does _not_ allow for execution of programs other than the command-line GnuPG client. We have been assigned CVE-2012-4884 for this vulnerability. If you are running 3.8.x and RTFM, you will need to install RTFM 2.4.5 to resolve
[rt-users] [rt-announce] RT 4.0.8 Released
RT 4.0.8 contains important security fixes, in addition to bugfixes. http://download.bestpractical.com/pub/rt/release/rt-4.0.8.tar.gz http://download.bestpractical.com/pub/rt/release/rt-4.0.8.tar.gz.sig SHA1 sums 7be074e86929c69b4f17d10503646ff070f7fa3b rt-4.0.8.tar.gz 7ee1ecf25a99472d0d75665ed577941cb94c64e7 rt-4.0.8.tar.gz.sig This release, in addition to being a bugfix release, also resolves a number of security vulnerabilities. It resolves CVE-2012-4730, CVE-2012-4731, CVE-2012-4732, CVE-2012-4734, CVE-2012-4735, and CVE-2012-4884. Bugfixes * Custom Fields BasedOn can be set from intialdata again. * Fix the 3.8.4 NotifyGroup upgrade script to properly join notification groups with a comma. * Correct the use of the 'approved' state from Lifecycles. It is now used only when all approvals are completed. * Use database-level row locking to ensure that scrips do not suffer from race conditions with scrips from other processes. * Remove multiple slashes so that page menus display and the active item is correctly highlighted. * Improve MaxAttachmentSize documentation. * Ensure that ticket links in the iCal feed are CSRF whitelisted. Features * New alias validator sbin/rt-validate-aliases which helps keep RT and /etc/aliases in sync. * Add support for GPG mails in inline format (PGP partitioned encoding) that are also encoded for transfer with Base64 or quoted printable. * Add a BeforeLocalization callback to message headers. * If you have DBIx::SearchBuilder 1.62 or higher and are using full text indexing on Pg or Oracle, rt-fulltext-indexer uses a faster query to find unindexed attachments. Developer * Add rt-apache for running a test instance of apache. * Add the rt-static-docs tool for generating HTML versions of our docs. A complete changelog is available from git by running git log rt-4.0.7..rt-4.0.8 or visiting https://github.com/bestpractical/rt/compare/rt-4.0.7...rt-4.0.8 - Alex ___ rt-announce mailing list rt-annou...@lists.bestpractical.com http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-announce Final RT training for 2012 in Atlanta, GA - October 23 24 http://bestpractical.com/training We're hiring! http://bestpractical.com/jobs
[rt-users] [rt-announce] RT 3.8.15 Released
This release of RT contains important security updates. You can download it from: http://download.bestpractical.com/pub/rt/release/rt-3.8.15.tar.gz http://download.bestpractical.com/pub/rt/release/rt-3.8.15.tar.gz.sig SHA1 sums abb7b0d52cb9843e3154aeff2490211ddcdc59b8 rt-3.8.15.tar.gz 9401cdd429565b99dd45c99e20d5d36ac8d0fe4c rt-3.8.15.tar.gz.sig This release resolves a number of security vulnerabilities. It resolves CVE-2012-4730, CVE-2012-4732, CVE-2012-4734, CVE-2012-4735, and CVE-2012-4884. In addition to these security fixes, RT 3.8.15 contains support for partitioned PGP messages. - Alex ___ rt-announce mailing list rt-annou...@lists.bestpractical.com http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-announce Final RT training for 2012 in Atlanta, GA - October 23 24 http://bestpractical.com/training We're hiring! http://bestpractical.com/jobs
[rt-users] [rt-announce] RTFM 2.4.5 Released
RTFM 2.4.5 contains important security fixes. http://download.bestpractical.com/pub/rt/release/rtfm-2.4.5.tar.gz http://download.bestpractical.com/pub/rt/release/rtfm-2.4.5.tar.gz.sig SHA1 sums 96c9800bf1eee94a5dd9978400a7cba8d9594b29 RTFM-2.4.5.tar.gz 1f136d9f047164d72c1cf3e0bd64839804fc49ae RTFM-2.4.5.tar.gz.asc This release resolves CVE-2012-4731. - Alex ___ rt-announce mailing list rt-annou...@lists.bestpractical.com http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-announce Final RT training for 2012 in Atlanta, GA - October 23 24 http://bestpractical.com/training We're hiring! http://bestpractical.com/jobs
Re: [rt-users] Apache taking up too much CPU
Hi Kevin, On Thu, Oct 04, 2012 at 07:33:44PM +1000, Bhowmik Shah wrote: Yep, debugging for both RT and Apache is enabled, the logs don't throw * up* anything out of the ordinary. I've got Perl 5.14.2 installed. I'm currently playing with strace and the Apache process to see if i can spot whats going wrong. I've tried stuff from the Performance Tuning page on the Wiki and though the Mason caching parameters improved performance but the problem still persists. 1) Ubuntu 12.04 with 613MB RAM That is a tiny amount of RAM, especially if you're running your database on the same host. Are you sure you aren't swapping and burning *CPU* doing that? Yep, i don't see any swapping happening, I also don't expect a large amount of users (Maximum 5 at any given time) and we only have 19 entries in the database so far. The database is on the same host. We are expecting about 1200 tickets at max per year for the current set up. I would've thought that RT would be able to manage that much load with 613 MB or RAM. How much RAM do you think I would need for a setup like this? I have just switched over Apache from Worker to Prefork to see if that makes any difference. -bhowmik -kevin We're hiring! http://bestpractical.com/jobs
