Enabling extensions in RT4.2.8?

Hi all,
I can’t seem to find the instructions for enabling extensions in 4.2.8.
I’ve found some for 3.x, but I thought I read somewhere that the syntax is
a bit different for 4.x. I know I add something to 50-debconf, but I’m not
sure exactly what. I have rt::extension::PriorityAsString unpacked
and–hopefully–installed correctly, I just need to “turn it on”. The
instructions also tell me to clear a “mason/obj” item, but I can’t find
that anywhere. Thanks.

Alex Hall
Automatic Distributors, IT department
ahall@autodist.com

Hi Alex,On Thu, Sep 22, 2016 at 12:50 PM, Alex Hall ahall@autodist.com wrote:

Hi all,
I can’t seem to find the instructions for enabling extensions in 4.2.8. I’ve
found some for 3.x, but I thought I read somewhere that the syntax is a bit
different for 4.x. I know I add something to 50-debconf, but I’m not sure
exactly what.

You can add the configuration “code” to any file in
/etc/request-tracker4/RT_SiteConfig.d.

The configuration “code” is:

Plugin(‘RT::Extension::PriorityAsString’);

So you might have a file like:

/etc/request-tracker4/RT_SiteConfig.d/70-priority-as-string

with the aforementioned Plugin line.

Then run your:

update-rt-siteconfig-4

Then clean your mason cache:

sudo find /var/cache/request-tracker4/mason_data/obj -delete

and restart your webserver

-m

Thanks for the response. Any thoughts on why I’m suddenly now getting
"child exited with code 255" when I run my usual spawn-fcgi command (using
this with Nginx)? I’ve never seen this error before, and can’t find much of
anything online about it. I’m not sure what’s going on, but this started
after I made 70-plugins, added the lines to it, ran update-rt-siteconfig-4,
and deleted /var/cache/request-tracker4/mason_data/obj.

I said I added lines to the file. After the line to enable the plugin, I
had to put in the priorities I want, according to the extension’s homepage:
Plugins(‘RT::Extension::PriorityAsString’);
Set(%PriorityAsString, (None => 0, Low => 10, Medium => 20, High => 30,
Critical => 40));

What little I found said that 255 is often caused by permission problems,
so I ran chown www-data on the mason_data directory to be sure the process
could re-create the obj/ directory. I can’t think what else to try. My log
file has nothing in it, /var/log/messages has nothing helpful, and my Nginx
file is of no use, as expected for this kind of problem.

I didn’t realize I could make my own files in the RT_SiteConfig.d
directory, I thought I had to use the existing ones. That’s handy.On Thu, Sep 22, 2016 at 2:04 PM, Matt Zagrabelny mzagrabe@d.umn.edu wrote:

Hi Alex,

On Thu, Sep 22, 2016 at 12:50 PM, Alex Hall ahall@autodist.com wrote:

Hi all,
I can’t seem to find the instructions for enabling extensions in 4.2.8.
I’ve
found some for 3.x, but I thought I read somewhere that the syntax is a
bit
different for 4.x. I know I add something to 50-debconf, but I’m not sure
exactly what.

You can add the configuration “code” to any file in
/etc/request-tracker4/RT_SiteConfig.d.

The configuration “code” is:

Plugin(‘RT::Extension::PriorityAsString’);

So you might have a file like:

/etc/request-tracker4/RT_SiteConfig.d/70-priority-as-string

with the aforementioned Plugin line.

Then run your:

update-rt-siteconfig-4

Then clean your mason cache:

sudo find /var/cache/request-tracker4/mason_data/obj -delete

and restart your webserver

-m

Alex Hall
Automatic Distributors, IT department
ahall@autodist.com

Strange… I get an exit code of 255 on my FCGI server with the extension
enabled. If I comment out the lines in my Plugins file and update
siteconfig, I get no error code, but the server immediately quits silently.
There’s nothing in any log to tell me what’s going on, at least that I can
find. RT was working perfectly until I installed and enabled the
PriorityAsString extension, though I don’t know if the install itself or
the attempt to modify my settings did it.

Is there a way to remove an extension so I can start over? I installed
using the commands on its homepage, not CPAN, so I don’t know if that
caused a problem. I don’t see any uninstall/remove commands on the plugin’s
page, but maybe there’s a standard way using Perl commands that I don’t
know?On Thu, Sep 22, 2016 at 3:25 PM, Alex Hall ahall@autodist.com wrote:

Thanks for the response. Any thoughts on why I’m suddenly now getting
"child exited with code 255" when I run my usual spawn-fcgi command (using
this with Nginx)? I’ve never seen this error before, and can’t find much of
anything online about it. I’m not sure what’s going on, but this started
after I made 70-plugins, added the lines to it, ran update-rt-siteconfig-4,
and deleted /var/cache/request-tracker4/mason_data/obj.

I said I added lines to the file. After the line to enable the plugin, I
had to put in the priorities I want, according to the extension’s homepage:
Plugins(‘RT::Extension::PriorityAsString’);
Set(%PriorityAsString, (None => 0, Low => 10, Medium => 20, High => 30,
Critical => 40));

What little I found said that 255 is often caused by permission problems,
so I ran chown www-data on the mason_data directory to be sure the process
could re-create the obj/ directory. I can’t think what else to try. My log
file has nothing in it, /var/log/messages has nothing helpful, and my Nginx
file is of no use, as expected for this kind of problem.

I didn’t realize I could make my own files in the RT_SiteConfig.d
directory, I thought I had to use the existing ones. That’s handy.

