Re: [rt-users] Slow Ticket History 3.8.8

2010-09-06 Thread Jeffrey Fearn
Hi Justin, I've recently been using siege to bash on RT, and have been 
testing the following two settings in our RT_SiteConfig.pm


Set($UseSQLForACLChecks, 1);
Set($WebExternalAuthContinuous, 0);

The combined effect has been a serious reduction in rendering speed in 
general, and particularly so for long tickets.


Cheers, Jeff.

RT Training in Washington DC, USA on Oct 25  26 2010
Last one this year -- Learn how to get the most out of RT!


Re: [rt-users] Install on CentOS, best current instructions

2010-08-08 Thread Jeffrey Fearn

Howard Jones wrote:

 On 06/08/2010 19:09, Jerrad Pierce wrote:

Install from source, with a non-system perl.

Why non-system perl, Jerrad? I've never had a problem with it (that I 
know of), but have I just been lucky?


My only RPM-related problem is having to reinstall a current version of 
Sys::Syslog after every yum update (anyone know why that happens?)


You are over writing files supplied by the perl package.

$ rpm -q --whatprovides 'perl(Sys::Syslog)'
perl-5.8.8-32.el5_5.1

When the perl package gets updated, RPM compares the checksums of the 
installed files to those in the new package, detects the checksums don't 
match, and installs the files from the new package over the existing ones.


This is correct behavior and the only sane way a package manager can 
operate.


Furthermore if you run a verify over your file system errors will be 
reported since the files installed do not match the checksums from the 
RPM, so you've made your system unverifiable. Probably not a great 
tragedy, but something you should avoid unless you have a very 
persuasive argument.


It's trivial to avoid this if you use RPM. You can either roll your own 
spec file or use cpanspec to do the heavy lifting for you. I use cpanspec.


1: install the cpanspec package (on your development box eh)

2: cpanspec Sys::Syslog

3: edit perl-Sys-Syslog.spec as below

4: rpmbuild -ba  --define _sourcedir `pwd` --define _builddir `pwd` 
--define _srcrpmdir `pwd` --define _rpmdir `pwd` perl-Sys-Syslog.spec


5: install the RPM where required, or setup a yum repo

All the --defines aren't strictly required, but it forces rpmbuild to 
use the current directory and that's generally where I want the RPMs to 
end up.


### spec file edits ###

%build
# add INSTALLVENDORMAN3DIR
%{__perl} Makefile.PL INSTALLDIRS=vendor OPTIMIZE=$RPM_OPT_FLAGS 
INSTALLVENDORMAN3DIR=/usr/local/share/man/man3


...

