Initial report on rt 2.1.70 on debian

with some help from Jesse, I finally got rt running under debian. Most
of the dependencies are packaged, I didn’t note the packages names
though, so you get to figure it out. I did have to build and install a
couple on my own. here are the commands I used:

dh-make-perl --build --install --cpan Locale::Maketext::Lexicon
dh-make-perl --build --install --cpan Locale::Maketext::Fuzzy
dh-make-perl --build --install --cpan Text::Quoted
dh-make-perl --build --install --cpan Regexp::Common

and while mailtools is built in debian, the version is old. (I’m sure
it will get updated, I was just impatient) I built a newer one:

wget http://search.cpan.org/CPAN/authors/id/M/MA/MARKOV/MailTools-1.58.tar.gz
tar xzf MailTools-1.58.tar.gz && cd MailTools-1.58
dh-make-perl --build --install .

a couple of minor notes about the install:

the 2.1.70 dependency check doesn’t check for Regexp::Common, so
make sure you have it. (yes best practical knows)

the 2.1.70 dependency check checks incorrectly for Apache::DBI, it’s
apt to say you don’t have it, when you probably do. This will
probably be fixed when the next version of Apache::DBI is rolled.
(yes best practical knows)

And now that it’s up and running, I’ve noticed a couple oddities…

fastcgi (with apache1, not apache2) is significantly slower than
mod-perl. This is quite a change from rt2.

If I create a user, seph, and give him full permissions; then create
a new queue; the new ticket dropdown doesn’t show that queue until I
logout and log back in. I did not do as good a job debugging this as
I ought.

seph

If I create a user, seph, and give him full permissions; then create
a new queue; the new ticket dropdown doesn’t show that queue until I
logout and log back in. I did not do as good a job debugging this as
I ought.

Wait one minute (literally, yes. one minute), then reload again.

There’s a cache for ACL queries. Currently it times out in 60 sec.

plasma

��Ǭ��y���Y�h�x�H,��o�|�����ݬ�~
http://edm-prg.epaper.com.tw/click.php?ad_code=1895
PC home Online �����a�x�G�|���Ĥ@�A�x�W�̤j���J�f����

It would be nice if there were some easy way to enable and disable the
caching of various objects. I’ve bumped into the cache several times.
Typically I make a change, then login as the user to make sure the acl
change I made does in-fact do what I thought it did. It really sucks to
be forced to wait for like 60seconds.

Rather, it would suck if I did have some /knowledge/ about ::Cacheable
and knew how to turn it off. Heh.

-Matt

If I create a user, seph, and give him full permissions; then create
a new queue; the new ticket dropdown doesn’t show that queue until I
logout and log back in. I did not do as good a job debugging this as
I ought.

Wait one minute (literally, yes. one minute), then reload again.
There’s a cache for ACL queries. Currently it times out in 60 sec.

No, you’re wrong. The queue listing is cached along with your session
for performance reasons. If you create or rename queues, they won’t show
up in that listing until you log out and back in.

plasma

�|� Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.

At 11:56 PM 11/02/2003 -0800, seph wrote:

with some help from Jesse, I finally got rt running under debian. Most
of the dependencies are packaged, I didn’t note the packages names
though, so you get to figure it out. I did have to build and install a
couple on my own. here are the commands I used:

dh-make-perl --build --install --cpan Locale::Maketext::Lexicon
dh-make-perl --build --install --cpan Locale::Maketext::Fuzzy
dh-make-perl --build --install --cpan Text::Quoted
dh-make-perl --build --install --cpan Regexp::Common

We just did the same tango on Monday to get rt-2.1.70 going. This seems to
work, although I don’t know these versions interact with ‘proper’ debian
packages that may appear at a later date (with the correct dependencies and
so forth).

a couple of minor notes about the install:

the 2.1.70 dependency check doesn’t check for Regexp::Common, so
make sure you have it. (yes best practical knows)

the 2.1.70 dependency check checks incorrectly for Apache::DBI, it’s
apt to say you don’t have it, when you probably do. This will
probably be fixed when the next version of Apache::DBI is rolled.
(yes best practical knows)

