QueueSummaryByLifecycle warning

RT Users
1

Hi,

I am using rt-4.2.2 on FreeBSD 9.2-RELEASE-p3 amd64 in apache22 fastcgi
mode and mysql. Its history goes from early 4.0.X, and originally it
was configured to use mod_perl, but i switched to fastcgi because of
apache segmentation faults described here:

Now I see the following in log:
[10853] [Thu Feb 13 09:53:35 2014] [warning]: Use of uninitialized
value in lc
at /usr/local/share/rt42/html/Elements/QueueSummaryByLifecycle line
131. (/usr/local/share/rt42/html/Elements/QueueSummaryByLifecycle:131)
[10853] [Thu Feb 13 09:53:35 2014] [warning]: Use of uninitialized
value in lc
at /usr/local/share/rt42/html/Elements/QueueSummaryByLifecycle line 66.
(/usr/local/share/rt42/html/Elements/QueueSummaryByLifecycle:66) [1726]
[Thu Feb 13 09:53:50 2014] [warning]: Use of uninitialized value in lc
at /usr/local/share/rt42/html/Elements/QueueSummaryByLifecycle line
131. (/usr/local/share/rt42/html/Elements/QueueSummaryByLifecycle:131)
[1726] [Thu Feb 13 09:53:50 2014] [warning]: Use of uninitialized value
in lc at /usr/local/share/rt42/html/Elements/QueueSummaryByLifecycle
line 66.
(/usr/local/share/rt42/html/Elements/QueueSummaryByLifecycle:66)
[10853] [Thu Feb 13 09:53:52 2014] [warning]: Use of uninitialized
value in lc
at /usr/local/share/rt42/html/Elements/QueueSummaryByLifecycle line
131. (/usr/local/share/rt42/html/Elements/QueueSummaryByLifecycle:131)
[10853] [Thu Feb 13 09:53:52 2014] [warning]: Use of uninitialized
value in lc
at /usr/local/share/rt42/html/Elements/QueueSummaryByLifecycle line 66.
(/usr/local/share/rt42/html/Elements/QueueSummaryByLifecycle:66)

I haven’t encountered any problem in functionality. Should I be worried
about this?
Marko Cupać

2

[10853] [Thu Feb 13 09:53:35 2014] [warning]: Use of uninitialized
value in lc
at /usr/local/share/rt42/html/Elements/QueueSummaryByLifecycle line
131. (/usr/local/share/rt42/html/Elements/QueueSummaryByLifecycle:131)
[10853] [Thu Feb 13 09:53:35 2014] [warning]: Use of uninitialized
value in lc
at /usr/local/share/rt42/html/Elements/QueueSummaryByLifecycle line 66.

I haven’t encountered any problem in functionality. Should I be worried
about this?

This implies your database doesn’t have correct Lifecycles on Queues.

show:

select Name, Lifecycle from Queues;

-kevin

3

This implies your database doesn’t have correct Lifecycles on Queues.

show:

select Name, Lifecycle from Queues;

mysql> select Name, Lifecycle from Queues;
| Name | Lifecycle |
| General | NULL |
| ___Approvals | approvals |
| Quality Dept. | default |
3 rows in set (0.00 sec)

Quality Dept. was just a test, actually for now we use only General
Queue.

Marko Cupać

4

mysql> select Name, Lifecycle from Queues;
±----------------------±----------+
| Name | Lifecycle |
±----------------------±----------+
| General | NULL |
| ___Approvals | approvals |
| Quality Dept. | default |
±----------------------±----------+
3 rows in set (0.00 sec)

This points to having skipped the 4.0.9 upgrade step. You should check
your upgrade history in Admin → Tools → System Configuration.

  • Alex
5

This points to having skipped the 4.0.9 upgrade step. You should
check your upgrade history in Admin → Tools → System Configuration.

Sorry for late reply, I was offline for weekend.

System configuration shows history starts from 4.0.19. Database was
exported on another server where rt was at 4.0.19. After that, new
server was installed with 4.2.2, database was imported, and then
upgraded to current version.

Anyway, how can this be fixed? Can I just re-run database upgrade from
earlier version? If so, from which? I am afraid at this moment it can’t
be said with certainty what was the original rt version, and which
database upgrades were skipped.
Marko Cupać

6

I re-run database upgrade, this time starting from 4.0.8, it went fine
until 4.1.1 where it failed complaining thatTable 'ObjectScrips’
already exists. As I know it was created in earlier upgrade I did not
worry.

My Queues table looks as follows now:
mysql> select Name, Lifecycle from Queues;
| Name | Lifecycle |
| General | default |
| ___Approvals | approvals |
| AvalaAda Laboratorija | default |

… and there are no more warnings in log.

Hope I did not spoil something else.
Marko Cupać

7

I re-run database upgrade, this time starting from 4.0.8, it went fine
until 4.1.1 where it failed complaining thatTable ‘ObjectScrips’
already exists. As I know it was created in earlier upgrade I did not
worry.

If you actually reran all of the upgrade scripts (instead of telling
make upgrade-database to run 4.0.8 → 4.0.19) then I suspect something
else will be wrong down the road.

-kevin