-
>
> Message: 2
> Date: Fri, 29 Aug 2014 16:59:59 -0500
> From: Kevin Falcone
> 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/
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
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
> To: rt-users@lists.bestpractical.com
> Subject: Re: [rt-users] Upgrade RT 3.8.7 to 4.0.1
> Message-ID: <20140822135941.ge3...@jibsh
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 < qu
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.
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?
UNSUBSCIBE
On 4 August 2014 09:28, Sternberger, Sven 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 postgresq
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://best
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
>
@lists.bestpractical.com
Subject: Re: [rt-users] Upgrade RT, what about plugin module?
On Thu, May 23, 2013 at 5:15 AM, Thomas Lau
mailto: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 n
On Thu, May 23, 2013 at 5:15 AM, Thomas Lau 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 a
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-Ex
Hello,
I want to upgrade our production RT v3.8.8 to the latest v4.0.6. I un-tarred
the RT 4.0.6 kit in /opt/rt-4.0.6.
on our production RT box. I want to be able to revert back to our current
production RT v3.8.8 system if
something goes wrong. I also am willing to build a new machine for RT 4
On Thu, Jan 12, 2012 at 01:09, Kevin Squire wrote:
> On Thu, 8 Dec 2011 02:14:30 +0400
> Ruslan Zakirov wrote:
>
>> On Tue, Dec 6, 2011 at 5:04 PM, Kevin Squire
>> wrote:
>> > When I would run 'make initdb' I would get an error:
>> > Now populating database schema.
>> > DBD::Pg::st execute fai
On Thu, 8 Dec 2011 02:14:30 +0400
Ruslan Zakirov wrote:
> On Tue, Dec 6, 2011 at 5:04 PM, Kevin Squire
> wrote:
> > When I would run 'make initdb' I would get an error:
> > Now populating database schema.
> > DBD::Pg::st execute failed: ERROR: relation "at_types" already
> > exists at /usr/sh
On Tue, Dec 6, 2011 at 5:04 PM, Kevin Squire wrote:
> When I would run 'make initdb' I would get an error:
> Now populating database schema.
> DBD::Pg::st execute failed: ERROR: relation "at_types" already exists
> at /usr/share/request-tracker3.8/lib/RT/Handle.pm line 506. ...returned
> with e
I have a system that we upgraded from RT 3.6.7 to 3.8.8 back in Aug.
I did a fresh install of RT. Then restored the database. Then
one-by-one added back in any customizations, plugins, etc.
We where using Asset Tracker on our 3.6.7 install (so the data was
restored when the DB was restored).
> I am looking for a way to use the binlogs to add the new tickets to the test
> server
>
> That way I don't have to dump the whole database again and the import and
> all that
> from the beginning.
Can't. The binlogs contain insert/update statements for a different schema.
If you tried to app
On 28 Apr 2009, at 7:01 pm, Asif Iqbal wrote:
> On Tue, Apr 28, 2009 at 1:53 PM, Tom Lahti
> wrote:
>
>>> Ok now that upgrade completed on the test system, I now see 5000
>>> more
>>> tickets already
>>> created on the production systems. Do I have to redo this whole
>>> thing? I
>>> have
On Tue, Apr 28, 2009 at 1:53 PM, Tom Lahti wrote:
> > Ok now that upgrade completed on the test system, I now see 5000 more
> > tickets already
> > created on the production systems. Do I have to redo this whole thing? I
> > have binlog enabled
> > since the beginning of the original instance. Ho
> Ok now that upgrade completed on the test system, I now see 5000 more
> tickets already
> created on the production systems. Do I have to redo this whole thing? I
> have binlog enabled
> since the beginning of the original instance. How do I append those new 500
> tickets?
> I guess I am now on a
On Tue, Nov 18, 2008 at 6:33 AM, Tim Cutts wrote:
>
> On 17 Nov 2008, at 10:34 pm, Asif Iqbal wrote:
>
> Do I upgrade from RT 3.4.5 to RT 3.8.1 directly? Or there is a roadmap
>> somewhere?
>>
>
> You can do this in almost one go, yes. It's almost exactly what I'm doing
> with my production RT,
Asif Iqbal wrote:
>
>
>
> Going to apply following upgrades:
> * 3.5.1
> * 3.7.1
> * 3.7.3
> * 3.7.10
> * 3.7.15
> * 3.7.19
> * 3.7.81
> * 3.7.82
> * 3.7.85
> * 3.7.86
> * 3.7.87
> * 3.8.0
> * 3.8.1
> * 3.8.2
>
> Enter RT version if you want to stop upgrade at some point,
> or leave it blank if
On Mon, Apr 27, 2009 at 11:19 AM, Asif Iqbal wrote:
>
>
> On Tue, Nov 18, 2008 at 6:33 AM, Tim Cutts wrote:
>
>>
>> On 17 Nov 2008, at 10:34 pm, Asif Iqbal wrote:
>>
>> Do I upgrade from RT 3.4.5 to RT 3.8.1 directly? Or there is a roadmap
>>> somewhere?
>>>
>>
>> You can do this in almost one
On Tue, Nov 18, 2008 at 6:33 AM, Tim Cutts wrote:
>
> On 17 Nov 2008, at 10:34 pm, Asif Iqbal wrote:
>
> Do I upgrade from RT 3.4.5 to RT 3.8.1 directly? Or there is a roadmap
>> somewhere?
>>
>
> You can do this in almost one go, yes. It's almost exactly what I'm doing
> with my production RT,
On Wed, Nov 19, 2008 at 10:08 AM, Tim Cutts wrote:
>
> On 18 Nov 2008, at 4:47 pm, Tim Cutts wrote:
>
> What switches did you use to dump the mysql? I see few gotcha's about
>>> using binary characters
>>> and separate dump for attachment table and stuff
>>>
>>
>> OK, yes, I've just looked at a
Asif, it's getting really hard to tell whose writing what with the way you
are quoting/replying to emails. It sounds like you are trying to not only
upgrade RT but also move your database from mysql 4.x.x to 5.x.x.
I would start by getting your current RT database dumped and successfully
moved to
On Wed, Nov 19, 2008 at 8:08 PM, Tim Cutts wrote:
>
> On 18 Nov 2008, at 4:47 pm, Tim Cutts wrote:
>
> What switches did you use to dump the mysql? I see few gotcha's about
>>> using binary characters
>>> and separate dump for attachment table and stuff
>>>
>>
>> OK, yes, I've just looked at an
On Thu, Apr 16, 2009 at 7:36 PM, Tim Cutts wrote:
>
> On 14 Apr 2009, at 3:09 pm, Asif Iqbal wrote:
>
> On Tue, Nov 18, 2008 at 10:37 PM, Tim Cutts wrote:
>>
>>
>>> On 18 Nov 2008, at 3:27 pm, Asif Iqbal wrote:
>>>
>>> What switches did you use to dump the mysql? I see few gotcha's about
>>>
>>
On 14 Apr 2009, at 3:09 pm, Asif Iqbal wrote:
> On Tue, Nov 18, 2008 at 10:37 PM, Tim Cutts wrote:
>
>>
>> On 18 Nov 2008, at 3:27 pm, Asif Iqbal wrote:
>>
>> What switches did you use to dump the mysql? I see few gotcha's about
>>> using binary characters
>>> and separate dump for attachment t
On Tue, Nov 18, 2008 at 10:37 PM, Tim Cutts wrote:
>
> On 18 Nov 2008, at 3:27 pm, Asif Iqbal wrote:
>
> What switches did you use to dump the mysql? I see few gotcha's about
>> using binary characters
>> and separate dump for attachment table and stuff
>>
>
> I haven't tested the attachments t
On Wed, Jan 21, 2009 at 04:34:58PM +0200, Alf Stockton wrote:
> I have just successfully installed 3.6 on my clients Ubuntu 8.04 server but
> would now appreciate getting some of the new features mentioned on the latest
> release.
> Please tell me how I go about upgrading?
>
Well, donwload the
I have just successfully installed 3.6 on my clients Ubuntu 8.04 server but
would now appreciate getting some of the new features mentioned on the latest
release.
Please tell me how I go about upgrading?
--
Regards,
Alf Stocktonwww.stockton.co.za
Don't tell any big lies today. Sma
Thanks very much, Ruslan.
On 19 Nov 2008, at 2:30 pm, Ruslan Zakirov wrote:
> As you're on mysql 4.1.x and RT older than 3.8 then you should
> dump/load data using binary character set to avoid any data
> conversions.
OK, so that's:
mysqldump --default-character-set=binary ... > dump.sql
yes?
On Wed, Nov 19, 2008 at 5:08 PM, Tim Cutts <[EMAIL PROTECTED]> wrote:
>
> On 18 Nov 2008, at 4:47 pm, Tim Cutts wrote:
>
>>> What switches did you use to dump the mysql? I see few gotcha's about
>>> using binary characters
>>> and separate dump for attachment table and stuff
>>
>> OK, yes, I've ju
On 18 Nov 2008, at 4:47 pm, Tim Cutts wrote:
>> What switches did you use to dump the mysql? I see few gotcha's about
>> using binary characters
>> and separate dump for attachment table and stuff
>
> OK, yes, I've just looked at an attachment to one of our tickets, and
> yes, it's corrupted. B
On 18 Nov 2008, at 4:47 pm, Tim Cutts wrote:
>> What switches did you use to dump the mysql? I see few gotcha's about
>> using binary characters
>> and separate dump for attachment table and stuff
>
> OK, yes, I've just looked at an attachment to one of our tickets, and
> yes, it's corrupted. B
> What switches did you use to dump the mysql? I see few gotcha's about
> using binary characters
> and separate dump for attachment table and stuff
OK, yes, I've just looked at an attachment to one of our tickets, and
yes, it's corrupted. Bugger. So I've obviously missed something. I
thou
On 18 Nov 2008, at 3:27 pm, Asif Iqbal wrote:
> What switches did you use to dump the mysql? I see few gotcha's about
> using binary characters
> and separate dump for attachment table and stuff
I haven't tested the attachments thoroughly yet, so I don't know
whether it worked. I just used o
On Tue, Nov 18, 2008 at 1:34 AM, Asif Iqbal <[EMAIL PROTECTED]> wrote:
> Do I upgrade from RT 3.4.5 to RT 3.8.1 directly? Or there is a roadmap
> somewhere?
>
> Do I upgrade the mysql 4.0.24 to 4.1 first before upgrading the RT?
Upgrade of mysql is not required, but mysql 4.0.x is not supported
an
On Tue, Nov 18, 2008 at 5:33 AM, Tim Cutts <[EMAIL PROTECTED]> wrote:
>
> On 17 Nov 2008, at 10:34 pm, Asif Iqbal wrote:
>
>> Do I upgrade from RT 3.4.5 to RT 3.8.1 directly? Or there is a roadmap
>> somewhere?
>
> You can do this in almost one go, yes. It's almost exactly what I'm doing
> with my
On 17 Nov 2008, at 10:34 pm, Asif Iqbal wrote:
> Do I upgrade from RT 3.4.5 to RT 3.8.1 directly? Or there is a roadmap
> somewhere?
You can do this in almost one go, yes. It's almost exactly what I'm
doing with my production RT, where I'm going from 3.4.2 to 3.8.1
>
> Do I upgrade the mysql
Do I upgrade from RT 3.4.5 to RT 3.8.1 directly? Or there is a roadmap
somewhere?
Do I upgrade the mysql 4.0.24 to 4.1 first before upgrading the RT?
It looks complicated w/o a roadmap.
I am using RT in production environment
On Fri, Nov 14, 2008 at 5:04 PM, Asif Iqbal <[EMAIL PROTECTED]> wrote
Hi All
Here is my current setup for RT
RT 3.4.5
Perl 5.8.6
DBIx::SearchBuilder 1.40
Apache 1.3.33
mod_perl 2.8.22
OpenSSL 0.9.7g
mysqld Ver 4.0.24-log for pc-solaris2.10 on i386 (Source distribution)
I like to upgrade it to latest RT.
Is there a path I can follow? Do I also need to upgrade mys
> Message: 4
> Date: Tue, 2 Jan 2007 21:26:07 +0530
> From: Raj Mathur <[EMAIL PROTECTED]>
> Subject: [rt-users] Upgrade RT 3.4 to 3.6 on Debian
> To: rt-users@lists.bestpractical.com
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=&quo
Hi,
I recently upgraded my Debian system running RT 3.4.5-1 with
PostgreSQL. The upgrade caused some issues, including the one
described in:
http://lists.fsck.com/pipermail/rt-users/2005-August/033304.html
I fixed that by hacking the code in Elements/Callback to change the
path to comp_roo
46 matches
Mail list logo