On Thu, Sep 22, 2016 at 2:04 PM, Matt Zagrabelny mzagrabe@d.umn.edu wrote:

Hi Alex,

On Thu, Sep 22, 2016 at 12:50 PM, Alex Hall ahall@autodist.com wrote:

Hi all,
I can’t seem to find the instructions for enabling extensions in 4.2.8.
I’ve
found some for 3.x, but I thought I read somewhere that the syntax is a
bit
different for 4.x. I know I add something to 50-debconf, but I’m not
sure
exactly what.

You can add the configuration “code” to any file in
/etc/request-tracker4/RT_SiteConfig.d.

The configuration “code” is:

Plugin(‘RT::Extension::PriorityAsString’);

So you might have a file like:

/etc/request-tracker4/RT_SiteConfig.d/70-priority-as-string

with the aforementioned Plugin line.

Then run your:

update-rt-siteconfig-4

Then clean your mason cache:

sudo find /var/cache/request-tracker4/mason_data/obj -delete

and restart your webserver

-m


Alex Hall
Automatic Distributors, IT department
ahall@autodist.com

Alex Hall
Automatic Distributors, IT department
ahall@autodist.com

Hi Alex,

Strange… I get an exit code of 255 on my FCGI server with the extension
enabled.

Hmmm. Enabling extensions shouldn’t be too complicated. There is
nothing tricky going on.

If I comment out the lines in my Plugins file and update

siteconfig, I get no error code, but the server immediately quits silently.
There’s nothing in any log to tell me what’s going on, at least that I can
find.

Is there a foreground option for your FCGI server?

Run it through strace?

strace -f /some/path/to/your/fcgi-server

RT was working perfectly until I installed and enabled the

PriorityAsString extension, though I don’t know if the install itself or the
attempt to modify my settings did it.

Check the actual siteconfig file after running your update-rt-siteconfig.

% view /etc/request-tracker4/RT_SiteConfig.pm

and see if the PriorityAsString is commented out or not.

Is there a way to remove an extension so I can start over?

You’d remove the files on disk. I’m not sure if the makefile that is
generated has an uninstall target.

Now that we’re talking about it, did you use the RTHOME variable to
set your RT libs when generating the makefile for the extension?

% tar xvfz some-rt-extension.tar.gz
% cd some-rt-extension
% RTHOME=/usr/share/request-tracker4/lib perl Makefile.PL

I installed using

the commands on its homepage, not CPAN, so I don’t know if that caused a
problem. I don’t see any uninstall/remove commands on the plugin’s page, but
maybe there’s a standard way using Perl commands that I don’t know?

If there were a standard way, then it would be the makefile that gets
generated would have an uninstall target.

-m

Sorry for not replying in-line. I’d like to, but Google seems to have
broken something in their accessibility, and I can’t navigate the quoted
text in my reply. The joys of using a screen reader.

To your questions: I ran strace, and I have a 1.5mb file of output. I don’t
pretend to understand any of it, but I was scanning backwards from the
bottom, and I may have found the problem.

12875 stat("/var/cache/request-tracker4/mason_data/obj",
{st_mode=S_IFDIR|S_ISGID|0755, st_size=4096, …}) = 0
12875
stat("/var/cache/request-tracker4/mason_data/obj/.__obj_create_marker",
0x1bf8238) = -1 ENOENT (No such file or directory)
12875
open("/var/cache/request-tracker4/mason_data/obj/.__obj_create_marker",
O_WRONLY|O_CREAT|O_TRUNC, 0666) = -1 EACCES (Permission denied)

When i cleared my mason cache, I deleted the obj folder as directed. It
looks like this process can’t re-create the necessary structure inside the
mason_data directory. I’ve made www-data the owner, but as I’m invoking
this command as root, perhaps I need to do something different? I’ve also
given /var/cache/request-tracker4/mason_data 777 permissions recursively,
and that did the trick! What permissions should I set, though, to be sure
it’s as secure as it needs to be? Oh, I should say, the FCGI command I use
is:

spawn-fcgi -u www-data -g www-data -a 127.0.0.1 -p 9876
/usr/share/request-tracker4/libexec/rt-server.fcgi

www-data is the same user used in Nginx, and I gather they have to match.

Anyway, back to the extension. Now that RT is running, I once again enabled
the plugin and updated my settings (yes, my main configuration file updates
as it should). But when I ran my FCGI command, I once again got the exit
code 255 message. I deleted sason_data/obj again, but that didn’t help. I
reset the permissions, but that, too, did nothing. There’s something odd
happening with the extension enabled that doesn’t seem to happen with it
disabled. I’m not sure what the deal is, though. Has anyone ever seen this
happen with an extension?On Fri, Sep 23, 2016 at 11:34 AM, Matt Zagrabelny mzagrabe@d.umn.edu wrote:

Hi Alex,

On Fri, Sep 23, 2016 at 7:07 AM, Alex Hall ahall@autodist.com wrote:

Strange… I get an exit code of 255 on my FCGI server with the extension
enabled.

Hmmm. Enabling extensions shouldn’t be too complicated. There is
nothing tricky going on.

If I comment out the lines in my Plugins file and update

siteconfig, I get no error code, but the server immediately quits
silently.
There’s nothing in any log to tell me what’s going on, at least that I
can
find.

Is there a foreground option for your FCGI server?

Run it through strace?

strace -f /some/path/to/your/fcgi-server

RT was working perfectly until I installed and enabled the

PriorityAsString extension, though I don’t know if the install itself or
the
attempt to modify my settings did it.

Check the actual siteconfig file after running your update-rt-siteconfig.

% view /etc/request-tracker4/RT_SiteConfig.pm

