I have finally installed FreeBSD 4.10 onto my test machine.
I went to the RT Wiki page, and followed the instructions on how to
install RT:
cd /usr/ports/www/rt3
sudo make install
The result is : rt3-3.0.9 This program only support perl 5.6.1 or above.
perl -v reveals that I have: 5.005_03 built for i386-freebsd.
I’ve searched through some of the The RT-Users Archives, but was
wondering if anybody would be willing to share what I need to do to get
Request Tracker installed with FreeBSD 4.10. That is:
What packages should I select during the FreeBSD install which are
relevant for Request Tracker
What should I do after installing FreeBSD to make Request Tracker
install
OR direct me to the archive which has the information.
Thanks again,
Ron
Scotiabank Information Commmons, University of Toronto
I have added some Global Custom Fields, however I can not get the
search at the top of RT to search in these fields.
I have checked the Wiki and have seen a couple items pertaining to
this, but one doesnt seem relevant to this version of RT and the other
pertains to Custom Queue Fields making it seem as Globals should just
work.
Thank you for the information. I was able to install perl5.8.2_5, but
the orginal perl5.005_03 is still taking precedence. Besides modifying
the path, what else should I do?
Thank you for the information. I was able to install perl5.8.2_5, but
the orginal perl5.005_03 is still taking precedence. Besides modifying
the path, what else should I do?
Thanks,
Ron
Someone failed to read the pkg-message… assuming you installed from the
ports, be sure to take a read of /usr/ports/lang/perl5.8/pkg-message
Regards,
Jason Wilson
Systems Engineer
Nobilis Software
Jason Taylor wrote:
As root:
cd /usr/ports/lang/perl5.8
make install clean
use.perl port
You may also want to try the rt32 port vs. the rt3 port.
Ron Tyro wrote:
Hi again.
Dell GX260
FreeBSD 4.10
I have finally installed FreeBSD 4.10 onto my test machine.
I went to the RT Wiki page, and followed the instructions on how to
install RT:
cd /usr/ports/www/rt3
sudo make install
The result is : rt3-3.0.9 This program only support perl 5.6.1 or
above.
: Thank you for the information. I was able to install perl5.8.2_5, but
: the orginal perl5.005_03 is still taking precedence. Besides modifying
: the path, what else should I do?
:
: Thanks,
: Ron
:
: Jason Taylor wrote:
: >
: > As root:
: >
: > cd /usr/ports/lang/perl5.8
: > make install clean
: > use.perl port
: >
: > You may also want to try the rt32 port vs. the rt3 port.
: >
: > Ron Tyro wrote:
: >
: > >Hi again.
: > >
: > >Dell GX260
: > >FreeBSD 4.10
: > >
: > >I have finally installed FreeBSD 4.10 onto my test machine.
: > >I went to the RT Wiki page, and followed the instructions on how to
: > >install RT:
: > >
: > >cd /usr/ports/www/rt3
: > >sudo make install
: > >
: > >The result is : rt3-3.0.9 This program only support perl 5.6.1 or
above.
: > >
: > >perl -v reveals that I have: 5.005_03 built for i386-freebsd.
: > >
: > >I’ve searched through some of the The RT-Users Archives, but was
: > >wondering if anybody would be willing to share what I need to do to get
: > >Request Tracker installed with FreeBSD 4.10. That is:
: > >
: > >1. What packages should I select during the FreeBSD install which are
: > >relevant for Request Tracker
: > >2. What should I do after installing FreeBSD to make Request Tracker
: > >install
: > >
: > >OR direct me to the archive which has the information.
: > >
: > >
: > >Thanks again,
: > >
: > >Ron
: > >
: > >
I followed the instructions on the rt-wiki page for FreeBSD, and
everything seemed to install okay.
When I run “make initialize-database”, I get “make: don’t know how to
make initialize-database. Stop”. I then noticed that only the mysql
client was installed, and nothing else.
For the FreeBSD installation, do I need to install all the required
components first or will the install do this for me?
Thanks,
Ron
Scotiabank Information Commmons, University of Toronto
: Hi.
:
: I followed the instructions on the rt-wiki page for FreeBSD, and
: everything seemed to install okay.
: When I run “make initialize-database”, I get “make: don’t know how to
: make initialize-database. Stop”. I then noticed that only the mysql
: client was installed, and nothing else.
:
: For the FreeBSD installation, do I need to install all the required
: components first or will the install do this for me?
:
: Thanks,
: Ron
:
: Scotiabank Information Commmons, University of Toronto
:
Ron,
For some reason RT from FreeBSD ports (4.10 Release) does not have
mysql-server as a required dependancy. You will need to add the appropriate
mysql-server port also, use the matching version of the mysql-client you
have.
Autrijus Tang is listed as the maintainer for this FreeBSD port and
sometimes posts to this list, perhaps he should be notified.
----- Original Message -----
From: “Ron Tyro” ron.tyro@utoronto.ca
Sent: Wednesday, November 24, 2004 9:05 AM
Subject: [rt-users] FreedBSD 4.10 and RT 3-3.0.9
: Hi.
:
: I followed the instructions on the rt-wiki page for FreeBSD, and
: everything seemed to install okay.
: When I run “make initialize-database”, I get “make: don’t know how to
: make initialize-database. Stop”. I then noticed that only the mysql
: client was installed, and nothing else.
:
: For the FreeBSD installation, do I need to install all the required
: components first or will the install do this for me?
:
: Thanks,
: Ron
:
: Scotiabank Information Commmons, University of Toronto
:
Ron,
For some reason RT from FreeBSD ports (4.10 Release) does not have
mysql-server as a required dependancy. You will need to add the appropriate
mysql-server port also, use the matching version of the mysql-client you
have.
The reason is (probably) that it’s not set in stone that the
mysql-server and RT have to be on the same host.
It’s the same with a lot of other apps in the ports-tree (e.g. PHP).
Autrijus Tang is listed as the maintainer for this FreeBSD port and
sometimes posts to this list, perhaps he should be notified.
I don’t think it is an error. It’s a design-decision
I was able to install the mysql server and the make initialize-database
worked. I am running RT and mysql on the same host. That was something
I was interested in as well: can RT talk to a remote database.
Now I need to configure httpd.conf, but I’m not sure what the defaults
are for RT of FreeBSD. Did it use mod_perl or fastcgi? Does anybody
know? Does the RT install create a log file which I can view?
Thanks,
Ron
Scotiabank Information Commmons, University of Toronto
I was able to install the mysql server and the make initialize-database
worked. I am running RT and mysql on the same host. That was something
I was interested in as well: can RT talk to a remote database.
Now I need to configure httpd.conf, but I’m not sure what the defaults
are for RT of FreeBSD. Did it use mod_perl or fastcgi? Does anybody
know? Does the RT install create a log file which I can view?
No, but you can run “script” prior install
pkg_info|grep mod
pkg_info|grep cgi
should also give a definitive answer.
But I think it is mod_perl by default - information on how to configure
apache is in the wiki. wiki.bestpractical.com
I did the default install of RT on FreeBSD. I ran the testdeps and it
came back with everything is up-to-date. I modified the httpd.conf file
as per instructions.
I’m getting errors in my httpd-error.log:
"Can’t locate RT/mason.pm in …all the paths. "
I did a locate and find on mason.pm, but it does not exist. The next
error in the httpd-error.log file is:
“Undefined subroutine &RT::mason::handler called”. Probably because the
mason.pm does not exist.
I noticed a thread started on this problem, but not sure if it has been
resolved, and another on Apache2 which I don’t think applies to my
install since I’m not using Apache2.
Any suggestions are/would be appreciated.
Thank you,
Ron
Scotiabank Information Commmons, University of Toronto
I’m currently running RT 3.4.1, and it’s working very well for me, except
that when I try to search on a custom field, it always returns 0 results
even when it should be returning results. Is this an issue that would be
resolved by upgrading to 3.4.4? Is there something to check that I may have
mis-configured?
I’m currently running RT 3.4.1, and it’s working very well for me, except
that when I try to search on a custom field, it always returns 0 results
even when it should be returning results. Is this an issue that would be
resolved by upgrading to 3.4.4? Is there something to check that I may
have mis-configured?
I’m currently running RT 3.4.1, and it’s working very well for me, except
that when I try to search on a custom field, it always returns 0 results
even when it should be returning results. Is this an issue that would be
resolved by upgrading to 3.4.4? Is there something to check that I may have
mis-configured?
Thanks for any help!
-cv
Turn on the option in MySQL where it logs all the SQL it runs
and then figure out what query was really generated.
SELECT DISTINCT main.* FROM ((Tickets main LEFT JOIN ObjectCustomFieldValues
ObjectCustomFieldValues_1 ON ((Obje
ctCustomFieldValues_1.ObjectType = ‘RT::Ticket’)) AND(
(ObjectCustomFieldValues_1.Disabled = ‘0’)) AND(
ObjectCustomFieldValues_1.ObjectId = main.id http://main.id)
) JOIN CustomFields CustomFields_2 ON ( CustomFields_2.id =
ObjectCustomFieldValues_1.CustomField) AND( (CustomFields_2.Name =
‘Product’))) WHERE
((main.EffectiveId = main.id http://main.id)) AND ((main.Status !=
‘deleted’)) AND ((main.Type = ‘ticket’)) AND
((ObjectCustomFieldValues_1.Content LIKE ‘%IPM%’)AND
( (main.Status = ‘new’)OR(main.Status = ‘open’) ) ) ORDER BY
main.idhttp://main.idASC LIMIT 50
Any ideas?On 10/8/05, Todd Chapman todd@chaka.net wrote:
On Fri, Oct 07, 2005 at 09:54:08AM -0700, Chris Valdez wrote:
Hi folks,
I’m currently running RT 3.4.1, and it’s working very well for me,
except
that when I try to search on a custom field, it always returns 0 results
even when it should be returning results. Is this an issue that would be
resolved by upgrading to 3.4.4? Is there something to check that I may
have
mis-configured?
Thanks for any help!
-cv
Turn on the option in MySQL where it logs all the SQL it runs
and then figure out what query was really generated.
