Re: [rt-users] Upgrade fail
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 2>&1 > 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 2>&1 | 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:
Re: [rt-users] Upgrade fail
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 2>&1 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 2>&1 | 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::Ad
Re: [rt-users] Upgrade fail
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 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
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 >
[rt-users] Upgrade fail
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] Only copy owner
On 02/13/2013 08:36 AM, Joshua Lansford wrote: Hi folks, I want to set up a queue monitored by multiple AdminCCs. Once one AdminCC becomes the owner, I would like the other AdminCCs to no longer receive update emails with each correspondence but still be able to view the ticket when logged in. Thinking of modifying the scrips, specifically "On Correspond Notify AdminCcs". But before I dive into the world of custom conditions and scrips, I want to make sure this is the correct direction to go. Thanks, ~Joshua Found my own answer: http://requesttracker.wikia.com/wiki/On_Correspond_Notify_AdminCcs_if_Not_Owned If someone else used custom scrips, it must be the way to go. Thanks, ~Joshua -- RT training in Amsterdam, March 20-21: http://bestpractical.com/services/training.html Help improve RT by taking our user survey: https://www.surveymonkey.com/s/N23JW9T
[rt-users] Only copy owner
Hi folks, I want to set up a queue monitored by multiple AdminCCs. Once one AdminCC becomes the owner, I would like the other AdminCCs to no longer receive update emails with each correspondence but still be able to view the ticket when logged in. Thinking of modifying the scrips, specifically "On Correspond Notify AdminCcs". But before I dive into the world of custom conditions and scrips, I want to make sure this is the correct direction to go. Thanks, ~Joshua -- RT training in Amsterdam, March 20-21: http://bestpractical.com/services/training.html Help improve RT by taking our user survey: https://www.surveymonkey.com/s/N23JW9T
Re: [rt-users] Ticket Image attach corruption
> Is this correct, that the IR update for RT 4.0 is not yet ready or did I > install an older release unnecessarily? Looks like there is an alpha version ready for testing: http://lists.bestpractical.com/pipermail/rtir/2011-October/000579.html -- Help improve RT by taking our user survey: https://www.surveymonkey.com/s/N23JW9T
Re: [rt-users] Ticket Image attach corruption
On 02/07/2013 03:41 PM, Jay Ashworth wrote: About the wiki, it's largely me you're complaining about, so you got the right guy: I did a large bolus of rework on it around 3.8 release time, and have not been using rt-due to job changes-since, so I haven't gotten around to reworking it again for 4.x. My apologies. Your article was indeed well written and did not provide me with any difficulty in setting up RT. Google also complements your hardwork by directing me to it when I needed the information. Sadly I didn't think to check if the referenced version was out of date. Do you think you could put a quick warning at the top as a stop gap measure for other folks who forget to check? ~Joshua -- Help improve RT by taking our user survey: https://www.surveymonkey.com/s/N23JW9T
Re: [rt-users] Ticket Image attach corruption
On 02/08/2013 05:15 AM, Dominic Hargreaves wrote: Which wiki, OOI? https://help.ubuntu.com/community/Request%20Tracker -- Help improve RT by taking our user survey: https://www.surveymonkey.com/s/N23JW9T
Re: [rt-users] Ticket Image attach corruption
On 02/07/2013 02:43 PM, Jay Ashworth wrote: Question: do you guys make a point, at all, of evangelizing to distro maintainers and packagers that they package 4.x, or, more to the point pull 3.x*out* of repos? I checked and there are separate packages for rt4. I understand leaving the 3.8 around as not to surprise folks when they do a system upgrade. It would have been nice if they had updated their wiki though. Quite a bummer as I just went live. I am going to try and set up a duplicate system on a virtual machine to test upgrade to 4.0. Thanks for pointing this out. I will be following this guide: http://blog.bestpractical.com/2011/07/upgrading-to-rt-4.html -- Help improve RT by taking our user survey: https://www.surveymonkey.com/s/N23JW9T
Re: [rt-users] Ticket Image attach corruption
On 02/07/2013 01:55 PM, Thomas Sibley wrote: Hopefully you're starting with the latest version of RT, 4.0.10, or at least close to it in the 4.0 series. The Ubuntu wiki page you link to is a bit outdated and installs the 3.8 series. Thomas 3.8.11 -- Help improve RT by taking our user survey: https://www.surveymonkey.com/s/N23JW9T
Re: [rt-users] Ticket Image attach corruption
On 02/07/2013 10:37 AM, Kevin Falcone wrote: Set($MaxAttachmentSize , 1000); Thank you. It is now working. :-) ~Joshua -- Help improve RT by taking our user survey: https://www.surveymonkey.com/s/N23JW9T
[rt-users] Ticket Image attach corruption
Thanks to whoever credit is due for the RT program. I have been looking for a while for a bug tracking system I could convince my company to use. I am now rolling out RT for our company and almost everyone I talk to about it is excited to use it. I believe the main contributing factor is the high integration with email. This allows me to place RT inline with existing communication and support practices with minimal retraining. I have discovered the multiple image custom field option. After the procedure for uploading the image completes and I click on the file name I get RT Error Corrupted customfieldvalue URL. By Googling I have discovered that the max filesize of an attachment is 512KB. http://kb.mit.edu/confluence/pages/viewpage.action?pageId=4272898 However even when restricting my upload to images below this size the same error occurs. RT is installed on Ubuntu 12.04.1 LTS \n \l RT was installed using the package manager following the instructions at https://help.ubuntu.com/community/Request%20Tracker I did move the location of the mysql database to a data drive according to these instructions V, but the system has been operating fine otherwise. http://www.ubuntugeek.com/how-to-change-the-mysql-data-default-directory.html A screenshot of the error is uploaded here http://public.laserlinc.com/temp/Joshua/Screenshot-2.png A screenshot of the ticket with the misbehaving tickets is found here http://public.laserlinc.com/temp/Joshua/Screenshot.png Thanks ~Joshua -- Help improve RT by taking our user survey: https://www.surveymonkey.com/s/N23JW9T
