Re: [rt-users] RT version 3.8.0 and RT-Authen-ExternalAuth-0.05
I know Mike Peachy hasn't had any time to look at this, but is there anyone who's got RT-Authen-ExternalAuth working with RT 3.8.x with LDAP (Sun Directory Service)? I wasn't sure if RT-Authen-ExternalAuth is either totally not working with 3.8.x, or working in some cases? After an upgrade from 3.6.6 LDAP authentication is not working here, but if there is no chance of it working I won't waste my time playing with the configuration and push back the upgrade to 3.8.x. Best regards, Justin Mike Peachey wrote: The primary problem here is that I haven't yet had enough available time to even run RT3.8 and so haven't yet got around to making the necessary modifications to ExternalAuth to make it properly compatible with 3.8. I will though, when I can. ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] Rt at Glance and upgrade from 3.2.1 to 3.8.0
d tbsky wrote: hi: your upgrade procedure is like what i did, which is wrong. if you use mysql, you should run the mysql upgrade script first, then run the rt upgrade script. or you will get empty RT at glance page. Thanks very much, So, trying to follow directions posted in thread : RT at a Glance HASH ref error during upgrade from 3.4 to 3.8, I am reloading my RT 3.2.1/mysql 4.0.20 database in the new RT 3.8.0/mysql 5.0.45. to do again the upgrade procedure. If I understood well, steps are : a) save DB on old server : mysqldump -u rt_user -p xxx --single-transaction --databases rt3 dump b) reload DB on new server : mysql -u root -p dump c) launch mysql upgrade script : etc/upgrade/schema.mysql-4.0-4.1.pl d) update the schema (I suppose the best is with the following) : /opt/rt3/sbin/rt-setup-database --dba root --prompt-for-dba-password --action upgrade Unfortunately the mysql upgrade script fails : [root]# perl rt-3.8.0/etc/upgrade/schema.mysql-4.0-4.1.pl rt3 rt_user x DBD::mysql::db column_info failed: column_info doesn't support column selection at rt-3.8.0/etc/upgrade/schema.mysql-4.0-4.1.pl line 227. DBD::mysql::db column_info failed: column_info doesn't support column selection at rt-3.8.0/etc/upgrade/schema.mysql-4.0-4.1.pl line 227. Also, I am not sure if I have to run this mysql update script ... I do not know what is the default Mysql character set in 4.0 and I do not know how to set it in the new Mysql 5.0... The systems both have locale set to en_US.UTF-8... Thanks for advices. JM -- Jean-michel BARBET| Tel: +33 (0)2 51 85 84 86 Laboratoire SUBATECH Nantes France| Fax: +33 (0)2 51 85 84 79 CNRS-IN2P3/Ecole des Mines/Universite | E-Mail: [EMAIL PROTECTED] ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
[rt-users] Locking accounts on password failure
Has anyone implemented locking accounts after so many login attempts? I'm sure I can add it myself but if there's a solution out there already. I'm using 3.6.3 Cheers, Justin ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] RT version 3.8.0 and RT-Authen-ExternalAuth-0.05
On 7 Aug 2008, at 10:45 am, [EMAIL PROTECTED] wrote: I know Mike Peachy hasn't had any time to look at this, but is there anyone who's got RT-Authen-ExternalAuth working with RT 3.8.x with LDAP (Sun Directory Service)? I wasn't sure if RT-Authen-ExternalAuth is either totally not working with 3.8.x, or working in some cases? I've found it works as far as LDAP authentication is concerned, but only if the account already exists within RT; in other words account autocreation isn't working. Tim -- The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE. ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] Install problem using a db server on a different host
Hello, Thank you! That solved the problem. I don't know how I missed the --with-db-rt-host variable, but I removed everything I had done (except perl modules - I'm not that stupid!) and started with the configure statement again - this time using the above variable. Everything went tickety-boo. The only thing I can think of is that I didn't read closely enough and assumed I had the db host setting taken care of with the --with-db-host. Duh. At any rate, thank you for the help and thanks to Best Practical for a wonderful product. Michael -Original Message- From: [EMAIL PROTECTED] [mailto:rt-users- [EMAIL PROTECTED] On Behalf Of Ruslan Zakirov Sent: Wednesday, August 06, 2008 6:45 PM To: [EMAIL PROTECTED] Cc: rt-users@lists.bestpractical.com Subject: Re: [rt-users] Install problem using a db server on a different host 1) check option --with-db-rt-host 2) try --enable-layout=RT3 Also want to note that you should run setup-database from dir where RT is installed. On Thu, Aug 7, 2008 at 3:22 AM, Michael Silver [EMAIL PROTECTED] wrote: Hello, I'm installing RT 3.8.0 on a CentOS box but using a mysql server on a different box. I've finished all the steps in the README up to the stage of doing make initialize-database. When I do that, it appears to be creating an ACL for my rt db user as [EMAIL PROTECTED] instead of [EMAIL PROTECTED] or [EMAIL PROTECTED] snip Michael Michael Silver, Network Administrator Parkland Regional Library 5404 56 Avenue Lacombe, AB T4L 1G1 Phone: 403.782.3850 [EMAIL PROTECTED] Fax: 403.782.4650 http://www.prl.ab.ca/ ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] RT-Users Digest, Vol 53, Issue 18
Date: Thu, 07 Aug 2008 16:50:47 +0200 From: Jean-Michel Barbet [EMAIL PROTECTED] Subject: Re: [rt-users] Rt at Glance and upgrade from 3.2.1 to 3.8.0 To: d tbsky [EMAIL PROTECTED] Cc: rt-users@lists.bestpractical.com Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-1; format=flowed d tbsky wrote: hi: your upgrade procedure is like what i did, which is wrong. if you use mysql, you should run the mysql upgrade script first, then run the rt upgrade script. or you will get empty RT at glance page. Thanks very much, So, trying to follow directions posted in thread : RT at a Glance HASH ref error during upgrade from 3.4 to 3.8, I am reloading my RT 3.2.1/mysql 4.0.20 database in the new RT 3.8.0/mysql 5.0.45. to do again the upgrade procedure. If I understood well, steps are : a) save DB on old server : mysqldump -u rt_user -p xxx --single-transaction --databases rt3 dump b) reload DB on new server : mysql -u root -p dump c) launch mysql upgrade script : etc/upgrade/schema.mysql-4.0-4.1.pl d) update the schema (I suppose the best is with the following) : /opt/rt3/sbin/rt-setup-database --dba root --prompt-for-dba-password --action upgrade Unfortunately the mysql upgrade script fails : [root]# perl rt-3.8.0/etc/upgrade/schema.mysql-4.0-4.1.pl rt3 rt_user x DBD::mysql::db column_info failed: column_info doesn't support column selection at rt-3.8.0/etc/upgrade/schema.mysql-4.0-4.1.pl line 227. DBD::mysql::db column_info failed: column_info doesn't support column selection at rt-3.8.0/etc/upgrade/schema.mysql-4.0-4.1.pl line 227. Also, I am not sure if I have to run this mysql update script ... I do not know what is the default Mysql character set in 4.0 and I do not know how to set it in the new Mysql 5.0... The systems both have locale set to en_US.UTF-8... Thanks for advices. JM Like a previous reply mentioned, it has to do with the DBD::mysql 3.x not supporting that method.. the 4.x does work. I believe this issue is addressed in the newer release candidates. Also I would be cautious with 4.007, it apparently introduced a bug that happens to a few people where the db connections timeout causing mod_perl/fastcgi etc to seg fault on each dead connection until it reconnects them. The cause of the bug i don't know the details 100% (I think broken keep-alive or something), but I basically downgraded back to the Debian packaged 3.x for stability. I heard 4.006 doesn't have the issue though. Curtis ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] [error] Can't call method crit
-Original Message- From: Ruslan Zakirov [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: RT-Users@lists.bestpractical.com Subject: Re: [rt-users] [error] Can't call method crit Date: Fri, 1 Aug 2008 04:42:45 +0400 By default no plugins are installed and desiable @Plugins option in your config. -- Is this related to why I get this error when using: # RT default Apache configuration Alias /rt/ /opt/rt3/share/html/ Directory /opt/rt3/share/html/ AllowOverride All Options ExecCGI FollowSymLinks Options Indexes FollowSymLinks IfModule mod_access.c Order allow,deny Allow from all /IfModule /Directory PerlRequire /opt/rt3/bin/webmux.pl Location /rt/ RewriteEngine On RedirectMatch permanent (.*)/$ $1/index.html AddDefaultCharset UTF-8 SetHandler perl-script PerlHandler RT::Mason /Location /var/log/apache2/error.log gives me this error. [Thu Aug 07 10:30:19 2008] [error] Can't call method crit on an undefined value at /opt/rt3/bin/../lib/RT.pm line 579.\nCompilation failed in require at (eval 2) line 1.\n [Thu Aug 07 10:30:19 2008] [error] Can't load Perl file: /opt/rt3/bin/webmux.pl for server PFServer7.pfsandiego.local:0, exiting... This is holding up using RT. -Adam ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
[rt-users] Minor Edit to Interface/Email.pm
(I don't have the original so I can't do a diff, but basically the
loop variable should (always) be my'ed to protect it from being
altered. There was a problem with the MailFrom plugin setting $_ and
then corrupting the loop varialbe!)
CUT---
# Since this needs loading, no matter what
foreach my $Class (@RT::MailPlugins) {
my ($Code, $NewAuthStat);
if ( ref($Class) eq CODE ) {
$Code = $Class;
} else {
$Class = RT::Interface::Email:: . $Class
unless $Class =~ /^RT::Interface::Email::/;
___
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] RT at a Glance HASH ref error during upgrade from 3.4 to 3.8
I think the following steps should make migration for you. NOTE FOR READERs: this is only correct for people migrating from 4.0 to 4.1 and newer. 1) when you do a mysqldump you don't need additional options, as mysql 4.0 has no --set-default-charset or --set-charset options, so use: mysqldump --opt rt3 rt3.mysql.dump or the following to gzip by the way mysqldump --opt rt3 | gzip rt3.mysql.dump.gz ok 2) Configure your mysql 4.1 or newer to use latin1 as default character set. I can not explain this, it will take too long. I checked mysql 5.0 documentation and it seems like latin1 is the default charset already? Is this correct? 3) You create new DB for RT in your mysql 4.1 or newer using RT thats this command rt-setup-database --action init --dba root --prompt-for-dba-password 4) You move the dump file to the server with mysql 4.1 or newer and restore data using mysql --set-default-charset=binary rt3.mysql.dump actually mysql --default-character-set=binary rt3.mysql.dump 5) You apply upgrade action on this new DB thats the 'rt-setup-database --action upgrade' command? 6) You apply commands generated by schema upgrade script ok I've seen differing reports and would like a definite answer on when upgrading whether you should do the 'rt-setup-database --action upgrade' command first or if you should do the mysql schema update first. I think I've covered all possibilities that can corrupt data during migration. Thanks, this has helped me a lot and I bet will help a lot other people out as well. ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] Filter::SpamAssassin
Sorry I forgot the extra s documentroot.com/SpamAssassin.pm - Erik On Thu, Aug 7, 2008 at 5:36 AM, Erik Aronesty [EMAIL PROTECTED] wrote: I made a version of Filter::SpamAssassin that works with the latest/greatest versions of both SpamAssassin and RT. http://www.documentroot.com/SpamAssasin.pm I didn't want to muck about with fetchmail, procmail or anything else to get it to work, and the version that was out there didn't seem to work at all... maybe some version of SpamAssassin grokked MIME:Entity - but not mine, as_string is safe though... should work for a long time. It supports the spamd daemon, which may or may not improve performance (but certainly allows some scalability) depending on how you implement your version of RT - Erik ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] Installation of RTFM 2.2.1 on RT 3.8.0 fails
Back in July, Cameron posted a message to the list regarding an installation problem. (See http://lists.bestpractical.com/pipermail/rt-users/2008-July/052816.html for his message.) As far as I can tell, there wasn't a response sent to the list, and I had a similar problem. I'm posting this in case my experience helps anyone else out. Thanks to Ruslan, I've now got a fresh working installation of RT 3.8.0. I went to install RTFM and ran into an issue with the initdb step. It returned Working with: Type: mysql Host: db01.prl.ab.ca Name: ref_ill_rt User: refrt DBA:refrt Now populating database schema. Couldn't finish 'schema' step. ERROR: Couldn't find schema file(s) '*' ...returned with error: 65280 make: *** [initdb] Error 255 I noticed that it was using the db-rt-user as both user and dba. The configure line for RT did specify the db-dba as root. I tried the refrt password, and it connected but returned the error above. (Using the root password with the above settings returned an access denied message as expected.) I then replaced the dba in the perl command line with root, but got the same error as above. I went hunting for the schema and found it in RTFM-2.2.1/etc/schema.mysql. So I cheated and ran mysql -h db01.prl.ab.ca -D ref_ill_rt -u root -p schema.mysql and it appears to have worked. The other line in the Makefile refers to acl, but the acl.mysql file says there aren't any changes needed in mysql for ACL so I didn't run it. Below is the complete run from perl Makefile.PL up to the error message in case it helps. Michael [EMAIL PROTECTED] RTFM-2.2.1]# perl Makefile.PL Using RT configurations from /opt/rt3/lib/RT.pm: ./bin = /opt/rt3/local/bin ./etc = /opt/rt3/local/etc/FM ./html = /opt/rt3/share/html ./lib = /opt/rt3/local/lib ./po= /opt/rt3/local/po/FM ./sbin = /opt/rt3/local/sbin For first-time installation, type 'make initdb'. *** Module::AutoInstall version 1.03 *** Checking for Perl dependencies... [Core Features] Cannot reliably compare non-decimal formatted versions. Please install version.pm or Sort::Versions. - RT...loaded. (3.8.0 = 3.4.2) - Text::WikiFormat ...loaded. (0.79) - Tree::Simple ...loaded. (1.18) - HTML::TreeBuilder ...loaded. (3.23) - Time::ParseDate ...loaded. (2006.0814) - HTML::FormatText ...loaded. (2.04) - YAML ...loaded. (0.66) *** Module::AutoInstall configuration finished. Open input '/root/RTFM-2.2.1/t/utils.pl' file for substitution Open output '/root/RTFM-2.2.1/t/utils.pl' file for substitution Writing Makefile for RTFM [EMAIL PROTECTED] RTFM-2.2.1]# make Manifying blib/man3/RT::FM::Topic_Overlay.3pm Manifying blib/man3/RT::FM::Article.3pm Manifying blib/man3/RT::FM::TopicCollection_Overlay.3pm Manifying blib/man3/RT::FM::ObjectTopic.3pm Manifying blib/man3/RT::FM::Record.3pm Manifying blib/man3/RT::FM::ObjectTopicCollection_Overlay.3pm Manifying blib/man3/RT::URI::fsck_com_rtfm.3pm Manifying blib/man3/RT::FM::Class.3pm Manifying blib/man3/RT::FM::ArticleCollection.3pm Manifying blib/man3/RT::URI::a.3pm Manifying blib/man3/RT::FM::Article_Overlay.3pm Manifying blib/man3/RT::FM::ObjectTopicCollection.3pm Manifying blib/man3/RT::FM::ClassCollection_Overlay.3pm Manifying blib/man3/RT::FM::ArticleCollection_Overlay.3pm Manifying blib/man3/RT::FM::Class_Overlay.3pm Manifying blib/man3/RT::FM::SearchBuilder.3pm Manifying blib/man3/RT::FM::TopicCollection.3pm Manifying blib/man3/RT::FM::Topic.3pm Manifying blib/man3/RT::FM::ClassCollection.3pm Manifying blib/man3/RT::FM::System.3pm [EMAIL PROTECTED] RTFM-2.2.1]# make install Writing /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi/auto/RTFM/.packli st Appending installation info to /usr/lib/perl5/5.8.8/i386-linux-thread-multi/perllocal.pod [EMAIL PROTECTED] RTFM-2.2.1]# make initdb /usr/bin/perl -Ilib -I/opt/rt3/local/lib -I/opt/rt3/lib /opt/rt3/sbin/rt-setup-database --action schema --datadir etc --datafile etc/initialdata --dba refrt --prompt-for-dba-password In order to create or update your RT database, this script needs to connect to your mysql instance on db01.prl.ab.ca as refrt Please specify that user's database password below. If the user has no database password, just press return. Password: Working with: Type: mysql Host: db01.prl.ab.ca Name: ref_ill_rt User: refrt DBA:refrt Now populating database schema. Couldn't finish 'schema' step. ERROR: Couldn't find schema file(s) '*' ...returned with error: 65280 make: *** [initdb] Error 255 ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] RT at a Glance HASH ref error during upgrade from 3.4 to 3.8
Ok, so I followed all these steps but I still have the same error on the RT at a glance page. Can't use string (BQYDAgQCAwQDAgoKTXkg) as a HASH ref while strict refs in use at /var/www/tickets01/share/html/Elements/MyRT line 76, line 505. Trying to change RT at a glance prefs also gives me the same error Can't use string (BQYDBAoEREVTQwVPcmRlcgpD) as a HASH ref while strict refs in use at /var/www/tickets01/share/html/Prefs/MyRT.html line 126, line 505. Anyone run into this before? From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Larry Han [EMAIL PROTECTED] Sent: Thursday, August 07, 2008 10:39 AM To: Ruslan Zakirov Cc: rt-users@lists.bestpractical.com Subject: Re: [rt-users] RT at a Glance HASH ref error during upgrade from 3.4 to 3.8 I think the following steps should make migration for you. NOTE FOR READERs: this is only correct for people migrating from 4.0 to 4.1 and newer. 1) when you do a mysqldump you don't need additional options, as mysql 4.0 has no --set-default-charset or --set-charset options, so use: mysqldump --opt rt3 rt3.mysql.dump or the following to gzip by the way mysqldump --opt rt3 | gzip rt3.mysql.dump.gz ok 2) Configure your mysql 4.1 or newer to use latin1 as default character set. I can not explain this, it will take too long. I checked mysql 5.0 documentation and it seems like latin1 is the default charset already? Is this correct? 3) You create new DB for RT in your mysql 4.1 or newer using RT thats this command rt-setup-database --action init --dba root --prompt-for-dba-password 4) You move the dump file to the server with mysql 4.1 or newer and restore data using mysql --set-default-charset=binary rt3.mysql.dump actually mysql --default-character-set=binary rt3.mysql.dump 5) You apply upgrade action on this new DB thats the 'rt-setup-database --action upgrade' command? 6) You apply commands generated by schema upgrade script ok I've seen differing reports and would like a definite answer on when upgrading whether you should do the 'rt-setup-database --action upgrade' command first or if you should do the mysql schema update first. I think I've covered all possibilities that can corrupt data during migration. Thanks, this has helped me a lot and I bet will help a lot other people out as well. ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] Installation of RTFM 2.2.1 on RT 3.8.0 fails
On Aug 7, 2008, at 2:21 PM, Michael Silver wrote: Back in July, Cameron posted a message to the list regarding an installation problem. (See http://lists.bestpractical.com/pipermail/rt-users/2008-July/ 052816.html for his message.) As far as I can tell, there wasn't a response sent to the list, and I had a similar problem. I'm posting this in case my experience helps anyone else out. There was a bug with the packaging tools and 3.8, this was corrected in the RTFM trunk. The problem was the --datafile etc/initialdata argument being passed during make initdb -kevin Thanks to Ruslan, I've now got a fresh working installation of RT 3.8.0. I went to install RTFM and ran into an issue with the initdb step. It returned Working with: Type: mysql Host: db01.prl.ab.ca Name: ref_ill_rt User: refrt DBA:refrt Now populating database schema. Couldn't finish 'schema' step. ERROR: Couldn't find schema file(s) '*' ...returned with error: 65280 make: *** [initdb] Error 255 I noticed that it was using the db-rt-user as both user and dba. The configure line for RT did specify the db-dba as root. I tried the refrt password, and it connected but returned the error above. (Using the root password with the above settings returned an access denied message as expected.) I then replaced the dba in the perl command line with root, but got the same error as above. I went hunting for the schema and found it in RTFM-2.2.1/etc/schema.mysql. So I cheated and ran mysql -h db01.prl.ab.ca -D ref_ill_rt -u root -p schema.mysql and it appears to have worked. The other line in the Makefile refers to acl, but the acl.mysql file says there aren't any changes needed in mysql for ACL so I didn't run it. Below is the complete run from perl Makefile.PL up to the error message in case it helps. Michael [EMAIL PROTECTED] RTFM-2.2.1]# perl Makefile.PL Using RT configurations from /opt/rt3/lib/RT.pm: ./bin = /opt/rt3/local/bin ./etc = /opt/rt3/local/etc/FM ./html = /opt/rt3/share/html ./lib = /opt/rt3/local/lib ./po= /opt/rt3/local/po/FM ./sbin = /opt/rt3/local/sbin For first-time installation, type 'make initdb'. *** Module::AutoInstall version 1.03 *** Checking for Perl dependencies... [Core Features] Cannot reliably compare non-decimal formatted versions. Please install version.pm or Sort::Versions. - RT...loaded. (3.8.0 = 3.4.2) - Text::WikiFormat ...loaded. (0.79) - Tree::Simple ...loaded. (1.18) - HTML::TreeBuilder ...loaded. (3.23) - Time::ParseDate ...loaded. (2006.0814) - HTML::FormatText ...loaded. (2.04) - YAML ...loaded. (0.66) *** Module::AutoInstall configuration finished. Open input '/root/RTFM-2.2.1/t/utils.pl' file for substitution Open output '/root/RTFM-2.2.1/t/utils.pl' file for substitution Writing Makefile for RTFM [EMAIL PROTECTED] RTFM-2.2.1]# make Manifying blib/man3/RT::FM::Topic_Overlay.3pm Manifying blib/man3/RT::FM::Article.3pm Manifying blib/man3/RT::FM::TopicCollection_Overlay.3pm Manifying blib/man3/RT::FM::ObjectTopic.3pm Manifying blib/man3/RT::FM::Record.3pm Manifying blib/man3/RT::FM::ObjectTopicCollection_Overlay.3pm Manifying blib/man3/RT::URI::fsck_com_rtfm.3pm Manifying blib/man3/RT::FM::Class.3pm Manifying blib/man3/RT::FM::ArticleCollection.3pm Manifying blib/man3/RT::URI::a.3pm Manifying blib/man3/RT::FM::Article_Overlay.3pm Manifying blib/man3/RT::FM::ObjectTopicCollection.3pm Manifying blib/man3/RT::FM::ClassCollection_Overlay.3pm Manifying blib/man3/RT::FM::ArticleCollection_Overlay.3pm Manifying blib/man3/RT::FM::Class_Overlay.3pm Manifying blib/man3/RT::FM::SearchBuilder.3pm Manifying blib/man3/RT::FM::TopicCollection.3pm Manifying blib/man3/RT::FM::Topic.3pm Manifying blib/man3/RT::FM::ClassCollection.3pm Manifying blib/man3/RT::FM::System.3pm [EMAIL PROTECTED] RTFM-2.2.1]# make install Writing /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi/auto/ RTFM/.packli st Appending installation info to /usr/lib/perl5/5.8.8/i386-linux-thread-multi/perllocal.pod [EMAIL PROTECTED] RTFM-2.2.1]# make initdb /usr/bin/perl -Ilib -I/opt/rt3/local/lib -I/opt/rt3/lib /opt/rt3/sbin/rt-setup-database --action schema --datadir etc -- datafile etc/initialdata --dba refrt --prompt-for-dba-password In order to create or update your RT database, this script needs to connect to your mysql instance on db01.prl.ab.ca as refrt Please specify that user's database password below. If the user has no database password, just press return. Password: Working with: Type: mysql Host: db01.prl.ab.ca Name: ref_ill_rt User: refrt DBA:refrt Now populating database schema. Couldn't finish 'schema' step. ERROR: Couldn't find schema file(s) '*' ...returned with error: 65280 make: *** [initdb] Error 255 ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Re: [rt-users] Minor Edit to Interface/Email.pm
You don't say what version you're running (probably 3.6.something)
It would be helpful if you sent a patch (you can download a fresh copy
of
3.6 from http://download.bestpractical.com ) and an explanation
of what bug you were seeing and how to reproduce it to
[EMAIL PROTECTED]
This would let us get a fix in the svn tree for future releases
thanks
-kevin
On Aug 7, 2008, at 1:35 PM, Erik Aronesty wrote:
(I don't have the original so I can't do a diff, but basically the
loop variable should (always) be my'ed to protect it from being
altered. There was a problem with the MailFrom plugin setting $_ and
then corrupting the loop varialbe!)
CUT---
# Since this needs loading, no matter what
foreach my $Class (@RT::MailPlugins) {
my ($Code, $NewAuthStat);
if ( ref($Class) eq CODE ) {
$Code = $Class;
} else {
$Class = RT::Interface::Email:: . $Class
unless $Class =~ /^RT::Interface::Email::/;
___
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
___
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] [error] Can't call method crit
I see the following in one of your previous messages: [Thu Jul 31 23:19:04 2008] [crit]: Plugin Extension-QuickDelete not found in /opt/rt3/local/plugins (/var/www/rt-3.8.0/sbin/../lib/RT.pm:579) [Thu Jul 31 23:19:04 2008] [crit]: Can't locate Extension-QuickDelete.pm in RT tries to load a plugin that is not installed, but is enabled in your RT_SiteConfig.pm, not apache's conig. On Thu, Aug 7, 2008 at 9:32 PM, PF IT [EMAIL PROTECTED] wrote: -Original Message- From: Ruslan Zakirov [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: RT-Users@lists.bestpractical.com Subject: Re: [rt-users] [error] Can't call method crit Date: Fri, 1 Aug 2008 04:42:45 +0400 By default no plugins are installed and desiable @Plugins option in your config. -- Is this related to why I get this error when using: # RT default Apache configuration Alias /rt/ /opt/rt3/share/html/ Directory /opt/rt3/share/html/ AllowOverride All Options ExecCGI FollowSymLinks Options Indexes FollowSymLinks IfModule mod_access.c Order allow,deny Allow from all /IfModule /Directory PerlRequire /opt/rt3/bin/webmux.pl Location /rt/ RewriteEngine On RedirectMatch permanent (.*)/$ $1/index.html AddDefaultCharset UTF-8 SetHandler perl-script PerlHandler RT::Mason /Location /var/log/apache2/error.log gives me this error. [Thu Aug 07 10:30:19 2008] [error] Can't call method crit on an undefined value at /opt/rt3/bin/../lib/RT.pm line 579.\nCompilation failed in require at (eval 2) line 1.\n [Thu Aug 07 10:30:19 2008] [error] Can't load Perl file: /opt/rt3/bin/webmux.pl for server PFServer7.pfsandiego.local:0, exiting... This is holding up using RT. -Adam ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com -- Best regards, Ruslan. ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] RT at a Glance HASH ref error during upgrade from 3.4 to 3.8
Hm, interesting... Sounds like some problem with serialization. We use Storable module to serialize data, it worth try either upgrade or downgrade. Please don't forget to remember the current installed version, so we can bump dependencies if problem is in this module. Install new or older version. Drop database, init, test. On Fri, Aug 8, 2008 at 1:47 AM, Larry Han [EMAIL PROTECTED] wrote: Actually, I don't think that it is a database problem. When I do a mysqladmin drop rt3; and then I do rt-setup-database --action init, the RT at a glance page still shows the same error. So I think it may be a problem with my perl or the RT install. Any suggestions? -- Best regards, Ruslan. ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
[rt-users] Slow Query Log
I'm using RT 3.8 and Mysql 5.0.51a on Fedora Core 9. I've been noticing some slowness using the interface. Most of the time it is when updating tickets. Reviewing the slow query log I found the following. Out of a total of 53133 log entries there where 14369 entries for SELECT count(main.id) FROM ObjectCustomF 5540 entries for SELECT * FROM Templates WHERE Queue = ' 18967 entries for SELECT main.* FROM CustomFields main JOI 9397 entries for SELECT main.* FROM Tickets main WHERE ( Oddly enough, I don't use CustomFields. Any suggestions on how to speed things up? ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
[rt-users] RTx::Shredder performance improvement (by adding new index)
In the process of investigating the performance of using Shredder to delete tickets, I found an index that seems to have a considerable improvement on performance, even above the indexes that are suggested in the documentation. I simply added: CREATE INDEX SHREDDER_CGM3 ON CachedGroupMembers(Val, Id); Before, when I had no indexes, deleting 500 tickets (there are ~ 100,000 in our database), the process took about 2 hours and 30 minutes. After adding the suggested indexes (which I found in the CPAN documentation), the process took about 1 hour, 15 minutes. After adding the above index, the process took about 16 minutes. I stumbled upon this while using the tool mytop (available at http://jeremy.zawodny.com/mysql/mytop/). I am pretty certain that, despite the occasionally self-referrential nature of the Val field in the CGM table, this index shouldn't lead to any difference in results, ordering, or completeness in deletion. I haven't had the time to check, though - so obviously I take no responsibility for any huge catastrophes that may occur on your particular database. Anyway, thanks to Ruslan Zakirov for a great tool. Cheers, -Drew Day ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] Slow Query Log
On Aug 7, 2008, at 6:37 PM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'm using RT 3.8 and Mysql 5.0.51a on Fedora Core 9. I've been noticing some slowness using the interface. Most of the time it is when updating tickets. Reviewing the slow query log I found the following. It'd help if you could: * send the complete queries * send the actual metainformation about how slow is slow * run 'explains' for these queries * tell us about your RT server hardware configuration * tell us a bit about what you've already done to tune your database Best, Jesse Out of a total of 53133 log entries there where 14369 entries for SELECT count(main.id) FROM ObjectCustomF 5540 entries for SELECT * FROM Templates WHERE Queue = ' 18967 entries for SELECT main.* FROM CustomFields main JOI 9397 entries for SELECT main.* FROM Tickets main WHERE ( Oddly enough, I don't use CustomFields. Any suggestions on how to speed things up? ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
