Re: [rt-users] Upgrade 3.6 to 3.8.

2011-01-25 Thread Jose Diaz
--- El Sáb 22/1/11, Patrick Hess ph...@cataphora.com escribió:

 De: Patrick Hess ph...@cataphora.com
 Asunto: RE: [rt-users] Upgrade 3.6 to 3.8.
 Para: 'Jose Diaz' xt4...@yahoo.com
 Fecha: Sábado 22 de Enero de 2011, 21:41
 Upgrading 3.6.x to 3.8.x seems pretty
 straightforward to me.  The only
 tricky part could be upgrading the database.  If
 you're using MySQL, like
 most of us, then the UPGRADING.mysql file looks like it
 has enough
 information to help someone complete the task.
 
 --phess
  
 
 -Original Message-
 From: rt-users-boun...@lists.bestpractical.com
 [mailto:rt-users-boun...@lists.bestpractical.com]
 On Behalf Of Jose Diaz
 Sent: Saturday, January 22, 2011 6:19 PM
 To: rt-users@lists.bestpractical.com
 Subject: [rt-users] Upgrade 3.6 to 3.8.
 
 Hi everyone and thanks in advance.
 
 does anyone know a good step by step guide to upgrade RT
 3.6.7 to latest
 stable RT 3.8.x ?, which version is appropiate coming from
 3.6.7 ?
 
 I have Debian Lenny installation working with RT 3.6.7 done
 with aptitude
 program.
 
 Thanks in advance.
 
 José.
 
 --
 Lic. José Gregorio Díaz Unda.
 Asesor de Tecnologías de Información y Comunicación.
 Tel.: 58.0412.5518085
 Skype: xt4mhz
 Web: www.usb.ve - jgdu.blogspot.com
 
 
 
 
 

Hi Patrick and thanks for the reference.

I'm checking these files from rt-3.8.8.tar.gz file:

- UPGRADING.Mysql
- README
- UPGRADING

You say tricky part ... any hints about this process ?

Thanks again.

José.


--
Lic. José Gregorio Díaz Unda.
Asesor de Tecnologías de Información y Comunicación.
Tel.: 58.0412.5518085
Skype: xt4mhz
Web: www.usb.ve - jgdu.blogspot.com





Re: [rt-users] Upgrade 3.6 to 3.8.

2011-01-25 Thread Jose Diaz
Hi Chris and thanks a lot for your help.

We started the reading of UPGRADING file as you mentioned.

In this file, there is a section starting with:

UPGRADING FROM 3.6.X and earlier - Changes: ...

I think this is for us.

It says:

New schema for mysql 4.1 and greater, read more in UPGRADING.mysql.

So we will follow the steps explained in UPGRADING.mysql

Did you refer to this UPGRADING.mysql

By the other hand, you mentioned we tried to apply all the other fixes listed 
in UPGRADING, but that turned out to be unneccessary (and in fact damaging)

What fixes can we override?

Thankks again.

Take care.

José.

--
Lic. José Gregorio Díaz Unda.
Asesor de Tecnologías de Información y Comunicación.
Tel.: 58.0412.5518085
Skype: xt4mhz
Web: www.usb.ve - jgdu.blogspot.com


--- El Sáb 22/1/11, Chris Hoy Poy ch...@central-data.net escribió:

 De: Chris Hoy Poy ch...@central-data.net
 Asunto: Re: [rt-users] Upgrade 3.6 to 3.8.
 Para: Jose Diaz xt4...@yahoo.com
 Fecha: Sábado 22 de Enero de 2011, 23:07
 Hi Jose,
 
 We just upgraded a couple of debian RT 3.6.6 to 3.8.8, and
 just followed the instructions in UPGRADING 
 
 This is from from a manually installed 3.6.6 on Debian
 Lenny to a manual latest 3.8.8 on Ubuntu 10.04 
 
 For the database, we just had to run this command to fix
 the database: 
   /opt/rt3/sbin/rt-setup-database --dba root
 --prompt-for-dba-password --action upgrade
 
 When prompted, enter the appropriate version and it just
 works tm.
 
 The libraries were more of a pain, but we just kept adding
 them whenever it complained. The database upgrade was
 simple. 
 
 As always, make sure you have a couple of backups :) I just
 had a couple of mysqldumps of that database. The first time
 we did it, we tried to apply all the other fixes listed in
 UPGRADING, but that turned out to be unneccessary (and in
 fact damaging) - all we actually needed to was run that one
 command.
 
 Chris Hoy Poy 
 Senior Infrastructure Engineer    
     
 
 Central Data Systems Pty Ltd 
 88 Havelock St.,West Perth, WA 6005 
 Phone: 08 9481 4010,Fax: 08 9481 4767 
 www.central-data.net 
 
 - Original Message -
 From: Jose Diaz xt4...@yahoo.com
 To: rt-users@lists.bestpractical.com
 Sent: Sunday, 23 January, 2011 10:19:19 AM
 Subject: [rt-users] Upgrade 3.6 to 3.8.
 
 Hi everyone and thanks in advance.
 
 does anyone know a good step by step guide to upgrade RT
 3.6.7 to
 latest stable RT 3.8.x ?, which version is appropiate
 coming from 3.6.7
 ?
 
 I have Debian Lenny installation working with RT 3.6.7 done
 with
 aptitude program.
 
 Thanks in advance.
 
 José.
 
 -- Lic. José Gregorio Díaz Unda.
 Asesor de Tecnologías de Información y Comunicación.
 Tel.: 58.0412.5518085
 Skype: xt4mhz
 Web: www.usb.ve - jgdu.blogspot.com
 