and see if the PriorityAsString is commented out or not.

Is there a way to remove an extension so I can start over?

You’d remove the files on disk. I’m not sure if the makefile that is
generated has an uninstall target.

Now that we’re talking about it, did you use the RTHOME variable to
set your RT libs when generating the makefile for the extension?

% tar xvfz some-rt-extension.tar.gz
% cd some-rt-extension
% RTHOME=/usr/share/request-tracker4/lib perl Makefile.PL

I installed using

the commands on its homepage, not CPAN, so I don’t know if that caused a
problem. I don’t see any uninstall/remove commands on the plugin’s page,
but
maybe there’s a standard way using Perl commands that I don’t know?

If there were a standard way, then it would be the makefile that gets
generated would have an uninstall target.

-m

Alex Hall
Automatic Distributors, IT department
ahall@autodist.com

Hi Alex,

Sorry for not replying in-line. I’d like to, but Google seems to have broken
something in their accessibility, and I can’t navigate the quoted text in my
reply. The joys of using a screen reader.

It’s okay. :slight_smile:

To your questions: I ran strace, and I have a 1.5mb file of output. I don’t
pretend to understand any of it, but I was scanning backwards from the
bottom, and I may have found the problem.

12875 stat("/var/cache/request-tracker4/mason_data/obj",
{st_mode=S_IFDIR|S_ISGID|0755, st_size=4096, …}) = 0
12875
stat("/var/cache/request-tracker4/mason_data/obj/.__obj_create_marker",
0x1bf8238) = -1 ENOENT (No such file or directory)
12875
open("/var/cache/request-tracker4/mason_data/obj/.__obj_create_marker",
O_WRONLY|O_CREAT|O_TRUNC, 0666) = -1 EACCES (Permission denied)

When i cleared my mason cache, I deleted the obj folder as directed. It
looks like this process can’t re-create the necessary structure inside the
mason_data directory.

Hmmm. Okay. It looks like my install of RT recreates the obj directory

  • sorry for the assumptive advice.

Here is a better command for clearing your mason cache, but leaving
the obj directory:

% sudo find /var/cache/request-tracker4/mason_data/obj -mindepth 1 -delete

I’ve made www-data the owner, but as I’m invoking this

command as root, perhaps I need to do something different? I’ve also given
/var/cache/request-tracker4/mason_data 777 permissions recursively, and that
did the trick! What permissions should I set, though, to be sure it’s as
secure as it needs to be?

On my installs:

www-data:www-data and 0755

You should only need to set that for the “obj” directory as the RT
process will build the rest of hierarchy.

Oh, I should say, the FCGI command I use is:

spawn-fcgi -u www-data -g www-data -a 127.0.0.1 -p 9876
/usr/share/request-tracker4/libexec/rt-server.fcgi

www-data is the same user used in Nginx, and I gather they have to match.

Anyway, back to the extension. Now that RT is running, I once again enabled
the plugin and updated my settings (yes, my main configuration file updates
as it should). But when I ran my FCGI command, I once again got the exit
code 255 message. I deleted sason_data/obj again, but that didn’t help. I
reset the permissions, but that, too, did nothing. There’s something odd
happening with the extension enabled that doesn’t seem to happen with it
disabled. I’m not sure what the deal is, though. Has anyone ever seen this
happen with an extension?

It almost sounds like your RT_SiteConfig.pm has invalid perl syntax.

Run:

perl -c /etc/request-tracker4/RT_SiteConfig.pm

Both before and after enabling and disabling your extension and
running the update-rt-siteconfig.

-m

Okay, good to know about the permissions and deleting everything below
mason_data/obj. I re-created the obj directory and set it to
www-data:www-data 755.

I ran perl -c on the main config file, with the two plugin lines commented
out and not, and on the RT_SiteConfig.d/70-plugins file I made that holds
those lines. In all three cases, Perl reports that the syntax is okay.

To make sure I’m not going nuts from all the things I’ve tried recently, I
tested things once more. I commented out the plugin lines, ran
update-rt-siteconfig and update-rt-siteconfig-4 (what’s the difference?),
and tried to spawn the FCGI server. It worked. Uncommented, and the FCGI
server exited with status code 255 when not commented. Oh, between the two
attempts I also ran the delete command you sent. Is there a step I’m
missing? Maybe something so obvious you didn’t think to mention it? This is
clearly atypical for RT plugins, so it almost has to be something I’m
missing/doing wrong.On Fri, Sep 23, 2016 at 2:49 PM, Matt Zagrabelny mzagrabe@d.umn.edu wrote:

Hi Alex,

On Fri, Sep 23, 2016 at 12:15 PM, Alex Hall ahall@autodist.com wrote:

Sorry for not replying in-line. I’d like to, but Google seems to have
broken
something in their accessibility, and I can’t navigate the quoted text
in my
reply. The joys of using a screen reader.

It’s okay. :slight_smile:

To your questions: I ran strace, and I have a 1.5mb file of output. I
don’t
pretend to understand any of it, but I was scanning backwards from the
bottom, and I may have found the problem.

12875 stat("/var/cache/request-tracker4/mason_data/obj",
{st_mode=S_IFDIR|S_ISGID|0755, st_size=4096, …}) = 0
12875
stat("/var/cache/request-tracker4/mason_data/obj/.__obj_create_marker",
0x1bf8238) = -1 ENOENT (No such file or directory)
12875
open("/var/cache/request-tracker4/mason_data/obj/.__obj_create_marker",
O_WRONLY|O_CREAT|O_TRUNC, 0666) = -1 EACCES (Permission denied)