%files
%defattr(-,root,root,-)
%doc Changes README README.win32
%{perl_vendorarch}/auto/*
%{perl_vendorarch}/Sys*
# change man path
/usr/local/share/man/man3/*

### end spec file edits ###

Since vendor is searched before core, the new module gets found first. 
Since the files are on a different path to the ones in the perl package 
they won't get affected when perl updates.


If you are having a clash in vendor, use site instead, which is even 
earlier in the perl path.


Easy!

Cheers, Jeff.

--
Jeff Fearn jfe...@redhat.com
Software Engineer
Engineering Operations
Red Hat, Inc
Freedom ... courage ... Commitment ... ACCOUNTABILITY

Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com


[rt-users] GPG issue on RHEL5 + RT 3.8.7

2010-04-22 Thread Jeffrey Fearn
Hi, I'm testing the GPG stuff on RHEL5 + RT 3.8.7, mainly for signature 
verification, but I'm getting the following error:


Apr 22 16:53:01 rt-stage RT: logger for 'd...@exampls.com': gpg: error 
reading key: public key not found 
(/usr/lib/perl5/vendor_perl/5.8.8/RT/Crypt/GnuPG.pm:2077)


I added the logger for 'd...@exampls.com': string just to make sure 
the email was being set properly.


RT_SiteConfig settings:

Set( %GnuPG,
Enable = 1,
OutgoingMessagesFormat = 'RFC', # Inline
AllowEncryptDataInDB   = 0,
RejectOnMissingPrivateKey = 1,
RejectOnBadData   = 1,
);

Set(%GnuPGOptions,
'no-permission-warning' = undef,
homedir = '/usr/share/rt3/gpg',
);

Set(@Plugins,(qw( RT::Interface::Email::Auth::MailFrom 
RT::Interface::Email::Auth::GnuPG )));


I don't get any other errors from GnuPG, so I'm pretty sure it's all 
configured properly.


I find a public key if I run gpg on the command line:

gpg --no-permission-warning --homedir=/usr/share/rt3/gpg 
--list-public-keys d...@example.com

pub   1024D/684EFF04 2010-01-18
uid  Dude d...@example.com
sub   2048g/FFE5A290 2010-01-18

Any help, much appreciated.

Here is the module list installed.

Perl v5.8.8 under linux
  Apache2::CmdParms v2.04;
  Apache2::Const v2.04;
  Apache2::Directive v2.04;
  Apache2::Log v2.04;
  Apache2::PerlSections v2.00;
  Apache2::RequestIO v2.04;
  Apache2::RequestRec v2.04;
  Apache2::RequestUtil v2.04;
  Apache2::Response v2.04;
  Apache2::ServerRec v2.04;
  Apache2::ServerUtil v2.04;
  Apache2::Status v4.00;
  Apache::DB v0.14;
  Apache::DProf v0.08;
  Apache::Session v1.86;
  Apache::Session::Generate::MD5 v2.1;
  Apache::Session::Lock::MySQL v1.01;
  Apache::Session::MySQL v1.01;
  Apache::Session::Serialize::Storable v1.01;
  Apache::Session::Store::DBI v1.02;
  Apache::Session::Store::MySQL v1.04;
  APR v0.009000;
  APR::Pool v0.009000;
  APR::Table v0.009000;
  AutoLoader v5.60;
  base v2.07;
  bytes v1.02;
  Cache::Simple::TimedExpiry v0.27;
  Carp v1.04;
  CGI v3.15;
  CGI::Cookie v1.26;
  CGI::Util v1.5;
  Class::Accessor v0.31;
  Class::Accessor::Fast v0.31;
  Class::Container v0.12;
  Class::Data::Inheritable v0.08;
  Class::Inspector v1.21_01;
  Class::ISA v0.33;
  Class::MethodMaker v2.08;
  Class::MethodMaker::Engine v2.08;
  Class::ReturnValue v0.55;
  Class::Struct v0.63;
  Clone v0.27;
  constant v1.05;
  Cwd v3.12;
  Data::Dumper v2.121_08;
  Date::Format v2.22;
  Date::Parse v2.27;
  DateTime v0.4304;
  DateTime::Locale v0.41;
  DateTime::TimeZone v0.7904;
  DateTime::TimeZone::Floating v0.01;
  DateTime::TimeZone::Local v0.01;
  DateTime::TimeZone::OffsetOnly v0.02;
  DateTime::TimeZone::UTC v0.01;
  DBD::mysql v4.008;
  DBI v1.52;
  DBIx::SearchBuilder v1.56;
  DBIx::SearchBuilder::Union v0;
  DBIx::SearchBuilder::Unique v0.01;
  Devel::StackTrace v1.22;
  Devel::StackTraceFrame v1.22;
  Digest::base v1.00;
  Digest::MD5 v2.36;
  DynaLoader v1.05;
  Email::Address v1.889;
  Encode v2.37;
  Encode::Alias v2.12;
  Encode::Config v2.05;
  Encode::Encoding v2.05;
  English v1.02;
  Errno v1.0901;
  Exception::Class v1.26;
  Exception::Class::Base v1.2;
  Exporter v5.58;
  Exporter::Heavy v5.58;
  Fatal v1.03;
  Fcntl v1.05;
  File::Basename v2.74;
  File::Glob v1.05;
  File::Path v1.08;
  File::ShareDir v1.00;
  File::Spec v3.12;
  File::Spec::Unix v1.5;
  File::Temp v0.22;
  FileHandle v2.01;
  GD v2.41;
  GD::Image v2.27;
  GnuPG::Interface v0.33;
  GraphViz v2.03;
  HTML::Element v3.23;
  HTML::Entities v1.35;
  HTML::Formatter v2.04;
  HTML::FormatText v2.04;
  HTML::Mason v1.40;
  HTML::Mason::ApacheHandler v1.69;
  HTML::Mason::Exception v1.1;
  HTML::Mason::Exception::Abort v1.1;
  HTML::Mason::Exception::Compilation v1.1;
  HTML::Mason::Exception::Compilation::IncompatibleCompiler v1.1;
  HTML::Mason::Exception::Compiler v1.1;
  HTML::Mason::Exception::Decline v1.1;
  HTML::Mason::Exception::Params v1.1;
  HTML::Mason::Exception::Syntax v1.1;
  HTML::Mason::Exception::System v1.1;
  HTML::Mason::Exception::TopLevelNotFound v1.1;
  HTML::Mason::Exception::VirtualMethod v1.1;
  HTML::Mason::Exceptions v1.43;
  HTML::Parser v3.55;
  HTML::Scrubber v0.08;
  HTML::Tagset v3.10;
  HTML::TreeBuilder v3.23;
  I18N::LangTags v0.35;
  I18N::LangTags::Detect v1.03;
  integer v1.00;
  IO v1.22;
  IO::File v1.13;
  IO::Handle v1.25;
  IO::InnerFile v2.110;
  IO::Lines v2.110;
  IO::ScalarArray v2.110;
  IO::Seekable v1.1;
  IO::WrapTie v2.110;
  IPC::Open2 v1.02;
  IPC::Open3 v1.02;
  IPC::Run v0.80;
  List::MoreUtils v0.22;
  List::Util v1.21;
  Locale::Maketext v1.09;
  Locale::Maketext::Fuzzy v0.10;
  Locale::Maketext::Lexicon v0.62;
  Locale::Maketext::Lexicon::Gettext v0.15;
  Log::Dispatch v2.20;
  Log::Dispatch::Base v1.09;
  Log::Dispatch::File v1.22;
  Log::Dispatch::Output v1.26;
  Log::Dispatch::Screen v1.17;
  Log::Dispatch::Syslog v1.18;
  Mail::Address v2.04;
  Mail::Field v2.04;
  Mail::Field::AddrList v2.04;
  

Re: [rt-users] GPG issue on RHEL5 + RT 3.8.7

2010-04-22 Thread Jeffrey Fearn

Jeffrey Fearn wrote:
Hi, I'm testing the GPG stuff on RHEL5 + RT 3.8.7, mainly for signature 
verification, but I'm getting the following error:


Apr 22 16:53:01 rt-stage RT: logger for 'd...@exampls.com': gpg: error 
reading key: public key not found 
(/usr/lib/perl5/vendor_perl/5.8.8/RT/Crypt/GnuPG.pm:2077)


I added the logger for 'd...@exampls.com': string just to make sure 
the email was being set properly.


Just a note that the email address got munged hiding the real one used, 
it matches on the server :}


Cheers, Jeff.

Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com


Re: [rt-users] GPG issue on RHEL5 + RT 3.8.7

2010-04-22 Thread Jeffrey Fearn
Hi Ruslan, thanks for the input ... sigh ... it's more stupid than 
this though. There was a fake user created with a typo in the user name, 
and I was checking the typo account instead of the real account ... _ 
... works fine when you check the right account!


Cheers, Jeff.

Ruslan Zakirov wrote:

Also, I think it may be trust level of the key. RT doesn't force any
trust levels and you have to maintain it yourself or use always
trust mode.

On Fri, Apr 23, 2010 at 12:04 AM, Ruslan Zakirov
ruslan.zaki...@gmail.com wrote:

Jeffrey,

Can you enable debug logging and send us more info from the log? GnuPG
is quiet noisy.

On Thu, Apr 22, 2010 at 11:22 AM, Jeffrey Fearn jfe...@redhat.com wrote:

Jeffrey Fearn wrote:

Hi, I'm testing the GPG stuff on RHEL5 + RT 3.8.7, mainly for signature
verification, but I'm getting the following error:

Apr 22 16:53:01 rt-stage RT: logger for 'd...@exampls.com': gpg: error
reading key: public key not found
(/usr/lib/perl5/vendor_perl/5.8.8/RT/Crypt/GnuPG.pm:2077)

I added the logger for 'd...@exampls.com': string just to make sure the
email was being set properly.

Just a note that the email address got munged hiding the real one used, it
matches on the server :}

Cheers, Jeff.

Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com




--
Best regards, Ruslan.








--
Jeff Fearn jfe...@redhat.com
Software Engineer
Engineering Operations
Red Hat, Inc
Freedom ... courage ... Commitment ... ACCOUNTABILITY

Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com


Re: [rt-users] Possible Exchange Issue

2010-04-22 Thread Jeffrey Fearn

Brian Tinsley wrote:

Hi,

 

I am responsible for a pricing email box. I get and receive emails into 
this email box. I also get my normal email in my standard inbox.



What happens is that I can not send from my x5quo...@x5solutions.com 
mailto:x5quo...@x5solutions.com email box to r...@x5solutions.com 
mailto:r...@x5solutions.com. It does not open a new ticket. Nor can I 
reply to a ticket that I created inside RT, for instance, I have an 
existing ticket and if I reply to it from my x5quo...@x5solutions.com 
mailto:x5quo...@x5solutions.com email, it doesn’t update the ticket. 
Yet if I reply to it from my inbox, btins...@x5solutions.com 
mailto:btins...@x5solutions.com, it works.


 


 RE: [[quotes] #474] AutoReply: Shawn-N042210-Burlington PRI

 

I need to keep this separate and get it to work from the 
x5quo...@x5solutions.com mailto:x5quo...@x5solutions.com email box. 
Does anyone have any suggestions on what might be wrong?


First thing that comes to mind is it's being filtered out in the mail 
loop check. What is $RTAddressRegexp set to in RT_SiteConfig.pm?


Another issue is that a lot of our tickets that are created in up in a 
general que and we’d like to be able to view that and be able to assign 
them.


Not sure what you mean by this.

Cheers, Jeff.

--
Jeff Fearn jfe...@redhat.com
Software Engineer
Engineering Operations
Red Hat, Inc
Freedom ... courage ... Commitment ... ACCOUNTABILITY

Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com