We noticed this as well. We uninstalled the official Debian package, and
installed it again via dh-make-perl/CPAN. Then the RT3 dependency checker
found it no problem. I don’t know if it’s a problem with the debian
package, or with Apache::DBI itself. Good to know that Best Practical knows. :slight_smile:

And now that it’s up and running, I’ve noticed a couple oddities…

fastcgi (with apache1, not apache2) is significantly slower than
mod-perl. This is quite a change from rt2.

On our box (mod_perl1/PostgreSQL 7.2.1 backend) RT3 is also a lot slower
than RT2 was. The new web front-end is quite slick; I’m very impressed so
far. A few notes:

  1. The memory footprint is quite large. Our memory footprint is now:

USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
www-data 20279 0.1 11.8 91992 14888 ? S Feb12 1:24 /usr/sbin/apache
www-data 20280 0.1 9.5 90532 12048 ? S Feb12 1:07 /usr/sbin/apache
www-data 20282 0.1 10.0 91692 12632 ? S Feb12 1:24 /usr/sbin/apache
www-data 20284 0.1 9.7 90512 12280 ? S Feb12 1:03 /usr/sbin/apache
www-data 20287 0.1 9.7 90468 12344 ? S Feb12 1:04 /usr/sbin/apache

Is this normal? This machine only has 128MB of RAM, so maybe that’s why it
seems so much slower. Granted, a lot of the VSZ is shared memory, but the
RSS is still quite large.

  1. The $LogoURL configuration parameter isn’t used by html/Elements/Header.
    I’m not sure if this is intentional or not. :slight_smile:

  2. How does Approval work? A quick search of the archives yields a post
    back in October talking about the use of scrips to configure it, but it’s
    not self-evident from the interface. Is this a UI element that’s not
    actively used yet?

Cheers,

  • Andrew
    PS. Jess: Thanks for resolving the language issues. :slight_smile:

Is this normal? This machine only has 128MB of RAM, so maybe that’s why it
seems so much slower. Granted, a lot of the VSZ is shared memory, but the
RSS is still quite large.

That’s really not a whole lot of RAM. I’d expect RT to be slow as a dog
on a box like that. Pop up the ram a bit and you’ll be mcuh happier.

  1. The $LogoURL configuration parameter isn’t used by html/Elements/Header.
    I’m not sure if this is intentional or not. :slight_smile:

Not really intentional, but I should probably pull the LogoURL parameter
from the config file.

  1. How does Approval work? A quick search of the archives yields a post
    back in October talking about the use of scrips to configure it, but it’s
    not self-evident from the interface. Is this a UI element that’s not
    actively used yet?

I’ve got an appointment with the tech writer this afternoon :wink:

Cheers,

  • Andrew
    PS. Jess: Thanks for resolving the language issues. :slight_smile:

rt-devel mailing list
rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel

�|� Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.

dh-make-perl --build --install --cpan Locale::Maketext::Lexicon
dh-make-perl --build --install --cpan Locale::Maketext::Fuzzy
dh-make-perl --build --install --cpan Text::Quoted
dh-make-perl --build --install --cpan Regexp::Common

We just did the same tango on Monday to get rt-2.1.70 going. This
seems to work, although I don’t know these versions interact with
‘proper’ debian packages that may appear at a later date (with the
correct dependencies and so forth).

they should interact fine with debian. dh-make-perl makes makes
packages with the same name as their debian counterparts are likely to
be. when one finally shows up in debian, apt should snarf it if the
version’s newer.

seph

At 11:49 AM 13/02/2003 -0500, Jesse Vincent wrote:

Is this normal? This machine only has 128MB of RAM, so maybe that’s why it
seems so much slower. Granted, a lot of the VSZ is shared memory, but the
RSS is still quite large.

That’s really not a whole lot of RAM. I’d expect RT to be slow as a dog
on a box like that. Pop up the ram a bit and you’ll be mcuh happier.

The same box seemed quick enough with RT2, although I agree it’s woefully
underpowered in this day and age. What sort of system will be recommended
for RT3 final?

  • Andrew

The same box seemed quick enough with RT2, although I agree it’s woefully
underpowered in this day and age. What sort of system will be recommended
for RT3 final?

It seems reasonably zippy for me on an 800mhz P3 with a gig of ram. (The
box also does a bunch of other things)

  • Andrew

�|� Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.