When i cleared my mason cache, I deleted the obj folder as directed. It
looks like this process can’t re-create the necessary structure inside
the
mason_data directory.

Hmmm. Okay. It looks like my install of RT recreates the obj directory

  • sorry for the assumptive advice.

Here is a better command for clearing your mason cache, but leaving
the obj directory:

% sudo find /var/cache/request-tracker4/mason_data/obj -mindepth 1 -delete

I’ve made www-data the owner, but as I’m invoking this

command as root, perhaps I need to do something different? I’ve also
given
/var/cache/request-tracker4/mason_data 777 permissions recursively, and
that
did the trick! What permissions should I set, though, to be sure it’s as
secure as it needs to be?

On my installs:

www-data:www-data and 0755

You should only need to set that for the “obj” directory as the RT
process will build the rest of hierarchy.

Oh, I should say, the FCGI command I use is:

spawn-fcgi -u www-data -g www-data -a 127.0.0.1 -p 9876
/usr/share/request-tracker4/libexec/rt-server.fcgi

www-data is the same user used in Nginx, and I gather they have to match.

Anyway, back to the extension. Now that RT is running, I once again
enabled
the plugin and updated my settings (yes, my main configuration file
updates
as it should). But when I ran my FCGI command, I once again got the exit
code 255 message. I deleted sason_data/obj again, but that didn’t help. I
reset the permissions, but that, too, did nothing. There’s something odd
happening with the extension enabled that doesn’t seem to happen with it
disabled. I’m not sure what the deal is, though. Has anyone ever seen
this
happen with an extension?

It almost sounds like your RT_SiteConfig.pm has invalid perl syntax.

Run:

perl -c /etc/request-tracker4/RT_SiteConfig.pm

Both before and after enabling and disabling your extension and
running the update-rt-siteconfig.

-m

Alex Hall
Automatic Distributors, IT department
ahall@autodist.com

Okay, good to know about the permissions and deleting everything below
mason_data/obj. I re-created the obj directory and set it to
www-data:www-data 755.

I ran perl -c on the main config file, with the two plugin lines commented
out and not, and on the RT_SiteConfig.d/70-plugins file I made that holds
those lines. In all three cases, Perl reports that the syntax is okay.

To make sure I’m not going nuts from all the things I’ve tried recently, I
tested things once more. I commented out the plugin lines, ran
update-rt-siteconfig and update-rt-siteconfig-4 (what’s the difference?),

update-rt-siteconfig is a symlink. It points to
update-rt-siteconfig-4. The command is obsolete in 4.4 since RT
natively supports config snippets without needing a command to
regenerate a site config.

and tried to spawn the FCGI server. It worked. Uncommented, and the FCGI
server exited with status code 255 when not commented. Oh, between the two
attempts I also ran the delete command you sent. Is there a step I’m
missing? Maybe something so obvious you didn’t think to mention it? This is
clearly atypical for RT plugins, so it almost has to be something I’m
missing/doing wrong.

What did you do to install the module?

Did you read my comment in a previous email about RTHOME?

Please list the exact commands and their output.

wget or curl?
tar?
perl Makefile.PL?

etc.

Maybe we’ll see something.

-m

I’ll run the install again and hope that doing so won’t cause any problems.
:slight_smile:

root@server24:/home/ahall/RT-Extension-PriorityAsString-1.04# perl
Makefile.PL
Using RT configuration from /usr/share/request-tracker4/lib/RT.pm:
html =>
/usr/local/share/request-tracker4/plugins/RT-Extension-PriorityAsString/html
lib =>
/usr/local/share/request-tracker4/plugins/RT-Extension-PriorityAsString/lib
Generating a Unix-style Makefile
Writing Makefile for RT::Extension::PriorityAsString
Writing MYMETA.yml and MYMETA.json

root@server24:/home/ahall/RT-Extension-PriorityAsString-1.04# make
Skip blib/lib/RT/Extension/PriorityAsString.pm (unchanged)
Manifying blib/man3/RT::Extension::PriorityAsString.3pm

root@server24:/home/ahall/RT-Extension-PriorityAsString-1.04# make install
Appending installation info to
/usr/local/share/request-tracker4/man/perllocal.pod
Couldn’t load RT config file RT_SiteConfig.pm:

Can’t locate object method “InitPluginPaths” via package
"RT::Extension::PriorityAsString" (perhaps you forgot to load
"RT::Extension::PriorityAsString"?) at
/usr/share/request-tracker4/lib/RT.pm line 654.
Compilation failed in require at
/usr/share/request-tracker4/lib/RT/Config.pm line 1106.
Makefile:796: recipe for target ‘install’ failed
make: *** [install] Error 255

Well, that’s new. Obviously this is the source of the trouble, but what
does it mean and how do I fix it? As far as I remember, I didn’t see this
on my last install, but I’m glad it’s here now if it illuminates the core
problem! And no, I think I missted the RTHOME comment. I’m going to search
for it as soon as I send this.On Fri, Sep 23, 2016 at 3:31 PM, Matt Zagrabelny mzagrabe@d.umn.edu wrote:

On Fri, Sep 23, 2016 at 2:20 PM, Alex Hall ahall@autodist.com wrote:

Okay, good to know about the permissions and deleting everything below
mason_data/obj. I re-created the obj directory and set it to
www-data:www-data 755.

I ran perl -c on the main config file, with the two plugin lines
commented
out and not, and on the RT_SiteConfig.d/70-plugins file I made that holds
those lines. In all three cases, Perl reports that the syntax is okay.

