I found an older post on the PostgreSQL mailinglist with same problems
http://www.postgresql.org/message-id/d960cb61b694cf459dcfb4b0128514c207bb6...@exadv11.host.magwien.gv.at
And I was able to fix the issue by dumping and re-importing the db!
# Create empty PG-DB
rt-setup-database --action
Hi,
you are right.
History is not affected but Subject, User Real Name, Signature stored in
User Preferences, Description of Scrips, Templates, Groups and Queues,
Template Content, Article Name
I noticed that the problem with the german umlauts is not in all fields.
In my history for
I have the same problem. I want to migrate my RT 4.2.12 mysql-database to
postgres. Did you find an solution for this problem?
I noticed that the problem with the german umlauts is not in all fields. In
my history for example the german umlauts displayed correctly but in the
ticket subject they
RT 4.2.8 and MySQL: old and new tickets looks perfectly, also the
serialized data seems to be ok.
With locale LANG=en_US.UTF-8
^^test ticket with umlaut ü^@^@^@^GSubject
locale LANG=POSIX
^^test ticket with umlaut ^@^@^@^GSubject
Maybe rt-importer or perl opens the binary files with
I'm now testing to serialize mysql and import to mysql again.
This is working, so it's a problem with Pg
smime.p7s
Description: S/MIME Cryptographic Signature
On 9/17/15 8:12 AM, Maik Nergert wrote:
Hexcode from ü → c3 bc
is encoded again to → c3 83 (Ã) and c2 bc (¼)
(http://www.utf8-zeichentabelle.de/)
First I've upgraded RT from 3.8 to 4.2 with mysql db (utf8) and
everything went smoothly.
Can you confirm that the umlaut can be sucessfully added
Hi RT Users,
I'm testing the migration from MySQL to PostgreSQL and I'm experiencing
problems with LATIN1 characters (particularly German umlauts) after the
migration. They look like ü instead ü
Hexcode from ü → c3 bc
is encoded again to → c3 83 (Ã) and c2 bc (¼)
Hello,
Sorry for the disturb !
I’ve found, the cause was callback.
Nice day
Horst
De : Kriegers Horst
Envoyé : vendredi 15 novembre 2013 08:21
À : 'ML - rt-users'
Objet : Migration 4.08 to 4.2 : no style sheet
Hi,
I’ve migrated RT 4.08 to 4.2 and no style sheet a used.
Any idea ?
Thanks
Hi,
I’ve migrated RT 4.08 to 4.2 and no style sheet a used.
Any idea ?
Thanks for your help
Horst
Note Importante: Le contenu de ce courriel est uniquement réservé à la personne
ou l'organisme à qui il est destiné. Si vous n'êtes pas le destinataire prévu,
Hello,
I have read the documentation on upgrading and none of the particulars
exactly fit.
I have a new VM (Centos6). I have installed RT 4.0.17 completely vanilla.
Old mysql:
mysql Ver 14.12 Distrib 5.0.81, for unknown-linux-gnu (x86_64) using
readline 5.2
Old RT is 3.8.9
New mysql:
mysql
On Tue, Aug 13, 2013 at 1:40 PM, Lois Bennett
lois.benn...@channing.harvard.edu wrote:
Hello,
I have read the documentation on upgrading and none of the particulars
exactly fit.
I have a new VM (Centos6). I have installed RT 4.0.17 completely vanilla.
Old mysql:
mysql Ver 14.12
-boun...@lists.bestpractical.com] On Behalf Of Thomas Sibley
Sent: Friday, August 09, 2013 3:46 PM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Migration Prep
On 08/09/2013 06:36 AM, Paul O'Rorke wrote:
When I look at syslog I see the following during startup:
Aug 9 08:28:04 rt4
OK - a little premature.
After running for a few hours I rebooted my new RT and get a database
connect fail. For some reason it's not trying to use a password in DBI
connect:
Aug 9 00:33:23 rt4 RT: DBI
connect('dbname=rtdb;host=localhost','rtuser',...) failed: Access
denied for
When I look at syslog I see the following during startup:
Aug 9 08:28:03 rt4 acpid: starting up with netlink and the input layer
Aug 9 08:28:03 rt4 acpid: 1 rule loaded
Aug 9 08:28:03 rt4 acpid: waiting for events: event logging is off
Aug 9 08:28:04 rt4 RT: DBI
A little more information.
If I run through the setup screens that are presented because RT thinks
there is no initialised database I get my new RT with the theme and logo
etc but it flips between that and again going to the login screen. Of
course this overwrites my RT_SiteConfig.pm but I'm
On 08/09/2013 06:36 AM, Paul O'Rorke wrote:
When I look at syslog I see the following during startup:
Aug 9 08:28:04 rt4 RT: DBI
connect('dbname=rtdb;host=localhost','rtuser',...) failed: Can't connect
to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
at
Thanks Thomas
Setting Apache to start after mysql seems to have done the trick.
Sent from my GT-I9305T on the Telstra 4G network
Original message
From: Thomas Sibley t...@bestpractical.com
Date:
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Migration Prep
Just a heads up that running the make upgrade-database on an upgrade
from 3.8.4 to 4.0.17 worked flawlessly once I successfully restored the
DB from mysqldump.
Thanks for the help and more importantly thanks for fixing that script.
:-)
*Paul O’Rorke*
Tracker Software Products
Thanks for all the support. I have a shiny new 4.0.17 ticking away
nicely. Very happy.
*Paul O’Rorke*
Tracker Software Products
p...@tracker-software.com mailto:paul.oro...@tracker-software.com
On Thu, Aug 01, 2013 at 12:40:44PM -0700, Paul O'Rorke wrote:
I don't remember skipping any errors during make upgrade-database. Here
are the table
descriptions you asked for. As you can see the Classes, Topics, Articles
tables do exist.
Do you have logs of the upgrade?
On Fri, Aug 2, 2013 at 10:48 AM, Kevin Falcone falc...@bestpractical.comwrote:
You can look at 'show create table sessions' which should be innodb
not myisam and look at your Attributes table, which should have a
LONGBLOB for Content.
I just did my test upgrade from rt 3.8.2 / mysql 5.0.75
On Fri, Aug 02, 2013 at 11:21:24AM -0400, Asif Iqbal wrote:
On Fri, Aug 2, 2013 at 10:48 AM, Kevin Falcone
[1]falc...@bestpractical.com wrote:
You can look at 'show create table sessions' which should be innodb
not myisam and look at your Attributes table, which should have a
On Fri, Aug 2, 2013 at 11:32 AM, Kevin Falcone falc...@bestpractical.comwrote:
I just did my test upgrade from rt 3.8.2 / mysql 5.0.75 to rt 4.0.16
/ mysql 5.5.32
but session table still showing myisam.
$ mysql -e 'use rt4; show create table sessions'
| sessions | CREATE
On Fri, Aug 02, 2013 at 12:49:47PM -0400, Asif Iqbal wrote:
Please show a log of your make upgrade-database step
* 3.9.8
* 4.0.1
That's definitely skipping steps.
It should read:
* 3.9.8
* 4.0.0rc2
* 4.0.0rc4
* 4.0.0rc7
* 4.0.1
What does ls -l etc/upgrade/ in the directory where
Thanks again Kevin,
OK - I'll roll back and run the upgrade again from 3.8.4.
Do you have logs of the upgrade?
How do I enable/check logging for that?
*Paul O'Rorke*
Tracker Software Products
p...@tracker-software.com mailto:paul.oro...@tracker-software.com
On 8/2/2013 7:48 AM, Kevin
On Fri, Aug 2, 2013 at 1:04 PM, Kevin Falcone falc...@bestpractical.comwrote:
On Fri, Aug 02, 2013 at 12:49:47PM -0400, Asif Iqbal wrote:
Please show a log of your make upgrade-database step
* 3.9.8
* 4.0.1
That's definitely skipping steps.
It should read:
* 3.9.8
*
On 08/02/2013 10:04 AM, Kevin Falcone wrote:
On Fri, Aug 02, 2013 at 12:49:47PM -0400, Asif Iqbal wrote:
Please show a log of your make upgrade-database step
* 3.9.8
* 4.0.1
That's definitely skipping steps.
It should read:
* 3.9.8
* 4.0.0rc2
* 4.0.0rc4
* 4.0.0rc7
*
On Tue, Jul 30, 2013 at 03:17:11PM -0700, Paul O'Rorke wrote:
I am assuming that I can't just UPDATE the passwords in MySQL because of
the hashing? I tried
without success:
mysql UPDATE rtdb.Users SET Password=PASSWORD('') WHERE
Name='jamie';
Query OK, 1 row
Sorry to keep bugging this list,
can anyone tell me why I can't set the password in MySQL with the UPDATE
statement below? I have upgraded from 3.8.4 to 4.0.14 and run the
password updater. MySQL was at 5.1 so I didn't need to do the MySQL
update stuff as far as my reading shows.
Is
Thanks again Kevin,
so I did try what's on that page you sent me to:
perl -I/opt/rt4/local/lib -I/opt/rt4/lib \
-MRT -MRT::User \
-e'RT::LoadConfig();RT::Init(); my $u =
RT::User-new($RT::SystemUser); $u-Load(root);
$u-SetPassword(secret)'
returned to a prompt with no
On Wed, Jul 31, 2013 at 10:24:29AM -0700, Paul O'Rorke wrote:
Password: !sha512!8MzDJesb8kr4UHIA!784B/mzwvLcUEEa
`Password` varbinary(40) DEFAULT NULL,
These are 3.8 versions of that table, not 4.0 versions.
Did you run all of the database upgrade steps? This was step
OK - I thought that *make upgrade-database* covered those - it suggested
it was doing all those incremental updates. It asked from which version
I was update from/to and showed each step as doing something. What is
it's purpose then?
Do I have to still do each one manually from 3.8.4 then?
On Wed, Jul 31, 2013 at 12:31:26PM -0700, Paul O'Rorke wrote:
OK - I thought that make upgrade-database covered those - it suggested it
was doing all those
incremental updates. It asked from which version I was update from/to and
showed each step as
doing something. What is it's
On Mon, Jul 29, 2013 at 02:30:35PM -0700, Paul O'Rorke wrote:
In the meanwhile I am finding that after running make upgrade-database
(took me through all
the upgrades from 3.8.4 to 4.0.15) and then trying to set up Apache again
I'm running into a
loop on the login page. If I run
Thanks for that Kevin,
not the first time - a silly little mistake had me scratching my head.
I had in my Apache config a rewrite rule for /rt and had the wrong value
in RT_Siteconfig for Set($WebPath, '');
So I now get my logon screen but cannot log in.
I did run the password updater:
Thanks Kevin,
I'm going through that right now. I must admit I'm a little confused by
the whole LifeCycle thing. I'm going through
http://bestpractical.com/docs/rt/4.0/customizing/lifecycles.html now to
see if I can swing this.
In the meanwhile I am finding that after running *make
I guess I should add that although I cannot log into RT through the WEB
I can confirm that both root and rtuser can access mysql locally via the
command line. I guess however that although the users that RT runs as
can access MySQL that does not mean that the users defined in there are
On Thu, Jul 25, 2013 at 01:47:07PM -0700, Paul O'Rorke wrote:
I meant the README Docs in the installer archive mostly.
My concern with the migration is that I used custom statuses for queues
and I have to now use
the LifeCycle set up. I wasn't sure how the DB restore would go
On Wed, Jul 24, 2013 at 08:36:43PM -0700, Paul O'Rorke wrote:
From what I've read it seems that the best approach might be to:
1. make a clone of the existing RT,
2. upgrade it to 4.0.13
3. do a mysqldump on the upgraded clone
4. restore the dump on the new server.
Since
Thanks for that Kevin,
I meant the README Docs in the installer archive mostly.
My concern with the migration is that I used custom statuses for queues
and I have to now use the LifeCycle set up. I wasn't sure how the DB
restore would go because I imagine I'm going to have different fields
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/26/2013 12:32 AM, Kevin Falcone wrote:
On Wed, Jul 24, 2013 at 08:36:43PM -0700, Paul O'Rorke wrote:
From what I've read it seems that the best approach might be to:
1. make a clone of the existing RT, 2. upgrade it to 4.0.13 3. do
a
Hi,
I've been putting off upgrading my RT 3.8.4 to current because I always
got stuck. Now I can't put it off any more. I have read lost about
upgrading but I don't want to upgrade the current server/installation, I
want to move it to a brand new server and OS.
From what I've read it
Hi,
I have inherited an RT 3.6.7 system with around 300,000 tickets in it,
taking up about 40GB of disk space.
The hardware this runs on is getting on a bit, and response times are
now getting to the frustratingly slow point.
I have a new server (Debian Squeeze) on which I have managed to
Hello Gary!
The better way it´s to dump your database.
After that, you need to upload to the new server, and finaly use the comand
make upgrad database.
I upgrade my server from 3.6.0 to 4.0.10.
Works like a charm.
2013/4/5 Gary Mason g.ma...@fairfx.com
Hi,
I have inherited an RT 3.6.7
On Fri, Apr 05, 2013 at 05:16:44PM +0100, Gary Mason wrote:
Hi,
I have inherited an RT 3.6.7 system with around 300,000 tickets in
it, taking up about 40GB of disk space.
The hardware this runs on is getting on a bit, and response times
are now getting to the frustratingly slow point.
:22 AM
To: Gary Mason
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Migration to a new server
Hello Gary!
The better way it´s to dump your database.
After that, you need to upload to the new server, and finaly use the comand
make upgrad database.
I upgrade my server from 3.6.0
Thanks. rt-validator did indeed balk, but recreating the internal groups
didn't solve the problem.
Anyway - As a workaround, we just created new tickets and merged the faulty
tickets into the newly created one and it appears to work.
--
troels
On 25 April 2012 15:03, Thomas Sibley
Hi list,
We are migrating over to RT3 from Lighthouse and I figured I could simply
write a script to fill data directly into the database, rather than going
through the RT api. The reason for me doing this, is that I'm really not
very fluent in perl.
Things appear to work except for one thing -
On 04/25/2012 04:45 AM, Troels Knak-Nielsen wrote:
I know I brought this upon myself, but does any one here have any idea
about what is wrong?
You didn't create the internal groups RT uses for roles on a ticket,
including Owner. Running rt-validator may be able to fix this up for
you, but it's
Hi all,
I'm about to migrate an old RT 3.6.3 system on a new (virtual) machine
with version 3.8.8.
I imported the old database (MySQL) and run the upgrade-schema-Script,
no problem with that.
After setting up the new system I imported another dump from the old
(still in use) system. All my
On Tue, Feb 01, 2011 at 09:52:49AM +0100, Obando, David DE - EV wrote:
Hi all,
I'm about to migrate an old RT 3.6.3 system on a new (virtual) machine
with version 3.8.8.
I imported the old database (MySQL) and run the upgrade-schema-Script, no
problem with that.
After
: [rt-users] Migration RT 3.6.3 to 3.8.8
On Tue, Feb 01, 2011 at 09:52:49AM +0100, Obando, David DE - EV wrote:
Hi all,
I'm about to migrate an old RT 3.6.3 system on a new (virtual) machine
with version 3.8.8.
I imported the old database (MySQL) and run the upgrade-schema-Script
Hi all,
My goal is to implement RT3 as new ticketing system but it seems a
demand is that the current history of OTRS needs to be integrated into
RT3.
I'm not all to happy with it but does someone have experience with this?
I haven't found any import scripts yet.
Met vriendelijke
On Mon, May 17, 2010 at 02:10:43PM +0200, Emmanuel Lacour wrote:
Maybe there is a better way as of recent postgres?
FYI: fwd
--
Zito
---BeginMessage---
* Václav Ovsík:
Is it possible that binding of binary data-type (bytea) without
data-type specification would behave like in MySQL in some
On Sat, May 15, 2010 at 01:35:36PM +0200, Václav Ovsík wrote:
Hi Emmanuel,
thanks for your reply.
On Sat, May 15, 2010 at 07:23:01AM +0200, Emmanuel Lacour wrote:
With Pg, this content is handled specifically, see _EncodeLOB in
lib/RT/Record.pm.
(see also mysql2Pg page on RTwiki).
On Mon, May 17, 2010 at 01:53:43PM +0200, Václav Ovsík wrote:
Oh yes, I was blind that RT uses DBIx::SearchBuilder. There is
a subroutine BinarySafeBLOBs defined in
DBIx::SearchBuilder::Handle::Pg.pm and returns undef. That is - Pg is
considered not capable handling binary in safe manner.
On Mon, May 17, 2010 at 02:10:43PM +0200, Emmanuel Lacour wrote:
On Mon, May 17, 2010 at 01:53:43PM +0200, Václav Ovsík wrote:
Oh yes, I was blind that RT uses DBIx::SearchBuilder. There is
a subroutine BinarySafeBLOBs defined in
DBIx::SearchBuilder::Handle::Pg.pm and returns undef. That
Hi Emmanuel,
thanks for your reply.
On Sat, May 15, 2010 at 07:23:01AM +0200, Emmanuel Lacour wrote:
With Pg, this content is handled specifically, see _EncodeLOB in
lib/RT/Record.pm.
(see also mysql2Pg page on RTwiki).
I saw Base64 encoding in script on wiki page and also elsewhere, but
Dear Users and Developers,
I'm facing a migration four instances RT 3.2.2 to RT 3.8.8 with a number
of customizations.
Back-end database is MySQL and I have prepared a script for loading
database dumps from old MySQL 3.23.58 to 5.0.51 (Debian Lenny)
and then upgrading RT schema
On Fri, May 14, 2010 at 11:43:35PM +0200, Václav Ovsík wrote:
Dear Users and Developers,
I'm facing a migration four instances RT 3.2.2 to RT 3.8.8 with a number
of customizations.
Back-end database is MySQL and I have prepared a script for loading
database dumps from old MySQL 3.23.58 to
This is VERY nice to have. I will add it to the wiki so that others may
reference it in the future:
http://wiki.bestpractical.com/view/MigrateBugzillaToRT
Javier Garcia wrote:
Hi all,
I haven't seen this on the list so I will send the email again.
Please find attached a short description
Valley
-Original Message-
From: rt-users-boun...@lists.bestpractical.com
[mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Javier
Garcia
Sent: 23 April 2009 14:03
To: Keith A McDermott; Ken Crocker
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Migration
Hi,
I've
Hi all,
I haven't seen this on the list so I will send the email again.
Please find attached a short description on how I migrated our 26K
bugzilla tickets to RT.
Any comments or fixes will be welcomed.
Environment:
- OS: Debian Etch 2.6.18-6-486
- RT version: 3.8.2
- MySQL version:
...@lists.bestpractical.com] *On Behalf Of
*Javier Garcia
*Sent:* 21 April 2009 10:50
*To:* Jo Rhett
*Cc:* rt-users@lists.bestpractical.com
*Subject:* Re: [rt-users] Migration
Hi all,
I have found the scripts here:
http://www.gossamer-threads.com/lists/rt/users/53073?do=post_view_threaded#53073
: Javier Garcia; rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Migration
Kenn,
I have not, however I am definitely not too good at programming - let
alone perl (my brain is hard-coded to procedural not object-oriented
programming). Sounds interesting though as a possible side-project
Of
*Javier Garcia
*Sent:* 21 April 2009 10:50
*To:* Jo Rhett
*Cc:* rt-users@lists.bestpractical.com
*Subject:* Re: [rt-users] Migration
Hi all,
I have found the scripts here:
http://www.gossamer-threads.com/lists/rt/users/53073?do=post_view_threaded#53073
But they are not working. After
Garcia
*Sent:* 21 April 2009 10:50
*To:* Jo Rhett
*Cc:* rt-users@lists.bestpractical.com
*Subject:* Re: [rt-users] Migration
Hi all,
I have found the scripts here:
http://www.gossamer-threads.com/lists/rt/users/53073?do=post_view_threaded#53073
But they are not working. After following the README I
@lists.bestpractical.com
Subject: Re: [rt-users] Migration
Yes. Search the mailing list archives or Google. Both of which return
the script you need quickly.
On Apr 20, 2009, at 8:59 AM, Javier Garcia wrote:
We are manually migrating all our Bugzilla databases to RT using
Perl, but we are having
: Re: [rt-users] Migration
Hi all,
I have found the scripts here:
http://www.gossamer-threads.com/lists/rt/users/53073?do=post_view_thread
ed#53073
But they are not working. After following the README I ran sh
migrate.sh and got the following:
Could not load Everyone group
-users@lists.bestpractical.com
Subject: Re: [rt-users] Migration
Hi all,
I have found the scripts here:
http://www.gossamer-threads.com/lists/rt/users/53073?do=post_view_threaded#53073
But they are not working. After following the README I ran “sh migrate.sh”
and got the following
Hi all,
We are manually migrating all our Bugzilla databases to RT using Perl,
but we are having issues with some of them and I can't find anything on
the Internet.
Is there a documented way on How to migrate Bugzilla to RT?
Does anybody have a script for that?
PS: Both servers are
Yes. Search the mailing list archives or Google. Both of which
return the script you need quickly.
On Apr 20, 2009, at 8:59 AM, Javier Garcia wrote:
We are manually migrating all our Bugzilla databases to RT using
Perl, but we are having issues with some of them and I can’t find
anything
Hi folks,
Has anyone any experience with migrating a Mantis installation / database
structure, to RT? Any hints, or scripts to save reinventing the wheel, would
be appreciated.
--
Richard Foley
Ciao - shorter than aufwiedersehen
http://www.rfi.net/
Greetings!
Has anyone had experience with data migration from other systems?
Specifically, we're moving from Mantis to RT, both with MySQL backends
but on physically different systems. It would be nice if we could
preserve the historical data that currenly resides on the older system.
Has
Kevin,
Right now we are about to design a perl program that will read an
Oracle DataBase and then use CLI to create the new tickets in RT. We
would REALLY be appreciative of anyone who could send us a good perl
model for that function. When we get it to work, we'll definitely post it.
Right now we are about to design a perl program that will read an
Oracle DataBase and then use CLI to create the new tickets in RT. We
would REALLY be appreciative of anyone who could send us a good perl
model for that function. When we get it to work, we'll definitely post it.
That
What does the schema for IRM look like?
On Wed, Jul 2, 2008 at 3:40 PM, Bo Lynch [EMAIL PROTECTED] wrote:
We currently use an open source solution called IRM for our ticket system.
It uses a mysql database. Does anyone have any knowledge of migrating from
IRM to RT. Any info would be greatly
We currently use an open source solution called IRM for our ticket system.
It uses a mysql database. Does anyone have any knowledge of migrating from
IRM to RT. Any info would be greatly appreciated.
Thanks
--
Bo Lynch
___
Also, one important question: all documentation made me believe that
there is a direct migration path (i.e., I don't need to install an
intermediary version) from 3.0.6 to 3.6.1. Is that true?
That's correct.
Goodbye!
--
Luis Motta Campos
Segula Technologies Portugal
Dear List
I'm planning to migrate a 300K tickets (650GB disc space) database
(with a lot of attachments) from RT 3.0.9 to RT3.6.1.
To what I'm concerned, this is a matter of importing the old RT system
database to the new system database and apply some SQL scripts to
patch/update the
Thanks for help.
I have imported database succesfully but now I want to
upgrade my database from 3.4.5 to 3.6.1. So I run the
following script
###
for action in schema acl insert; do
/usr/sbin/rt-setup-database --dba root --dba-password
mypass --action $action --datadir
Its Azfar wrote:
How could I transfer my existing RT database to a new
RT host.
mysqldump -u mysql_user -p mysql_password rt_db rt.sql
on the original box
mv the file (rt.sql) to the new box
and on
Hi,
We are trying to migrate rt2 to rt3 using mysql. The size of the
database is 100 Mb with 3500 tickets. It took 45 min to migrate to rt3
(mysql 5). Anybody has similar experience of the time it took.
Ultimately we would like to migrate the main database of size 6 GB. At
this ratio it might
83 matches
Mail list logo