Re: [rt-users] Upgrade 3.6 to 3.8.

2011-01-23 Thread Dominic Hargreaves
On Sat, Jan 22, 2011 at 06:19:19PM -0800, Jose Diaz wrote:
 Hi everyone and thanks in advance.
 
 does anyone know a good step by step guide to upgrade RT 3.6.7 to latest 
 stable RT 3.8.x ?, which version is appropiate coming from 3.6.7 ?
 
 I have Debian Lenny installation working with RT 3.6.7 done with aptitude 
 program.

Hi,

You can get request-tracker3.8 packages from lenny-backports
(http://backports.debian.org/) or in the next version of Debian,
squeeze, which is due to be released in the next month or so.

Unfortunately there is no automated process for migrating between
request-tracker3.6 and request-tracker3.8 (I'm hoping that things will
be better for migrations between request-tracker3.8 and
request-tracker4.0), but I've put together some ideas for a general
migration process below. They are rough untested notes based on my
experience maintaining the RT Debian packages and managing RT
installations with them, but there are no guarantees that they will work
for you. That said, I'd be interested in any corrections you have for
them. They assume that you want to do an in-place upgrade on the same
host. Depending on your environment, something more elaborate may be
required. Generally speaking, when moving between major versions of RT,
you should spend a decent amount of time testing the new version before
moving your live service across. Installing request-tracker3.8 on a new
host may be useful, and potentially less risky, especially if you use
mod_perl rather than FastCGI.

Don't just rely on these suggestions; make sure you read through
the UPGRADING document which comes with request-tracker3.8 too for
supplementary information. Also, if you've installed any extensions,
things will become more complicated.

All that aside, here is the rough process I might follow:

*  Upgrade to squeeze or configure lenny-backports (in both cases I
   recommend you wait for 3.8.8-7, which includes a recent security
   fix, to become available)
*  apt-get install request-tracker3.8
   *  Answer questions based on your current install. Make sure that
  RTName remains the same, or you will run into problems. Perhaps use
  a different WebPath temporily (but you can't use both versions
  together in the same Apache instance if you're using mod_perl).
   *  Decide whether to use dbconfig database configuration, maybe
  based on how request-tracker3.6 is set up. Use a different
  database name from your live install.
*  Configure Apache to use the new install (bearing in mind the above
   mod_perl caveat, and making sure you use a different base path in
   Apache, for example by modifying the
   /etc/request-tracker3.8/apache2-*.conf file you're using)
*  Perfom some initial testing with a fresh database
*  Dump your live database using native database tools, then load
   it into the database you're using to test with.
*  Run /usr/sbin/rt-setup-database-3.8 --action upgrade (probably as
   the www-data user)
*  Run /usr/sbin/rt-vulnerable-passwords-3.8 --fix (assuming you have
   3.8.8-7 or greater; probably as the www-data)
*  Run some tests against your live data
*  When ready to switch over service, stop your MTA and Apache,
   redump your database and go over the same database upgrade procedures
   above, reconfigure RT to use the same WebPath as your live service
   (dpkg-reconfigure request-tracker3.8) and then reconfigure Apache
   to use RT 3.8.
*  Start up your web server and MTA again

Dominic.

-- 
Dominic Hargreaves, Systems Development and Support Team
Computing Services, University of Oxford


signature.asc
Description: Digital signature