To make sure I’m not going nuts from all the things I’ve tried recently,
I
tested things once more. I commented out the plugin lines, ran
update-rt-siteconfig and update-rt-siteconfig-4 (what’s the difference?),

update-rt-siteconfig is a symlink. It points to
update-rt-siteconfig-4. The command is obsolete in 4.4 since RT
natively supports config snippets without needing a command to
regenerate a site config.

and tried to spawn the FCGI server. It worked. Uncommented, and the FCGI
server exited with status code 255 when not commented. Oh, between the
two
attempts I also ran the delete command you sent. Is there a step I’m
missing? Maybe something so obvious you didn’t think to mention it? This
is
clearly atypical for RT plugins, so it almost has to be something I’m
missing/doing wrong.

What did you do to install the module?

Did you read my comment in a previous email about RTHOME?

Please list the exact commands and their output.

wget or curl?
tar?
perl Makefile.PL?

etc.

Maybe we’ll see something.

-m

Alex Hall
Automatic Distributors, IT department
ahall@autodist.com

I just now tried the RTHOME suggestion, after which I ran make and make
install. I got the exact same error as in my previous message,
unfortunately.On Fri, Sep 23, 2016 at 3:43 PM, Alex Hall ahall@autodist.com wrote:

I’ll run the install again and hope that doing so won’t cause any
problems. :slight_smile:

root@server24:/home/ahall/RT-Extension-PriorityAsString-1.04# perl
Makefile.PL
Using RT configuration from /usr/share/request-tracker4/lib/RT.pm:
html => /usr/local/share/request-tracker4/plugins/RT-Extension-
PriorityAsString/html
lib => /usr/local/share/request-tracker4/plugins/RT-Extension-
PriorityAsString/lib
Generating a Unix-style Makefile
Writing Makefile for RT::Extension::PriorityAsString
Writing MYMETA.yml and MYMETA.json

root@server24:/home/ahall/RT-Extension-PriorityAsString-1.04# make
Skip blib/lib/RT/Extension/PriorityAsString.pm (unchanged)
Manifying blib/man3/RT::Extension::PriorityAsString.3pm

root@server24:/home/ahall/RT-Extension-PriorityAsString-1.04# make install
Appending installation info to /usr/local/share/request-
tracker4/man/perllocal.pod
Couldn’t load RT config file RT_SiteConfig.pm:

Can’t locate object method “InitPluginPaths” via package “RT::Extension::PriorityAsString”
(perhaps you forgot to load “RT::Extension::PriorityAsString”?) at
/usr/share/request-tracker4/lib/RT.pm line 654.
Compilation failed in require at /usr/share/request-tracker4/lib/RT/Config.pm
line 1106.
Makefile:796: recipe for target ‘install’ failed
make: *** [install] Error 255

Well, that’s new. Obviously this is the source of the trouble, but what
does it mean and how do I fix it? As far as I remember, I didn’t see this
on my last install, but I’m glad it’s here now if it illuminates the core
problem! And no, I think I missted the RTHOME comment. I’m going to search
for it as soon as I send this.

On Fri, Sep 23, 2016 at 3:31 PM, Matt Zagrabelny mzagrabe@d.umn.edu wrote:

On Fri, Sep 23, 2016 at 2:20 PM, Alex Hall ahall@autodist.com wrote:

Okay, good to know about the permissions and deleting everything below
mason_data/obj. I re-created the obj directory and set it to
www-data:www-data 755.

I ran perl -c on the main config file, with the two plugin lines
commented
out and not, and on the RT_SiteConfig.d/70-plugins file I made that
holds
those lines. In all three cases, Perl reports that the syntax is okay.

To make sure I’m not going nuts from all the things I’ve tried
recently, I
tested things once more. I commented out the plugin lines, ran
update-rt-siteconfig and update-rt-siteconfig-4 (what’s the
difference?),

update-rt-siteconfig is a symlink. It points to
update-rt-siteconfig-4. The command is obsolete in 4.4 since RT
natively supports config snippets without needing a command to
regenerate a site config.

and tried to spawn the FCGI server. It worked. Uncommented, and the FCGI
server exited with status code 255 when not commented. Oh, between the
two
attempts I also ran the delete command you sent. Is there a step I’m
missing? Maybe something so obvious you didn’t think to mention it?
This is
clearly atypical for RT plugins, so it almost has to be something I’m
missing/doing wrong.

What did you do to install the module?

Did you read my comment in a previous email about RTHOME?

Please list the exact commands and their output.

wget or curl?
tar?
perl Makefile.PL?

etc.

Maybe we’ll see something.

-m


Alex Hall
Automatic Distributors, IT department
ahall@autodist.com

Alex Hall
Automatic Distributors, IT department
ahall@autodist.com

Hey Alex,

I may have gotten the RTHOME incantation wrong. I just ran the install
on my Debian system and here is the output:

% cd /tmp

% wget https://cpan.metacpan.org/authors/id/B/BP/BPS/RT-Extension-PriorityAsString-1.04.tar.gz
–2016-09-23 15:00:25–
https://cpan.metacpan.org/authors/id/B/BP/BPS/RT-Extension-PriorityAsString-1.04.tar.gz
Resolving cpan.metacpan.org (cpan.metacpan.org)… 151.101.44.129
Connecting to cpan.metacpan.org
(cpan.metacpan.org)|151.101.44.129|:443… connected.
HTTP request sent, awaiting response… 200 OK
Length: 36285 (35K) [application/x-gzip]
Saving to: ‘RT-Extension-PriorityAsString-1.04.tar.gz’

