[rt-users] upgrade-assets error

[support]

Hello everyone,

After I upgrade my RT to 4.4.1 on centos 6. I'm trying to run the
assets-upgrade and I'm getting the error below.

How do I solve this issue. I remove the plugin from the configuration
already.

## ERROR
/upgrade-assets
Can't locate RT/Interface/CLI.pm in @INC (@INC contains: lib local/lib
/usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl
/usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at
./upgrade-assets line 56.
BEGIN failed--compilation aborted at ./upgrade-assets line 56.

Thank you.
David

-
RT 4.4 and RTIR training sessions, and a new workshop day! 
https://bestpractical.com/training
* Los Angeles - January 9-11 2017

[rt-users] Upgrade from 4.2.12 -> 4.4.1 breaks Self Service?

[Stephen Switzer]

I upgraded last night, and all seems great, except an issue was reported 
today. The "My open tickets" section in Self Service is blank. The 
closed tickets are viewable, however. I had the user log out and back 
in, cleared the mason cache, restarted apache...


Where can I look first to determine the issue?

Thank you!


--
Best regards,

*Stephen H. Switzer*
*voice:* 585.298.9420 [ x7001 ]
*cell:* 585.202.8312
*fax:* 585.625.0020
*email:* st...@sbsroc.com 
/Technical Consultant & System Engineer/
- VMware VSP
- Microsoft MCP, Desktop/Server


*Switzer Business Solutions, LLC*

*web:* www.SwitzerBusinessSolutions.com 


*fb:* www.facebook.com/sbsolutions 
- VMware VIP Partner
- HP Authorized Business Development Partner
- Xorcom Certified Dealer


-
RT 4.4 and RTIR training sessions, and a new workshop day! 
https://bestpractical.com/training
* Los Angeles - September 12-14, 2016

[rt-users] upgrade-sla sets Due to (not set [RT 4.4])

[andriuss]

Hello I have done the upgrade procedure to move from 4.2.12 to 4.4 version.
Cleaned cache, started my webserver, enable SLA on all queues and then run
the etc/upgrade/upgrade-sla scritp. I have noticed that the Due of all
tickets is set to ('not set'). How can I avoid this?

Status: rejected
SLA: Incident
Priority:   Lower/Highest
Queue:  RT_support


#
2016-04-07 14:24:25 The RT System itself - SLA changed from (no value) to
'Incident' 
#
2016-04-07 14:24:25 The RT System itself - Due changed from 2013-09-06
13:20:50 to Not set 




--
View this message in context: 
http://requesttracker.8502.n7.nabble.com/upgrade-sla-sets-Due-to-not-set-RT-4-4-tp61676.html
Sent from the Request Tracker - User mailing list archive at Nabble.com.
-
RT 4.4 and RTIR Training Sessions https://bestpractical.com/training
* Washington DC - May 23 & 24, 2016

Re: [rt-users] Upgrade-database from 4.0.8 to 4.4.0rc2 fails

[Christopher Kunz]

Hi again,

> Now populating database schema.
> [11815] [Wed Nov 25 10:44:40 2015] [critical]: DBD::mysql::st execute
> failed: Duplicate column name 'Disabled' at
> /usr/local/src/rt-4.4/sbin/../lib/RT/Handle.pm line 552.
> (/usr/local/src/rt-4.4/sbin/../lib/RT.pm:390)
> DBD::mysql::st execute failed: Duplicate column name 'Disabled' at
> /usr/local/src/rt-4.4/sbin/../lib/RT/Handle.pm line 552.
> Makefile:391: recipe for target 'upgrade-database' failed
> make: *** [upgrade-database] Error 255
> 
FWIW, I manually fixed about a dozen errors (non-existant columns,
double columns and the likes) in the various database schemas and ran
make upgrade-database multiple times until it finally completed
successfully. Took me about an hour (and I'm not sure what caused it,
since my 4.0.8 installation is vanilla, database-wise).

--ck

[rt-users] Upgrade-database from 4.0.8 to 4.4.0rc2 fails

[Christopher Kunz]

Hi,

I'm trying to upgrade an RT 4.0.8 instance (only lightly modified in
RT_SiteConfig.pm, no fancy stuff) to 4.4.0RC2. The 'make
upgrade-database' target fails at the following points:

== 4.0.8 => 4.0.9 ==
Processing 4.0.9
Now inserting data.
[11815] [Wed Nov 25 10:44:34 2015] [warning]: DBD::mysql::st execute
failed: Unknown column 'main.SortOrder' in 'order clause' at
/usr/local/share/perl/5.20.2/DBIx/SearchBuilder/Handle.pm line 586, <>
line 1. (/usr/local/share/perl/5.20.2/DBIx/SearchBuilder/Handle.pm:586)
[11815] [Wed Nov 25 10:44:34 2015] [warning]: RT::Handle=HASH(0x4878b28)
couldn't execute the query 'SELECT main.* FROM Queues main  WHERE
(main.Lifecycle IS NULL OR main.Lifecycle = '' OR main.Lifecycle = '0')
 ORDER BY main.SortOrder ASC, main.Name ASC ' at
/usr/local/share/perl/5.20.2/DBIx/SearchBuilder/Handle.pm line 599, <>
line 1.
DBIx::SearchBuilder::Handle::SimpleQuery(RT::Handle=HASH(0x4878b28),
"SELECT main.* FROM Queues main  WHERE (main.Lifecycle IS NULL"...)
called at /usr/local/share/perl/5.20.2/DBIx/SearchBuilder.pm line 239
DBIx::SearchBuilder::_DoSearch(RT::Queues=HASH(0x996a060)) called at
/usr/local/src/rt-4.4/sbin/../lib/RT/SearchBuilder.pm line 982
RT::SearchBuilder::_DoSearch(RT::Queues=HASH(0x996a060)) called at
/usr/local/share/perl/5.20.2/DBIx/SearchBuilder.pm line 507
DBIx::SearchBuilder::Next(RT::Queues=HASH(0x996a060)) called at
./etc/upgrade/4.0.9/content line 29
RT::Handle::__ANON__() called at
/usr/local/src/rt-4.4/sbin/../lib/RT/Handle.pm line 866
eval {...} called at /usr/local/src/rt-4.4/sbin/../lib/RT/Handle.pm
line 866
RT::Handle::InsertData(RT::Handle=HASH(0x4878b28),
"./etc/upgrade/4.0.9/content", undef) called at sbin/rt-setup-database
line 390
main::__ANON__() called at ./etc/upgrade/4.1.13/backcompat line 34
main::__ANON__(CODE(0x98e2f50)) called at sbin/rt-setup-database line 
400
main::__ANON__() called at sbin/rt-setup-database line 403
main::action_insert("backcompat", ARRAY(0xe413f0), "action", "upgrade",
"prompt-for-dba-password", 1, "datafile", undef, "datadir", ...) called
at sbin/rt-setup-database line 571
main::action_upgrade("action", "upgrade", "prompt-for-dba-password", 1,
"package", "RT") called at sbin/rt-setup-database line 210
(/usr/share/perl/5.20/Carp.pm:169)

Then the upgrades to 4.0.12 through 4.1.0 run through without issue, but
after that:

Processing 4.1.1
Now populating database schema.
[11815] [Wed Nov 25 10:44:40 2015] [critical]: DBD::mysql::st execute
failed: Duplicate column name 'Disabled' at
/usr/local/src/rt-4.4/sbin/../lib/RT/Handle.pm line 552.
(/usr/local/src/rt-4.4/sbin/../lib/RT.pm:390)
DBD::mysql::st execute failed: Duplicate column name 'Disabled' at
/usr/local/src/rt-4.4/sbin/../lib/RT/Handle.pm line 552.
Makefile:391: recipe for target 'upgrade-database' failed
make: *** [upgrade-database] Error 255

How can I fix this issue? Can't find anything in the upgrade docs, let
alone UPGRADING.mysql, that points to a possible cause for these errors.

Thanks for any pointers!

Regards,

--ck

[rt-users] upgrade from 4.0.10 to 4.2.12

[charlyc...@yahoo.com.ar]

Hello all,
I finally upgraded my RT from 4.0.10 to 4.2.12 and I'm facing some problems now.
1. When inserting an article in a ticket now I get the HTML code on it, for 
example this:
Dear customer,The change you have requested is not possible.Thank 
you.

If I apply the same article in the 4.0.10 we don't have the HTML code on it.

2. When creating new tickets on the 4.0.10 we could apply different format to 
the text but not possible on the 4.2.12
You can see both screenshots attached.

Thank you all for your help!
Charly

Re: [rt-users] upgrade from 4.0.10 to 4.2.12

[charlyc...@yahoo.com.ar]

Hi Matt,
Thank you for your quick response.
Configuration was "Use default (yes)", I tried forcing it to Yes and still the 
same problem.
Thank you,Charly
 


 El Lunes, 26 de octubre, 2015 18:37:02, Matt Zagrabelny 
 escribió:
   

 On Mon, Oct 26, 2015 at 5:24 PM, charlyc...@yahoo.com.ar
 wrote:
> Hello all,
>
> I finally upgraded my RT from 4.0.10 to 4.2.12 and I'm facing some problems
> now.
>
> 1. When inserting an article in a ticket now I get the HTML code on it, for
> example this:
>
> Dear customer,
> The change you have requested is not possible.
> Thank you.
>
> If I apply the same article in the 4.0.10 we don't have the HTML code on it.
>
>
> 2. When creating new tickets on the 4.0.10 we could apply different format
> to the text but not possible on the 4.2.12

In 4.2.12 you are not using a WYSIWYG editor. Try to change to using a
WYSIWYG editor in your settings->preferences.

-m


  

Re: [rt-users] upgrade from 4.0.10 to 4.2.12

[Matt Zagrabelny]

On Mon, Oct 26, 2015 at 5:24 PM, charlyc...@yahoo.com.ar
 wrote:
> Hello all,
>
> I finally upgraded my RT from 4.0.10 to 4.2.12 and I'm facing some problems
> now.
>
> 1. When inserting an article in a ticket now I get the HTML code on it, for
> example this:
>
> Dear customer,
> The change you have requested is not possible.
> Thank you.
>
> If I apply the same article in the 4.0.10 we don't have the HTML code on it.
>
>
> 2. When creating new tickets on the 4.0.10 we could apply different format
> to the text but not possible on the 4.2.12

In 4.2.12 you are not using a WYSIWYG editor. Try to change to using a
WYSIWYG editor in your settings->preferences.

-m

[rt-users] upgrade to 4.2.x and mod_rewrite

[Marc Burri]

Hi,

We somehow managed to upgrade from 3.8 to 4.2.11, yesterday but it seems
something changed with RT so our Apache mod_rewrite rules doesn't work
anymore.

To beautify the URL in the mail templates we shorten it for our
customers like
{RT-Config-Get('WebURL')}ticket/{$Ticket-id}
and created a rewrite rule accordingly
RewriteRule ^/[Tt]icket/([0-9]+)$ /Ticket/Display.html?id=$1 [L]

I can see in the Apache logs that the rewrite is still working but RT
doesn't seem to look at it.

Did I miss something during the upgrade?

BR,
Marc

--
Acceleris AG

Re: [rt-users] Upgrade 2.8.8 - 4.0.23 issues: Upload multiple images custom field

[Jasper Greve]

For what it's worth, a predecessor of mine disabled the thumbnail preview
by editing html/Elements/ShowCustomFieldImage. I reproduced that on the new
install and consider this resolved.

On Tue, Mar 31, 2015 at 2:27 PM, Jasper Greve jasper.gr...@gmail.com
wrote:

 Hi all,

 We use this custom field in multiple queue's and with the upgrade it
 started loading thumbnails of these images. I set :

 Set($ShowTransactionImages, 0);

 to now avail, is there a way to switch this functionality off?

 Thanks,

 Jasper

 PS I have been looking through https://www.bestpractical.com/docs/rt/4.0/,
 mailing lists, and wikia to resolve some of my questions. Are there any
 resources I'm missing?

[rt-users] Upgrade 2.8.8 - 4.0.23 issues: Upload multiple images custom field

[Jasper Greve]

Hi all,

We use this custom field in multiple queue's and with the upgrade it
started loading thumbnails of these images. I set :

Set($ShowTransactionImages, 0);

to now avail, is there a way to switch this functionality off?

Thanks,

Jasper

PS I have been looking through https://www.bestpractical.com/docs/rt/4.0/,
mailing lists, and wikia to resolve some of my questions. Are there any
resources I'm missing?

[rt-users] Upgrade 3.8.8 - 4.0.23 issues: Lost Dashboards

[Jasper Greve]

Hi all,

I recently moved RT to a new server and upgraded to a slightly less
outdated version. After the move the Dashboards option disappeared from
the Tools menu. Does anybody have any idea what might be going on?

Thanks,

Jasper

Re: [rt-users] Upgrade to 4.2.9 Lost Dashboards.

[Sam Maher]

Hi Alex,

I have upgraded from 4.0.4, But the strange thing is that some people kept 
their dashboards and some didn't.

Sam

