Hello,
I’m have installed Apache/2.0.58 (Unix) mod_ssl/2.0.58 OpenSSL/0.9.8a
PHP/4.4.2 mod_fastcgi/2.4.2 mod_perl/2.0.2 Perl/v5.8.7 with Mysql on
a solaris 10 server in an effort to try to get RT3 running. However
when i try to access the RT3 site it eventually fails with a browser
error
“500 Internal Server Error” When i look at the error log for apache2 i
see the below. Does anyone know what I may be missing or know what
the below errors mean and how to fix it ?
[Wed May 31 18:53:13 2006] [warn] FastCGI: server
“/usr/local/rt3/bin/mason_handler.fcgi” restarted (pid 2721)
Can’t locate Locale/Maketext/Lexicon.pm in @INC (@INC contains:
/usr/local/rt3/local/lib /usr/local/rt3/lib
/usr/local/lib/perl5/5.8.7/i86pc-solaris /usr/local/lib/perl5/5.8.7
/usr/local/lib/perl5/site_perl/5.8.7/i86pc-solaris
/usr/local/lib/perl5/site_perl/5.8.7 /usr/local/lib/perl5/site_perl)
at /usr/local/rt3/lib/RT/I18N.pm line 34.
BEGIN failed–compilation aborted at /usr/local/rt3/lib/RT/I18N.pm
line 34.
Compilation failed in require at /usr/local/rt3/lib/RT.pm line 29.
BEGIN failed–compilation aborted at /usr/local/rt3/lib/RT.pm line 29.
Compilation failed in require at /usr/local/rt3/bin/webmux.pl line 42.
BEGIN failed–compilation aborted at /usr/local/rt3/bin/webmux.pl line 42.
Compilation failed in require at /dev/fd/3 line 28.
[Wed May 31 18:53:13 2006] [warn] FastCGI: server
“/usr/local/rt3/bin/mason_handler.fcgi” (pid 2721) terminated by
calling exit with status ‘2’
[Wed May 31 18:53:13 2006] [warn] FastCGI: server
“/usr/local/rt3/bin/mason_handler.fcgi” has failed to remain running
for 30 seconds given 3 attempts, its restart interval has been backed
off to 600 seconds
thank you in advance
Brent Bailey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
Hello,
I’m have installed Apache/2.0.58 (Unix) mod_ssl/2.0.58 OpenSSL/0.9.8a
PHP/4.4.2 mod_fastcgi/2.4.2 mod_perl/2.0.2 Perl/v5.8.7 with Mysql on
a solaris 10 server in an effort to try to get RT3 running. However
when i try to access the RT3 site it eventually fails with a browser
error
“500 Internal Server Error” When i look at the error log for apache2 i
see the below. Does anyone know what I may be missing or know what
the below errors mean and how to fix it ?
[Wed May 31 18:53:13 2006] [warn] FastCGI: server
“/usr/local/rt3/bin/mason_handler.fcgi” restarted (pid 2721)
Can’t locate Locale/Maketext/Lexicon.pm in @INC
It looks like you haven’t installed Locale::Maketext::Lexicon. Try running:
make fixdeps
Michael
Michael S. Liebman m-liebman@northwestern.edu http://msl521.freeshell.org/
“I have vision and the rest of the world wears bifocals.”
-Paul Newman in “Butch Cassidy & the Sundance Kid”
[In the future, please reply to the list so everyone can benefit.]On 6/12/06, Brent bbailey66@metrocast.net wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
From what directory do i run “make fixdeps”. Also is that a perl
thing that could be added via CPAN ?
Run it from your RT install directory. You could install the module from
CPAN by hand, but you should make sure you have all of the modules correctly
installed. Running make fixdeps will do that for you. See the README for
more information.
Michael
Michael S. Liebman m-liebman@northwestern.edu http://msl521.freeshell.org/
“I have vision and the rest of the world wears bifocals.”
-Paul Newman in “Butch Cassidy & the Sundance Kid”
We’re working on a transition from a system running RT 3.0.12 to 3.4.5 and
I’ve run into a problem using the RT CLI - which is important to me
because I’ve built a bunch of automation on top of the RT CLI commands.
As far as I’ve tested, all the existing CLI functionality exists … EXCEPT for adding comments. Any attempt add a comment with the CLI gets
this terse response:
Ticket comment does not exist.
Even trying something as simple as this:
rt comment -m test 144149
Ticket comment does not exist.
Is this a known problem? Is there a fix/workaround? Thanks.
joel anderson * joela@umn.edu * 612-625-7389
→ pager: 612-648-6823
Be a part of the Next Age of Exploration http://www.planetary.org/
We’re working on a transition from a system running RT 3.0.12 to 3.4.5 and
I’ve run into a problem using the RT CLI - which is important to me
because I’ve built a bunch of automation on top of the RT CLI commands.
As far as I’ve tested, all the existing CLI functionality exists … EXCEPT for adding comments. Any attempt add a comment with the CLI gets
this terse response:
I’m getting resistance to a pre-release; is there any way to resolve the
issue in 3.4.5?> On Mon, Jun 12, 2006 at 01:58:28PM -0500, Joel Peter Anderson wrote:
We’re working on a transition from a system running RT 3.0.12 to 3.4.5 and
I’ve run into a problem using the RT CLI - which is important to me
because I’ve built a bunch of automation on top of the RT CLI commands.
As far as I’ve tested, all the existing CLI functionality exists … EXCEPT for adding comments. Any attempt add a comment with the CLI gets
this terse response:
This is fixed in RT 3.60pre3.
Ticket comment does not exist.
Even trying something as simple as this:
rt comment -m test 144149
Ticket comment does not exist.
Is this a known problem? Is there a fix/workaround? Thanks.
joel anderson * joela@umn.edu * 612-625-7389
→ pager: 612-648-6823
Be a part of the Next Age of Exploration http://www.planetary.org/
As noted - we cannot move to the pre-release; how soon is the official
3.6? And - again, does anyone have a work-around (other than RT
3.60pre3.)
I’m getting resistance to a pre-release; is there any way to resolve the
issue in 3.4.5?
We’re working on a transition from a system running RT 3.0.12 to 3.4.5 and
I’ve run into a problem using the RT CLI - which is important to me
because I’ve built a bunch of automation on top of the RT CLI commands.
As far as I’ve tested, all the existing CLI functionality exists … EXCEPT for adding comments. Any attempt add a comment with the CLI gets
this terse response:
This is fixed in RT 3.60pre3.
Ticket comment does not exist.
Even trying something as simple as this:
rt comment -m test 144149
Ticket comment does not exist.
joel anderson * joela@umn.edu * 612-625-7389
→ pager: 612-648-6823
Be a part of the Next Age of Exploration http://www.planetary.org/
Yes please. When do you anticipate 3.6 going stable. I’ve been working
on a project for the last two months trying to get an upgrade in place
and just found out that they don’t want me using 3.6.0rc3 because it is
’beta’. As much work as I’ve put into this I would love to continue
with this version before I have to revert to 3.4.5.
Mathew Snyder
Systems Administrator
Network+
ServerVault TechOps
Yes please. When do you anticipate 3.6 going stable. I’ve been working
on a project for the last two months trying to get an upgrade in place
and just found out that they don’t want me using 3.6.0rc3 because it is
‘beta’. As much work as I’ve put into this I would love to continue
with this version before I have to revert to 3.4.5.
Mathew Snyder
Systems Administrator
Network+
ServerVault TechOps
Joel Peter Anderson wrote:
As noted - we cannot move to the pre-release; how soon is the official
3.6? And - again, does anyone have a work-around (other than RT
3.60pre3.)
I’m getting resistance to a pre-release; is there any way to resolve the
issue in 3.4.5?
On Mon, Jun 12, 2006 at 01:58:28PM -0500, Joel Peter Anderson wrote:
We’re working on a transition from a system running RT 3.0.12 to 3.4.5 and
I’ve run into a problem using the RT CLI - which is important to me
because I’ve built a bunch of automation on top of the RT CLI commands.
As far as I’ve tested, all the existing CLI functionality exists … EXCEPT for adding comments. Any attempt add a comment with the CLI gets
this terse response:
This is fixed in RT 3.60pre3.
Ticket comment does not exist.
Even trying something as simple as this:
rt comment -m test 144149
Ticket comment does not exist.
joel anderson * joela@umn.edu * 612-625-7389
→ pager: 612-648-6823
Be a part of the Next Age of Exploration http://www.planetary.org/
You could backport the cli changes…or hong on a couple days. I’m giving a talk at the nordic perl workshop that might help assuage those concerns ;)------- Original message -------
From: Joel Peter Anderson joela@umn.edu
Sent: 12.6.'06, 14:45
I’m getting resistance to a pre-release; is there any way to resolve the
issue in 3.4.5?
On Mon, Jun 12, 2006 at 01:58:28PM -0500, Joel Peter Anderson wrote:
We’re working on a transition from a system running RT 3.0.12 to 3.4.5 and
I’ve run into a problem using the RT CLI - which is important to me
because I’ve built a bunch of automation on top of the RT CLI commands.
As far as I’ve tested, all the existing CLI functionality exists … EXCEPT for adding comments. Any attempt add a comment with the CLI gets
this terse response:
This is fixed in RT 3.60pre3.
Ticket comment does not exist.
Even trying something as simple as this:
rt comment -m test 144149
Ticket comment does not exist.
Is this a known problem? Is there a fix/workaround? Thanks.
joel anderson * joela@umn.edu * 612-625-7389
→ pager: 612-648-6823
Be a part of the Next Age of Exploration http://www.planetary.org/
Yes please. When do you anticipate 3.6 going stable. I’ve been
working on a project for the last two months trying to get an upgrade
in place and just found out that they don’t want me using 3.6.0rc3
because it is ‘beta’. As much work as I’ve put into this I would love
to continue with this version before I have to revert to 3.4.5.
Mathew Snyder
Systems Administrator
Network+
ServerVault TechOps
Joel Peter Anderson wrote:
As noted - we cannot move to the pre-release; how soon is the
official 3.6? And - again, does anyone have a work-around (other
than RT
3.60pre3.)
I’m getting resistance to a pre-release; is there any way to
resolve the issue in 3.4.5?
We’re working on a transition from a system running RT 3.0.12 to
3.4.5 and I’ve run into a problem using the RT CLI - which is
important to me because I’ve built a bunch of automation on top of
the RT CLI commands.
As far as I’ve tested, all the existing CLI functionality exists … EXCEPT for adding comments. Any attempt add a comment with the
CLI gets this terse response:
This is fixed in RT 3.60pre3.
Ticket comment does not exist.
Even trying something as simple as this:
rt comment -m test 144149
Ticket comment does not exist.
joel anderson * joela@umn.edu * 612-625-7389
→ pager: 612-648-6823 Be a part of the Next
Age of Exploration http://www.planetary.org/
Yes please. When do you anticipate 3.6 going stable. I’ve been working
on a project for the last two months trying to get an upgrade in place
and just found out that they don’t want me using 3.6.0rc3 because it is
‘beta’. As much work as I’ve put into this I would love to continue
with this version before I have to revert to 3.4.5.
Mathew Snyder
Systems Administrator
Network+
ServerVault TechOps
Joel Peter Anderson wrote:
As noted - we cannot move to the pre-release; how soon is the official
3.6? And - again, does anyone have a work-around (other than RT
3.60pre3.)
I’m getting resistance to a pre-release; is there any way to
resolve the
issue in 3.4.5?
On Mon, Jun 12, 2006 at 01:58:28PM -0500, Joel Peter Anderson wrote:
We’re working on a transition from a system running RT 3.0.12 to
3.4.5 and
I’ve run into a problem using the RT CLI - which is important to me
because I’ve built a bunch of automation on top of the RT CLI
commands.
As far as I’ve tested, all the existing CLI functionality exists … EXCEPT for adding comments. Any attempt add a comment with the
CLI gets
this terse response:
This is fixed in RT 3.60pre3.
Ticket comment does not exist.
Even trying something as simple as this:
rt comment -m test 144149
Ticket comment does not exist.
joel anderson * joela@umn.edu * 612-625-7389
→ pager: 612-648-6823
Be a part of the Next Age of Exploration http://www.planetary.org/
i