RT-Extension-PriorityAsString
100%[===============================================>] 35.43K
–.-KB/s in 0.02s

2016-09-23 15:00:25 (1.91 MB/s) -
‘RT-Extension-PriorityAsString-1.04.tar.gz’ saved [36285/36285]

% tar xfz RT-Extension-PriorityAsString-1.04.tar.gz

% cd RT-Extension-PriorityAsString-1.04

% RTHOME=/usr/share/request-tracker4 perl Makefile.PL
Using RT configuration from /usr/share/request-tracker4/lib/RT.pm:
html => /usr/local/share/request-tracker4/plugins/RT-Extension-PriorityAsString/html
lib => /usr/local/share/request-tracker4/plugins/RT-Extension-PriorityAsString/lib
Checking if your kit is complete…
Looks good
Generating a Unix-style Makefile
Writing Makefile for RT::Extension::PriorityAsString
Writing MYMETA.yml and MYMETA.json

% make
cp lib/RT/Extension/PriorityAsString.pm
blib/lib/RT/Extension/PriorityAsString.pm
Manifying 1 pod document

% make test
No tests defined for RT::Extension::PriorityAsString extension.

% sudo make install
Manifying 1 pod document
Installing /usr/local/share/request-tracker4/plugins/RT-Extension-PriorityAsString/lib/RT/Extension/PriorityAsString.pm
Installing /usr/local/share/request-tracker4/man/man3/RT::Extension::PriorityAsString.3pm
Appending installation info to
/usr/local/share/request-tracker4/man/perllocal.pod
Installing /usr/local/share/request-tracker4/plugins/RT-Extension-PriorityAsString/html/Elements/SelectPriorityAsString
Installing /usr/local/share/request-tracker4/plugins/RT-Extension-PriorityAsString/html/Elements/SelectPriority
Installing /usr/local/share/request-tracker4/plugins/RT-Extension-PriorityAsString/html/Callbacks/PriorityAsString/Search/Elements/PickBasics/Default
Installing /usr/local/share/request-tracker4/plugins/RT-Extension-PriorityAsString/html/Callbacks/PriorityAsString/Elements/RT__Ticket/ColumnMap/Once
Installing /usr/local/share/request-tracker4/plugins/RT-Extension-PriorityAsString/html/Callbacks/PriorityAsString/Ticket/Elements/EditBasics/MassageFields
Installing /usr/local/share/request-tracker4/plugins/RT-Extension-PriorityAsString/html/Ticket/Elements/ShowPriority

% tree /usr/local/share/request-tracker4/plugins/RT-Extension-PriorityAsString
/usr/local/share/request-tracker4/plugins/RT-Extension-PriorityAsString
├── html
│ ├── Callbacks
│ │ └── PriorityAsString
│ │ ├── Elements
│ │ │ └── RT__Ticket
│ │ │ └── ColumnMap
│ │ │ └── Once
│ │ ├── Search
│ │ │ └── Elements
│ │ │ └── PickBasics
│ │ │ └── Default
│ │ └── Ticket
│ │ └── Elements
│ │ └── EditBasics
│ │ └── MassageFields
│ ├── Elements
│ │ ├── SelectPriority
│ │ └── SelectPriorityAsString
│ └── Ticket
│ └── Elements
│ └── ShowPriority
└── lib
└── RT
└── Extension
└── PriorityAsString.pm

18 directories, 7 filesOn Fri, Sep 23, 2016 at 2:46 PM, Alex Hall ahall@autodist.com wrote:

I just now tried the RTHOME suggestion, after which I ran make and make
install. I got the exact same error as in my previous message,
unfortunately.

On Fri, Sep 23, 2016 at 3:43 PM, Alex Hall ahall@autodist.com wrote:

I’ll run the install again and hope that doing so won’t cause any
problems. :slight_smile:

root@server24:/home/ahall/RT-Extension-PriorityAsString-1.04# perl
Makefile.PL
Using RT configuration from /usr/share/request-tracker4/lib/RT.pm:
html =>
/usr/local/share/request-tracker4/plugins/RT-Extension-PriorityAsString/html
lib =>
/usr/local/share/request-tracker4/plugins/RT-Extension-PriorityAsString/lib
Generating a Unix-style Makefile
Writing Makefile for RT::Extension::PriorityAsString
Writing MYMETA.yml and MYMETA.json

root@server24:/home/ahall/RT-Extension-PriorityAsString-1.04# make
Skip blib/lib/RT/Extension/PriorityAsString.pm (unchanged)
Manifying blib/man3/RT::Extension::PriorityAsString.3pm

root@server24:/home/ahall/RT-Extension-PriorityAsString-1.04# make install
Appending installation info to
/usr/local/share/request-tracker4/man/perllocal.pod
Couldn’t load RT config file RT_SiteConfig.pm:

Can’t locate object method “InitPluginPaths” via package
"RT::Extension::PriorityAsString" (perhaps you forgot to load
"RT::Extension::PriorityAsString"?) at /usr/share/request-tracker4/lib/RT.pm
line 654.
Compilation failed in require at
/usr/share/request-tracker4/lib/RT/Config.pm line 1106.
Makefile:796: recipe for target ‘install’ failed
make: *** [install] Error 255

Well, that’s new. Obviously this is the source of the trouble, but what
does it mean and how do I fix it? As far as I remember, I didn’t see this on
my last install, but I’m glad it’s here now if it illuminates the core
problem! And no, I think I missted the RTHOME comment. I’m going to search
for it as soon as I send this.

On Fri, Sep 23, 2016 at 3:31 PM, Matt Zagrabelny mzagrabe@d.umn.edu wrote:

On Fri, Sep 23, 2016 at 2:20 PM, Alex Hall ahall@autodist.com wrote:

Okay, good to know about the permissions and deleting everything below
mason_data/obj. I re-created the obj directory and set it to
www-data:www-data 755.

I ran perl -c on the main config file, with the two plugin lines
commented
out and not, and on the RT_SiteConfig.d/70-plugins file I made that
holds
those lines. In all three cases, Perl reports that the syntax is okay.

To make sure I’m not going nuts from all the things I’ve tried
recently, I
tested things once more. I commented out the plugin lines, ran
update-rt-siteconfig and update-rt-siteconfig-4 (what’s the
difference?),

update-rt-siteconfig is a symlink. It points to
update-rt-siteconfig-4. The command is obsolete in 4.4 since RT
natively supports config snippets without needing a command to
regenerate a site config.

and tried to spawn the FCGI server. It worked. Uncommented, and the
FCGI
server exited with status code 255 when not commented. Oh, between the
two
attempts I also ran the delete command you sent. Is there a step I’m
missing? Maybe something so obvious you didn’t think to mention it?
This is
clearly atypical for RT plugins, so it almost has to be something I’m
missing/doing wrong.

What did you do to install the module?

Did you read my comment in a previous email about RTHOME?

Please list the exact commands and their output.

wget or curl?
tar?
perl Makefile.PL?

etc.

Maybe we’ll see something.

-m


Alex Hall
Automatic Distributors, IT department
ahall@autodist.com


Alex Hall
Automatic Distributors, IT department
ahall@autodist.com

If I’m reading that right, the difference is that RTHOME should be
/usr/share/request-tracker4, with no /lib on the end? Trying that, I still
get the error. I didn’t use CPAN, and I didn’t see the part about verifying
my kit, but other than that our two outputs looked similar right up to
’make install’ when mine goes sideways. I also ran your commands exactly as
shown, using wget and /tmp instead of the gz file I downloaded earlier in
my home directory. Yet, I still got exactly the same error at exactly the
same point.

Appending installation info to
/usr/local/share/request-tracker4/man/perllocal.pod
Couldn’t load RT config file RT_SiteConfig.pm:

Can’t locate object method “InitPluginPaths” via package
"RT::Extension::PriorityAsString" (perhaps you forgot to load
"RT::Extension::PriorityAsString"?) at
/usr/share/request-tracker4/lib/RT.pm line 654.
Compilation failed in require at
/usr/share/request-tracker4/lib/RT/Config.pm line 1106.
Makefile:796: recipe for target ‘install’ failed
make: *** [install] Error 255

Thanks for all your time on this. If you, or anyone else, can see what
might be going on… I’ll try just about anything.On Fri, Sep 23, 2016 at 4:06 PM, Matt Zagrabelny mzagrabe@d.umn.edu wrote:

Hey Alex,

I may have gotten the RTHOME incantation wrong. I just ran the install
on my Debian system and here is the output:

% cd /tmp

% wget https://cpan.metacpan.org/authors/id/B/BP/BPS/RT-
Extension-PriorityAsString-1.04.tar.gz
–2016-09-23
https://cpan.metacpan.org/authors/id/B/BP/BPS/RT-Extension-PriorityAsString-1.04.tar.gz --2016-09-23
15:00:25–
https://cpan.metacpan.org/authors/id/B/BP/BPS/RT-
Extension-PriorityAsString-1.04.tar.gz
Resolving cpan.metacpan.org (cpan.metacpan.org)… 151.101.44.129
Connecting to cpan.metacpan.org
(cpan.metacpan.org)|151.101.44.129|:443… connected.
HTTP request sent, awaiting response… 200 OK
Length: 36285 (35K) [application/x-gzip]
Saving to: ‘RT-Extension-PriorityAsString-1.04.tar.gz’

RT-Extension-PriorityAsString
100%[===============================================>] 35.43K
–.-KB/s in 0.02s

2016-09-23 15:00:25 (1.91 MB/s) -
‘RT-Extension-PriorityAsString-1.04.tar.gz’ saved [36285/36285]

% tar xfz RT-Extension-PriorityAsString-1.04.tar.gz

% cd RT-Extension-PriorityAsString-1.04

% RTHOME=/usr/share/request-tracker4 perl Makefile.PL
Using RT configuration from /usr/share/request-tracker4/lib/RT.pm:
html => /usr/local/share/request-tracker4/plugins/RT-Extension-
PriorityAsString/html
lib => /usr/local/share/request-tracker4/plugins/RT-Extension-
PriorityAsString/lib
Checking if your kit is complete…
Looks good
Generating a Unix-style Makefile
Writing Makefile for RT::Extension::PriorityAsString
Writing MYMETA.yml and MYMETA.json

% make
cp lib/RT/Extension/PriorityAsString.pm
blib/lib/RT/Extension/PriorityAsString.pm
Manifying 1 pod document

% make test
No tests defined for RT::Extension::PriorityAsString extension.