-Original Message-
From: rt-users [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of 
Alex Vandiver
Sent: 05 March 2015 19:57
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Upgrade to 4.2.9 Lost Dashboards.

On Thu, 5 Mar 2015 14:52:39 -0500 Alex Vandiver ale...@bestpractical.com 
wrote:
 On Wed, 25 Feb 2015 11:52:37 + Sam Maher
 sam.ma...@lawsonlewisblakers.co.uk wrote:
  I have moved to a new server and upgraded to the latest version but
  all my privileged users except one have lost their dashboards. Has
  anyone else had this problem?

 Please specify what you mean by latest version.

I missed that the subject specified you upgraded to 4.2.9.  What version were 
you upgrading from?
 - Alex



Sam Maher - IT Technician
Lawson Lewis Blakers
T: 01323 720142
F: 01323 725349


Partners: Jeremy H Sogno, Nadine M Ashford and Mark Barrett
Lawson Lewis  Blakers Solicitors Authorised and Regulated by the Solicitors 
Regulation Authority. SRA No: 00053703

THIS E-MAIL AND ANY ATTACHED FILES ARE CONFIDENTIAL AND MAY BE LEGALLY 
PRIVILEGED
If you are not the addressee or the intended recipient any disclosure, copying, 
distribution, or other use of this e-mail and attachments is strictly 
prohibited.
If you have received this e-mail in error please notify the sender immediately 
and delete this e-mail.

E-mail transmission cannot be guaranteed to be secure or error free as 
information could be intercepted, corrupted, lost, destroyed, arrive late, be 
incomplete or contain viruses.
We do not accept liability for any errors or omissions which arise as a result 
of e-mail transmission. Any e-mail attachment may contain software viruses.
Whilst reasonable precaution has been taken to minimise this risk, we cannot 
accept liability for any damage which you sustain as a result of software 
viruses.

Lawson Lewis Blakers reserves the right to monitor or record e-mails for any 
purpose allowed by prevailing legislation.

Re: [rt-users] Upgrade to 4.2.9 Lost Dashboards.

[Alex Vandiver]

On Thu, 5 Mar 2015 14:52:39 -0500 Alex Vandiver
ale...@bestpractical.com wrote:
 On Wed, 25 Feb 2015 11:52:37 + Sam Maher
 sam.ma...@lawsonlewisblakers.co.uk wrote:
  I have moved to a new server and upgraded to the latest version but
  all my privileged users except one have lost their dashboards. Has
  anyone else had this problem?
 
 Please specify what you mean by latest version.

I missed that the subject specified you upgraded to 4.2.9.  What
version were you upgrading from?
 - Alex

Re: [rt-users] Upgrade to 4.2.9 Lost Dashboards.

[Alex Vandiver]

On Wed, 25 Feb 2015 11:52:37 + Sam Maher
sam.ma...@lawsonlewisblakers.co.uk wrote:
 I have moved to a new server and upgraded to the latest version but
 all my privileged users except one have lost their dashboards. Has
 anyone else had this problem?

Please specify what you mean by latest version.  Are the dashboards
listed in Home → All Dashboards?
 - Alex

[rt-users] Upgrade to 4.2.9 Lost Dashboards.

[Sam Maher]

Hi,

I have moved to a new server and upgraded to the latest version but all my 
privileged users except one have lost their dashboards. Has anyone else had 
this problem?

Sam




Sam Maher - IT Technician
Lawson Lewis Blakers
T: 01323 720142
F: 01323 725349

Partners: Jeremy H Sogno, Nadine M Ashford and Mark Barrett
Lawson Lewis  Blakers Solicitors Authorised and Regulated by the Solicitors 
Regulation Authority. SRA No: 00053703

THIS E-MAIL AND ANY ATTACHED FILES ARE CONFIDENTIAL AND MAY BE LEGALLY 
PRIVILEGED
If you are not the addressee or the intended recipient any disclosure, copying, 
distribution, or other use of this e-mail and attachments is strictly 
prohibited.
If you have received this e-mail in error please notify the sender immediately 
and delete this e-mail.

E-mail transmission cannot be guaranteed to be secure or error free as 
information could be intercepted, corrupted, lost, destroyed, arrive late, be 
incomplete or contain viruses.
We do not accept liability for any errors or omissions which arise as a result 
of e-mail transmission. Any e-mail attachment may contain software viruses.
Whilst reasonable precaution has been taken to minimise this risk, we cannot 
accept liability for any damage which you sustain as a result of software 
viruses.

Lawson Lewis Blakers reserves the right to monitor or record e-mails for any 
purpose allowed by prevailing legislation.

Re: [rt-users] Upgrade fail

[Joshua Lansford]

Here is the upgrade error in full.
mysql -u root -p
create database rt4;
quit;
git clone git://github.com/bestpractical/rt.git -b stable
cd rt
autoconf
./configure  configure.log
sudo make fixdeps  fixdeps.log
make testdeps  testdeps.log
sudo make upgrade  upgrade.log 21
mysql -u root -p rt4  ../../rtbackup.sql
cat  EOF | sudo tee /opt/rt4/etc/RT_SiteConfig.pm
Set( \$DatabaseRequireSSL, '' );
Set( \$DatabaseType, 'mysql' );
Set( \$CommentAddress, '**hidden**' );
Set( \$CorrespondAddress, '**hidden**' );
Set( \$DatabaseHost, 'localhost' );
Set( \$DatabaseName, 'rt4' );
Set( \$DatabasePassword, '**hidden**' );
Set( \$DatabasePort, '' );
Set( \$DatabaseUser, 'rt_user' );
Set( \$Organization, 'public.laserlinc.com' );
Set( \$OwnerEmail, '**hidden**' );
Set( \$SendmailPath, '/usr/sbin/sendmail' );
Set( \$WebDomain, 'public.laserlinc.com' );
Set( \$WebPort, '80' );
Set( \$rtname, 'public.laserlinc.com' );
Set( \$WebPath, /rt );
1;
EOF
sudo make upgrade-database 21 | tee upgrade-database.log

The outputs are attached.
~Joshua

On Fri, Feb 6, 2015 at 3:44 PM, Joshua Lansford 
joshua.lansf...@laserlinc.com wrote:

 Upgrading in stages did solve the problem.  I downloaded version 3.9.7
 which is the version Lifecycle was introduced.  Upgrading using this
 version and then upgrading using the latest version of the code completed
 without errors.  From the log I believe I am now on 4.2.10.

 I'll back up and restore the unupgraded database to reproduce the complete
 error message.
 ~Joshua



/usr/bin/perl -I/opt/rt4/local/lib -I/opt/rt4/lib sbin/rt-setup-database --action upgrade --prompt-for-dba-password
In order to create or update your RT database, this script needs to connect to your  mysql instance on localhost (port '') as root
Please specify that user's database password below. If the user has no database
password, just press return.

Password: 
Working with:
Type:	mysql
Host:	localhost
Port:	
Name:	rt4
User:	rt_user
DBA:	root
Enter RT version you're upgrading from: 
* There are upgrades for 4.2.10, which is later than 4.2.10rc1,
* which you are nominally upgrading to.  Upgrading to 4.2.10 instead.

Going to apply following upgrades:
* 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
* 4.0.9
* 4.0.12
* 4.0.13
* 4.0.18
* 4.0.19
* 4.1.0
* 4.1.1
* 4.1.4
* 4.1.5
* 4.1.6
* 4.1.7
* 4.1.8
* 4.1.9
* 4.1.10
* 4.1.11
* 4.1.12
* 4.1.13
* 4.1.14
* 4.1.15
* 4.1.16
* 4.1.17
* 4.1.18
* 4.1.19
* 4.1.20
* 4.1.21
* 4.1.22
* 4.1.23
* 4.2.1
* 4.2.2
* 4.2.4
* 4.2.6
* 4.2.7
* 4.2.8
* 4.2.10

Enter RT version if you want to stop upgrade at some point,
  or leave it blank if you want apply above upgrades: 
IT'S VERY IMPORTANT TO BACK UP BEFORE THIS STEP

Proceed [y/N]:Processing 3.9.1
[31689] [Mon Feb  9 13:11:50 2015] [info]: Using internal Perl HTML - text conversion (/home/user/temp/rt/sbin/../lib/RT/Interface/Email.pm:1817)
[31689] [Mon Feb  9 13:11:50 2015] [warning]: DBD::mysql::db selectcol_arrayref failed: Unknown column 'main.Lifecycle' in 'field list' at /usr/local/share/perl/5.18.2/DBIx/SearchBuilder.pm line 635. (/usr/local/share/perl/5.18.2/DBIx/SearchBuilder.pm:635)
[31689] [Mon Feb  9 13:11:50 2015] [critical]: DBD::mysql::db selectcol_arrayref failed: Unknown column 'main.Lifecycle' in 'field list' at /usr/local/share/perl/5.18.2/DBIx/SearchBuilder.pm line 635. (/home/user/temp/rt/sbin/../lib/RT.pm:388)
DBD::mysql::db selectcol_arrayref failed: Unknown column 'main.Lifecycle' in 'field list' at /usr/local/share/perl/5.18.2/DBIx/SearchBuilder.pm line 635.
make: *** [upgrade-database] Error 255
/usr/bin/perl ./sbin/rt-test-dependencies --verbose --with-mysql --with-fastcgi
perl:
	=5.10.1(5.18.2) ...found
users:
	rt group (www-data) ...found
	bin owner (root) ...found
	libs owner (root) ...found
	libs group (bin) ...found
	web owner (www-data) ...found
	web group (www-data) ...found
CLI dependencies:
	Term::ReadKey ...found
	LWP ...found
	Text::ParseWords ...found
	HTTP::Request::Common ...found
	Getopt::Long = 2.24 ...found
	Term::ReadLine ...found
CORE dependencies:
	Devel::StackTrace = 1.19 ...found
	LWP::Simple ...found
	File::Spec = 0.8 ...found
	Email::Address = 1.897 ...found
	Text::Password::Pronounceable ...found
	List::MoreUtils ...found
	Sys::Syslog = 0.16 ...found
	Date::Extract = 0.02 ...found
	Module::Versions::Report = 1.05 ...found
	Apache::Session = 1.53 ...found
	DBIx::SearchBuilder = 1.65 ...found
	DateTime = 0.44 ...found
	DBI = 1.37 ...found
	DateTime::Format::Natural = 0.67 ...found
	HTML::Entities ...found
	Email::Address::List = 0.02 ...found
	Errno ...found
	HTML::Quoted ...found
	Mail::Header = 2.12 ...found
	Scalar::Util ...found
	Date::Manip ...found
	UNIVERSAL::require ...found
	CGI::PSGI = 0.12 ...found
	Regexp::IPv6 ...found
	CGI::Emulate::PSGI ...found
	XML::RSS = 1.05 ...found
	Devel::GlobalDestruction ...found
	Class::Accessor = 0.34 ...found
	Locale::Maketext::Fuzzy = 0.11 ...found
	Crypt::Eksblowfish 

Re: [rt-users] Upgrade fail

[Joshua Lansford]

Trying that again with .txt attachments to prevent mail list scrubbing.


On Mon, Feb 9, 2015 at 8:17 AM, Joshua Lansford 
joshua.lansf...@laserlinc.com wrote:

 Here is the upgrade error in full.
 mysql -u root -p
 create database rt4;
 quit;
 git clone git://github.com/bestpractical/rt.git -b stable
 cd rt
 autoconf
 ./configure  configure.log
 sudo make fixdeps  fixdeps.log
 make testdeps  testdeps.log
 sudo make upgrade  upgrade.log 21
 mysql -u root -p rt4  ../../rtbackup.sql
 cat  EOF | sudo tee /opt/rt4/etc/RT_SiteConfig.pm
 Set( \$DatabaseRequireSSL, '' );
 Set( \$DatabaseType, 'mysql' );
 Set( \$CommentAddress, '**hidden**' );
 Set( \$CorrespondAddress, '**hidden**' );
 Set( \$DatabaseHost, 'localhost' );
 Set( \$DatabaseName, 'rt4' );
 Set( \$DatabasePassword, '**hidden**' );
 Set( \$DatabasePort, '' );
 Set( \$DatabaseUser, 'rt_user' );
 Set( \$Organization, 'public.laserlinc.com' );
 Set( \$OwnerEmail, '**hidden**' );
 Set( \$SendmailPath, '/usr/sbin/sendmail' );
 Set( \$WebDomain, 'public.laserlinc.com' );
 Set( \$WebPort, '80' );
 Set( \$rtname, 'public.laserlinc.com' );
 Set( \$WebPath, /rt );
 1;
 EOF
 sudo make upgrade-database 21 | tee upgrade-database.log

 The outputs are attached.
 ~Joshua

 On Fri, Feb 6, 2015 at 3:44 PM, Joshua Lansford 
 joshua.lansf...@laserlinc.com wrote:

 Upgrading in stages did solve the problem.  I downloaded version 3.9.7
 which is the version Lifecycle was introduced.  Upgrading using this
 version and then upgrading using the latest version of the code completed
 without errors.  From the log I believe I am now on 4.2.10.

 I'll back up and restore the unupgraded database to reproduce the
 complete error message.
 ~Joshua




/usr/bin/perl -I/opt/rt4/local/lib -I/opt/rt4/lib sbin/rt-setup-database 
--action upgrade --prompt-for-dba-password
In order to create or update your RT database, this script needs to connect to 
your  mysql instance on localhost (port '') as root
Please specify that user's database password below. If the user has no database
password, just press return.

Password: 
Working with:
Type:   mysql
Host:   localhost
Port:   
Name:   rt4
User:   rt_user
DBA:root
Enter RT version you're upgrading from: 
* There are upgrades for 4.2.10, which is later than 4.2.10rc1,
* which you are nominally upgrading to.  Upgrading to 4.2.10 instead.

Going to apply following upgrades:
* 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
* 4.0.9
* 4.0.12
* 4.0.13
* 4.0.18
* 4.0.19
* 4.1.0
* 4.1.1
* 4.1.4
* 4.1.5
* 4.1.6
* 4.1.7
* 4.1.8
* 4.1.9
* 4.1.10
* 4.1.11
* 4.1.12
* 4.1.13
* 4.1.14
* 4.1.15
* 4.1.16
* 4.1.17
* 4.1.18
* 4.1.19
* 4.1.20
* 4.1.21
* 4.1.22
* 4.1.23
* 4.2.1
* 4.2.2
* 4.2.4
* 4.2.6
* 4.2.7
* 4.2.8
* 4.2.10

Enter RT version if you want to stop upgrade at some point,
  or leave it blank if you want apply above upgrades: 
IT'S VERY IMPORTANT TO BACK UP BEFORE THIS STEP

Proceed [y/N]:Processing 3.9.1
[31689] [Mon Feb  9 13:11:50 2015] [info]: Using internal Perl HTML - text 
conversion (/home/user/temp/rt/sbin/../lib/RT/Interface/Email.pm:1817)
[31689] [Mon Feb  9 13:11:50 2015] [warning]: DBD::mysql::db selectcol_arrayref 
failed: Unknown column 'main.Lifecycle' in 'field list' at 
/usr/local/share/perl/5.18.2/DBIx/SearchBuilder.pm line 635. 
(/usr/local/share/perl/5.18.2/DBIx/SearchBuilder.pm:635)
[31689] [Mon Feb  9 13:11:50 2015] [critical]: DBD::mysql::db 
selectcol_arrayref failed: Unknown column 'main.Lifecycle' in 'field list' at 
/usr/local/share/perl/5.18.2/DBIx/SearchBuilder.pm line 635. 
(/home/user/temp/rt/sbin/../lib/RT.pm:388)
DBD::mysql::db selectcol_arrayref failed: Unknown column 'main.Lifecycle' in 
'field list' at /usr/local/share/perl/5.18.2/DBIx/SearchBuilder.pm line 635.
make: *** [upgrade-database] Error 255
/usr/bin/perl ./sbin/rt-test-dependencies --verbose --with-mysql --with-fastcgi
perl:
=5.10.1(5.18.2) ...found
users:
rt group (www-data) ...found
bin owner (root) ...found
libs owner (root) ...found
libs group (bin) ...found
web owner (www-data) ...found
web group (www-data) ...found
CLI dependencies:
Term::ReadKey ...found
LWP ...found
Text::ParseWords ...found
HTTP::Request::Common ...found
Getopt::Long = 2.24 ...found
Term::ReadLine ...found
CORE dependencies:
Devel::StackTrace = 1.19 ...found
LWP::Simple ...found
File::Spec = 0.8 ...found
Email::Address = 1.897 ...found
Text::Password::Pronounceable ...found
List::MoreUtils ...found
Sys::Syslog = 0.16 ...found
Date::Extract = 0.02 ...found
Module::Versions::Report = 1.05 ...found
Apache::Session = 1.53 ...found
DBIx::SearchBuilder = 1.65 ...found
DateTime = 0.44 ...found
DBI = 1.37 ...found
DateTime::Format::Natural = 0.67 ...found
HTML::Entities ...found
  

Re: [rt-users] Upgrade fail

[Joshua Lansford]

Upgrading in stages did solve the problem.  I downloaded version 3.9.7
which is the version Lifecycle was introduced.  Upgrading using this
version and then upgrading using the latest version of the code completed
without errors.  From the log I believe I am now on 4.2.10.

I'll back up and restore the unupgraded database to reproduce the complete
error message.
~Joshua

On Fri, Feb 6, 2015 at 2:02 PM, Alex Vandiver ale...@bestpractical.com
wrote:

 On Fri, 6 Feb 2015 13:44:06 -0500 Joshua Lansford 
 joshua.lansf...@laserlinc.com wrote:
  Ok.  So I have done some additional investigation and here is what I have
  found.  The new Queues table has two new fields named Lifecycle and
  SubjectTag.  Lifecycle field is accessed in the RT::Init which is called
 at
  the top of action_insert before it can do the insert portion of the first
  upgrade step... I think.  It is looking like the code is assuming stuff
  about the database structure which isn't true just in trying to set up to
  do the upgrade steps.

 Please show the complete output of 'make upgrade-database', not just a
 small snippet.

  I suppose this means I am trying to jump too many versions at once and I
  need to do an intermediate upgrade at an intermediate step.  Probably at
  the version which introduces these columns.  If that version couldn't
 have
  upgraded everyone would have gotten stuck.

 It shouldn't be necessary to to the upgrade in multiple steps.
  - Alex

Re: [rt-users] Upgrade fail

[Alex Vandiver]

On Fri, 6 Feb 2015 13:44:06 -0500 Joshua Lansford 
joshua.lansf...@laserlinc.com wrote:
 Ok.  So I have done some additional investigation and here is what I have
 found.  The new Queues table has two new fields named Lifecycle and
 SubjectTag.  Lifecycle field is accessed in the RT::Init which is called at
 the top of action_insert before it can do the insert portion of the first
 upgrade step... I think.  It is looking like the code is assuming stuff
 about the database structure which isn't true just in trying to set up to
 do the upgrade steps.

Please show the complete output of 'make upgrade-database', not just a
small snippet.

 I suppose this means I am trying to jump too many versions at once and I
 need to do an intermediate upgrade at an intermediate step.  Probably at
 the version which introduces these columns.  If that version couldn't have
 upgraded everyone would have gotten stuck.

It shouldn't be necessary to to the upgrade in multiple steps.
 - Alex

[rt-users] Upgrade fail

[Joshua Lansford]

Hello.
  I am trying to upgrade from 3.8.11 to stable and make upgrade-database is
bombing.  The error message is
=
9449] [Thu Feb  5 19:23:36 2015] [critical]: DBD::mysql::db
selectcol_arrayref failed: Unknown column 'main.Lifecycle' in 'field list'
at /usr/local/share/perl/5.18.2/DBIx/SearchBuilder.pm line 635.
(/home/user/temp/rt/sbin/../lib/RT.pm:388)
DBD::mysql::db selectcol_arrayref failed: Unknown column 'main.Lifecycle'
in 'field list' at /usr/local/share/perl/5.18.2/DBIx/SearchBuilder.pm line
635.
make: *** [upgrade-database] Error 255
=

I setup a fresh vm for this job to test.  I was able to set up RT from
stable just fine without an upgrade.  So then I dropped that rt4 database,
deleted the /opt/rt4 install folder, dumped the rtdb old database to a sql
file.  Copied the sql dump over to the vm.  Imported it as rt4.  Did make
upgrade to recreate the rt4 folder.  Configured the database user and
password in RT_SiteConfig.pm.  Granted permissions to the rt4 user with
that password to the rt4 folder and hit make upgrade-database.  After
giving the root mysql password the above error is presented.

Assistance at this point would be appreciated.  Let me know what additional
information I can provide.
Thank you,
~Joshua

Re: [rt-users] Upgrade fail

[Joshua Lansford]

Ok.  So I have done some additional investigation and here is what I have
found.  The new Queues table has two new fields named Lifecycle and
SubjectTag.  Lifecycle field is accessed in the RT::Init which is called at
the top of action_insert before it can do the insert portion of the first
upgrade step... I think.  It is looking like the code is assuming stuff
about the database structure which isn't true just in trying to set up to
do the upgrade steps.

I suppose this means I am trying to jump too many versions at once and I
need to do an intermediate upgrade at an intermediate step.  Probably at
the version which introduces these columns.  If that version couldn't have
upgraded everyone would have gotten stuck.

Sound plausible?
~Joshua

On Fri, Feb 6, 2015 at 7:05 AM, Joshua Lansford 
joshua.lansf...@laserlinc.com wrote:

 Hello.
   I am trying to upgrade from 3.8.11 to stable and make upgrade-database
 is bombing.  The error message is
 =
 9449] [Thu Feb  5 19:23:36 2015] [critical]: DBD::mysql::db
 selectcol_arrayref failed: Unknown column 'main.Lifecycle' in 'field list'
 at /usr/local/share/perl/5.18.2/DBIx/SearchBuilder.pm line 635.
 (/home/user/temp/rt/sbin/../lib/RT.pm:388)
 DBD::mysql::db selectcol_arrayref failed: Unknown column 'main.Lifecycle'
 in 'field list' at /usr/local/share/perl/5.18.2/DBIx/SearchBuilder.pm line
 635.
 make: *** [upgrade-database] Error 255
 =

 I setup a fresh vm for this job to test.  I was able to set up RT from
 stable just fine without an upgrade.  So then I dropped that rt4 database,
 deleted the /opt/rt4 install folder, dumped the rtdb old database to a sql
 file.  Copied the sql dump over to the vm.  Imported it as rt4.  Did make
 upgrade to recreate the rt4 folder.  Configured the database user and
 password in RT_SiteConfig.pm.  Granted permissions to the rt4 user with
 that password to the rt4 folder and hit make upgrade-database.  After
 giving the root mysql password the above error is presented.

 Assistance at this point would be appreciated.  Let me know what
 additional information I can provide.
 Thank you,
 ~Joshua

Re: [rt-users] Upgrade of RT

[Alex Peters]

Perform a mysqldump of the old database, and import it into a new location
as is.

Follow the instructions included with RT for a new installation, ignoring
the database steps.

Add the new database connection details to your new installation's
RT_SiteConfig.pm file (ensuring that the $DatabaseAdmin value is set
appropriately).

Run sbin/rt-setup-database from the root of the new RT installation with
the appropriate options (including --action upgrade).  See --help.

When I upgrade, I tend to follow the steps above rather than upgrading in
place like RT's instructions suggest.

On Fri, 16 Jan 2015 12:53 am Iain Vowles iain.vow...@mcgill.ca wrote:

  Hi,



 We are new to the whole RT upgrading game and would like to do the
 following:



 · A clean install the new RT 4.2.9 on a new server (server is
 already configured with the correct Apache (2.2.15), Perl (5.10.1), and
 MySQL (5.1.73))

 · Export the MySQL data from our old RT server - version 3.6.11

 · Import the data to the new 4.2.9 version



 Can someone let us know how to go about this.



 Many Thanks,



 Iain Vowles





 *Iain Vowles* | Senior Analyst, Information Services/ Analyst Senior,
 Services d’Information

 *Université McGill University* | University Advancement / Avancement
 universitaire
 1555, rue Peel, # 937 | Montréal (Québec) Canada H3A 3L8
 *T* 514.398.8098 | *C* 514.443.0328 | *E* *iain.vow...@mcgill.ca
 iain.vow...@mcgill.ca*
 *McGill* http://www.mcgill.ca | *AOC* http://aoc.mcgill.ca/ |
 *Facebook* https://www.facebook.com/McGillUniversityAlumni | *Twitter*
 http://twitter.com/McGillAlumni | *LinkedIn*
 http://www.linkedin.com/groups?home=gid=49847trk=anet_ug_hm | *Give
 now / Faire un don*
 https://www.alumni.mcgill.ca/aoc/online-giving/step1.php?new=1
  https://www.alumni.mcgill.ca/aoc/online-giving/step1.php?new=1
 *This message is confidential.* *If you are not the person to whom it is
 addressed, please alert us as soon as possible and delete it immediately.
 If you are not the correct addressee, any disclosure, copying or other
 distribution of this message is strictly prohibited.* */ Ce message est
 confidentiel.* *Si vous n’êtes pas la personne à laquelle il est destiné
 veuillez nous en aviser le plus tôt possible et le détruire immédiatement.
 Si ce message ne vous est pas destiné, il vous est strictement interdit de
 divulguer, de copier ou de distribuer le contenu de ce message par quelque
 moyen que ce soit.*

[rt-users] Upgrade of RT

[Iain Vowles]

Hi,

We are new to the whole RT upgrading game and would like to do the following:


· A clean install the new RT 4.2.9 on a new server (server is already 
configured with the correct Apache (2.2.15), Perl (5.10.1), and MySQL (5.1.73))

· Export the MySQL data from our old RT server - version 3.6.11

· Import the data to the new 4.2.9 version

Can someone let us know how to go about this.

Many Thanks,

Iain Vowles


Iain Vowles | Senior Analyst, Information Services/ Analyst Senior, Services 
d'Information
Université McGill University | University Advancement / Avancement universitaire
1555, rue Peel, # 937 | Montréal (Québec) Canada H3A 3L8
T 514.398.8098 | C 514.443.0328 | E 
iain.vow...@mcgill.camailto:iain.vow...@mcgill.ca
McGillwww.mcgill.ca | AOChttp://aoc.mcgill.ca/ | 
Facebookhttps://www.facebook.com/McGillUniversityAlumni | 
Twitterhttp://twitter.com/McGillAlumni | 
LinkedInhttp://www.linkedin.com/groups?home=gid=49847trk=anet_ug_hm | Give 
now / Faire un 
donhttps://www.alumni.mcgill.ca/aoc/online-giving/step1.php?new=1
https://www.alumni.mcgill.ca/aoc/online-giving/step1.php?new=1
This message is confidential. If you are not the person to whom it is 
addressed, please alert us as soon as possible and delete it immediately. If 
you are not the correct addressee, any disclosure, copying or other 
distribution of this message is strictly prohibited. / Ce message est 
confidentiel. Si vous n'êtes pas la personne à laquelle il est destiné veuillez 
nous en aviser le plus tôt possible et le détruire immédiatement. Si ce message 
ne vous est pas destiné, il vous est strictement interdit de divulguer, de 
copier ou de distribuer le contenu de ce message par quelque moyen que ce soit.

Re: [rt-users] Upgrade RT 3.8.7 to 4.0.1

[Felipe Agnelli Barbosa]

 |
+---+--+
1 row in set (0.00 sec)
##
##
##
mysql show create table ACL;
+---++
| Table | Create
Table
|
+---++
| ACL   | CREATE TABLE `ACL` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `PrincipalType` varchar(25) CHARACTER SET ascii NOT NULL,
  `PrincipalId` int(11) NOT NULL,
  `RightName` varchar(25) CHARACTER SET ascii NOT NULL,
  `ObjectType` varchar(25) CHARACTER SET ascii NOT NULL,
  `ObjectId` int(11) NOT NULL DEFAULT '0',
  `Creator` int(11) NOT NULL DEFAULT '0',
  `Created` datetime DEFAULT NULL,
  `LastUpdatedBy` int(11) NOT NULL DEFAULT '0',
  `LastUpdated` datetime DEFAULT NULL,
  PRIMARY KEY (`id`),
  KEY `ACL1`
