Problems after Postgresql -> MySQL move

RT Users
1

I moved from Postgresql to MySQL yesterday, which appeared to have
worked. But this morning I noticed problems with users being
auto-created.

I’m using MySQL 4.1.7 with RT 3.0.12. I gave RT 3.2.2 a quick go, but it
didn’t help, so I’ve stuck with 3.0.12 so I don’t have other problems to
deal with at the same time.

This is what I’m getting in my webserver logs:

DBD::mysql::st execute failed: Unknown MySQL error at /usr/local/packages/perl-5.8.5/lib/perl5/site_perl/5.8.5/DBIx/SearchBuilder/Handle.pm line 481.
DBD::mysql::st fetchrow_hashref failed: fetch() without execute() at /usr/local/packages/perl-5.8.5/lib/perl5/site_perl/5.8.5/DBIx/SearchBuilder/Record.pm line 981.
DBD::mysql::st execute failed: Unknown MySQL error at /usr/local/packages/perl-5.8.5/lib/perl5/site_perl/5.8.5/DBIx/SearchBuilder/Handle.pm line 481.
DBD::mysql::st fetchrow_hashref failed: fetch() without execute() at /usr/local/packages/perl-5.8.5/lib/perl5/site_perl/5.8.5/DBIx/SearchBuilder/Record.pm line 981.

And in my RT logs:

[Fri Oct 29 13:04:08 2004] [debug]: Guessed encoding: ascii (/usr/local/packages/rt-3.0.12/lib/RT/I18N.pm:357)
[Fri Oct 29 13:04:08 2004] [debug]: Guessed encoding: ascii (/usr/local/packages/rt-3.0.12/lib/RT/I18N.pm:357)
[Fri Oct 29 13:04:08 2004] [debug]: Converting ‘ascii’ to ‘utf-8’ for text/plain - testing (/usr/local/packages/rt-3.0.12/lib/RT/I18N.pm:200)
[Fri Oct 29 13:04:08 2004] [err]: Couldn’t load from the users database. (/usr/local/packages/rt-3.0.12/lib/RT/CurrentUser.pm:111)
[Fri Oct 29 13:04:08 2004] [crit]: User creation failed in mailgateway: No permission to create users (/usr/local/packages/rt-3.0.12/lib/RT/Interface/Email.pm:224)
[Fri Oct 29 13:04:09 2004] [warning]: Couldn’t load user ‘tim.bishop@gmail.com’.giving up (/usr/local/packages/rt-3.0.12/lib/RT/Interface/Email.pm:239)
[Fri Oct 29 13:04:09 2004] [crit]: User ‘tim.bishop@gmail.com’ could not be loaded in the mail gateway (/usr/local/packages/rt-3.0.12/lib/RT/Interface/Email.pm:240)
[Fri Oct 29 13:04:09 2004] [error]: RT could not load a valid user, and RT’s configuration does not allow for the creation of a new user for this email (tim.bishop@gmail.com).

You might need to grant ‘Everyone’ the right ‘CreateTicket’ for the
queue cs-syshelp.

(/usr/local/packages/rt-3.0.12/lib/RT/Interface/Email.pm:552)
[Fri Oct 29 13:04:09 2004] [error]: RT could not load a valid user, and RT’s configuration does not allow for the creation of a new user for your email.

(/usr/local/packages/rt-3.0.12/lib/RT/Interface/Email.pm:565)

I definately have CreateTicket permissions set for Everyone - I even
took it off and put it back for good measure. This configuration also
used to work prior to the Postgresql to MySQL move.

I’m pretty stuck now… I’ve checked everything I can check such as the
database permissions, and I’m not sure what else there is I can do.

There’s no errors in the MySQL logs either, for what it’s worth,
despsite the messages above.

Cheers,
Tim.

Tim Bishop

PGP Key: 0x5AE7D984

2

I moved from Postgresql to MySQL yesterday, which appeared to have
worked. But this morning I noticed problems with users being
auto-created.

I’m using MySQL 4.1.7 with RT 3.0.12. I gave RT 3.2.2 a quick go, but it
didn’t help, so I’ve stuck with 3.0.12 so I don’t have other problems to
deal with at the same time.

Why don’t you back down to MySQL 4.0.x. 4.1.7 was just declared stable
by mysql inc and hasn’t had that much field testng.

3

I moved from Postgresql to MySQL yesterday, which appeared to have
worked. But this morning I noticed problems with users being
auto-created.

I’m using MySQL 4.1.7 with RT 3.0.12. I gave RT 3.2.2 a quick go, but it
didn’t help, so I’ve stuck with 3.0.12 so I don’t have other problems to
deal with at the same time.

Why don’t you back down to MySQL 4.0.x. 4.1.7 was just declared stable
by mysql inc and hasn’t had that much field testng.

This was a new installation, so 4.1.7 seemed like a sensible move.
However, I’ve spotted all sorts of oddities, so for now I’m just
attempting to undo stuff back to postgres.

Tim.

Tim Bishop

PGP Key: 0x5AE7D984