[rt-users] Upgrade of RTFM has lost content of articles.

Kevin Falcone falcone at bestpractical.com
Fri Jan 2 10:21:11 EST 2009


On Jan 2, 2009, at 8:51 AM, Michael O' Neill wrote:

> Regarding this previous post, did anyone find the answer as I have  
> this exact issue as well.
> RTFM was upgraded from an unknown version and we lost all the  
> content of the RTFM articles.

Did you run the migrate-2.0-to-2.1 script?  It sounds like none of the  
usual things I
expect to see migrated as a result of that script were moved.

-kevin

>
>
> ---------- Start of article
>
> Bill Davis
> 日付:  2006-12-19 09:56  -000
> To: rt-users
> 題目: Re: [rt-users] Problems upgrading RTFM to 2.2.0RC4
> Bob Goldstein wrote:
> >> I'm using RT 3.6.1 with an unknown version of RTFM installed  
> (though I
> >> think it is probably RTFM 2.1.40 based on the time frame  
> installed) and
> >> am trying to migrate to RTFM 2.2.0RC4. Downloaded the file, read  
> the
> >> README file, didn't seem to fit the upgrade instructions (not  
> upgrading
> >>
> > >from a 2.0.x release), ... so tried the normal install instructions
> >
> >> (make Makefile.PL, make install), omitted "make initdb" because it
> >> wasn't an "initial install", stopped and started the webserver.
> >>
> >> Appears I now have an upgraded version, however all previous RTFM
> >> articles, while they still exist, have no content.
> >>
> >> Before I muck it up further would appreciate some advice:
> >>
> >> 1. How do you tell what version of RTFM is installed? ... I can't  
> seem
> >> to find it anywhere?
> >> 2. How can I get my article content back & properly complete the
> >> upgrade? ... should I run the "make initdb" command or will this
> >> overwrite the existing tables in the database?
> >>
> >>
> >
> > Notice that /etc/upgrades has three directories:
> > 2.1.0 2.1.30 2.2.0RC2
> >
> > You must apply the upgrade from these for each version
> > later than the one you are upgrading. If you are starting with
> > 2.1.40, then you need apply 2.2.0RC2
> >
> > But also, the README left out a critical piece.
> > That is, the upgrade will break the association of
> > which custom fields go with which classes (which is why
> > your articles now appear to have no content.) To get it back:
> >
> > Login the RT web interface->
> > Config->RTFM->Custom Fields-><CUSTOM FIELD NAME>->Apply-> Select  
> the classes
> > the customfield will apply to (the common is to select all) and  
> then click Send
> >
> > bobg
> Thanks for the reply. Since I'd already run "make Makefile.PL" & "make
> install", picked up the update instructions with (producing the
> responses indicated):
>
> > [root at BlackHole RTFM-2.2.0RC4]# /opt/rt3/sbin/rt-setup-database
> > --action schema \ --datadir etc/upgrade/2.2.0RC2 --dba root
> > --dba-password xxxxxx
> > Creating database schema.
> > readline() on closed filehandle SCHEMA_LOCAL at
> > /opt/rt3/sbin/rt-setup-database line 192.
> > Problem with statement:
> >
> > CREATE TABLE Attachments (
> > id INTEGER NOT NULL AUTO_INCREMENT,
> > TransactionId integer NOT NULL ,
> > Parent integer NOT NULL DEFAULT 0 ,
> > MessageId varchar(160) NULL ,
> > Subject varchar(255) NULL ,
> > Filename varchar(255) NULL ,
> > ContentType varchar(80) NULL ,
> > ContentEncoding varchar(80) NULL ,
> > Content LONGTEXT NULL ,
> > Headers LONGTEXT NULL ,
> > Creator integer NOT NULL DEFAULT 0 ,
> > Created DATETIME NULL ,
> > PRIMARY KEY (id)
> > ) TYPE=InnoDB
> > Table 'Attachments' already exists at
> > /opt/rt3/sbin/rt-setup-database line 212.
> > [root at BlackHole RTFM-2.2.0RC4]# /opt/rt3/sbin/rt-setup-database
> > --action acl \ - -datadir etc/upgrade/2.2.0RC2 --dba root
> > --dba-password xxxxxx
> > Done setting up database ACLs.
> > [root at BlackHole RTFM-2.2.0RC4]# /opt/rt3/sbin/rt-setup-database
> > --action insert \ --datadir etc/upgrade/2.2.0RC2 --dba root
> > --dba-password xxxxxx
> > Use of uninitialized value in concatenation (.) or string at
> > /opt/rt3/sbin/rt-se tup-database line 162.
> > [Tue Dec 19 09:25:12 2006] [crit]: Can't locate /content in @INC
> > (@INC contains: /opt/rt3/lib /opt/rt3/local/lib
> > /usr/lib/perl5/site_perl/5.8.8/i386-linux-threa d-multi
> > /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi
> > /usr/lib/perl5/si te_perl/5.8.6/i386-linux-thread-multi
> > /usr/lib/perl5/site_perl/5.8.5/i386-linux- thread-multi
> > /usr/lib/perl5/site_perl/5.8.4/i386-linux-thread-multi
> > /usr/lib/per l5/site_perl/5.8.3/i386-linux-thread-multi
> > /usr/lib/perl5/site_perl/5.8.8 /usr/l ib/perl5/site_perl/5.8.7
> > /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl /5.8.5
> > /usr/lib/perl5/site_perl/5.8.4 /usr/lib/perl5/site_perl/5.8.3
> > /usr/lib/pe rl5/site_perl
> > /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/
> > perl5/vendor_perl/5.8.7/i386-linux-thread-multi
> > /usr/lib/perl5/vendor_perl/5.8.6 /i386-linux-thread-multi
> > /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-mult i
> > /usr/lib/perl5/vendor_perl/5.8.4/i386-linux-thread-multi
> > /usr/lib/perl5/vendor _perl/5.8.3/i386-linux-thread-multi
> > /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/pe rl5/vendor_perl/5.8.7
> > /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_per l/5.8.5
> > /usr/lib/perl5/vendor_perl/5.8.4 /usr/lib/perl5/vendor_perl/5.8.3
> > /usr/l ib/perl5/vendor_perl
> > /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5 /5.8.8
> > .) at /opt/rt3/sbin/rt-setup-database line 456.
> > (/opt/rt3/lib/RT.pm:317)
> > Can't locate /content in @INC (@INC contains: /opt/rt3/lib
> > /opt/rt3/local/lib /u
> > sr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi
> > /usr/lib/perl5/site_perl/5. 8.7/i386-linux-thread-multi
> > /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-mul ti
> > /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi
> > /usr/lib/perl5/site_pe rl/5.8.4/i386-linux-thread-multi
> > /usr/lib/perl5/site_perl/5.8.3/i386-linux-threa d-multi
> > /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7
> > /usr/lib/p erl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5
> > /usr/lib/perl5/site_perl/5.8 .4 /usr/lib/perl5/site_perl/5.8.3
> > /usr/lib/perl5/site_perl /usr/lib/perl5/vendor
> > _perl/5.8.8/i386-linux-thread-multi
> > /usr/lib/perl5/vendor_perl/5.8.7/i386-linux- thread-multi
> > /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi
> > /usr/lib/p erl5/vendor_perl/5.8.5/i386-linux-thread-multi
> > /usr/lib/perl5/vendor_perl/5.8.4/ i386-linux-thread-multi
> > /usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi
> > /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/5.8.7
> > /usr/lib/perl 5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5
> > /usr/lib/perl5/vendor_perl/ 5.8.4 /usr/lib/perl5/vendor_perl/5.8.3
> > /usr/lib/perl5/vendor_perl /usr/lib/perl5
> > /5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 .) at
> > /opt/rt3/sbin/rt-setup -database line 456.
> > [root at BlackHole RTFM-2.2.0RC4]#
> This collection of errors messages didn't give me a warm fuzzy
> feeling & stopping & restarting the webserver, I'm seeing the same
> results: previous articles listed, but with no contents. The
> configuration for RTFM also seems to have no custom fields listed.
>
> Ideas welcome ...
> Bill Davis
>
> ---------- End of article
>
> Our ethos: protecting the future of your business
>
> This is an e-mail from Ethos Information Solutions Limited and is  
> intended only for the addressee named above.  The contents of this  
> message should not be disclosed to any other person nor copies taken  
> or forwarded without written permission.  Any views or opinions  
> presented are solely those of the sender and do not necessarily  
> represent the views of Ethos Information Solutions Limited.
>
> We do not accept any responsibility for the contents of this message  
> and although this message has been scanned for viruses prior to  
> transmission we would recommend that you check before opening any  
> attachments as we cannot accept liability for any damage sustained  
> as a result of any software viruses.  Please notify the sender  
> immediately if you have received this e-mail by mistake and delete  
> it from your systems, or report it to our support database at support at ethos-is.net
>
> For more information about the services we provide please visit our  
> web site at http://www.ethos-is.com
>
>
>
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>
> Community help: http://wiki.bestpractical.com
> Commercial support: sales at bestpractical.com
>
>
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> Buy a copy at http://rtbook.bestpractical.com




More information about the rt-users mailing list