(`RightName`,`ObjectType`,`ObjectId`,`PrincipalType`,`PrincipalId`)
) ENGINE=InnoDB AUTO_INCREMENT=1731 DEFAULT CHARSET=utf8 |
+---++




--

 Message: 2
 Date: Fri, 29 Aug 2014 16:59:59 -0500
 From: Kevin Falcone falc...@bestpractical.com
 To: rt-users@lists.bestpractical.com
 Subject: Re: [rt-users] Upgrade RT 3.8.7 to 4.0.1
 Message-ID: 20140829215959.gd3...@jibsheet.com
 Content-Type: text/plain; charset=us-ascii

 On Fri, Aug 29, 2014 at 01:18:11PM -0300, Felipe Agnelli Barbosa wrote:
  Show the schema of your Users table, although if your ACL table is
  also messed up then you've not completed the upgrade.

 You neglected this information

 run 'show create table Users' and 'show create table ACL' and share it
 with us.

 -kevin
 -- next part --
 A non-text attachment was scrubbed...
 Name: not available
 Type

Re: [rt-users] Upgrade RT 3.8.7 to 4.0.1

[Felipe Agnelli Barbosa]

Hi Kevin,

I already understood where i was wrong.
Here my answers,

Message: 12
 Date: Fri, 22 Aug 2014 09:59:41 -0400
 From: Kevin Falcone falc...@bestpractical.com
 To: rt-users@lists.bestpractical.com
 Subject: Re: [rt-users] Upgrade RT 3.8.7 to 4.0.1
 Message-ID: 20140822135941.ge3...@jibsheet.com
 Content-Type: text/plain; charset=us-ascii

 On Mon, Aug 18, 2014 at 06:02:41PM -0300, Felipe Agnelli Barbosa wrote:
 
  4. Apply upgrade the schema at the current server and after in the new
 server
  $perl /usr/share/request-tracker3.8/etc/upgrade/[1]
 upgrade-mysql-schema.pl rtdb
  root password  queries.sql
  $mysql -u root -p rtdb  queries.sql

 Why?
 Step 1 of
 http://bestpractical.com/docs/rt/4.0/UPGRADING.mysql.html
 tells you not to run that


ok

  5. Run the upgrade database at the new server
  $rt-setup-database-4 --prompt-for-dba-password --action upgrade

 I assume this has not completed properly

 here, i receive following msg,

