So I figured I'd give 4.0.0rc5 a try on a disposable RHEL6 virtual machine 
tonight with a dump of our 3.6.4 database. I have to say, the various upgrade 
scripts seemed to have worked wonders, and I actually have a functioning 
4.0.0rc5 running. It's reporting a lot of errors in syslog however, most of 
them to do with 'lifecycle', such as:

Feb 18 20:01:51 rt RT: DBD::mysql::st execute failed: Unknown column 
'lifecycle' in 'field list' at 
/usr/local/share/perl5/DBIx/SearchBuilder/Handle.pm line 509. 
(/usr/local/share/perl5/DBIx/SearchBuilder/Handle.pm:509)

The Queues table looks like:

mysql> describe Queues;
+-------------------+--------------+------+-----+---------+----------------+
| Field             | Type         | Null | Key | Default | Extra          |
+-------------------+--------------+------+-----+---------+----------------+
| id                | int(11)      | NO   | PRI | NULL    | auto_increment |
| Name              | varchar(200) | NO   | UNI |         |                |
| Description       | varchar(255) | YES  |     | NULL    |                |
| CorrespondAddress | varchar(120) | YES  |     | NULL    |                |
| CommentAddress    | varchar(120) | YES  |     | NULL    |                |
| InitialPriority   | int(11)      | NO   |     | 0       |                |
| FinalPriority     | int(11)      | NO   |     | 0       |                |
| DefaultDueIn      | int(11)      | NO   |     | 0       |                |
| Creator           | int(11)      | NO   |     | 0       |                |
| Created           | datetime     | YES  |     | NULL    |                |
| LastUpdatedBy     | int(11)      | NO   |     | 0       |                |
| LastUpdated       | datetime     | YES  |     | NULL    |                |
| Disabled          | smallint(6)  | NO   | MUL | 0       |                |
+-------------------+--------------+------+-----+---------+----------------+
13 rows in set (0.01 sec)


What'd I miss?

A second, more fatal problem that has me completely baffled presently is that 
after the initial cycle of:

- import old database
- upgrade to 3.7.87 using the script that allows you to specify start/end 
revisions
- generate the queries.sql file and then run those

I seem to be able to login once, but as soon as I explicitly logout, I can no 
longer login no matter how many mason/browser cache clearing loops I do.

A third problem is that I can't seem to get RT to run when I first start 
apache. I get:

        mkdir /opt/rt4/var/mason_data/obj/3452818388: Permission denied at 
/usr/local/share/perl5/HTML/Mason/Compiler/ToObject.pm line 107

Looks like the various directories were created as root:

[root@rt rt-4.0.0rc5]# ls -al /opt/rt4/var/mason_data/
total 16
drwxrwx---. 4 apache apache 4096 Feb 18 20:21 .
drwxr-xr-x. 5 root   root   4096 Feb 18 17:50 ..
drwxr-xr-x. 2 root   root   4096 Feb 18 19:41 cache
drwxr-xr-x. 2 root   root   4096 Feb 18 20:21 obj
[root@rt rt-4.0.0rc5]# 

If I delete the subdirs under mason_data while apache is still running, it 
recreates the obj directory with a user ID it can deal with:

[root@rt rt-4.0.0rc5]# ls -al /opt/rt4/var/mason_data/
total 12
drwxrwx---. 3 apache apache 4096 Feb 18 20:25 .
drwxr-xr-x. 5 root   root   4096 Feb 18 17:50 ..
drwxr-xr-x. 3 apache apache 4096 Feb 18 20:25 obj
[root@rt rt-4.0.0rc5]# 

and the site loads. Still can't login tho.

Feb 18 20:12:24 rt RT: FAILED LOGIN for root from ##.##.##.## 
(/opt/rt4/sbin/../lib/RT/Interface/Web.pm:605)
Feb 18 20:12:37 rt RT: FAILED LOGIN for root from 
##.##.##.##(/opt/rt4/sbin/../lib/RT/Interface/Web.pm:605)
Feb 18 20:13:08 rt RT: FAILED LOGIN for root from ##.##.##.## 
(/opt/rt4/sbin/../lib/RT/Interface/Web.pm:605)


Help?

-d

Reply via email to