Ticket creation error after using migration script s

Hi,

From This:
Mon Apr 7 07:49:08 2003] [warning]: DBD::Pg::st execute failed: ERROR:
Cannot insert a duplicate key into unique index tickets_pkey at
/usr/lib/perl5/site_perl/5.8.0/DBIx/SearchBuilder/Handle.pm line 376.
(/opt/rt3/lib/RT.pm:222)

I can only assume that the counter for tickets didn’t get increased when the
old tickets got in, cause now it is trying to add an index number that
already exists. have a look at tickets_pkey.

/Shmulik.-----Original Message-----
From: Jamie Wilkinson [mailto:jaq@spacepants.org]
Sent: Mon, April 07, 2003 9:57 AM
To: rt-users@lists.fsck.com
Subject: [rt-users] ticket creation error after using migration scripts

Hi all.

I’ve just spent an exciting few days moving our RT installation from Red Hat
7.0, RT 2.0.14, with a pile of CPAN installed with chewing gum and straw, to
Red Hat 8.0, RT 3.0.0 (on httpd 2.0.40, mod_perl 1.99 and postgresql 7.3.2).
Atually most of it went smoothly, I would highly recommend cpan2rpm for
those
package management control freaks ( http://perl.arix.com/cpan2rpm/man.html
).

After installing the new rt3 code, and running make initialize-database, I
can create tickets from the web interface and from rt-mailgate.

Then I did a make dropdb (to clear out these dummy tickets) and make
initialize-database again.

I used rt2-to-rt3 1.7 to dump the old database from the old machine, and
reimported it without errors into the new database.

Now, I’ve logged in with the username and password from rt2 (so the import
must have worked), and checked my ACLs:

Everyone can CreateTicket, CommentOnTicket, ReplyToTicket, and SeeQueue
Requestor can ShowTicket
staff can ModifyTicket, OwnTicket, ShowTicket, ShowTicketComments, Watch,
WatchAsAdminCC
and finally, my own user has most of the other rights enabled.

I create the ticket by clicking on the New ticket in button, and pressing
Create on the next page.

RT3 responds with:

RT Error
Ticket could not be created due to an internal error

and rt.log has the following:

[Mon Apr 7 07:49:08 2003] [warning]: DBD::Pg::st execute failed: ERROR:
Cannot insert a duplicate key into unique index tickets_pkey at
/usr/lib/perl5/site_perl/5.8.0/DBIx/SearchBuilder/Handle.pm line 376.
(/opt/rt3/lib/RT.pm:222)
[Mon Apr 7 07:49:08 2003] [warning]: RT::Handle=HASH(0x93501d0) couldn’t
execute the query 'INSERT INTO Tickets (Owner, Type, InitialPriority,
LastUpdatedBy, Resolved, Starts, Subject, Status, Created, FinalPriority,
Priority, Queue, Due,
LastUpdated, Creator) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)'
at /usr/lib/perl5/site_perl/5.8.0/DBIx/SearchBuilder/Handle.pm line 383.
(/opt/rt3/lib/RT.pm:222)
[Mon Apr 7 07:49:08 2003] [warning]: DBD::Pg::st execute failed: ERROR:
current transaction is aborted, queries ignored until end of transaction
block at /usr/lib/perl5/site_perl/5.8.0/DBIx/SearchBuilder/Handle.pm line
376.
(/opt/rt3/lib/RT.pm:222)
[Mon Apr 7 07:49:08 2003] [warning]: RT::Handle=HASH(0x93501d0) couldn’t
execute the query 'UPDATE Tickets SET EffectiveId=? WHERE id=? ’ at
/usr/lib/perl5/site_perl/5.8.0/DBIx/SearchBuilder/Handle.pm line 383.
(/opt/rt3/lib/RT.pm:222)
[Mon Apr 7 07:49:08 2003] [err]: RT::Ticket=HASH(0x97796d0) ->Create
couldn’t set EffectiveId: EffectiveId could not be set to 0.
(/opt/rt3/lib/RT/Ticket_Overlay.pm:490)
[Mon Apr 7 07:49:09 2003] [warning]: DBD::Pg::st execute failed: ERROR:
current transaction is aborted, queries ignored until end of transaction
block at /usr/lib/perl5/site_perl/5.8.0/DBIx/SearchBuilder/Handle.pm line
376.
(/opt/rt3/lib/RT.pm:222)
[Mon Apr 7 07:49:09 2003] [warning]: RT::Handle=HASH(0x93501d0) couldn’t
execute the query ‘INSERT INTO Principals (PrincipalType, Disabled,
ObjectId) VALUES (?, ?, ?)’ at
/usr/lib/perl5/site_perl/5.8.0/DBIx/SearchBuilder/Handle.pm line 383.
(/opt/rt3/lib/RT.pm:222)
[Mon Apr 7 07:49:09 2003] [warning]: DBD::Pg::st execute failed: ERROR:
current transaction is aborted, queries ignored until end of transaction
block at /usr/lib/perl5/site_perl/5.8.0/DBIx/SearchBuilder/Handle.pm line
376.
(/opt/rt3/lib/RT.pm:222)
[Mon Apr 7 07:49:09 2003] [warning]: RT::Handle=HASH(0x93501d0) couldn’t
execute the query ‘UPDATE Principals SET ObjectId=? WHERE id=? ’ at
/usr/lib/perl5/site_perl/5.8.0/DBIx/SearchBuilder/Handle.pm line 383.
(/opt/rt3/lib/RT.pm:222)
[Mon Apr 7 07:49:09 2003] [warning]: DBD::Pg::st execute failed: ERROR:
current transaction is aborted, queries ignored until end of transaction
block at /usr/lib/perl5/site_perl/5.8.0/DBIx/SearchBuilder/Handle.pm line
376.
(/opt/rt3/lib/RT.pm:222)
[Mon Apr 7 07:49:09 2003] [warning]: RT::Handle=HASH(0x93501d0) couldn’t
execute the query ‘INSERT INTO Groups (Type, Instance, Id, Domain, Name,
Description)
VALUES (?, ?, ?, ?, ?, ?)’ at
/usr/lib/perl5/site_perl/5.8.0/DBIx/SearchBuilder/Handle.pm line 383.
(/opt/rt3/lib/RT.pm:222)
[Mon Apr 7 07:49:09 2003] [error]: Couldn’t create a ticket group of type
’Requestor’ for ticket : Could not create group
(/opt/rt3/lib/RT/Ticket_Overlay.pm:1282)
[Mon Apr 7 07:49:09 2003] [crit]: Couldn’t create ticket groups for ticket
. aborting Ticket creation. (/opt/rt3/lib/RT/Ticket_Overlay.pm:495)
[Mon Apr 7 07:49:09 2003] [error]: WebRT: Ticket could not be created due
to an internal error () (/opt/rt3/share/html/Elements/Error:53)

I am guessing this is a problem with ACLs, possibly, because the only thing
that has changed is the contents of the database.

jaq@spacepants.org http://spacepants.org/jaq.gpg
rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

This one time, at band camp, Shmulik Gazit wrote:

From This:
Mon Apr 7 07:49:08 2003] [warning]: DBD::Pg::st execute failed: ERROR:
Cannot insert a duplicate key into unique index tickets_pkey at
/usr/lib/perl5/site_perl/5.8.0/DBIx/SearchBuilder/Handle.pm line 376.
(/opt/rt3/lib/RT.pm:222)

I can only assume that the counter for tickets didn’t get increased when the
old tickets got in, cause now it is trying to add an index number that
already exists. have a look at tickets_pkey.

rt3=# \d tickets_pkey
Index "public.tickets_pkey"
Column | Type
id | integer
primary key, btree, for table “public.tickets”

which is interesting, as Postgres has a serial type just for this sort of
thing.

Would making ‘id’ a serial type instead of an integer solve this problem, or
should I expect massive breakage?

jaq@spacepants.org http://spacepants.org/jaq.gpg