Processing 3.8.8
Now inserting data.
[ [warning]: Couldn't set SortOrder: That is already the current value
(/usr/share/request-tracker4/etc/upgrade/3.8.8/content:32)
Processing 3.8.9
Now inserting data.
[warning]: Use of uninitialized value in string eq at
/usr/share/request-tracker4/lib/RT/Template.pm line 656,  line 1.
(/usr/share/request-tracker4/lib/RT/Template.pm:656)
[warning]: Use of uninitialized value in string eq at
/usr/share/request-tracker4/lib/RT/Template.pm line 656,  line 1.
(/usr/share/request-tracker4/lib/RT/Template.pm:656)
[warning]: Use of uninitialized value in string eq at
/usr/share/request-tracker4/lib/RT/Template.pm line 656,  line 1.
(/usr/share/request-tracker4/lib/RT/Template.pm:656)
Processing 3.9.1
Now inserting data.
Processing 3.9.2
Now inserting data.
Processing 3.9.3
Now populating database schema.
Processing 3.9.5
Now populating database schema.
Processing 3.9.6
Now populating database schema.
Processing 3.9.7
Now populating database schema.
Now inserting data.
Processing 3.9.8
Now populating database schema.
Now inserting data.
Processing 4.0.0rc2
Now populating database schema.
Processing 4.0.0rc4
Now populating database schema.
Processing 4.0.0rc7
Now inserting data.
Processing 4.0.1
Now inserting data.
Processing 4.0.3
Now inserting data.
Processing 4.0.4
Now inserting data.
Processing 4.0.6
Now populating database schema.
Now inserting data.
Processing 4.0.9
Now inserting data.
Processing 4.0.12
Now populating database schema.
Processing 4.0.13
Now populating database schema.
Processing 4.0.18
Now inserting data.
Processing 4.0.19
Now populating database schema.
Now inserting data.
Done.

Whats mean the warning message? and more, after that, when I restarted
webserver, i receive too a msg, like that,

[warning]: Use of uninitialized value in numeric eq (==) at
/usr/share/request-tracker4/lib/RT/ScripAction.pm line 202.
(/usr/share/request-tracker4/lib/RT/ScripAction.pm:202)


Thank you for your help,



  6. Start webserver at the new server
  $service apache2 start
 
  Than, i can do login once after changing my password and i can't create
 ticket
  neither change the owner they.

 Show the schema of your Users table, although if your ACL table is
 also messed up then you've not completed the upgrade.

 Show your database upgrade.

 -kevin
 -- next part --
 A non-text attachment was scrubbed...
 Name: not available
 Type: application/pgp-signature
 Size: 221 bytes
 Desc: not available
 URL: 
 http://lists.bestpractical.com/pipermail/rt-users/attachments/20140822/f5c2bd88/attachment-0001.pgp
 





-- 
 A dúvida é o principio da sabedoria 
-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

Re: [rt-users] Upgrade RT 3.8.7 to 4.0.1

[Kevin Falcone]

On Fri, Aug 29, 2014 at 01:18:11PM -0300, Felipe Agnelli Barbosa wrote:
 Show the schema of your Users table, although if your ACL table is
 also messed up then you've not completed the upgrade.

You neglected this information

run 'show create table Users' and 'show create table ACL' and share it
with us.

-kevin


pgpmDuxwJ_7yw.pgp
Description: PGP signature
-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

Re: [rt-users] Upgrade-Database make***Fehler 254

[Kevin Falcone]

On Thu, Aug 21, 2014 at 10:27:48PM -0700, Dergeiletyp wrote:
 Hey, i am using Debian 7 Squeeze. I installed rt4.0.7 via apt-get so far, and
 its running... but i can upgrade to version 4.2.6 I get this Error:
 Upgrade-Database make***Fehler 254 How can i fix ths

You need to show much more of what you did for context.

Keep in mind that upgrading to a tarball of 4.2.6 will conflict with
4.0.7 from APT and you'll need to uninstall (or really know what
you're doing).

-kevin


pgpxl81J6MLTT.pgp
Description: PGP signature
-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

Re: [rt-users] Upgrade RT 3.8.7 to 4.0.1

[Kevin Falcone]

On Mon, Aug 18, 2014 at 06:02:41PM -0300, Felipe Agnelli Barbosa wrote:
 
 4. Apply upgrade the schema at the current server and after in the new server
 $perl /usr/share/request-tracker3.8/etc/upgrade/[1]upgrade-mysql-schema.pl 
 rtdb
 root password  queries.sql
 $mysql -u root -p rtdb  queries.sql

Why?
Step 1 of 
http://bestpractical.com/docs/rt/4.0/UPGRADING.mysql.html
tells you not to run that

 5. Run the upgrade database at the new server
 $rt-setup-database-4 --prompt-for-dba-password --action upgrade

I assume this has not completed properly

 6. Start webserver at the new server
 $service apache2 start
 
 Than, i can do login once after changing my password and i can't create ticket
 neither change the owner they.

Show the schema of your Users table, although if your ACL table is
also messed up then you've not completed the upgrade.

Show your database upgrade.

-kevin


pgpfwxsEw1Hh1.pgp
Description: PGP signature
-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

[rt-users] Upgrade-Database make***Fehler 254

[Dergeiletyp]

Hey, i am using Debian 7 Squeeze. I installed rt4.0.7 via apt-get so far, and
its running... but i can upgrade to version 4.2.6 I get this Error:
Upgrade-Database make***Fehler 254How can i fix ths



--
View this message in context: 
http://requesttracker.8502.n7.nabble.com/Upgrade-Database-make-Fehler-254-tp58370.html
Sent from the Request Tracker - User mailing list archive at Nabble.com.-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

Re: [rt-users] Upgrade-Database make***Fehler 254

[Jon Witts]

If you installed via apt-get I do not think you will be able to manually 
upgrade to 4.2.6. If you want to use the latest version of RT then you should 
download, compile ans install it manually. RT 4.2 is not available until Debian 
Sid (Unstable): 
https://packages.debian.org/search?suite=sidsearchon=nameskeywords=rt4

Jon



Director of Digital Strategy
Queen Margaret's School
01904 727600

http://www.queenmargarets.com


From: rt-users [rt-users-boun...@lists.bestpractical.com] on behalf of 
Dergeiletyp [twage...@elomech.de]
Sent: 22 August 2014 6:27 AM
To: rt-users@lists.bestpractical.com
Subject: [rt-users] Upgrade-Database make***Fehler 254

Hey, i am using Debian 7 Squeeze. I installed rt4.0.7 via apt-get so far, and 
its running... but i can upgrade to version 4.2.6 I get this Error: 
Upgrade-Database make***Fehler 254 How can i fix ths

View this message in context: Upgrade-Database make***Fehler 
254http://requesttracker.8502.n7.nabble.com/Upgrade-Database-make-Fehler-254-tp58370.html
Sent from the Request Tracker - User mailing list 
archivehttp://requesttracker.8502.n7.nabble.com/Request-Tracker-User-f3.html 
at Nabble.com.


This email has been processed by Smoothwall Anti-Spam - www.smoothwall.net

-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

[rt-users] Upgrade RT 3.8.7 to 4.0.1

[Felipe Agnelli Barbosa]

Hi Guys,

 I'm migrating of server and i would like to upgrade my rt instalation.
My current configuration is it,

Ubuntu 10.0.4
RT(via apt-get) 3.8.7
Mysql 5.1.6

New server:
Ubuntu 14.0.4
RT(via apt-get) 4.0.19
Mysql 5.5.3

So, I follow the documentation, README,  UPGRADING-3.8.gz,
UPGRADING-4.0.gz, UPGRADING.mysql, NOTES.Debian.gz, README.Debian.gz among
other.
I find to other cases like me at the list but it don't help to fix my
problem.

And, i did the following :

1. Backup at the current server
$/usr/bin/mysqldump -u root -password --default-character-set=latin1
--databases rtdb  rtdb.dump

2. Imported at the new server
$mysql -u root -password --default-character-set=latin1 rtdb  rtdb.dump

3. Exec this script at the new server
$perl /usr/share/request-tracker4/etc/upgrade/vulnerable-passwords

4. Apply upgrade the schema at the current server and after in the new
server
$perl /usr/share/request-tracker3.8/etc/upgrade/upgrade-mysql-schema.pl
rtdb root password  queries.sql
$mysql -u root -p rtdb  queries.sql

5. Run the upgrade database at the new server
$rt-setup-database-4 --prompt-for-dba-password --action upgrade

6. Start webserver at the new server
$service apache2 start


Than, i can do login once after changing my password and i can't create
ticket neither change the owner they.

So you guy, can me give a hint?

I appreciate your help.
-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

[rt-users] Upgrade RT and migrate to postgresql

[Sternberger, Sven]

Hi!

we want to upgrade our RT from 3.8.7 to 4.2.6
and we want to migrate from mysql to postgresql.

Is it possible to combine these 2 steps, or is
it better to first upgrade the RT and in a second step
migrate to postgresql?

best regards!

Sven
-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

Re: [rt-users] Upgrade RT and migrate to postgresql

[Kevin Bailey]

UNSUBSCIBE

On 4 August 2014 09:28, Sternberger, Sven sven.sternber...@desy.de wrote:
 Hi!

 we want to upgrade our RT from 3.8.7 to 4.2.6
 and we want to migrate from mysql to postgresql.

 Is it possible to combine these 2 steps, or is
 it better to first upgrade the RT and in a second step
 migrate to postgresql?

 best regards!

 Sven
 --
 RT Training - Boston, September 9-10
 http://bestpractical.com/training
-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

Re: [rt-users] Upgrade RT and migrate to postgresql

[Kevin Falcone]

On Mon, Aug 04, 2014 at 10:28:00AM +0200, Sternberger, Sven wrote:
 we want to upgrade our RT from 3.8.7 to 4.2.6
 and we want to migrate from mysql to postgresql.
 
 Is it possible to combine these 2 steps, or is
 it better to first upgrade the RT and in a second step
 migrate to postgresql?

The migration tool is part of RT 4.2.  Upgrade first, make sure you're
happy with the upgrade, then migrate.  Or you can take a longer
downtime and do it all in one weekend, but you can also upgrade one
month and convert the next.

-kevin


pgptnJGXnp5Kl.pgp
Description: PGP signature
-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

Re: [rt-users] Upgrade from 4.2.2 to 4.2.6 - simple search not using sphinx when searching

[Radu Tureac]

Thanks for your quick answer, Alex.

I got the Simple.pm from rt-4.2.3 and put it the local dir. Now it's back
to normal.

The explain looks like this:

++-++--+---+---+-+--+---++
| id | select_type | table  | type | possible_keys | key
| key_len | ref  | rows  | Extra
   |
++-++--+---+---+-+--+---++
|  1 | SIMPLE  | main   | ALL  | PRIMARY   | NULL
   | NULL| NULL | 41262 | Using where
 |
|  1 | SIMPLE  | Transactions_1 | ref  | Transactions1 |
Transactions1 | 70  | const,rt.main.id | 1 | Using where; Using
index   |
|  1 | SIMPLE  | Attachments_2  | ref  | Attachments2  |
Attachments2  | 4   | rt.Transactions_1.id | 3 | Using where
 |
|  1 | SIMPLE  | AttachmentsIndex_3 | ALL  | NULL  | NULL
   | NULL| NULL |20 | Using where; Using join
buffer (Block Nested Loop) |
++-++--+---+---+-+--+---++

I will give the 4.2/mysql-native-fts branch a test run when I have time and
give you back some feedback.

Thanks again,
Radu


On Tue, Jul 29, 2014 at 8:10 PM, Alex Vandiver ale...@bestpractical.com
wrote:

 On 07/29/2014 11:24 AM, Radu Tureac wrote:
  I have fulltext search implemented with sphinx and mysql 5.6.15.
 
  The problem is that after upgrade, I started to get these large queries
  in mysql when using simple search:

 RT 4.2.4 and above do a full-content search with simple search if
 indexed full-test searching is enabled.

  # Time: 140725 13:15:31
  # User@Host: rt_user[rt_user] @ localhost []  Id:26
  # Query_time: 10.390028  Lock_time: 0.000276 Rows_sent: 1
   Rows_examined: 910059
  SET timestamp=1406283331;
  SELECT COUNT(DISTINCT main.id http://main.id) FROM Tickets main JOIN
  Transactions Transactions_1  ON ( Transactions_1.ObjectType =
  'RT::Ticket' ) AND ( Transactions_1.ObjectId = main.id http://main.id
  ) LEFT JOIN Attachments Attachments_2  ON ( Attachments_2.TransactionId
  = Transactions_1.id ) LEFT JOIN AttachmentsIndex AttachmentsIndex_3  ON
  ( AttachmentsIndex_3.id = Attachments_2.id )  WHERE (main.IsMerged IS
  NULL) AND (main.Status != 'deleted') AND (main.Type = 'ticket') AND ( (
   ( main.Subject LIKE '%*word*%' OR  ( AttachmentsIndex_3.query =
  '*word*;limit=1;maxmatches=1' AND Attachments_2.Filename IS NULL
  )  )  ) );

 This failure is likely a failure of the Sphinx index to be picked up
 correctly, and is a limitation of the Sphinx search engine.  You can
 confirm this by showing the output of EXPLAIN on the above query.

  Is there any way that I could make the simple search use the sphinx
  engine by default for all the queries? Or any way to revert it?

 You likely have two options:
  1. Use a local overlay to replace the HandleDefault function in
 lib/RT/Search/Simple.pm with the version from 4.2.3 or earlier, which
 only searches subject, not subject and content.
  2. Try the 4.2/mysql-native-fts branch, which uses the indexed
 full-text search for InnoDB tables which is available in MySQL 5.6.

  - Alex

-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

[rt-users] Upgrade from 4.2.2 to 4.2.6 - simple search not using sphinx when searching

[Radu Tureac]

Hello,

I have fulltext search implemented with sphinx and mysql 5.6.15.

The problem is that after upgrade, I started to get these large queries in
mysql when using simple search:


# Time: 140725 13:15:31
# User@Host: rt_user[rt_user] @ localhost []  Id:26
# Query_time: 10.390028  Lock_time: 0.000276 Rows_sent: 1  Rows_examined:
910059
SET timestamp=1406283331;
SELECT COUNT(DISTINCT main.id) FROM Tickets main JOIN Transactions
Transactions_1  ON ( Transactions_1.ObjectType = 'RT::Ticket' ) AND (
Transactions_1.ObjectId = main.id ) LEFT JOIN Attachments Attachments_2  ON
( Attachments_2.TransactionId = Transactions_1.id ) LEFT JOIN
AttachmentsIndex AttachmentsIndex_3  ON ( AttachmentsIndex_3.id =
Attachments_2.id )  WHERE (main.IsMerged IS NULL) AND (main.Status !=
'deleted') AND (main.Type = 'ticket') AND ( (  ( main.Subject LIKE '%*word*%'
OR  ( AttachmentsIndex_3.query = '*word*;limit=1;maxmatches=1' AND
Attachments_2.Filename IS NULL )  )  ) );


Is there any way that I could make the simple search use the sphinx engine
by default for all the queries? Or any way to revert it?

I also mention that the content search is still working with sphinx as
before, if I write fulltext:word I can find the query in the
RT_ROOT/var/sphinx/query.log

[Wed Jun 25 16:41:45.057 2014] 0.002 sec 0.002 sec [all/0/rel 3 (0,1)]
[rt,rtdelta] word
[Wed Jun 25 16:41:45.191 2014] 0.002 sec 0.002 sec [all/0/rel 3 (0,1)]
[rt,rtdelta] word
[Wed Jun 25 16:41:58.256 2014] 0.002 sec 0.002 sec [all/0/rel 3 (0,1)]
[rt,rtdelta] word
[Wed Jun 25 16:42:36.063 2014] 0.002 sec 0.002 sec [all/0/rel 3 (0,1)]
[rt,rtdelta] word

Thank you!
-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

Re: [rt-users] Upgrade from 4.2.2 to 4.2.6 - simple search not using sphinx when searching

[Alex Vandiver]

On 07/29/2014 11:24 AM, Radu Tureac wrote:
 I have fulltext search implemented with sphinx and mysql 5.6.15.
 
 The problem is that after upgrade, I started to get these large queries
 in mysql when using simple search:

RT 4.2.4 and above do a full-content search with simple search if
indexed full-test searching is enabled.

 # Time: 140725 13:15:31
 # User@Host: rt_user[rt_user] @ localhost []  Id:26
 # Query_time: 10.390028  Lock_time: 0.000276 Rows_sent: 1
  Rows_examined: 910059
 SET timestamp=1406283331;
 SELECT COUNT(DISTINCT main.id http://main.id) FROM Tickets main JOIN
 Transactions Transactions_1  ON ( Transactions_1.ObjectType =
 'RT::Ticket' ) AND ( Transactions_1.ObjectId = main.id http://main.id
 ) LEFT JOIN Attachments Attachments_2  ON ( Attachments_2.TransactionId
 = Transactions_1.id ) LEFT JOIN AttachmentsIndex AttachmentsIndex_3  ON
 ( AttachmentsIndex_3.id = Attachments_2.id )  WHERE (main.IsMerged IS
 NULL) AND (main.Status != 'deleted') AND (main.Type = 'ticket') AND ( (
  ( main.Subject LIKE '%*word*%' OR  ( AttachmentsIndex_3.query =
 '*word*;limit=1;maxmatches=1' AND Attachments_2.Filename IS NULL
 )  )  ) );

This failure is likely a failure of the Sphinx index to be picked up
correctly, and is a limitation of the Sphinx search engine.  You can
confirm this by showing the output of EXPLAIN on the above query.

 Is there any way that I could make the simple search use the sphinx
 engine by default for all the queries? Or any way to revert it?

You likely have two options:
 1. Use a local overlay to replace the HandleDefault function in
lib/RT/Search/Simple.pm with the version from 4.2.3 or earlier, which
only searches subject, not subject and content.
 2. Try the 4.2/mysql-native-fts branch, which uses the indexed
full-text search for InnoDB tables which is available in MySQL 5.6.

 - Alex
-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

Re: [rt-users] Upgrade History shows Upgrade Incomplete

[Dominic Hargreaves]

On Thu, May 22, 2014 at 04:33:01PM -0400, Kevin Falcone wrote:
 On Wed, May 21, 2014 at 04:23:15PM -0400, Nathan Baker wrote:
 On Wed, May 21, 2014 at 1:22 PM, Kevin Falcone 
  [1]falc...@bestpractical.com wrote:
  
   On Wed, May 21, 2014 at 11:33:20AM -0400, Nathan Baker wrote:
Hello everyone,
   
I just upgraded from 4.0.6 to 4.2.3 using the Debian packages. ? 
  During the
database upgrade, I received a few errors:
  
   I'm guessing you set up a new machine, installed request-tracker4 from
   testing, restored your database and then did the upgrade?
  
 Actually this is on a system that was running 4.0.6 previously. ? I just 
  did apt-get install
 request-tracker4 (using the testing repository) and it upgraded all the 
  packages.?
 
 I find that surprising, since you had a 4.2 only table.
 
   You have an unclean database with 4.2 tables in it, and you're
   tripping over some of the code we added to help RT handle that more
   gracefully.
  
 What I'm wondering is how I can tell if the database is unclean or if 
  it's okay. ? The
 upgrade history section in System Configuration shows that it did 
  Upgrade from 4.0.19 to
 4.2.3 once without errors, and then it did it again and it says 
  (Incomplete). ? Maybe that
 doesn't actually mean it tried twice though, I'm not sure.
 
 oh.
 You cannot safely upgrade RT like that.
 
 Restore from a backup and upgrade cleanly.
 
 I wouldn't trust a database that had run the upgrades twice.

Ah, I had always assumed that updates were idempotent. Sounds like
we need to adjust the error handling in the Debian package then.
(What I think happened in Nathan's case was that the upgrade itself
went okay but something else went wrong in the package postinst).

-- 
Dominic Hargreaves, Systems Development and Support Section
IT Services, University of Oxford, 13 Banbury Road, Oxford, OX2 6NN


signature.asc
Description: Digital signature
-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

Re: [rt-users] Upgrade History shows Upgrade Incomplete

[Kevin Falcone]

On Wed, May 21, 2014 at 04:23:15PM -0400, Nathan Baker wrote:
On Wed, May 21, 2014 at 1:22 PM, Kevin Falcone 
 [1]falc...@bestpractical.com wrote:
 
  On Wed, May 21, 2014 at 11:33:20AM -0400, Nathan Baker wrote:
   Hello everyone,
  
   I just upgraded from 4.0.6 to 4.2.3 using the Debian packages. � 
 During the
   database upgrade, I received a few errors:
 
  I'm guessing you set up a new machine, installed request-tracker4 from
  testing, restored your database and then did the upgrade?
 
Actually this is on a system that was running 4.0.6 previously. � I just 
 did apt-get install
request-tracker4 (using the testing repository) and it upgraded all the 
 packages.�

I find that surprising, since you had a 4.2 only table.

  You have an unclean database with 4.2 tables in it, and you're
  tripping over some of the code we added to help RT handle that more
  gracefully.
 
What I'm wondering is how I can tell if the database is unclean or if 
 it's okay. � The
upgrade history section in System Configuration shows that it did 
 Upgrade from 4.0.19 to
4.2.3 once without errors, and then it did it again and it says 
 (Incomplete). � Maybe that
doesn't actually mean it tried twice though, I'm not sure.

oh.
You cannot safely upgrade RT like that.

Restore from a backup and upgrade cleanly.

I wouldn't trust a database that had run the upgrades twice.

-kevin


pgpiqSOOU6nzm.pgp
Description: PGP signature
-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

[rt-users] Upgrade History shows Upgrade Incomplete

[Nathan Baker]

Hello everyone,

I just upgraded from 4.0.6 to 4.2.3 using the Debian packages.  During the
database upgrade, I received a few errors:

 Processing 4.1.1

Now populating database schema.

[12453] [Wed May 21 03:19:36 2014] [critical]: DBD::Pg::st execute failed:
ERROR:  cannot drop sequence objectscrips_id_seq because other objects
depend on it

DETAIL:  default for table objectscrips column id depends on sequence
objectscrips_id_seq

HINT:  Use DROP ... CASCADE to drop the dependent objects too. at
/usr/share/request-tracker4/lib/RT/Handle.pm line 529.
(/usr/share/request-tracker4/lib/RT.pm:394)

DBD::Pg::st execute failed: ERROR:  cannot drop sequence
objectscrips_id_seq because other objects depend on it

DETAIL:  default for table objectscrips column id depends on sequence
objectscrips_id_seq

HINT:  Use DROP ... CASCADE to drop the dependent objects too. at
/usr/share/request-tracker4/lib/RT/Handle.pm line 529.

error encountered processing
/usr/share/dbconfig-common/scripts/request-tracker4/upgrade/pgsql/4.2.3:

/usr/share/dbconfig-common/scripts/request-tracker4/upgrade/pgsql/4.2.3
exited with non-zero status


There could be an issue with the Debian packages (they are still in the
testing branch), but I'm trying to figure out what state the database is in
now.  The system is working fine, and shows version 4.2.3.  If I navigate
to Admin - Tools - System Configuration, then in the RT Upgrade History
section it looks like it might have tried to upgrade the database twice,
and the second time it failed (understandably).


Is there a way I can verify that the database schema is completely up to
date?


Here is what the RT Upgrade History section shows: (Sorry for the HTML,
wasn't sure how else to show it)
RT (Current version: 4.2.3) ActionDateElapsedRT VersionInsert from
/usr/share/request-tracker4/etc/upgrade/4.0.9/contentTue May 20 23:17:45
20141 second4.2.3Insert from
/usr/share/request-tracker4/etc/upgrade/4.0.18/contentTue May 20 23:17:53
20141 second4.2.3Insert from
/usr/share/request-tracker4/etc/upgrade/4.0.19/contentTue May 20 23:17:55
20140 seconds4.2.3 http://rt/Admin/Tools/Configuration.html#Upgrade from
4.0.19 to 4.2.3Tue May 20 23:17:56 20142 minutes4.2.3Insert from
/usr/share/request-tracker4/etc/upgrade/4.0.9/contentTue May 20 23:19:29
20140 seconds4.2.3Insert from
/usr/share/request-tracker4/etc/upgrade/4.0.18/contentTue May 20 23:19:34
20140 seconds4.2.3Insert from
/usr/share/request-tracker4/etc/upgrade/4.0.19/contentTue May 20 23:19:35
20140 seconds4.2.3 http://rt/Admin/Tools/Configuration.html#Upgrade from
4.0.19 to 4.2.3 (Incomplete)Tue May 20 23:19:36 20144.2.3Upgrade from
4.0.19 to 4.1.0Tue May 20 23:19:36 20140 seconds4.2.3Insert from
/usr/share/request-tracker4/etc/upgrade/4.1.0/contentTue May 20 23:19:36
20140 seconds4.2.3Upgrade from 4.1.0 to 4.1.1 (Incomplete)Tue May 20
23:19:36 20144.2.3Schema updates from
/usr/share/request-tracker4/etc/upgrade/4.1.1 (Incomplete)Tue May 20
23:19:36 20144.2.3
Thanks,
Nate
-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

Re: [rt-users] Upgrade History shows Upgrade Incomplete

[Kevin Falcone]

On Wed, May 21, 2014 at 11:33:20AM -0400, Nathan Baker wrote:
 Hello everyone,
 
 I just upgraded from 4.0.6 to 4.2.3 using the Debian packages.  During the
 database upgrade, I received a few errors:

I'm guessing you set up a new machine, installed request-tracker4 from
testing, restored your database and then did the upgrade?

You have an unclean database with 4.2 tables in it, and you're
tripping over some of the code we added to help RT handle that more
gracefully.

I've pushed
https://github.com/bestpractical/rt/commit/0ac64855f479b4133f4fe838af6b8b2dec8f5d18.patch
and it should be in 4.2.5.  You may be able to apply the patch
manually to /usr/share/request-tracker4/etc/upgrade/4.1.1/schema.Pg
or just clean out your DB by hand before letting the debian upgrade
scripts go.

-kevin

  Processing 4.1.1
 
 Now populating database schema.
 
 [12453] [Wed May 21 03:19:36 2014] [critical]: DBD::Pg::st execute failed:
 ERROR:  cannot drop sequence objectscrips_id_seq because other objects
 depend on it
 
 DETAIL:  default for table objectscrips column id depends on sequence
 objectscrips_id_seq
 
 HINT:  Use DROP ... CASCADE to drop the dependent objects too. at
 /usr/share/request-tracker4/lib/RT/Handle.pm line 529.
 (/usr/share/request-tracker4/lib/RT.pm:394)
 
 DBD::Pg::st execute failed: ERROR:  cannot drop sequence
 objectscrips_id_seq because other objects depend on it
 
 DETAIL:  default for table objectscrips column id depends on sequence
 objectscrips_id_seq
 
 HINT:  Use DROP ... CASCADE to drop the dependent objects too. at
 /usr/share/request-tracker4/lib/RT/Handle.pm line 529.
 
 error encountered processing
 /usr/share/dbconfig-common/scripts/request-tracker4/upgrade/pgsql/4.2.3:
 
 /usr/share/dbconfig-common/scripts/request-tracker4/upgrade/pgsql/4.2.3
 exited with non-zero status
 
 
 There could be an issue with the Debian packages (they are still in the
 testing branch), but I'm trying to figure out what state the database is in
 now.  The system is working fine, and shows version 4.2.3.  If I navigate
 to Admin - Tools - System Configuration, then in the RT Upgrade History
 section it looks like it might have tried to upgrade the database twice,
 and the second time it failed (understandably).
 
 
 Is there a way I can verify that the database schema is completely up to
 date?
 
 
 Here is what the RT Upgrade History section shows: (Sorry for the HTML,
 wasn't sure how else to show it)
 RT (Current version: 4.2.3) ActionDateElapsedRT VersionInsert from
 /usr/share/request-tracker4/etc/upgrade/4.0.9/contentTue May 20 23:17:45
 20141 second4.2.3Insert from
 /usr/share/request-tracker4/etc/upgrade/4.0.18/contentTue May 20 23:17:53
 20141 second4.2.3Insert from
 /usr/share/request-tracker4/etc/upgrade/4.0.19/contentTue May 20 23:17:55
 20140 seconds4.2.3 http://rt/Admin/Tools/Configuration.html#Upgrade from
 4.0.19 to 4.2.3Tue May 20 23:17:56 20142 minutes4.2.3Insert from
 /usr/share/request-tracker4/etc/upgrade/4.0.9/contentTue May 20 23:19:29
 20140 seconds4.2.3Insert from
 /usr/share/request-tracker4/etc/upgrade/4.0.18/contentTue May 20 23:19:34
 20140 seconds4.2.3Insert from
 /usr/share/request-tracker4/etc/upgrade/4.0.19/contentTue May 20 23:19:35
 20140 seconds4.2.3 http://rt/Admin/Tools/Configuration.html#Upgrade from
 4.0.19 to 4.2.3 (Incomplete)Tue May 20 23:19:36 20144.2.3Upgrade from
 4.0.19 to 4.1.0Tue May 20 23:19:36 20140 seconds4.2.3Insert from
 /usr/share/request-tracker4/etc/upgrade/4.1.0/contentTue May 20 23:19:36
 20140 seconds4.2.3Upgrade from 4.1.0 to 4.1.1 (Incomplete)Tue May 20
 23:19:36 20144.2.3Schema updates from
 /usr/share/request-tracker4/etc/upgrade/4.1.1 (Incomplete)Tue May 20
 23:19:36 20144.2.3
 Thanks,
 Nate



pgpnoqdvz8sSz.pgp
Description: PGP signature
-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

Re: [rt-users] Upgrade History shows Upgrade Incomplete

[Nathan Baker]

On Wed, May 21, 2014 at 1:22 PM, Kevin Falcone falc...@bestpractical.comwrote:

 On Wed, May 21, 2014 at 11:33:20AM -0400, Nathan Baker wrote:
  Hello everyone,
 
  I just upgraded from 4.0.6 to 4.2.3 using the Debian packages.  During
 the
  database upgrade, I received a few errors:

 I'm guessing you set up a new machine, installed request-tracker4 from
 testing, restored your database and then did the upgrade?


Actually this is on a system that was running 4.0.6 previously.  I just did
apt-get install request-tracker4 (using the testing repository) and it
upgraded all the packages.


 You have an unclean database with 4.2 tables in it, and you're
 tripping over some of the code we added to help RT handle that more
 gracefully.


What I'm wondering is how I can tell if the database is unclean or if
it's okay.  The upgrade history section in System Configuration shows
that it did Upgrade from 4.0.19 to 4.2.3 once without errors, and then it
did it again and it says (Incomplete).  Maybe that doesn't actually mean
it tried twice though, I'm not sure.



 I've pushed

 https://github.com/bestpractical/rt/commit/0ac64855f479b4133f4fe838af6b8b2dec8f5d18.patch
 and it should be in 4.2.5.  You may be able to apply the patch
 manually to /usr/share/request-tracker4/etc/upgrade/4.1.1/schema.Pg
 or just clean out your DB by hand before letting the debian upgrade
 scripts go.


Can I safely just drop  the table, drop the sequence, create the sequence,
and create the table?  I won't lose anything critical by doing that?

I'm guessing there's a bunch of stuff it was supposed to do after that, but
it probably stopped at that point.  I'm just thrown off by it being in the
upgrade history twice, the first time it looks like it did a whole bunch
of stuff successfully, including this step and lot after this step.

-kevin

   Processing 4.1.1
 
  Now populating database schema.
 
  [12453] [Wed May 21 03:19:36 2014] [critical]: DBD::Pg::st execute
 failed:
  ERROR:  cannot drop sequence objectscrips_id_seq because other objects
  depend on it
 
  DETAIL:  default for table objectscrips column id depends on sequence
  objectscrips_id_seq
 
  HINT:  Use DROP ... CASCADE to drop the dependent objects too. at
  /usr/share/request-tracker4/lib/RT/Handle.pm line 529.
  (/usr/share/request-tracker4/lib/RT.pm:394)
 
  DBD::Pg::st execute failed: ERROR:  cannot drop sequence
  objectscrips_id_seq because other objects depend on it
 
  DETAIL:  default for table objectscrips column id depends on sequence
  objectscrips_id_seq
 
  HINT:  Use DROP ... CASCADE to drop the dependent objects too. at
  /usr/share/request-tracker4/lib/RT/Handle.pm line 529.
 
  error encountered processing
  /usr/share/dbconfig-common/scripts/request-tracker4/upgrade/pgsql/4.2.3:
 
  /usr/share/dbconfig-common/scripts/request-tracker4/upgrade/pgsql/4.2.3
  exited with non-zero status
 
 
  There could be an issue with the Debian packages (they are still in the
  testing branch), but I'm trying to figure out what state the database is
 in
  now.  The system is working fine, and shows version 4.2.3.  If I navigate
  to Admin - Tools - System Configuration, then in the RT Upgrade
 History
  section it looks like it might have tried to upgrade the database twice,
  and the second time it failed (understandably).
 
 
  Is there a way I can verify that the database schema is completely up to
  date?
 
 
  Here is what the RT Upgrade History section shows: (Sorry for the HTML,
  wasn't sure how else to show it)
  RT (Current version: 4.2.3) ActionDateElapsedRT VersionInsert from
  /usr/share/request-tracker4/etc/upgrade/4.0.9/contentTue May 20 23:17:45
  20141 second4.2.3Insert from
  /usr/share/request-tracker4/etc/upgrade/4.0.18/contentTue May 20 23:17:53
  20141 second4.2.3Insert from
  /usr/share/request-tracker4/etc/upgrade/4.0.19/contentTue May 20 23:17:55
  20140 seconds4.2.3 http://rt/Admin/Tools/Configuration.html#Upgrade
 from
  4.0.19 to 4.2.3Tue May 20 23:17:56 20142 minutes4.2.3Insert from
  /usr/share/request-tracker4/etc/upgrade/4.0.9/contentTue May 20 23:19:29
  20140 seconds4.2.3Insert from
  /usr/share/request-tracker4/etc/upgrade/4.0.18/contentTue May 20 23:19:34
  20140 seconds4.2.3Insert from
  /usr/share/request-tracker4/etc/upgrade/4.0.19/contentTue May 20 23:19:35
  20140 seconds4.2.3 http://rt/Admin/Tools/Configuration.html#Upgrade
 from
  4.0.19 to 4.2.3 (Incomplete)Tue May 20 23:19:36 20144.2.3Upgrade from
  4.0.19 to 4.1.0Tue May 20 23:19:36 20140 seconds4.2.3Insert from
  /usr/share/request-tracker4/etc/upgrade/4.1.0/contentTue May 20 23:19:36
  20140 seconds4.2.3Upgrade from 4.1.0 to 4.1.1 (Incomplete)Tue May 20
  23:19:36 20144.2.3Schema updates from
  /usr/share/request-tracker4/etc/upgrade/4.1.1 (Incomplete)Tue May 20
  23:19:36 20144.2.3
  Thanks,
  Nate


 --
 RT Training - Boston, September 9-10
 http://bestpractical.com/training


Thanks,
Nate
-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

Re: [rt-users] Upgrade History shows Upgrade Incomplete

[Nathan Baker]

After looking at all of the schema.Pg files after 4.1.1, it looks like all
of the changes have already been applied.  The subsequent changes in the
4.1.1 script have also been applied already (Disabled column was added,
Stage and Queue columns were removed), so I don't think it would work to
patch my 4.1.1 file and run the upgrade again.

From what I can tell, the upgrade was successful the first time and failed
the second time, which is probably for the best anyway.  I'm not sure what
caused that, but I did notify Dominic about it.  I guess unless I notice
any problems, I'm just going to leave it and consider it to be normal/clean.

Thanks,
Nate


On Wed, May 21, 2014 at 4:23 PM, Nathan Baker bak...@gmail.com wrote:


 On Wed, May 21, 2014 at 1:22 PM, Kevin Falcone 
 falc...@bestpractical.comwrote:

 On Wed, May 21, 2014 at 11:33:20AM -0400, Nathan Baker wrote:
  Hello everyone,
 
  I just upgraded from 4.0.6 to 4.2.3 using the Debian packages.  During
 the
  database upgrade, I received a few errors:

 I'm guessing you set up a new machine, installed request-tracker4 from
 testing, restored your database and then did the upgrade?


 Actually this is on a system that was running 4.0.6 previously.  I just
 did apt-get install request-tracker4 (using the testing repository) and it
 upgraded all the packages.


 You have an unclean database with 4.2 tables in it, and you're
 tripping over some of the code we added to help RT handle that more
 gracefully.


 What I'm wondering is how I can tell if the database is unclean or if
 it's okay.  The upgrade history section in System Configuration shows
 that it did Upgrade from 4.0.19 to 4.2.3 once without errors, and then it
 did it again and it says (Incomplete).  Maybe that doesn't actually mean
 it tried twice though, I'm not sure.



 I've pushed

 https://github.com/bestpractical/rt/commit/0ac64855f479b4133f4fe838af6b8b2dec8f5d18.patch
 and it should be in 4.2.5.  You may be able to apply the patch
 manually to /usr/share/request-tracker4/etc/upgrade/4.1.1/schema.Pg
 or just clean out your DB by hand before letting the debian upgrade
 scripts go.


 Can I safely just drop  the table, drop the sequence, create the sequence,
 and create the table?  I won't lose anything critical by doing that?

 I'm guessing there's a bunch of stuff it was supposed to do after that,
 but it probably stopped at that point.  I'm just thrown off by it being in
 the upgrade history twice, the first time it looks like it did a whole
 bunch of stuff successfully, including this step and lot after this step.

 -kevin

   Processing 4.1.1
 
  Now populating database schema.
 
  [12453] [Wed May 21 03:19:36 2014] [critical]: DBD::Pg::st execute
 failed:
  ERROR:  cannot drop sequence objectscrips_id_seq because other objects
  depend on it
 
  DETAIL:  default for table objectscrips column id depends on sequence
  objectscrips_id_seq
 
  HINT:  Use DROP ... CASCADE to drop the dependent objects too. at
  /usr/share/request-tracker4/lib/RT/Handle.pm line 529.
  (/usr/share/request-tracker4/lib/RT.pm:394)
 
  DBD::Pg::st execute failed: ERROR:  cannot drop sequence
  objectscrips_id_seq because other objects depend on it
 
  DETAIL:  default for table objectscrips column id depends on sequence
  objectscrips_id_seq
 
  HINT:  Use DROP ... CASCADE to drop the dependent objects too. at
  /usr/share/request-tracker4/lib/RT/Handle.pm line 529.
 
  error encountered processing
  /usr/share/dbconfig-common/scripts/request-tracker4/upgrade/pgsql/4.2.3:
 
  /usr/share/dbconfig-common/scripts/request-tracker4/upgrade/pgsql/4.2.3
  exited with non-zero status
 
 
  There could be an issue with the Debian packages (they are still in the
  testing branch), but I'm trying to figure out what state the database
 is in
  now.  The system is working fine, and shows version 4.2.3.  If I
 navigate
  to Admin - Tools - System Configuration, then in the RT Upgrade
 History
  section it looks like it might have tried to upgrade the database twice,
  and the second time it failed (understandably).
 
 
  Is there a way I can verify that the database schema is completely up to
  date?
 
 
  Here is what the RT Upgrade History section shows: (Sorry for the
 HTML,
  wasn't sure how else to show it)
  RT (Current version: 4.2.3) ActionDateElapsedRT VersionInsert from
  /usr/share/request-tracker4/etc/upgrade/4.0.9/contentTue May 20 23:17:45
  20141 second4.2.3Insert from
  /usr/share/request-tracker4/etc/upgrade/4.0.18/contentTue May 20
 23:17:53
  20141 second4.2.3Insert from
  /usr/share/request-tracker4/etc/upgrade/4.0.19/contentTue May 20
 23:17:55
  20140 seconds4.2.3 http://rt/Admin/Tools/Configuration.html#Upgrade
 from
  4.0.19 to 4.2.3Tue May 20 23:17:56 20142 minutes4.2.3Insert from
  /usr/share/request-tracker4/etc/upgrade/4.0.9/contentTue May 20 23:19:29
  20140 seconds4.2.3Insert from
  /usr/share/request-tracker4/etc/upgrade/4.0.18/contentTue May 20
 23:19:34
  20140 seconds4.2.3Insert from
  

Re: [rt-users] Upgrade from 4.2.1 to 4.2.3 - no more outgoing e-mails

[Nicolas]

On Wed, 30 Apr 2014 13:56:46 -0400
Kevin Falcone falc...@bestpractical.com wrote:

 On Tue, Apr 29, 2014 at 06:32:41PM +0200, Web wrote:
  The *only* problem I have now, is that no e-mail goes out from the
  RT server. Nada.
  
  I can create tickets by sending e-mails to the RT server, I can
  browse the ticket through the web interface, I can reply, comment,
  do whatever on tickets, but no e-mail are sent.
  
  I've attached a debug file of a ticket reply action. All I see is
  No recipients found for deferred delivery on transaction.
 
  So I guess that my problem lies around this message, but I have no
  clue where to search next in order to solve this ...
  
 All this message means is that there were no users who had to be
 marked to send mail later.  It is not your problem.
 
  Any hint would be appreciated :)
 
 If RT appears to be generating email (and it certainly does appear to
 be generating email) I would be reading mail logs.
 
 You can use the Message-ID fields in the logs to match up with your
 mail logs.

Hello, well the problem was that I had nothing in my mail logs. I was
using msmtp as a mta, with the msmtp-wrapper configuration from the
Wiki (http://requesttracker.wikia.com/wiki/Msmtp).

But for an unknown reason, since the upgrade of RT and some other parts
of the system (but not msmtp), the ¨communication¨ between RT and the
MTA wasn´t working anymore.

So eventually I installed nullmailer, and it works perfectly now.


Thank you for your answer anyway.

 
 -kevin
 

Nicolas
-- 
RT Training - Dallas May 20-21
http://bestpractical.com/training

Re: [rt-users] Upgrade from 4.2.1 to 4.2.3 - no more outgoing e-mails

[Kevin Falcone]

On Tue, Apr 29, 2014 at 06:32:41PM +0200, Web wrote:
 The *only* problem I have now, is that no e-mail goes out from the RT
 server. Nada.
 
 I can create tickets by sending e-mails to the RT server, I can browse
 the ticket through the web interface, I can reply, comment, do whatever
 on tickets, but no e-mail are sent.
 
 I've attached a debug file of a ticket reply action. All I see is No
 recipients found for deferred delivery on transaction.

 So I guess that my problem lies around this message, but I have no clue
 where to search next in order to solve this ...
 
All this message means is that there were no users who had to be
marked to send mail later.  It is not your problem.

 Any hint would be appreciated :)

If RT appears to be generating email (and it certainly does appear to
be generating email) I would be reading mail logs.

You can use the Message-ID fields in the logs to match up with your
mail logs.

-kevin


pgprglmvZoXKp.pgp
Description: PGP signature
-- 
RT Training - Dallas May 20-21
http://bestpractical.com/training

[rt-users] Upgrade from 4.2.1 to 4.2.3 - no more outgoing e-mails

[Web]

# RT 4.2.3 on Debian Wheezy, Nginx 1.6.0, Postgresql 9.1


Hello everyone,

I have a problem I can't solve on my own.

I've just upgraded my RT server from 4.2.1 to 4.2.3. The upgrade process
went fine, no errors, everything seems to be running well.

The *only* problem I have now, is that no e-mail goes out from the RT
server. Nada.

I can create tickets by sending e-mails to the RT server, I can browse
the ticket through the web interface, I can reply, comment, do whatever
on tickets, but no e-mail are sent.

I've attached a debug file of a ticket reply action. All I see is No
recipients found for deferred delivery on transaction.

So I guess that my problem lies around this message, but I have no clue
where to search next in order to solve this ...


Any hint would be appreciated :)


Nicolas

[3425] [Tue Apr 29 16:17:16 2014] [debug]: Converting 'utf-8' to 'utf-8' for 
text/html - Subjectless message (/opt/rt4/sbin/../lib/RT/I18N.pm:295)
[3425] [Tue Apr 29 16:17:16 2014] [debug]: Converting 'utf-8' to 'utf-8' for 
text/html - Subjectless message (/opt/rt4/sbin/../lib/RT/I18N.pm:295)
[3425] [Tue Apr 29 16:17:17 2014] [debug]: About to prepare scrips for 
transaction #1500 (/opt/rt4/sbin/../lib/RT/Transaction.pm:187)
[3425] [Tue Apr 29 16:17:17 2014] [debug]: Found 6 scrips for TransactionCreate 
stage with applicable type(s) Correspond for txn #1500 on ticket #99 
(/opt/rt4/sbin/../lib/RT/Scrips.pm:495)
[3425] [Tue Apr 29 16:17:17 2014] [debug]: Converting 'utf-8' to 'utf-8' for 
text/plain - Subjectless message (/opt/rt4/sbin/../lib/RT/I18N.pm:295)
[3425] [Tue Apr 29 16:17:17 2014] [debug]: Converting 'utf-8' to 'utf-8' for 
text/html - Subjectless message (/opt/rt4/sbin/../lib/RT/I18N.pm:295)
[3425] [Tue Apr 29 16:17:17 2014] [debug]: Encode::Guess guessed encoding: 
ascii (/opt/rt4/sbin/../lib/RT/I18N.pm:595)
[3425] [Tue Apr 29 16:17:17 2014] [debug]: Encode::Guess guessed encoding: 
ascii (/opt/rt4/sbin/../lib/RT/I18N.pm:595)
[3425] [Tue Apr 29 16:17:17 2014] [debug]: Converting 'utf-8' to 'utf-8' for 
text/plain - Subjectless message (/opt/rt4/sbin/../lib/RT/I18N.pm:295)
[3425] [Tue Apr 29 16:17:17 2014] [debug]: Converting 'utf-8' to 'utf-8' for 
text/html - Subjectless message (/opt/rt4/sbin/../lib/RT/I18N.pm:295)
[3425] [Tue Apr 29 16:17:17 2014] [debug]: Encode::Guess guessed encoding: 
ascii (/opt/rt4/sbin/../lib/RT/I18N.pm:595)
[3425] [Tue Apr 29 16:17:17 2014] [debug]: Encode::Guess guessed encoding: 
ascii (/opt/rt4/sbin/../lib/RT/I18N.pm:595)
[3425] [Tue Apr 29 16:17:17 2014] [debug]: Converting 'utf-8' to 'utf-8' for 
text/plain - Subjectless message (/opt/rt4/sbin/../lib/RT/I18N.pm:295)
[3425] [Tue Apr 29 16:17:17 2014] [debug]: Converting 'utf-8' to 'utf-8' for 
text/html - Subjectless message (/opt/rt4/sbin/../lib/RT/I18N.pm:295)
[3425] [Tue Apr 29 16:17:17 2014] [debug]: Encode::Guess guessed encoding: 
ascii (/opt/rt4/sbin/../lib/RT/I18N.pm:595)
[3425] [Tue Apr 29 16:17:17 2014] [debug]: Encode::Guess guessed encoding: 
ascii (/opt/rt4/sbin/../lib/RT/I18N.pm:595)
[3425] [Tue Apr 29 16:17:17 2014] [debug]: Skipping Scrip #6 because it didn't 
Prepare (/opt/rt4/sbin/../lib/RT/Scrips.pm:361)
[3425] [Tue Apr 29 16:17:17 2014] [debug]: Skipping Scrip #11 because it isn't 
applicable (/opt/rt4/sbin/../lib/RT/Scrips.pm:353)
[3425] [Tue Apr 29 16:17:17 2014] [debug]: About to commit scrips for 
transaction #1500 (/opt/rt4/sbin/../lib/RT/Transaction.pm:210)
[3425] [Tue Apr 29 16:17:17 2014] [debug]: Committing scrip #3 on txn #1500 of 
ticket #99 (/opt/rt4/sbin/../lib/RT/Scrips.pm:306)
[3425] [Tue Apr 29 16:17:17 2014] [debug]: Calling SetRecipientDigests for 
transaction RT::Transaction=HASH(0x68eac00), id 1500 
(/opt/rt4/sbin/../lib/RT/Action/SendEmail.pm:623)
[3425] [Tue Apr 29 16:17:17 2014] [debug]: Working on mailfield To; recipients 
are  (/opt/rt4/sbin/../lib/RT/Action/SendEmail.pm:639)
[3425] [Tue Apr 29 16:17:17 2014] [debug]: X-RT-Originator: 
customerc...@blip.com
Subject: [blip.com #99] Test from Gmail after RT upgrade
In-Reply-To: 535f820c.1030...@gmail.com
X-Managed-BY: RT 4.2.3 (http://www.bestpractical.com/rt/)
References: rt-ticket...@blip.com 535f820c.1030...@gmail.com
Content-Type: multipart/alternative; boundary=--=_1398788237-3425-11
Reply-To: supp...@blip.com
Message-ID: rt-4.2.3-3425-1398788237-984.99-...@blip.com
X-RT-Loop-Prevention: blip.com
BCC: customerc...@blip.com
X-RT-Ticket: blip.com #99
From: root via Inred supp...@blip.com 
(/opt/rt4/sbin/../lib/RT/Action/SendEmail.pm:646)
[3425] [Tue Apr 29 16:17:17 2014] [debug]: Removing deferred recipients from 
To: line (/opt/rt4/sbin/../lib/RT/Action/SendEmail.pm:669)
[3425] [Tue Apr 29 16:17:17 2014] [debug]: Setting deferred recipients for 
attribute creation (/opt/rt4/sbin/../lib/RT/Action/SendEmail.pm:678)
[3425] [Tue Apr 29 16:17:17 2014] [debug]: Working on mailfield Cc; recipients 
are  (/opt/rt4/sbin/../lib/RT/Action/SendEmail.pm:639)
[3425] [Tue Apr 29 16:17:17 2014] [debug]: X-RT-Originator: 

Re: [rt-users] Upgrade / Migration Help from version 3.8.1 to 4.2.3

[Kevin Falcone]

On Sat, Apr 19, 2014 at 12:58:23AM -0500, Lists wrote:
 
 1.  Build new server with new OS and newer version of Perl, Apache, 
 mySQL and latest version of RT and then try to migrate or copy over our 
 customizations and databases.

This is what we do during a Best Practical upgrade.
You import your database and follow our upgrade instructions and then
you get to play whack-a-mole with your customizations and figure out
what is already a core feature.

-kevin


pgpiDDZC8Zki8.pgp
Description: PGP signature
-- 
RT Training - Dallas May 20-21
http://bestpractical.com/training

[rt-users] Upgrade / Migration Help from version 3.8.1 to 4.2.3

[Lists]

Hi,

I am new to the RT lists as well as new to the administration of the RT 
product.  My company has used RT for many years but was maintained by 
another admin.


I have been asked to upgrade our RT system from version 3.8.1 running on 
CentOS 5.9 to version 4.2.3 running on CentOS 6.5.  Since I am 
installing a new OS on new hardware, I will be installing Apache, Perl, 
mySQL, etc from the CentOS 6.5 rpm repositories.


Being completely new to the administration of RT, I was not sure which 
path was most practical (or possible).


1.  Build new server with new OS and newer version of Perl, Apache, 
mySQL and latest version of RT and then try to migrate or copy over our 
customizations and databases.


-or-

2.  Build new server, OS, Perl, Apache, mySQL but copy over our current 
version (3.8.1) of RT, get it to work on the new server and then perform 
upgrades?


I wasn't sure if one path was more reliable, practical, etc.

I am currently in the process of doing a new install just so I can 
become familiar with everything before I pick a path.


Any advice would be appreciated.

Thanks,

-David
--
RT Training - Dallas May 20-21
http://bestpractical.com/training

Re: [rt-users] Upgrade

[Alex Vandiver]

On Wed, 2014-03-26 at 13:08 +, Bryon Baker wrote:
 Where can I find instructions on how to apply this patch?

GET https://github.com/bestpractical/rt/commit/7d100f10.patch | patch -p1 -d 
/opt/rt4

Clear your Mason cache and restart Apache.
 - Alex

-- 
RT Training - Dallas May 20-21
http://bestpractical.com/training

Re: [rt-users] Upgrade

[Bryon Baker]

Thanks Alex

Bryon Baker
Network Operations Manager
Copesan - Specialists in Pest Solutions
800-267-3726  .  262-783-6261 ext. 2296
bba...@copesan.com
www.copesan.com
Servicing North America with Local Care

-Original Message-
From: rt-users-boun...@lists.bestpractical.com 
[mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Alex Vandiver
Sent: Thursday, March 27, 2014 11:21 AM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Upgrade

On Wed, 2014-03-26 at 13:08 +, Bryon Baker wrote:
 Where can I find instructions on how to apply this patch?

GET https://github.com/bestpractical/rt/commit/7d100f10.patch | patch -p1 -d 
/opt/rt4

Clear your Mason cache and restart Apache.
 - Alex

-- 
RT Training - Dallas May 20-21
http://bestpractical.com/training

-- 
RT Training - Dallas May 20-21
http://bestpractical.com/training

Re: [rt-users] Upgrade

[Bryon Baker]

Where can I find instructions on how to apply this patch?

Thanks
Bryon Baker
Network Operations Manager
Copesan - Specialists in Pest Solutions
800-267-3726  .  262-783-6261 ext. 2296
bba...@copesan.com
www.copesan.com
Servicing North America with Local Care


-Original Message-
From: rt-users-boun...@lists.bestpractical.com 
[mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Alex Vandiver
Sent: Tuesday, March 25, 2014 9:49 PM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Upgrade

On Wed, 2014-03-26 at 02:20 +, Bryon Baker wrote:
 I just upgrade from 4.2.0 to 4.2.3 I thought this was going to fix the 
 auto fill for email addresses when forwarding messages.  Was this not 
 true? Did I miss something?

This is not true.  I don't believe we've ever said that 4.2.3 does that.

The branch is still pending review.  You can apply the patch to your local 
instance if you'd like:

https://github.com/bestpractical/rt/commit/7d100f10.patch

 - Alex

--
RT Training - Dallas May 20-21
http://bestpractical.com/training

-- 
RT Training - Dallas May 20-21
http://bestpractical.com/training

[rt-users] Upgrade

[Bryon Baker]

I just upgrade from 4.2.0 to 4.2.3 I thought this was going to fix the auto 
fill for email addresses when forwarding messages.  Was this not true? Did I 
miss something?

Because it still does not work.

Thanks for the help

Bryon Baker
Network Operations Manager
Copesan - Specialists in Pest Solutions
800-267-3726  *  262-783-6261 ext. 2296
bba...@copesan.commailto:cstep...@copesan.com
www.copesan.comhttp://www.copesan.com/
Servicing North America with Local Care

-- 
RT Training - Dallas May 20-21
http://bestpractical.com/training

Re: [rt-users] Upgrade

[Alex Vandiver]

On Wed, 2014-03-26 at 02:20 +, Bryon Baker wrote:
 I just upgrade from 4.2.0 to 4.2.3 I thought this was going to fix the
 auto fill for email addresses when forwarding messages.  Was this not
 true? Did I miss something?

This is not true.  I don't believe we've ever said that 4.2.3 does that.

The branch is still pending review.  You can apply the patch to your
local instance if you'd like:

https://github.com/bestpractical/rt/commit/7d100f10.patch

 - Alex

-- 
RT Training - Dallas May 20-21
http://bestpractical.com/training

Re: [rt-users] upgrade from 3.6 to 4 mysql upgrade error

[Kevin Falcone]

On Wed, Mar 05, 2014 at 01:47:42PM -0700, George Kelbley wrote:
 
 ERROR 1062 (23000) at line 220: Duplicate entry '' for key 'Users1'
 
 This problem appears in some other postings on the list, but I'm not
 sure how to proceed.  If its caused by
 a bad ticket, (this database was started in 1997!),  maybe I can
 shred the ticket(s) in question, but version 3.6
 does not support shredding if I'm reading things correctly.

I believe I've answered this before, but as I can't trivially find the
message, I'll recreate it here.

What has happened is that your Users table contains some users whose
Users.Name contain invalid characters and so when they're transformed
into UTF8 there is no valid mapping and they collapse to ''.
Once there are two of those, you validate the unique index on Name.

So, to proceed.
SHOW CREATE TABLE Users; # confirm that Users1 is the Unique index
drop index Users1 on Users;
copy/paste the last ALTER TABLE statement from queries.sql and
rerun it (or create a new file containing only the last statement and
run it).
select * from Users where Name = '';
marvel at the encoding failures
update Users set Name = CONCAT('SPAMUSER-',id) where Name = '';
tweak SPAMUSER as you desire
CREATE UNIQUE INDEX Users1 ON Users (Name) ;

Generally, once I know that I have a data set with a failure like
this, I rework my upgrade to do

drop index;
mysql -uroot -p  queries.sql
update;
create index;

I'll look into adding some part of this to UPGRADING.mysql

-kevin


pgpIolu0y7BK3.pgp
Description: PGP signature
-- 
RT Training London, March 19-20 and Dallas May 20-21
http://bestpractical.com/training

Re: [rt-users] upgrade from 3.6 to 4 mysql upgrade error

[George Kelbley]

Thanks, this seems to have worked.  We use rt daily to handle user 
problems/requests, but we've let it get a little long in the tooth.


At this point I'm trying to figure out how long its going to take for us 
to upgrade.


thanks again!

On 3/6/14 9:39 AM, Kevin Falcone wrote:

CREATE UNIQUE INDEX Users1 ON Users (Name) ;

--
RT Training London, March 19-20 and Dallas May 20-21
http://bestpractical.com/training

[rt-users] upgrade from 3.6 to 4 mysql upgrade error

[George Kelbley]

I'm migrating an old 3.6 install of rt to a new server running version 4 
(installed on debian wheezy from

packages), using mysql on both old and new servers.

I've followed the steps in the documentation for a trial run:

dumped the rt database on my old server with the 
--default-character-set=binary option,


and created a new database on the new server with the latin1 character 
set, imported the database and
run the upgrade-mysql-schema script.  When importing the produced 
queries.sql into my database, I get


ERROR 1062 (23000) at line 220: Duplicate entry '' for key 'Users1'

This problem appears in some other postings on the list, but I'm not 
sure how to proceed.  If its caused by
a bad ticket, (this database was started in 1997!),  maybe I can shred 
the ticket(s) in question, but version 3.6

does not support shredding if I'm reading things correctly.

The ALTER TABLES Users section of the queries.sql has these lines:

ALTER TABLE Users
   MODIFY WebEncoding VARCHAR(16) CHARACTER SET ascii NULL DEFAULT NULL,
   MODIFY AuthSystem VARCHAR(30) CHARACTER SET utf8 NULL DEFAULT NULL,
   MODIFY MobilePhone VARCHAR(30) CHARACTER SET utf8 NULL DEFAULT NULL,
   MODIFY WorkPhone VARCHAR(30) CHARACTER SET utf8 NULL DEFAULT NULL,
   MODIFY PagerPhone VARCHAR(30) CHARACTER SET utf8 NULL DEFAULT NULL,
   MODIFY ExternalContactInfoId VARCHAR(100) CHARACTER SET utf8 NULL 
DEFAULT NULL,
   MODIFY ContactInfoSystem VARCHAR(30) CHARACTER SET utf8 NULL DEFAULT 
NULL,

   MODIFY HomePhone VARCHAR(30) CHARACTER SET utf8 NULL DEFAULT NULL,
   MODIFY Address1 VARCHAR(200) CHARACTER SET utf8 NULL DEFAULT NULL,
   MODIFY ExternalAuthId VARCHAR(100) CHARACTER SET utf8 NULL DEFAULT NULL,
   MODIFY Comments TEXT CHARACTER SET utf8 NULL DEFAULT NULL,
   MODIFY NickName VARCHAR(16) CHARACTER SET utf8 NULL DEFAULT NULL,
   MODIFY Address2 VARCHAR(200) CHARACTER SET utf8 NULL DEFAULT NULL,
   MODIFY Timezone VARCHAR(50) CHARACTER SET ascii NULL DEFAULT NULL,
   MODIFY FreeformContactInfo TEXT CHARACTER SET utf8 NULL DEFAULT NULL,
   MODIFY RealName VARCHAR(120) CHARACTER SET utf8 NULL DEFAULT NULL,
   MODIFY City VARCHAR(100) CHARACTER SET utf8 NULL DEFAULT NULL,
   MODIFY EmailAddress VARCHAR(120) CHARACTER SET ascii NULL DEFAULT NULL,
   MODIFY EmailEncoding VARCHAR(16) CHARACTER SET ascii NULL DEFAULT NULL,
   MODIFY State VARCHAR(100) CHARACTER SET utf8 NULL DEFAULT NULL,
   MODIFY Signature TEXT CHARACTER SET utf8 NULL DEFAULT NULL,
   MODIFY Zip VARCHAR(16) CHARACTER SET utf8 NULL DEFAULT NULL,
   MODIFY Organization VARCHAR(200) CHARACTER SET utf8 NULL DEFAULT NULL,
   MODIFY Lang VARCHAR(16) CHARACTER SET ascii NULL DEFAULT NULL,
   MODIFY Gecos VARCHAR(16) CHARACTER SET utf8 NULL DEFAULT NULL,
   MODIFY Country VARCHAR(50) CHARACTER SET utf8 NULL DEFAULT NULL,
   MODIFY Name VARCHAR(200) CHARACTER SET utf8 NOT NULL DEFAULT '';

Any thoughts greatly appreciated
--
RT Training London, March 19-20 and Dallas May 20-21
http://bestpractical.com/training

[rt-users] Upgrade problems (seems to be between 4.0.18 and 4.1.0)

[James Craig]

I am in the process of doing a long-needed upgrade, but have hit
a stumbling block.  Any help would be appreciated!




/usr/bin/perl -I/opt/rt4/local/lib -I/opt/rt4/lib sbin/rt-setup-database
--action upgrade --prompt-for-dba-password
In order to create or update your RT database, this script needs to connect to
your  mysql instance on localhost (port '') as root
Please specify that user's database password below. If the user has no database
password, just press return.

Password: Working with:
Type:   mysql
Host:   localhost
Port:
Name:   rt3
User:   root
DBA:root
Enter RT version you're upgrading from: 3.8.7

Going to apply following upgrades:
* 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
* 4.0.9
* 4.0.12
* 4.0.13
* 4.0.18
* 4.1.0
* 4.1.1
* 4.1.4
* 4.1.5
* 4.1.6
* 4.1.7
* 4.1.8
* 4.1.9
* 4.1.10
* 4.1.11
* 4.1.12
* 4.1.13
* 4.1.14
* 4.1.15
* 4.1.16
* 4.1.17
* 4.1.18
* 4.1.19
* 4.1.20
* 4.1.21
* 4.1.22
* 4.1.23
* 4.2.1

Enter RT version if you want to stop upgrade at some point,
  or leave it blank if you want apply above upgrades:

IT'S VERY IMPORTANT TO BACK UP BEFORE THIS STEP
Proceed [y/N]:y
Processing 3.8.8
Now inserting data.
Processing 3.8.9
Now inserting data.
[7072] [Thu Dec 19 21:15:26 2013] [warning]: Use of uninitialized value in
string eq at /local/linroot/rt-4.2.1/sbin/../lib/RT/Template.pm line 750, 
line 4. (/local/linroot/rt-4.2.1/sbin/../lib/RT/Template.pm:750)
[7072] [Thu Dec 19 21:15:26 2013] [warning]: Use of uninitialized value in
string eq at /local/linroot/rt-4.2.1/sbin/../lib/RT/Template.pm line 750, 
line 4. (/local/linroot/rt-4.2.1/sbin/../lib/RT/Template.pm:750)
Processing 3.9.1
Now inserting data.
Processing 3.9.2
Now inserting data.
Processing 3.9.3
Now populating database schema.
Processing 3.9.5
Now populating database schema.
Processing 3.9.6
Now populating database schema.
Processing 3.9.7
Now populating database schema.
Now inserting data.
Processing 3.9.8
Now populating database schema.
Now inserting data.
Processing 4.0.0rc2
Now populating database schema.
Processing 4.0.0rc4
Now populating database schema.
Processing 4.0.0rc7
Now inserting data.
Processing 4.0.1
Now inserting data.
[7072] [Thu Dec 19 21:15:44 2013] [error]: Invalid right. Couldn't canonicalize
right 'DelegateRights' (/local/linroot/rt-4.2.1/sbin/../lib/RT/ACE.pm:456)
[7072] [Thu Dec 19 21:15:44 2013] [error]: Invalid right. Couldn't canonicalize
right 'DelegateRights' (/local/linroot/rt-4.2.1/sbin/../lib/RT/ACE.pm:456)
[7072] [Thu Dec 19 21:15:44 2013] [error]: Invalid right. Couldn't canonicalize
right 'DelegateRights' (/local/linroot/rt-4.2.1/sbin/../lib/RT/ACE.pm:456)
Processing 4.0.3
Now inserting data.
Processing 4.0.4
Now inserting data.
Processing 4.0.6
Now populating database schema.
Now inserting data.
Processing 4.0.9
Now inserting data.
Processing 4.0.12
Now populating database schema.
Processing 4.0.13
Now populating database schema.
Processing 4.0.18
Now inserting data.
Processing 4.1.0
Now inserting data.
Couldn't finish 'upgrade' step.

ERROR: One of initial functions failed: Can't call method Content on an
undefined value at ./etc/upgrade/4.1.0/content line 35,  line 18.


make: *** [upgrade-database] Error 255




James Craig



--
James Craig, Department of Computer Science, RIT
102 Lomb Memorial Drive, Rochester, NY 14623
mailto:j...@cs.rit.edu, voice: (585) 475-5254

CONFIDENTIALITY NOTE: The information transmitted, including attachments, is
intended only for the person(s) or entity to which it is addressed and may
contain confidential and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon this
information by persons or entities other than the intended recipient is
prohibited. If you received this in error, please contact the sender and
destroy any copies of this information.

Re: [rt-users] Upgrade problems (seems to be between 4.0.18 and 4.1.0)

[Kevin Falcone]

On Fri, Dec 20, 2013 at 09:57:37AM -0500, James Craig wrote:
 
 I am in the process of doing a long-needed upgrade, but have hit
 a stumbling block.  Any help would be appreciated!
 Processing 4.1.0
 Now inserting data.
 Couldn't finish 'upgrade' step.
 
 ERROR: One of initial functions failed: Can't call method Content on an
 undefined value at ./etc/upgrade/4.1.0/content line 35,  line 18.

This implies you don't have a default homepage setting.
I'm not sure how the front page of your RT works without it
(presumably all of your privileged users have a customized one, but
you must have errors when adding new privileged users who log in for
the first time).

Examine the results of
select id, Name, Description, Creator from Attributes where Name like 
'%HomepageSettings%';

using sbin/rt-attributes-viewer as needed to peek inside those that
exist.

The upgrade script expects that one exists at the system, not user
level, it would look like this:

 6 | HomepageSettings | HomepageSettings |   1

-kevin


pgp6DTwEOsrZk.pgp
Description: PGP signature

Re: [rt-users] Upgrade problems (seems to be between 4.0.18 and 4.1.0)

[James Craig]

On Fri, 20 Dec 2013, Kevin Falcone wrote:


On Fri, Dec 20, 2013 at 09:57:37AM -0500, James Craig wrote:


I am in the process of doing a long-needed upgrade, but have hit
a stumbling block.  Any help would be appreciated!
Processing 4.1.0
Now inserting data.
Couldn't finish 'upgrade' step.

ERROR: One of initial functions failed: Can't call method Content on an
undefined value at ./etc/upgrade/4.1.0/content line 35,  line 18.


This implies you don't have a default homepage setting.
I'm not sure how the front page of your RT works without it
(presumably all of your privileged users have a customized one, but
you must have errors when adding new privileged users who log in for
the first time).



With our very old version, we didn't have any errors of any sort that
I saw or was aware of.
(the hardware we were running died, and so we opted to
 do an upgrade of hardware and software, hoping to import a
 cold file of the database)

I was hoping that getting it to upgrade from our version would put
stuff that was missing into place.



Examine the results of
select id, Name, Description, Creator from Attributes where Name like 
'%HomepageSettings%';

using sbin/rt-attributes-viewer as needed to peek inside those that
exist.

The upgrade script expects that one exists at the system, not user
level, it would look like this:

6 | HomepageSettings | HomepageSettings |   1



I will admit that I do very little database stuff; It'll take me a
bit of time to figure this out.

Thank you for the quick response!


James Craig

--
James Craig, Department of Computer Science, RIT
102 Lomb Memorial Drive, Rochester, NY 14623
mailto:j...@cs.rit.edu, voice: (585) 475-5254

CONFIDENTIALITY NOTE: The information transmitted, including attachments, is
intended only for the person(s) or entity to which it is addressed and may
contain confidential and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon this
information by persons or entities other than the intended recipient is
prohibited. If you received this in error, please contact the sender and
destroy any copies of this information.

Re: [rt-users] Upgrade problems (seems to be between 4.0.18 and 4.1.0)

[Kevin Falcone]

On Fri, Dec 20, 2013 at 02:57:36PM -0500, James Craig wrote:
 
 Just to follow up,
 
 it turns out the documentation I had was wrong; the old version was
 3.4.2
 
 your comment about the HomepageSettings made me question the notes I
   was working from.
 
   Once I started the upgrade from 3.4.2 instead of 3.8.7,
   the  make upgrade-database completed.

Glad to hear it was something that simple.

-kevin


pgp3ssObvVIGN.pgp
Description: PGP signature

Re: [rt-users] upgrade issues 4.0.17 - 4.2.1

[Mike W]

On 12/3/2013 11:01 PM, Alex Vandiver wrote:

On Tue, 2013-12-03 at 22:35 -0600, Mike W wrote:

Aha! I found:

Upgrade from 4.1.0 to 4.1.1 (Incomplete)

Fixed that and got things rolling properly. Thanks for telling me about
that. Had no idea it logged that there.


It's new in 4.2.  However, it is no substitute for reading the 'make
upgrade-database' output itself.
  - Alex




Fair point, unfortunately I mis-understood just where it broke down 
(thought it died in 4.1.1, not 4.1.0 because it was in the 4.1.1 section 
where I saw the errors).


The new log feature definitely helps.

--

Mike Wilson

Re: [rt-users] Upgrade from 4.0.x to 4.2.x - Fresh install with DB upgrade ok?

[Alex Vandiver]

On Mon, 2013-12-02 at 17:49 +, Cena, Stephen (ext. 300) wrote:
 I'm getting ready to do an upgrade from 4.0.18 to 4.2.1 here on two
 servers. When I try the upgrade in a test environment, I get a bunch
 of errors that fly by (I don't have them, sorry :( )

Get them and look at them.  It may well solve you large amounts of time
and data loss later.

  but the site appears to be working. My question is, is it safe to do
 a fresh install of 4.2.1 and then use the 'make upgrade-database-
 script against the current database, use my current RT_SiteConfig.pm
 file  spin up the site?

That's the recommended set of steps to upgrade, yes.  Though it was
written for 3.8 - 4.0, you may find
http://blog.bestpractical.com/2011/07/upgrading-to-rt-4.html helpful.
 - Alex

[rt-users] upgrade issues 4.0.17 - 4.2.1

[Mike W]

Upgrade from 4.0.17 and having some issues with email notices. It seems 
to be connected to scrips. I did run the make upgrade-database



[11794] [Wed Dec  4 03:20:20 2013] [warning]: DBD::mysql::st execute 
failed: Table 'rt4.ObjectScrips' doesn't exist at sbin/rt-validator line 
1300. (sbin/rt-validator:1300)
[11794] [Wed Dec  4 03:20:20 2013] [critical]: DBD::mysql::st execute 
failed: Table 'rt4.ObjectScrips' doesn't exist at sbin/rt-validator line 
1300. (/usr/local/rt4/sbin/../lib/RT.pm:391)
DBD::mysql::st execute failed: Table 'rt4.ObjectScrips' doesn't exist at 
sbin/rt-validator line 1300.



Is there a way I can manually correct this missing rt4.ObjectScrips 
entry? Or better yet script I can run in the upgrade area?


--

Mike Wilson

Re: [rt-users] upgrade issues 4.0.17 - 4.2.1

[Alex Vandiver]

On Tue, 2013-12-03 at 21:37 -0600, Mike W wrote:
 Upgrade from 4.0.17 and having some issues with email notices. It seems 
 to be connected to scrips. I did run the make upgrade-database

The errors below imply that it if you did run it, it did not complete.

Show the RT Upgrade History section of Admin → Tools → System
Configuration.
 - Alex

Re: [rt-users] upgrade issues 4.0.17 - 4.2.1

[Mike W]

On 12/3/2013 10:09 PM, Alex Vandiver wrote:

On Tue, 2013-12-03 at 21:37 -0600, Mike W wrote:

Upgrade from 4.0.17 and having some issues with email notices. It seems
to be connected to scrips. I did run the make upgrade-database


The errors below imply that it if you did run it, it did not complete.

Show the RT Upgrade History section of Admin → Tools → System
Configuration.
  - Alex



Aha! I found:

Upgrade from 4.1.0 to 4.1.1 (Incomplete)

Fixed that and got things rolling properly. Thanks for telling me about 
that. Had no idea it logged that there.


--

Mike Wilson

Re: [rt-users] upgrade issues 4.0.17 - 4.2.1

[Alex Vandiver]

On Tue, 2013-12-03 at 22:35 -0600, Mike W wrote:
 Aha! I found:
 
 Upgrade from 4.1.0 to 4.1.1 (Incomplete)
 
 Fixed that and got things rolling properly. Thanks for telling me about 
 that. Had no idea it logged that there.

It's new in 4.2.  However, it is no substitute for reading the 'make
upgrade-database' output itself.
 - Alex

[rt-users] Upgrade from 4.0.x to 4.2.x - Fresh install with DB upgrade ok?

[Cena, Stephen (ext. 300)]

I'm getting ready to do an upgrade from 4.0.18 to 4.2.1 here on two servers. 
When I try the upgrade in a test environment, I get a bunch of errors that fly 
by (I don't have them, sorry :( ) but the site appears to be working. My 
question is, is it safe to do a fresh install of 4.2.1 and then use the 'make 
upgrade-database- script against the current database, use my current 
RT_SiteConfig.pm file  spin up the site?

[rt-users] Upgrade steps for Ubuntu 13.10 RT4.2.0 to RT4.2.1

[mmahoney]

My Linux/RT Kung-Fu is weak and I realize that the new version of RT has only
been out for a few days, if someone has the upgrade steps for upgrading to
4.2.1, I would appreciate it immensely. Happy Thanksgiving and stuff!



--
View this message in context: 
http://requesttracker.8502.n7.nabble.com/Upgrade-steps-for-Ubuntu-13-10-RT4-2-0-to-RT4-2-1-tp55904.html
Sent from the Request Tracker - User mailing list archive at Nabble.com.

Re: [rt-users] Upgrade steps for Ubuntu 13.10 RT4.2.0 to RT4.2.1

[Adam Hutchins]

Go here: https://www.bestpractical.com/docs/rt/4.2/

Start with README. It's very simple.

Adam Hutchins, Systems Administrator
Town of Kernersville, NC, USA
o-336.992.5456 m-336.529.7164

-Original Message-
From: mmahoney [mailto:mmaho...@nhsocal.com]
Sent: Friday, November 22, 2013 1:32 PM
To: rt-users@lists.bestpractical.com
Subject: [rt-users] Upgrade steps for Ubuntu 13.10 RT4.2.0 to RT4.2.1

My Linux/RT Kung-Fu is weak and I realize that the new version of RT has only 
been out for a few days, if someone has the upgrade steps for upgrading to 
4.2.1, I would appreciate it immensely. Happy Thanksgiving and stuff!



--
View this message in context: 
http://requesttracker.8502.n7.nabble.com/Upgrade-steps-for-Ubuntu-13-10-RT4-2-0-to-RT4-2-1-tp55904.html
Sent from the Request Tracker - User mailing list archive at Nabble.com.

This email message, and any attachment(s) hereto, as well as any email 
message(s) that may be sent in response to it, may be considered Public Record, 
and as such are subject to requests for review.  If you are not the intended 
recipient, please destroy this message and inform the sender immediately.  The 
information contained in this email may be confidential and, in any event, is 
intended only for the use of the entity or individual to whom it is addressed.  
Thank you.

Re: [rt-users] upgrade from 4.0.5 to 4.2.0, lifecycle name error

[Kevin Falcone]

On Mon, Nov 11, 2013 at 12:52:10PM -0500, Ryan Whalen wrote:
I disabled the RTIR Incidents queue and the errors stopped.

There is no version of RTIR which is compatible with RT 4.2.0

On Mon, Nov 11, 2013 at 9:32 AM, Ryan Whalen [1]rwha...@advanceweb.com 
 wrote:
 
  Hello,
  I upgraded from 4.0.5 to 4.2.0, which went smooth for the most part.
  Now when I go to my dashboard it stops loading and says An internal RT 
 error has occurred.
  Your administrator can find more details in RT's log files.
  It only stops when there is a widget with queue information. Here is 
 what the logs show:
  httpd error log:
  [error]: Can't call mehod Name on an undefined value at
  RTROOT/share/html/Elements/QueueSummaryByStatus line130
  Stack:
  [RTROOT/share/html/Elements/QueueSummaryByStatus:130]
  [RTROOT/share/html/Elements/MyAdminQueues:52]
  [RTROOT/share/html/Elements/TitleBox:56]
  [RTROOT/share/html/Elements/MyAdminQueues:52]
  [RTROOT/share/html/Elements/MyRT:97]
  ...
  some more
  ...
  Any ideas when happened? I ran the upgrade for MySQL. without any 
 problems, and everything
  else seems to work so far.
  Thanks,
  Ryan


pgpgQmqJCQvXI.pgp
Description: PGP signature

[rt-users] upgrade from 4.0.5 to 4.2.0, lifecycle name error

[Ryan Whalen]

Hello,

I upgraded from 4.0.5 to 4.2.0, which went smooth for the most part.

Now when I go to my dashboard it stops loading and says An internal RT
error has occurred. Your administrator can find more details in RT's log
files.

It only stops when there is a widget with queue information. Here is what
the logs show:

httpd error log:

[error]: Can't call mehod Name on an undefined value at
RTROOT/share/html/Elements/QueueSummaryByStatus line130

Stack:
 [RTROOT/share/html/Elements/QueueSummaryByStatus:130]
 [RTROOT/share/html/Elements/MyAdminQueues:52]
 [RTROOT/share/html/Elements/TitleBox:56]
 [RTROOT/share/html/Elements/MyAdminQueues:52]
 [RTROOT/share/html/Elements/MyRT:97]
...
some more
...

Any ideas when happened? I ran the upgrade for MySQL. without any problems,
and everything else seems to work so far.

Thanks,
Ryan

Re: [rt-users] upgrade from 4.0.5 to 4.2.0, lifecycle name error

[Ryan Whalen]

I disabled the RTIR Incidents queue and the errors stopped.




On Mon, Nov 11, 2013 at 9:32 AM, Ryan Whalen rwha...@advanceweb.com wrote:

 Hello,

 I upgraded from 4.0.5 to 4.2.0, which went smooth for the most part.

 Now when I go to my dashboard it stops loading and says An internal RT
 error has occurred. Your administrator can find more details in RT's log
 files.

 It only stops when there is a widget with queue information. Here is what
 the logs show:

 httpd error log:

 [error]: Can't call mehod Name on an undefined value at
 RTROOT/share/html/Elements/QueueSummaryByStatus line130

 Stack:
  [RTROOT/share/html/Elements/QueueSummaryByStatus:130]
  [RTROOT/share/html/Elements/MyAdminQueues:52]
  [RTROOT/share/html/Elements/TitleBox:56]
  [RTROOT/share/html/Elements/MyAdminQueues:52]
  [RTROOT/share/html/Elements/MyRT:97]
 ...
 some more
 ...

 Any ideas when happened? I ran the upgrade for MySQL. without any
 problems, and everything else seems to work so far.

 Thanks,
 Ryan

[rt-users] Upgrade to 4.0.18, now RT not working

[Max McGrath]

This is what I'm seeing in rt.log:

[1892] [Thu Oct 17 13:17:58 2013] [error]: mkdir
/opt/rt4/var/mason_data/obj/1972688873: Permission denied at
/usr/local/share/perl/5.14.2/HTML/Mason/Compiler/ToObject.pm line 107.

Stack:
  [/usr/local/share/perl/5.14.2/Carp.pm:100]
  [/usr/share/perl/5.14/File/Path.pm:156]
  [/usr/share/perl/5.14/File/Path.pm:132]
  [/usr/share/perl/5.14/File/Path.pm:114]
  [/usr/local/share/perl/5.14.2/HTML/Mason/Compiler/ToObject.pm:107]
  [/usr/local/share/perl/5.14.2/HTML/Mason/Interp.pm:437]
  [/usr/local/share/perl/5.14.2/HTML/Mason/Request.pm:249]
  [/usr/local/share/perl/5.14.2/HTML/Mason/Request.pm:212]
  [/opt/rt4/sbin/../lib/RT/Interface/Web/Request.pm:62]
  [/usr/local/share/perl/5.14.2/Class/Container.pm:275]
  [/usr/local/share/perl/5.14.2/Class/Container.pm:353]
  [/usr/local/share/perl/5.14.2/HTML/Mason/Interp.pm:348]
  [/usr/local/share/perl/5.14.2/HTML/Mason/Interp.pm:342]
  [/usr/local/share/perl/5.14.2/HTML/Mason/PSGIHandler.pm:48]
  [/usr/local/share/perl/5.14.2/HTML/Mason/PSGIHandler/Streamy.pm:52]
  [/opt/rt4/sbin/../lib/RT/Interface/Web/Handler.pm:303]
  [/usr/local/share/perl/5.14.2/Plack/Util.pm:324]
  [/usr/local/share/perl/5.14.2/Plack/Handler/Apache2.pm:68]
  [/usr/local/share/perl/5.14.2/Plack/Handler/Apache2.pm:91]
  [-e:0] (/opt/rt4/sbin/../lib/RT/Interface/Web/Handler.pm:208)


Max
--
Max McGrath
Network Administrator
Carthage College
262-552-5512
mmcgr...@carthage.edu

Re: [rt-users] Upgrade to 4.0.18, now RT not working

[Max McGrath]

Cleared mason cache again and all is well.

--
Max McGrath
Network Administrator
Carthage College
262-552-5512
mmcgr...@carthage.edu


On Thu, Oct 17, 2013 at 8:18 AM, Max McGrath mmcgr...@carthage.edu wrote:

 This is what I'm seeing in rt.log:

 [1892] [Thu Oct 17 13:17:58 2013] [error]: mkdir
 /opt/rt4/var/mason_data/obj/1972688873: Permission denied at
 /usr/local/share/perl/5.14.2/HTML/Mason/Compiler/ToObject.pm line 107.

 Stack:
   [/usr/local/share/perl/5.14.2/Carp.pm:100]
   [/usr/share/perl/5.14/File/Path.pm:156]
   [/usr/share/perl/5.14/File/Path.pm:132]
   [/usr/share/perl/5.14/File/Path.pm:114]
   [/usr/local/share/perl/5.14.2/HTML/Mason/Compiler/ToObject.pm:107]
   [/usr/local/share/perl/5.14.2/HTML/Mason/Interp.pm:437]
   [/usr/local/share/perl/5.14.2/HTML/Mason/Request.pm:249]
   [/usr/local/share/perl/5.14.2/HTML/Mason/Request.pm:212]
   [/opt/rt4/sbin/../lib/RT/Interface/Web/Request.pm:62]
   [/usr/local/share/perl/5.14.2/Class/Container.pm:275]
   [/usr/local/share/perl/5.14.2/Class/Container.pm:353]
   [/usr/local/share/perl/5.14.2/HTML/Mason/Interp.pm:348]
   [/usr/local/share/perl/5.14.2/HTML/Mason/Interp.pm:342]
   [/usr/local/share/perl/5.14.2/HTML/Mason/PSGIHandler.pm:48]
   [/usr/local/share/perl/5.14.2/HTML/Mason/PSGIHandler/Streamy.pm:52]
   [/opt/rt4/sbin/../lib/RT/Interface/Web/Handler.pm:303]
   [/usr/local/share/perl/5.14.2/Plack/Util.pm:324]
   [/usr/local/share/perl/5.14.2/Plack/Handler/Apache2.pm:68]
   [/usr/local/share/perl/5.14.2/Plack/Handler/Apache2.pm:91]
   [-e:0] (/opt/rt4/sbin/../lib/RT/Interface/Web/Handler.pm:208)


 Max
 --
 Max McGrath
 Network Administrator
 Carthage College
 262-552-5512
 mmcgr...@carthage.edu

Re: [rt-users] Upgrade to 4.2 fail

[Max McGrath]

Yeah...a co-worker of mine got it working.  Sorry, I can't be more clear on
what he did.  He said it was a mixture of your suggestions and some other
things.  Apache configurations are above my head...

But it's working now!

--
Max McGrath
Network Administrator
Carthage College
262-552-5512
mmcgr...@carthage.edu


On Mon, Oct 7, 2013 at 3:26 PM, Len Jaffe lenja...@jaffesystems.com wrote:

 Anything?


 On Fri, Oct 4, 2013 at 10:49 AM, Len Jaffe lenja...@jaffesystems.comwrote:

 in httpd.conf   and this will depend on your version of apache, and
 how you've structured your configurations files.

 You need to load the fastcgi module

 LoadModule fastcgi_module modules/mod_fastcgi.so

 You need to declare your fastcgi service

 FastCgiServer /pathto/RT/sbin/rt-server.fcgi -processes 5
 -idle-timeout 30

 your settings for processes and timeout will vary according to your load

 Inside your virtual host definitions, tell apache how to handle fcgi
 requests

  AddHandler fastcgi-script fcgi


 Tell apache how to run the RT code


 Alias /RT /pathto/RT/sbin/rt-server.fcgi/
 Directory/pathto/RT/sbin/*
   Options Indexes +ExecCGI FollowSymLinks
   AllowOverRide None
   Satisfy Any
   Order allow,deny
   Allow from all
 /Directory

 and tell apache about the directory where the RT source lives

 Alias /RT/NoAuth/images/  /pathto/RT/share/html/NoAuth/images/
 Directory /pathto/RT/share/html/*
   Options Indexes FollowSymLinks
   AllowOverride None
   Order allow,deny
   Allow from all
 /Directory




 On Fri, Oct 4, 2013 at 9:37 AM, Max McGrath mmcgr...@carthage.eduwrote:

 Thanks!

 Tried moving to FastCgi and I now get:

 You're almost there!You haven't yet configured your webserver to run
 RT. You appear to have installed RT's web interface correctly, but haven't
 yet configured your web server to run the RT server which powers the web
 interface. The next step is to edit your webserver's configuration file to
 instruct it to use RT's *mod_perl* or *FastCGI* handler. If you need
 commercial support, please contact us at sa...@bestpractical.com.

 I'm definitely not a web server expert...so...any advice?

 Max

 --
 Max McGrath
 Network Administrator
 Carthage College
 262-552-5512
 mmcgr...@carthage.edu


 On Wed, Oct 2, 2013 at 10:53 PM, Alex Vandiver ale...@bestpractical.com
  wrote:

 On Wed, 2013-10-02 at 21:53 -0500, Max McGrath wrote:
  Nope...definitely did that step: [snp]

 Ah.  Then the perl that your mod_perl is linked against is not the perl
 that you configured RT with -- did you recompile a newer perl to meet
 the = 5.10.1 dep, but not recompile mod_perl?  Deploying with mod_fcgi
 or mod_fastcgi is probably easier than upgrading mod_perl.
  - Alex





 --
 RT Training in New York, October 8th and 9th:
 http://bestpractical.com/training




 --
 lenja...@jaffesystems.com   614-404-4214@lenjaffe
 Software Engineer, Founder Volunteerable http://www.volunteerable..com/,
 Host of Columbus Code Jam http://www.meetup.com/techlifecolumbus/
 www.lenjaffe.com http://www.theycomewithcheese.com
 Perl Advent Planet http://www.lenjaffe.com/PerlAdventPlanet/ - Advent
 Calendars: Perlish and otherwise.




 --
 lenja...@jaffesystems.com   614-404-4214@lenjaffe
 Software Engineer, Founder Volunteerable http://www.volunteerable..com/,
 Host of Columbus Code Jam http://www.meetup.com/techlifecolumbus/
 www.lenjaffe.com http://www.theycomewithcheese.com
 Perl Advent Planet http://www.lenjaffe.com/PerlAdventPlanet/ - Advent
 Calendars: Perlish and otherwise.

Re: [rt-users] Upgrade to 4.2 fail

[Len Jaffe]

Anything?


On Fri, Oct 4, 2013 at 10:49 AM, Len Jaffe lenja...@jaffesystems.comwrote:

 in httpd.conf   and this will depend on your version of apache, and
 how you've structured your configurations files.

 You need to load the fastcgi module

 LoadModule fastcgi_module modules/mod_fastcgi.so

 You need to declare your fastcgi service

 FastCgiServer /pathto/RT/sbin/rt-server.fcgi -processes 5
 -idle-timeout 30

 your settings for processes and timeout will vary according to your load

 Inside your virtual host definitions, tell apache how to handle fcgi
 requests

  AddHandler fastcgi-script fcgi


 Tell apache how to run the RT code


 Alias /RT /pathto/RT/sbin/rt-server.fcgi/
 Directory/pathto/RT/sbin/*
   Options Indexes +ExecCGI FollowSymLinks
   AllowOverRide None
   Satisfy Any
   Order allow,deny
   Allow from all
 /Directory

 and tell apache about the directory where the RT source lives

 Alias /RT/NoAuth/images/  /pathto/RT/share/html/NoAuth/images/
 Directory /pathto/RT/share/html/*
   Options Indexes FollowSymLinks
   AllowOverride None
   Order allow,deny
   Allow from all
 /Directory




 On Fri, Oct 4, 2013 at 9:37 AM, Max McGrath mmcgr...@carthage.edu wrote:

 Thanks!

 Tried moving to FastCgi and I now get:

 You're almost there!You haven't yet configured your webserver to run RT.
 You appear to have installed RT's web interface correctly, but haven't yet
 configured your web server to run the RT server which powers the web
 interface. The next step is to edit your webserver's configuration file to
 instruct it to use RT's *mod_perl* or *FastCGI* handler. If you need
 commercial support, please contact us at sa...@bestpractical.com.

 I'm definitely not a web server expert...so...any advice?

 Max

 --
 Max McGrath
 Network Administrator
 Carthage College
 262-552-5512
 mmcgr...@carthage.edu


 On Wed, Oct 2, 2013 at 10:53 PM, Alex Vandiver 
 ale...@bestpractical.comwrote:

 On Wed, 2013-10-02 at 21:53 -0500, Max McGrath wrote:
  Nope...definitely did that step: [snp]

 Ah.  Then the perl that your mod_perl is linked against is not the perl
 that you configured RT with -- did you recompile a newer perl to meet
 the = 5.10.1 dep, but not recompile mod_perl?  Deploying with mod_fcgi
 or mod_fastcgi is probably easier than upgrading mod_perl.
  - Alex





 --
 RT Training in New York, October 8th and 9th:
 http://bestpractical.com/training




 --
 lenja...@jaffesystems.com   614-404-4214@lenjaffe
 Software Engineer, Founder Volunteerable http://www.volunteerable..com/,
 Host of Columbus Code Jam http://www.meetup.com/techlifecolumbus/
 www.lenjaffe.com http://www.theycomewithcheese.com
 Perl Advent Planet http://www.lenjaffe.com/PerlAdventPlanet/ - Advent
 Calendars: Perlish and otherwise.




-- 
lenja...@jaffesystems.com   614-404-4214@lenjaffe
Software Engineer, Founder Volunteerable http://www.volunteerable..com/,
Host of Columbus Code Jam http://www.meetup.com/techlifecolumbus/
www.lenjaffe.com http://www.theycomewithcheese.com
Perl Advent Planet http://www.lenjaffe.com/PerlAdventPlanet/ - Advent
Calendars: Perlish and otherwise.

-- 
RT Training in New York, October 8th and 9th: http://bestpractical.com/training

Re: [rt-users] Upgrade to 4.2 fail

[Max McGrath]

Thanks!

Tried moving to FastCgi and I now get:

You're almost there!You haven't yet configured your webserver to run RT.
You appear to have installed RT's web interface correctly, but haven't yet
configured your web server to run the RT server which powers the web
interface. The next step is to edit your webserver's configuration file to
instruct it to use RT's *mod_perl* or *FastCGI* handler. If you need
commercial support, please contact us at sa...@bestpractical.com.

I'm definitely not a web server expert...so...any advice?

Max

--
Max McGrath
Network Administrator
Carthage College
262-552-5512
mmcgr...@carthage.edu


On Wed, Oct 2, 2013 at 10:53 PM, Alex Vandiver ale...@bestpractical.comwrote:

 On Wed, 2013-10-02 at 21:53 -0500, Max McGrath wrote:
  Nope...definitely did that step: [snp]

 Ah.  Then the perl that your mod_perl is linked against is not the perl
 that you configured RT with -- did you recompile a newer perl to meet
 the = 5.10.1 dep, but not recompile mod_perl?  Deploying with mod_fcgi
 or mod_fastcgi is probably easier than upgrading mod_perl.
  - Alex




-- 
RT Training in New York, October 8th and 9th: http://bestpractical.com/training

Re: [rt-users] Upgrade to 4.2 fail

[Len Jaffe]

in httpd.conf   and this will depend on your version of apache, and how
you've structured your configurations files.

You need to load the fastcgi module

LoadModule fastcgi_module modules/mod_fastcgi.so

You need to declare your fastcgi service

FastCgiServer /pathto/RT/sbin/rt-server.fcgi -processes 5 -idle-timeout
30

your settings for processes and timeout will vary according to your load

Inside your virtual host definitions, tell apache how to handle fcgi
requests

 AddHandler fastcgi-script fcgi


Tell apache how to run the RT code


Alias /RT /pathto/RT/sbin/rt-server.fcgi/
Directory/pathto/RT/sbin/*
  Options Indexes +ExecCGI FollowSymLinks
  AllowOverRide None
  Satisfy Any
  Order allow,deny
  Allow from all
/Directory

and tell apache about the directory where the RT source lives

Alias /RT/NoAuth/images/  /pathto/RT/share/html/NoAuth/images/
Directory /pathto/RT/share/html/*
  Options Indexes FollowSymLinks
  AllowOverride None
  Order allow,deny
  Allow from all
/Directory




On Fri, Oct 4, 2013 at 9:37 AM, Max McGrath mmcgr...@carthage.edu wrote:

 Thanks!

 Tried moving to FastCgi and I now get:

 You're almost there!You haven't yet configured your webserver to run RT.
 You appear to have installed RT's web interface correctly, but haven't yet
 configured your web server to run the RT server which powers the web
 interface. The next step is to edit your webserver's configuration file to
 instruct it to use RT's *mod_perl* or *FastCGI* handler. If you need
 commercial support, please contact us at sa...@bestpractical.com.

 I'm definitely not a web server expert...so...any advice?

 Max

 --
 Max McGrath
 Network Administrator
 Carthage College
 262-552-5512
 mmcgr...@carthage.edu


 On Wed, Oct 2, 2013 at 10:53 PM, Alex Vandiver 
 ale...@bestpractical.comwrote:

 On Wed, 2013-10-02 at 21:53 -0500, Max McGrath wrote:
  Nope...definitely did that step: [snp]

 Ah.  Then the perl that your mod_perl is linked against is not the perl
 that you configured RT with -- did you recompile a newer perl to meet
 the = 5.10.1 dep, but not recompile mod_perl?  Deploying with mod_fcgi
 or mod_fastcgi is probably easier than upgrading mod_perl.
  - Alex





 --
 RT Training in New York, October 8th and 9th:
 http://bestpractical.com/training




-- 
lenja...@jaffesystems.com   614-404-4214@lenjaffe
Software Engineer, Founder Volunteerable http://www.volunteerable..com/,
Host of Columbus Code Jam http://www.meetup.com/techlifecolumbus/
www.lenjaffe.com http://www.theycomewithcheese.com
Perl Advent Planet http://www.lenjaffe.com/PerlAdventPlanet/ - Advent
Calendars: Perlish and otherwise.

-- 
RT Training in New York, October 8th and 9th: http://bestpractical.com/training

[rt-users] Upgrade to 4.2 fail

[Max McGrath]

Trying to get from 4.0.16 to 4.2.0rc5.

Make upgrade and make database-upgrade go fine, but when I restart Apache I
get:

root@help:/tmp/rt-4.2.0rc5# /etc/init.d/apache2 restart
Syntax error on line 44 of /etc/apache2/sites-enabled/000-default:
Can't locate Symbol/Global/Name.pm in @INC (@INC contains:
/opt/rt4/sbin/../local/lib /opt/rt4/sbin/../lib /etc/perl
/usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2 /usr/lib/perl5
/usr/share/perl5 /usr/lib/perl/5.14 /usr/share/perl/5.14
/usr/local/lib/site_perl . /etc/apache2) at
/opt/rt4/sbin/../lib/RT/Config.pm line 55.\nBEGIN failed--compilation
aborted at /opt/rt4/sbin/../lib/RT/Config.pm line 55.\nCompilation failed
in require at /opt/rt4/sbin/../lib/RT.pm line 156.\n
Action 'configtest' failed.
The Apache error log may have more information.
   ...fail!

Below is line 44 of 000-defaultbut I'm not sure where the syntax error
is.  This is getting above and beyond my knowledge of linux/apache!

 35 Location /rt/
 36 Order allow,deny
 37 Allow from all
 38
 39 SetHandler modperl
 40 PerlResponseHandler Plack::Handler::Apache2
 41 PerlSetVar psgi_app /opt/rt4/sbin/rt-server
 42 /Location
 43 Perl
 44 use Plack::Handler::Apache2;
 45 Plack::Handler::Apache2-preload(/opt/rt4/sbin/rt-server);
 46 /Perl
 47 /VirtualHost


Any help is appreciated!

Max

--
Max McGrath
Network Administrator
Carthage College
262-552-5512
mmcgr...@carthage.edu

-- 
RT Training in New York, October 8th and 9th: http://bestpractical.com/training

Re: [rt-users] Upgrade to 4.2 fail

[Alex Vandiver]

On Wed, 2013-10-02 at 21:26 -0500, Max McGrath wrote:
 Trying to get from 4.0.16 to 4.2.0rc5.
 
 
 Make upgrade and make database-upgrade go fine, but when I restart
 Apache I get:
 
 
 root@help:/tmp/rt-4.2.0rc5# /etc/init.d/apache2 restart
 Syntax error on line 44 of /etc/apache2/sites-enabled/000-default:
 Can't locate Symbol/Global/Name.pm in @INC

RT 4.2 has additional dependencies that RT 4.0 does not.  You skipped
step 3 (`make testdeps`) of the upgrade steps in README:

http://bestpractical.com/docs/rt/4.2.0/README

 - Alex


-- 
RT Training in New York, October 8th and 9th: http://bestpractical.com/training

Re: [rt-users] Upgrade to 4.2 fail

[Max McGrath]

Nope...definitely did that step:

root@help:/tmp/rt-4.2.0rc5# make testdeps
/usr/bin/perl ./sbin/rt-test-dependencies --verbose --with-mysql
--with-fastcgi
perl:
=5.10.1(5.14.2) ...found
users:
rt group (www-data) ...found
bin owner (root) ...found
libs owner (root) ...found
libs group (bin) ...found
web owner (www-data) ...found
web group (www-data) ...found
CLI dependencies:
Text::ParseWords ...found
Term::ReadKey ...found
Getopt::Long = 2.24 ...found
HTTP::Request::Common ...found
Term::ReadLine ...found
LWP ...found
CORE dependencies:
Storable = 2.08 ...found
Encode = 2.39 ...found
Crypt::Eksblowfish ...found
Module::Versions::Report = 1.05 ...found
List::MoreUtils ...found
Errno ...found
DBI = 1.37 ...found
Devel::StackTrace = 1.19 ...found
HTTP::Message = 6.0 ...found
Text::Password::Pronounceable ...found
Devel::GlobalDestruction ...found
Time::ParseDate ...found
IPC::Run3 ...found
Tree::Simple = 1.04 ...found
HTML::Scrubber = 0.08 ...found
HTML::Quoted ...found
Sys::Syslog = 0.16 ...found
Mail::Mailer = 1.57 ...found
Data::GUID ...found
HTML::Mason = 1.43 ...found
HTML::Entities ...found
LWP::Simple ...found
Symbol::Global::Name = 0.04 ...found
DateTime::Format::Natural = 0.67 ...found
Plack = 1.0002 ...found
File::Glob ...found
Class::Accessor = 0.34 ...found
Text::Wrapper ...found
Regexp::Common::net::CIDR ...found
Log::Dispatch = 2.30 ...found
HTML::FormatText::WithLinks::AndTables ...found
DateTime = 0.44 ...found
CGI::Emulate::PSGI ...found
Text::Quoted = 2.07 ...found
Regexp::IPv6 ...found
CGI = 3.38 ...found
CSS::Squish = 0.06 ...found
DateTime::Locale = 0.40 ...found
CGI::PSGI = 0.12 ...found
Apache::Session = 1.53 ...found
Date::Extract = 0.02 ...found
Digest::SHA ...found
HTML::Mason::PSGIHandler = 0.52 ...found
MIME::Entity = 5.504 ...found
Locale::Maketext::Lexicon = 0.32 ...found
Module::Refresh = 0.03 ...found
Role::Basic = 0.12 ...found
Digest::base ...found
File::Temp = 0.19 ...found
Date::Manip ...found
Locale::Maketext = 1.06 ...found
HTML::RewriteAttributes = 0.05 ...found
Text::Template = 1.44 ...found
CGI::Cookie = 1.20 ...found
Scalar::Util ...found
XML::RSS = 1.05 ...found
Text::WikiFormat = 0.76 ...found
File::Spec = 0.8 ...found
DBIx::SearchBuilder = 1.65 ...found
File::ShareDir ...found
Regexp::Common ...found
Digest::MD5 = 2.27 ...found
HTML::FormatText::WithLinks = 0.14 ...found
Mail::Header = 2.12 ...found
Locale::Maketext::Fuzzy = 0.11 ...found
Time::HiRes ...found
Email::Address::List ...found
Net::CIDR ...found
JSON ...found
UNIVERSAL::require ...found
Email::Address = 1.897 ...found
Plack::Handler::Starlet ...found
DASHBOARDS dependencies:
URI::QueryParam ...found
URI = 1.59 ...found
MIME::Types ...found
FASTCGI dependencies:
FCGI::ProcManager ...found
FCGI = 0.74 ...found
GD dependencies:
GD::Text ...found
GD ...found
GD::Graph = 1.47 ...found
GPG dependencies:
File::Which ...found
PerlIO::eol ...found
GnuPG::Interface ...found
ICAL dependencies:
Data::ICal ...found
MAILGATE dependencies:
Pod::Usage ...found
LWP::UserAgent = 6.0 ...found
Crypt::SSLeay ...found
Getopt::Long ...found
Net::SSL ...found
LWP::Protocol::https ...found
Mozilla::CA ...found
MYSQL dependencies:
DBD::mysql = 2.1018 ...found
SMIME dependencies:
String::ShellQuote ...found
File::Which ...found
Crypt::X509 ...found
USERLOGO dependencies:
Convert::Color ...found

*All dependencies have been found.*


--
Max McGrath
Network Administrator
Carthage College
262-552-5512
mmcgr...@carthage.edu


On Wed, Oct 2, 2013 at 9:44 PM, Alex Vandiver ale...@bestpractical.comwrote:

 On Wed, 2013-10-02 at 21:26 -0500, Max McGrath wrote:
  Trying to get from 4.0.16 to 4.2.0rc5.
 
 
  Make upgrade and make database-upgrade go fine, but when I restart
  Apache I get:
 
 
  root@help:/tmp/rt-4.2.0rc5# /etc/init.d/apache2 restart
  Syntax error on line 44 of /etc/apache2/sites-enabled/000-default:
  Can't locate Symbol/Global/Name.pm in @INC

 RT 4.2 has additional dependencies that RT 4.0 does not.  You skipped
 step 3 (`make testdeps`) of the upgrade steps in README:

 http://bestpractical.com/docs/rt/4.2.0/README

  - Alex


 --
 RT Training in New York, 

Re: [rt-users] Upgrade to 4.2 fail

[Alex Vandiver]

On Wed, 2013-10-02 at 21:53 -0500, Max McGrath wrote:
 Nope...definitely did that step: [snp]

Ah.  Then the perl that your mod_perl is linked against is not the perl
that you configured RT with -- did you recompile a newer perl to meet
the = 5.10.1 dep, but not recompile mod_perl?  Deploying with mod_fcgi
or mod_fastcgi is probably easier than upgrading mod_perl.
 - Alex



-- 
RT Training in New York, October 8th and 9th: http://bestpractical.com/training

Re: [rt-users] Upgrade question

[Alan Murrell]

Quoting Kevin Falcone falc...@bestpractical.com:


4.0.17 was actually added to unstable and testing at the end of
August.  The Debian packager for RT works quite hard.


Ah, I did not know that, though I only run stable in a production  
environment.



  2.) Install RT v4.0.17 on new server.  Import configs and database
from current 4.0.7 server.  Jump to the database schema upgrade part
of the upgrade instructions


This is what I would do.


OK, thanks for the confirmation that that is the way to go (don't  
worry, I won't hold you accountable for anything that goes wrong! lol)


-Alan


--
RT Training in New York, October 8th and 9th: http://bestpractical.com/training

[rt-users] Upgrade question

[Alan Murrell]

Hello,

I currently have RT v4.0.7 installed on a Debian server (RT was  
installed from Debian repositories).  For various reasons, I need to  
put RT onto a new server, and was going to stick with Debian, but  
instead of using RT from the repositories, I am planning on doing a  
source install (the repositories are not updated very often, and doing  
a source install will be easier to keep RT updated, IMO)


I am wondering what the best way to go about this is. I am seeing two  
ways to do this:


  1.) Install RT v4.0.7 on the new server, then import current  
configs and database.  Once confirmed all is working properly, perform  
upgrade to v4.0.17.  Or


  2.) Install RT v4.0.17 on new server.  Import configs and database  
from current 4.0.7 server.  Jump to the database schema upgrade part  
of the upgrade instructions


The second option would of course be easier and more efficient, as it  
eliminates a step, and it seems to me that it should work, since it  
seems the biggest part of upgrading RT seems to be the database schema  
part; I just don;t know if there might be any gotchas doing it that  
way.


What would be the best/recommended way to go?

Thanks! :-)

-Alan
RT Training in New York, October 8th and 9th: http://bestpractical.com/training

Re: [rt-users] Upgrade question

[Kevin Falcone]

On Wed, Sep 11, 2013 at 11:51:52PM -0700, Alan Murrell wrote:
 source install (the repositories are not updated very often, and
 doing a source install will be easier to keep RT updated, IMO)

4.0.17 was actually added to unstable and testing at the end of
August.  The Debian packager for RT works quite hard.

   2.) Install RT v4.0.17 on new server.  Import configs and database
 from current 4.0.7 server.  Jump to the database schema upgrade part
 of the upgrade instructions

This is what I would do.  It's a new server, so you even have plenty
of opportunity to do a test upgrade first.

-kevin


pgpJOuyQ9HUbL.pgp
Description: PGP signature

-- 
RT Training in New York, October 8th and 9th: http://bestpractical.com/training

Re: [rt-users] Upgrade: RTFM Article, Content CustomField not displaying

[Anthony Gladdish]

Hi Kevin,

-Original Message-
From: rt-users-boun...@lists.bestpractical.com [mailto:rt-
users-boun...@lists.bestpractical.com] On Behalf Of Kevin
Falcone
Sent: 20 August 2013 13:29
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Upgrade: RTFM Article, Content
CustomField not displaying

On Fri, Aug 16, 2013 at 09:26:41AM +, Anthony Gladdish
wrote:
 Test system ( RT 3.8.17 + RTFM 2.4.5 ):

  For both menus:
  Menu: RTFM - Configuration - Custom Fields
  Menu: Configuration - RTFM - Custom Fields

  Lists record #32 from the CustomFields table.
Applied column is empty.
  Lists record #31 from the CustomFields table.
Applied column is empty.

  Clicking on each CustomField, Applies to is
RTFM Articles.

Are you quoting us the Applies To dropdown or the results of
clicking
on the Applies To link, which is where you apply Custom Fields to
appropriate RT objects?

Test system: for each CustomField, the Applies to drop down box has RTFM 
Articles selected.
Production system: Tickets is selected instead and does not display an RTFM 
Articles option. Assigning this Tickets option in my test system appears to 
have no effect.

Test system: for each CustomField, clicking on the Applies to link shows a 
list of unselected objects - RT and my queues. Selecting these and submitting, 
does not display the CF in the Article's page.

  I think it should be referencing CF records from
FM_CustomFields table instead?

FM_CustomFields has not been a relevant RTFM table since
before the
2.4.0 release.  All RTFM CF data is stored in RT's core Custom
Field
tables.

Good to know.

Hope this sheds more light,
Anthony

Re: [rt-users] Upgrade: RTFM Article, Content CustomField not displaying

[Kevin Falcone]

On Wed, Aug 21, 2013 at 08:54:17AM +, Anthony Gladdish wrote:

 Production system: Tickets is selected instead and does not display an 
 RTFM Articles option. Assigning this Tickets option in my test system 
 appears to have no effect.

I'm a little confused how RTFM works on production if you don't see
RTFM Articles as a Custom Field option.

I assume it worked when you set up the system, but then someone broke
something later (Since you mention the FM_CustomFields table I know
you upgraded from a very old RTFM at some point).

You can go look in the Database at the LookupType field to confirm.

Assigning it to Tickets in test would just break.

 Test system: for each CustomField, clicking on the Applies to link
 shows a list of unselected objects - RT and my queues. Selecting these
 and submitting, does not display the CF in the Article's page.

It shouldn't show Queues, it'll show classes.

Change it back to RTFM Articles, then click on Applies to and then
assign it to the relevant Classes.

-kevin


pgpiEBCeOKE1F.pgp
Description: PGP signature

Re: [rt-users] upgrade-database push to the mysql replica ?

[Asif Iqbal]

On Tue, Aug 20, 2013 at 11:59 AM, Asif Iqbal vad...@gmail.com wrote:




 On Mon, Aug 19, 2013 at 11:37 PM, Asif Iqbal vad...@gmail.com wrote:

 Hi All,

 If I run make upgrade-database on mysql master, will it push the change
 to mysql slave ?

 I could not find any answer in the mailing list, unless I missed it.

 Thanks


 I did a test make updgrade-database while running 'show processlist' on
 slave and it looks
 the slave rt4 gets the upgrade-database too. Please let me know if someone
 thinks otherwise.



It does seem that ``make upgrade-database'' pushes the change to slave as
well. Just needed
to double check with all before migrating about 8 million transactions this
weekend from
old environment (sparc/solaris/rt3.8.2/mysql 5.0.55) to
new environment ( 2 supermicro/linux/rt 4.0.17/mysql 5.5.32/ master/master
active/passive)




-- 
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?

Re: [rt-users] Upgrade: RTFM Article, Content CustomField not displaying

[Kevin Falcone]

On Fri, Aug 16, 2013 at 09:26:41AM +, Anthony Gladdish wrote:
 Test system ( RT 3.8.17 + RTFM 2.4.5 ):
 
   For both menus:
   Menu: RTFM - Configuration - Custom Fields
   Menu: Configuration - RTFM - Custom Fields
 
   Lists record #32 from the CustomFields table. Applied 
 column is empty.
   Lists record #31 from the CustomFields table. Applied 
 column is empty.
 
   Clicking on each CustomField, Applies to is RTFM Articles.
 
Are you quoting us the Applies To dropdown or the results of clicking
on the Applies To link, which is where you apply Custom Fields to
appropriate RT objects?

   I think it should be referencing CF records from 
 FM_CustomFields table instead?

FM_CustomFields has not been a relevant RTFM table since before the
2.4.0 release.  All RTFM CF data is stored in RT's core Custom Field
tables.

-kevin


pgpW0yBJo_EhG.pgp
Description: PGP signature

Re: [rt-users] upgrade-database push to the mysql replica ?

[Asif Iqbal]

On Mon, Aug 19, 2013 at 11:37 PM, Asif Iqbal vad...@gmail.com wrote:

 Hi All,

 If I run make upgrade-database on mysql master, will it push the change to
 mysql slave ?

 I could not find any answer in the mailing list, unless I missed it.

 Thanks


I did a test make updgrade-database while running 'show processlist' on
slave and it looks
the slave rt4 gets the upgrade-database too. Please let me know if someone
thinks otherwise.

Thanks




 --
 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?




-- 
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] upgrade-database push to the mysql replica ?

[Asif Iqbal]

Hi All,

If I run make upgrade-database on mysql master, will it push the change to
mysql slave ?

I could not find any answer in the mailing list, unless I missed it.

Thanks

-- 
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] Upgrade: RTFM Article, Content CustomField not displaying

[Anthony Gladdish]

Hi,

When viewing/editing an RTFM Article, Content CustomField is not displaying.

This is after installing a fresh copy of RT 3.8.17 + RTFM 2.4.5 and pointing at 
copy of database, and upgraded as per steps in: 
http://www.bestpractical.com/docs/rt/3.8/UPGRADING.html from 3.8.2.
I chose not to run optional perl etc/upgrade/split-out-cf-categories in 3.8.5 
step.

CustomFields already exist; I don't need to create new ones. The data in 
database has not changed during database upgrade.

Test system ( RT 3.8.17 + RTFM 2.4.5 ):

For both menus:
Menu: RTFM - Configuration - Custom Fields
Menu: Configuration - RTFM - Custom Fields

Lists record #32 from the CustomFields table. Applied 
column is empty.
Lists record #31 from the CustomFields table. Applied 
column is empty.

Clicking on each CustomField, Applies to is RTFM Articles.

I think it should be referencing CF records from 
FM_CustomFields table instead?

Works fine with RT 3.8.2 + RTFM 2.4.1.

Is this a bug or have I missed something?

Thanks,
Anthony

Re: [rt-users] Upgrade help

[Kevin Falcone]

On Tue, Jul 16, 2013 at 07:22:59AM -0700, ofadl wrote:
 I have two versions of RT set up, one is 3.0, which is the old version and
 in current use. The other is the newer version, 4.0, which id like to start
 using. I would like to do an upgrade on the old server where RT 3 is before
 I can move the data to the new server. The upgrade process modifies the
 database so it’s compatible with the new version. Any help is greatly
 appreciated. 

You don't say what you've tried/failed, but start with our UPGRADING
docs on http://docs.bestpractical.com and review this blog post I
wrote a while back.
http://blog.bestpractical.com/2011/07/upgrading-to-rt-4.html

-kevin


pgpl4732Wb7ft.pgp
Description: PGP signature

[rt-users] Upgrade help

[ofadl]

Hello everyone, 

I have two versions of RT set up, one is 3.0, which is the old version and
in current use. The other is the newer version, 4.0, which id like to start
using. I would like to do an upgrade on the old server where RT 3 is before
I can move the data to the new server. The upgrade process modifies the
database so it’s compatible with the new version. Any help is greatly
appreciated. 

Thanks 



--
View this message in context: 
http://requesttracker.8502.n7.nabble.com/Upgrade-help-tp54646.html
Sent from the Request Tracker - User mailing list archive at Nabble.com.

Re: [rt-users] Upgrade RT, what about plugin module?

[Thomas Lau]

Hi, Thanks for replying.


Does it means basically no extra step should do on plugin during minor version 
upgrade?

From: ruslan.zaki...@gmail.com [mailto:ruslan.zaki...@gmail.com] On Behalf Of 
Ruslan Zakirov
Sent: Thursday, May 23, 2013 1:27 PM
To: Thomas Lau
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Upgrade RT, what about plugin module?

On Thu, May 23, 2013 at 5:15 AM, Thomas Lau 
thomas@principleone.commailto:thomas@principleone.com wrote:
Hi,

I am wondering if plugin would have problem if I perform general minor version 
upgrade on 4.0.x?

They shouldn't. We work hard not to break backwards compatibility in minor 
versions and avoid database changes as much as possible.


Recently we intensively use more and more plugin which I am not sure if it will 
drive the upgrade more complicated.

We are using RT-Extension-CommandByMail, RT-Extension-RepeatTicket and 
RT-Extension-SLA.

All these should work with recent versions of 4.0.x.




--
RT Training in Seattle, June 19-20: http://bestpractical.com/training



--
Best regards, Ruslan.


-- 
RT Training in Seattle, June 19-20: http://bestpractical.com/training

Re: [rt-users] Upgrade RT, what about plugin module?

[Ruslan Zakirov]

On Thu, May 23, 2013 at 12:31 PM, Thomas Lau thomas@principleone.comwrote:

  Hi, Thanks for replying.

 ** **

 ** **

 Does it means basically no extra step should do on plugin during minor
 version upgrade?


Shouldn't be. Create a dev environment where you can play with things and
you will be more confident.


 

 ** **

 *From:* ruslan.zaki...@gmail.com [mailto:ruslan.zaki...@gmail.com] *On
 Behalf Of *Ruslan Zakirov
 *Sent:* Thursday, May 23, 2013 1:27 PM
 *To:* Thomas Lau
 *Cc:* rt-users@lists.bestpractical.com
 *Subject:* Re: [rt-users] Upgrade RT, what about plugin module?

 ** **

 On Thu, May 23, 2013 at 5:15 AM, Thomas Lau thomas@principleone.com
 wrote:

  Hi,

  

 I am wondering if plugin would have problem if I perform general minor
 version upgrade on 4.0.x?

  ** **

 They shouldn't. We work hard not to break backwards compatibility in minor
 versions and avoid database changes as much as possible.

  

   

 Recently we intensively use more and more plugin which I am not sure if it
 will drive the upgrade more complicated.

  

 We are using RT-Extension-CommandByMail, RT-Extension-RepeatTicket and
 RT-Extension-SLA.

  ** **

 All these should work with recent versions of 4.0.x.

  




 --
 RT Training in Seattle, June 19-20: http://bestpractical.com/training



 

 ** **

 --
 Best regards, Ruslan. 



 --
 RT Training in Seattle, June 19-20: http://bestpractical.com/training




-- 
Best regards, Ruslan.


-- 
RT Training in Seattle, June 19-20: http://bestpractical.com/training

[rt-users] Upgrade RT, what about plugin module?

[Thomas Lau]

Hi,

I am wondering if plugin would have problem if I perform general minor version 
upgrade on 4.0.x?

Recently we intensively use more and more plugin which I am not sure if it will 
drive the upgrade more complicated.

We are using RT-Extension-CommandByMail, RT-Extension-RepeatTicket and 
RT-Extension-SLA.


-- 
RT Training in Seattle, June 19-20: http://bestpractical.com/training

Re: [rt-users] Upgrade RT, what about plugin module?

[Ruslan Zakirov]

On Thu, May 23, 2013 at 5:15 AM, Thomas Lau thomas@principleone.comwrote:

  Hi,

 ** **

 I am wondering if plugin would have problem if I perform general minor
 version upgrade on 4.0.x?


They shouldn't. We work hard not to break backwards compatibility in minor
versions and avoid database changes as much as possible.


 

 ** **

 Recently we intensively use more and more plugin which I am not sure if it
 will drive the upgrade more complicated.

 ** **

 We are using RT-Extension-CommandByMail, RT-Extension-RepeatTicket and
 RT-Extension-SLA.


All these should work with recent versions of 4.0.x.


 



 --
 RT Training in Seattle, June 19-20: http://bestpractical.com/training




-- 
Best regards, Ruslan.


-- 
RT Training in Seattle, June 19-20: http://bestpractical.com/training

Re: [rt-users] Upgrade from RT 4.0.9 to 4.0.11

[Carlos Santos]

With 4.0.9 install I went with /usr/local/rt which ended up being my problem.
• ./configure --prefix=/usr/local/rt 
• make testdeps 
• make upgrade 
• make upgrade-database 
And all works fine.




--
View this message in context: 
http://requesttracker.8502.n7.nabble.com/Upgrade-from-RT-4-0-9-to-4-0-11-tp53677p53689.html
Sent from the Request Tracker - User mailing list archive at Nabble.com.