RT 3.0.0rc4 is now available. It contains a partial fix for the
new/open/new issue, as well as all the postgres fixes we’ve discussed.
For both postgres and mysql, there have been small but important
schema changes. the “full” release notes for this release candidate
(Friday morning) will include instructions as to how to do this, if you
can’t handle it on your own.
-j
Request Tracker — Best Practical Solutions – Trouble Ticketing. Free.
RT 3.0 RC4 Release notes
There are several minor isses with RC4 that will be slipstreamed in
before 3.0.0, but otherwise, I believe we’re basically there.
You can pick up this release from
http://fsck.com/pub/rt/devel/rt-3-0-0rc4.tar.gz
Changelog
23 11 New french translation
25 12 Brazilian Portuguese translation
26 13 Postgres fixes
27 14 Postgres schema tweak
28 15 Further postgres tweaks and fixes
29 16 RT should now be less overzealous about opening and then
marking a ticket 'new' again
30 17 Bumping to 3.0.0rc4
As is often the case, several schema issues popped up at the last minute. Below are instructions for bringing an existing database up to date.
Mysql:
New column added
mysql rt3 -e 'alter table sessions add column LastUpdated timestamp'
Postgres:
Several unavoidable changes have been made to RT's postgres database
schema.
You'll need to issue the following commands to postgres in order
to bring your schema up to date:
ALTER TABLE Attachments RENAME COLUMN Content to OldContent;
ALTER TABLE Attachments ADD COLUMN Content text NULL;
UPDATE Attachments SET Content = OldContent;
ALTER TABLE Attachments RENAME COLUMN Headers to OldHeaders;
ALTER TABLE Attachments ADD COLUMN Headers text NULL;
UPDATE Attachments SET Headers = OldHeaders;
ALTER TABLE sessions ADD COLUMN LastUpdated TIMESTAMP not null default current_timestamp;
(The following two commands will only work on Postgres 7.3)
ALTER TABLE Attachments DROP Column OldContent;
ALTER TABLE Attachments DROP Column OldHeaders;
Request Tracker — Best Practical Solutions – Trouble Ticketing. Free.
rt-announce mailing list
rt-announce@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-announce
-----BEGIN PGP SIGNED MESSAGE-----
I’m just curious about the line:
ALTER TABLE sessions ADD COLUMN LastUpdated TIMESTAMP not nulldefault
current_timestamp;It doesn’t work in postgres 7.3.2 so I’m just wondering how important it is?
Define “doesn’t work”
Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.
-----BEGIN PGP SIGNED MESSAGE-----
On 24-Mar-2003, Jesse Vincent wrote message “Re: [rt-devel] [rt-announce] RT
3.0.0rc4”
Define “doesn’t work”
rt3=# ALTER TABLE sessions ADD COLUMN LastUpdated TIMESTAMP not null default
current_timestamp;
ERROR: Adding columns with defaults is not implemented.
Add the column, then use ALTER TABLE SET DEFAULT.
psql (PostgreSQL) 7.3.2
contains support for command-line editing
Andy Harrison
Great Works Internet
System Operations
ajharrison@gwi.net
RSA 1024 pgp key: http://www.nachoz.com/andy.pub
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8
iQCVAwUBPn9IDFPEkLgodAWVAQH+IgP/XT9DA/NtzYWwHVH0tuY42rF0BPiOG7JZ
PQiFAqK3IOyYR/OEpiaRpZqHeE5hFOOAY1RHo8mRlpwfCTQz/jGQ5Dkscis5ENmY
eZUYs5KaedfRRPzJxhYhZj9a+o+CnDGKLyPekP8mce4hXAYDW3ivbbqtee/qKPsl
qVALY3h6rBM=
=KPLl
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Just another FYI, when doing the dump import into either postgres 7.2.4 or
7.3.2, I get errors like the following when doing the user import:
ERROR: pg_atoi: error in “ajharrison@gwi.net”: can’t parse “ajharrison@gwi.net”
Andy Harrison
Great Works Internet
System Operations
ajharrison@gwi.net
RSA 1024 pgp key: http://www.nachoz.com/andy.pub
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8
iQCVAwUBPn9XMVPEkLgodAWVAQECVAQAnumWEmWweV7/DysgHCGBitmLO6oac2Hp
Cehg34eMHjRslZZIRO/2GcRn9JwBuBVOnZIXtYvPkCdvqBmvo+9S4FR5kJYTgN5n
uenB2m11XYlimIl56K26PSDedh9W8Poz9KPP+DZbe2vX1Iiz4JpfqNzSM/Ovr2s5
h7PMm1TMwc8=
=pmg3
-----END PGP SIGNATURE-----
Can you give us some more context on these errors? There’s no way I can
debug this stuff without debugging information like what it was trying
to import at the time, what table it failed to import into, what SQL
query failed, etc…On Mon, Mar 24, 2003 at 02:06:26PM -0500, Andy Harrison wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Just another FYI, when doing the dump import into either postgres 7.2.4 or
7.3.2, I get errors like the following when doing the user import:ERROR: pg_atoi: error in “ajharrison@gwi.net”: can’t parse “ajharrison@gwi.net”
~~
Andy Harrison
Great Works Internet
System Operations
ajharrison@gwi.net
RSA 1024 pgp key: http://www.nachoz.com/andy.pub-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8iQCVAwUBPn9XMVPEkLgodAWVAQECVAQAnumWEmWweV7/DysgHCGBitmLO6oac2Hp
Cehg34eMHjRslZZIRO/2GcRn9JwBuBVOnZIXtYvPkCdvqBmvo+9S4FR5kJYTgN5n
uenB2m11XYlimIl56K26PSDedh9W8Poz9KPP+DZbe2vX1Iiz4JpfqNzSM/Ovr2s5
h7PMm1TMwc8=
=pmg3
-----END PGP SIGNATURE-----
Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.
-----BEGIN PGP SIGNED MESSAGE-----
On 24-Mar-2003, Jesse Vincent wrote message “Re: [rt-devel] [rt-announce] RT
3.0.0rc4”
Can you give us some more context on these errors? There’s no way I can
debug this stuff without debugging information like what it was trying
to import at the time, what table it failed to import into, what SQL
query failed, etc…
Ok, well, I did a new dump from the production rt server. I’m not sure what
version of rt2 it’s running:
% head rt2/bin/rt
#!/usr/bin/perl -w
It appears to be running postgres 7.1.2.
It created the dump without incident. I pulled that dump over to my machine
and imported it. I had previously been experimenting with pg7.2.4 and wanted
to get rt3rc4 working in pg7.3.2 so I got 7.3.2 back up and running. I redid my
configure, make install, make dropdb, make initialize-database and started the
dump. When the import was complete, I started having problems immediately when
trying to connect to the webserver in my browser. The httpd error log showed:
FATAL 1: This connection has been terminated by the administrator.
[Mon Mar 24 13:45:45 2003] [error] Connect Failed could not connect to server:
Connection refused
at /opt/rt3/lib/RT.pm line 123
I then looked at the postgres log and noticed all the atoi errors. I wasn’t
sure if this had been doing this in pg7.2.4 so I fired that back up and tried
with that and noticed the same atoi errors, but I was able to access webrt from
my browser without any problems.
The only errors shown in the postgres log are the atoi errors when it tries to
import each user. Note that the user is imported and I can see it when I look
(i’m just being lazy and using phpPgAdmin).
Not sure what more information you need, let me know and I’ll provide it.
Andy Harrison
Great Works Internet
System Operations
ajharrison@gwi.net
RSA 1024 pgp key: http://www.nachoz.com/andy.pub
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8
iQCVAwUBPn9cOVPEkLgodAWVAQFIgAP/b3m6iBPQIIO0TLtjmwiI2l7TFJE52SK2
G/4NHSaKkOtAja20GXAABDAS8NJFMBGxhg5Fx+pt8UyrLyAKV29kZMM+1If4XhH/
NjwKkJ1akXpLgCDptTAmLCXJSdWc6ajRAM5CWU/54vpG2BgMsTHkPQ9HpwsmbhQs
451Kwz2EFMQ=
=lRgI
-----END PGP SIGNATURE-----
Can you give us some more context on these errors? There’s no way I can
debug this stuff without debugging information like what it was trying
to import at the time, what table it failed to import into, what SQL
query failed, etc…Not sure what more information you need, let me know and I’ll provide it.
Please see above.
~~
Andy Harrison
Great Works Internet
System Operations
ajharrison@gwi.net
RSA 1024 pgp key: http://www.nachoz.com/andy.pub-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8iQCVAwUBPn9cOVPEkLgodAWVAQFIgAP/b3m6iBPQIIO0TLtjmwiI2l7TFJE52SK2
G/4NHSaKkOtAja20GXAABDAS8NJFMBGxhg5Fx+pt8UyrLyAKV29kZMM+1If4XhH/
NjwKkJ1akXpLgCDptTAmLCXJSdWc6ajRAM5CWU/54vpG2BgMsTHkPQ9HpwsmbhQs
451Kwz2EFMQ=
=lRgI
-----END PGP SIGNATURE-----
rt-devel mailing list
rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.