[rt-users] Errors initializing database in RT 3.6.1

[Scott Courtney]

Greetings!

I searched the list archives and Google, but haven't seen any reports of this
problem by anyone else. I'm convinced that it's "pilot error" on my part, not
an RT bug, but I still need to ask for some help in solving it.

I'm doing a fresh install of RT 3.6.1 on a Debian Etch system, with MySQL 5.x
as the backing store. I have successfully installed RT 3.4.4 a number of
times, so I'm familiar with the basic processes, but this is my first exposure
to 3.6.x.

I've created a database "rt3" and an RT user ID of "rt" for that database. I
verified that user "rt" has all privileges on the "rt3" database and can login
with its assigned password from the MySQL command prompt.

Running "rt-setup-database-3.6 --action schema ......" works just fine, and
creates the schema with no errors.

However, running "rt-setup-database-3.6 --action insert --datafile \
/etc/request-tracker3.6/initialdata" fails with multiple error messages, to
wit:

Creating Superuser  ACL...[Wed Mar 28 13:05:22 2007] [err]: System error. right not granted. (/usr/share/request-tracker3.6/lib/RT/ACE_Overlay.pm:753)
done.
Creating groups...1.2.3.4.5.6.7.done.
Creating users...[Wed Mar 28 13:05:22 2007] [err]: Couldn't load  from the users database. (/usr/share/request-tracker3.6/lib/RT/CurrentUser.pm:145)
(Error: No permission to create users)0.[Wed Mar 28 13:05:22 2007] [err]: Couldn't load  from the users database. (/usr/share/request-tracker3.6/lib/RT/CurrentUser.pm:145)
(Error: No permission to create users)0.done.
Creating queues...[Wed Mar 28 13:05:22 2007] [err]: Couldn't load  from the users database. (/usr/share/request-tracker3.6/lib/RT/CurrentUser.pm:145)
(Error: No permission to create queues)0.[Wed Mar 28 13:05:22 2007] [err]: Couldn't load  from the users database. (/usr/share/request-tracker3.6/lib/RT/CurrentUser.pm:145)
(Error: No permission to create queues)0.done.
Creating ACL...[Wed Mar 28 13:05:22 2007] [crit]: 1 (/usr/share/request-tracker3.6/lib/RT/ACE_Overlay.pm:907)
[Wed Mar 28 13:05:22 2007] [crit]: Can't load a principal for id  (/usr/share/request-tracker3.6/lib/RT/ACE_Overlay.pm:908)
Principal  not found..[Wed Mar 28 13:05:22 2007] [crit]: 1 (/usr/share/request-tracker3.6/lib/RT/ACE_Overlay.pm:907)
[Wed Mar 28 13:05:22 2007] [crit]: Can't load a principal for id  (/usr/share/request-tracker3.6/lib/RT/ACE_Overlay.pm:908)
Principal  not found..done.

And so on. It just goes downhill from there, though I'm fairly convinced
that the first error is the indirect cause of most of the others and that
if I can fix it, I'll have fixed the rest.

I've looked at the Perl code a bit, but to be honest I'm a Java guy and not
all that literate in Perl.

Is this thing failing because of a MySQL command not executing, and if so, is
there a way for me to tell Perl to show me all the MySQL commands as it runs
them? I'm enough of a MySQL wiz that if I can see what's failing there, I can
fix it on my own.

Or am I doing something wrong with my rt-setup-database-3.6 command?

I looked at the ACL command, and that seems redundant to what I've already
granted from the MySQL command prompt.

Any help would be appreciated. This is on a new, not-yet-in-production server,
rather than an upgrade, so dropping and recreating the database is no problem
at all. (In fact, I've already done it a few times trying different things to
fix the problem.)

Thanks for any advice.

Kind regards,

Scott


-- 
------------------------------------------------------------------------------
Scott Courtney         | "I don't mind Microsoft making money. I mind them
scott at 4th.com          | having a bad operating system."    -- Linus Torvalds
http://4th.com/        | ("The Rebel Code," NY Times, 21 February 1999)
                       | PGP Public Key at http://4th.com/keys/scott.pubkey