% sudo make install
Manifying 1 pod document
Installing /usr/local/share/request-tracker4/plugins/RT-Extension-
PriorityAsString/lib/RT/Extension/PriorityAsString.pm
Installing /usr/local/share/request-tracker4/man/man3/RT::
Extension::PriorityAsString.3pm
Appending installation info to
/usr/local/share/request-tracker4/man/perllocal.pod
Installing /usr/local/share/request-tracker4/plugins/RT-Extension-
PriorityAsString/html/Elements/SelectPriorityAsString
Installing /usr/local/share/request-tracker4/plugins/RT-Extension-
PriorityAsString/html/Elements/SelectPriority
Installing /usr/local/share/request-tracker4/plugins/RT-Extension-
PriorityAsString/html/Callbacks/PriorityAsString/
Search/Elements/PickBasics/Default
Installing /usr/local/share/request-tracker4/plugins/RT-Extension-
PriorityAsString/html/Callbacks/PriorityAsString/
Elements/RT__Ticket/ColumnMap/Once
Installing /usr/local/share/request-tracker4/plugins/RT-Extension-
PriorityAsString/html/Callbacks/PriorityAsString/
Ticket/Elements/EditBasics/MassageFields
Installing /usr/local/share/request-tracker4/plugins/RT-Extension-
PriorityAsString/html/Ticket/Elements/ShowPriority

% tree /usr/local/share/request-tracker4/plugins/RT-Extension-
PriorityAsString
/usr/local/share/request-tracker4/plugins/RT-Extension-PriorityAsString
├── html
│ ├── Callbacks
│ │ └── PriorityAsString
│ │ ├── Elements
│ │ │ └── RT__Ticket
│ │ │ └── ColumnMap
│ │ │ └── Once
│ │ ├── Search
│ │ │ └── Elements
│ │ │ └── PickBasics
│ │ │ └── Default
│ │ └── Ticket
│ │ └── Elements
│ │ └── EditBasics
│ │ └── MassageFields
│ ├── Elements
│ │ ├── SelectPriority
│ │ └── SelectPriorityAsString
│ └── Ticket
│ └── Elements
│ └── ShowPriority
└── lib
└── RT
└── Extension
└── PriorityAsString.pm

18 directories, 7 files

On Fri, Sep 23, 2016 at 2:46 PM, Alex Hall ahall@autodist.com wrote:

I just now tried the RTHOME suggestion, after which I ran make and make
install. I got the exact same error as in my previous message,
unfortunately.

On Fri, Sep 23, 2016 at 3:43 PM, Alex Hall ahall@autodist.com wrote:

I’ll run the install again and hope that doing so won’t cause any
problems. :slight_smile:

root@server24:/home/ahall/RT-Extension-PriorityAsString-1.04# perl
Makefile.PL
Using RT configuration from /usr/share/request-tracker4/lib/RT.pm:
html =>
/usr/local/share/request-tracker4/plugins/RT-Extension-
PriorityAsString/html

lib =>
/usr/local/share/request-tracker4/plugins/RT-Extension-
PriorityAsString/lib

Generating a Unix-style Makefile
Writing Makefile for RT::Extension::PriorityAsString
Writing MYMETA.yml and MYMETA.json

root@server24:/home/ahall/RT-Extension-PriorityAsString-1.04# make
Skip blib/lib/RT/Extension/PriorityAsString.pm (unchanged)
Manifying blib/man3/RT::Extension::PriorityAsString.3pm

root@server24:/home/ahall/RT-Extension-PriorityAsString-1.04# make
install

Appending installation info to
/usr/local/share/request-tracker4/man/perllocal.pod
Couldn’t load RT config file RT_SiteConfig.pm:

Can’t locate object method “InitPluginPaths” via package
"RT::Extension::PriorityAsString" (perhaps you forgot to load
"RT::Extension::PriorityAsString"?) at /usr/share/request-tracker4/
lib/RT.pm

line 654.
Compilation failed in require at
/usr/share/request-tracker4/lib/RT/Config.pm line 1106.
Makefile:796: recipe for target ‘install’ failed
make: *** [install] Error 255

Well, that’s new. Obviously this is the source of the trouble, but what
does it mean and how do I fix it? As far as I remember, I didn’t see
this on

my last install, but I’m glad it’s here now if it illuminates the core
problem! And no, I think I missted the RTHOME comment. I’m going to
search

for it as soon as I send this.

On Fri, Sep 23, 2016 at 3:31 PM, Matt Zagrabelny mzagrabe@d.umn.edu wrote:

On Fri, Sep 23, 2016 at 2:20 PM, Alex Hall ahall@autodist.com wrote:

Okay, good to know about the permissions and deleting everything
below

mason_data/obj. I re-created the obj directory and set it to
www-data:www-data 755.

I ran perl -c on the main config file, with the two plugin lines
commented
out and not, and on the RT_SiteConfig.d/70-plugins file I made that
holds
those lines. In all three cases, Perl reports that the syntax is
okay.

To make sure I’m not going nuts from all the things I’ve tried
recently, I
tested things once more. I commented out the plugin lines, ran
update-rt-siteconfig and update-rt-siteconfig-4 (what’s the
difference?),

update-rt-siteconfig is a symlink. It points to
update-rt-siteconfig-4. The command is obsolete in 4.4 since RT
natively supports config snippets without needing a command to
regenerate a site config.

and tried to spawn the FCGI server. It worked. Uncommented, and the
FCGI
server exited with status code 255 when not commented. Oh, between
the

two
attempts I also ran the delete command you sent. Is there a step I’m
missing? Maybe something so obvious you didn’t think to mention it?
This is
clearly atypical for RT plugins, so it almost has to be something I’m
missing/doing wrong.

What did you do to install the module?

Did you read my comment in a previous email about RTHOME?

Please list the exact commands and their output.

wget or curl?
tar?
perl Makefile.PL?

etc.

Maybe we’ll see something.

-m


Alex Hall
Automatic Distributors, IT department
ahall@autodist.com


Alex Hall
Automatic Distributors, IT department
ahall@autodist.com

Alex Hall
Automatic Distributors, IT department
ahall@autodist.com