[rt-users] Output contents of Custom field via command line

2015-09-23 Thread Yourevilness
Hello,  RT 4.2.11 on Centos 6

I'm trying to generate a list of all unresolved tickets via command line and
output the contents of a custom field value to a log file.  I have another
system checking this log file to verify the contents.

Without going too far into the requirements.  Is there any way to do this?

I've tried RT-Crontool (Via Mysql), RT CLI queries etc. I can find the
tickets ID but cannot extract the correct information I am after.


CLI - /opt/rt4/bin/rt list -i "status != 'resolved' AND (Queue =
'Operations')"
#This gives me a list of the tickets.
/opt/rt4/bin/rt show -t ticket 265550 -f 'CF.{A Number}'
#This gives me the contents of the custom field called "A number" 

I cannot seem to combine them into one command.

Likewise with rt-crontool... I can gather the necessary ticket ID's but
cannot get any further information.

I am aware of the REST interface and its ability to do what I am after, but
I've not had much luck with it creating issues with the Mysql process.



--
View this message in context: 
http://requesttracker.8502.n7.nabble.com/Output-contents-of-Custom-field-via-command-line-tp60701.html
Sent from the Request Tracker - User mailing list archive at Nabble.com.


[rt-users] Internal server error

2015-09-23 Thread Jonathan Murray

Folks, I'm running:

RT 4.2.9
CentOS 6.7
httpd-2.2.15-47.el6.centos.x86_64

when I go to the rt URL:

Internal Server Error

The server encountered an internal error or misconfiguration and was 
unable to complete your request.


Please contact the server administrator, root@localhost and inform them 
of the time the error occurred, and anything you might have done that 
may have caused the error.


More information about this error may be available in the server error log.
Apache/2.2.15 (CentOS) Server at rtdev.whoi.edu Port 443

I checked /opt/rt4/var/log and discovered that I needed something called

[1920] [Wed Sep 23 20:33:11 2015] [critical]: Can't locate 
RT/Authen/ExternalAuth.pm in @INC (@INC contains: 
/opt/rt4/sbin/../local/lib /opt/rt4/sbin/../lib /usr/local/lib64/perl5 
/usr/local/share/perl5 /usr/lib64/perl5/vendor_perl 
/usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at 
/opt/rt4/sbin/../lib/RT.pm line 729. (/opt/rt4/sbin/../lib/RT.pm:388)


so I got that via

cpan> install RT::Authen::ExternalAuth

seemed to work OK. Restarted the web server,

Then I got this:

[3160] [Wed Sep 23 21:39:04 2015] [critical]: Can't locate 
RT/Extension/ActivityReports.pm in @INC (@INC contains: 
/opt/rt4/sbin/../local/lib 
/opt/rt4/local/plugins/RT-Authen-ExternalAuth/lib /opt/rt4/sbin/../lib 
/usr/local/lib64/perl5 /usr/local/share/perl5 
/usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl 
/usr/lib64/perl5 /usr/share/perl5 .) at /opt/rt4/sbin/../lib/RT.pm line 
729,  line 755. (/opt/rt4/sbin/../lib/RT.pm:388)


I was able to get that install in

/opt/rt4/local/plugins/RT-Extension-ActivityReports/lib/RT/Extension/ActivityReports.pm

Now I'm looking for something called Ex.pm

[3414] [Wed Sep 23 21:55:08 2015] [critical]: Can't locate RT/Ex.pm in 
@INC (@INC contains: /opt/rt4/sbin/../local/lib 
/opt/rt4/local/plugins/RT-Authen-ExternalAuth/lib 
/opt/rt4/local/plugins/RT-Extension-ActivityReports/lib 
/opt/rt4/sbin/../lib /usr/local/lib64/perl5 /usr/local/share/perl5 
/usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl 
/usr/lib64/perl5 /usr/share/perl5 .) at /opt/rt4/sbin/../lib/RT.pm line 
729,  line 755. (/opt/rt4/sbin/../lib/RT.pm:388)


Can someone direct me to a place where I can download that? I can't seem 
to find that specific module anywhere.


Also, if I can get that installed, is there a way to make sure that I 
can get all the dependencies associated with it? Or is the normal mode 
to just keep chasing each one individually. Happy to do that, or 
(most)anything to get this running. Sorry, absolute beginner here.


Thank you, Jonathan



Re: [rt-users] Keeping RT URLs off of port 80

2015-09-23 Thread Jason L Tibbitts III
> "MB" == Matt Brennan  writes:

MB> Someone may later say this is incorrect, but in my config, my web
MB> port is still 80. I have:

If I switch it around I get the opposite complaint.

MB> Then I used Apache mod_rewrite:

I just do a redirectmatch.

RedirectMatch permanent ^$ https://XXX/
RedirectMatch permanent ^/(.*) https://XXX/$1

This is on a virtualhost that listens on port 80 and serves no RT
content.  The virtualhost which serves RT listens only on port 443.

I suppose there's a possibility that RT just doesn't like that kind of
thing, but I still don't see how any of this would cause RT to redirect
to an http URL after someone has logged into the site.

I'll keep poking at it.  Maybe I do need to set WebBaseURL or WebURL,
though the documentation explicitly says that I shouldn't need to do so.

 - J<


Re: [rt-users] Keeping RT URLs off of port 80

2015-09-23 Thread Matt Brennan
Someone may later say this is incorrect, but in my config, my web port is
still 80. I have:

Set($WebBaseURL,
'https://'
. RT->Config->Get('WebDomain')
);

Then I used Apache mod_rewrite:

RewriteEngine On
RewriteCond %{SERVER_PORT} !^443$
RewriteRule ^.*$ https://rt.domain.com/%{REQUEST_URI} [L,R]


On Wed, Sep 23, 2015 at 3:50 PM, Jason L Tibbitts III 
wrote:

> I've just completed a migration from our ancient RT 3.8.8 install to a
> shiny new 4.2.12 install (using the Fedora packages).  Everything went
> smoothly except for a few Selinux issues (relating to a domain
> transition between the MTA and rt-mailgate) which I'm working out with
> the Fedora selinux folks.
>
> There's one issue which I've not yet manage to figure out, however.  I'm
> afraid it must be a FAQ but I can't find any solution which applies.  My
> web server is configured to redirect any http access to the
> corresponding https: URL and RT itself is only configured to use port
> 443.  However, immediately after login, RT itself issues a redirect that
> sends the user to an http: URL.  This is of course immediately directed
> back to https: by the web server, but when that happens I see the
> following:
>
> [warning]: The requested port (80) does NOT match the configured WebPort
> (443).  Perhaps you should Set($WebPort, 80); in RT_SiteConfig.pm,
> otherwise your internal links may be broken.
> (/usr/share/perl5/vendor_perl/RT/Interface/Web.pm:1308
>
> So far this is merely annoying; everything seems to function properly.
> But I simply cannot figure out any way to keep RT from redirecting the
> user to an http: URL after login.  I've played with
> $CanonicalizeRedirectURLs and $WebBaseURL but they seem to make no
> difference in this case.  $WebPort is set to 443 as indicated in the
> message.
>
> Is there some magical configuration setting I'm missing, or have I
> perhaps messed something else up?
>
>  - J<
>


[rt-users] Keeping RT URLs off of port 80

2015-09-23 Thread Jason L Tibbitts III
I've just completed a migration from our ancient RT 3.8.8 install to a
shiny new 4.2.12 install (using the Fedora packages).  Everything went
smoothly except for a few Selinux issues (relating to a domain
transition between the MTA and rt-mailgate) which I'm working out with
the Fedora selinux folks.

There's one issue which I've not yet manage to figure out, however.  I'm
afraid it must be a FAQ but I can't find any solution which applies.  My
web server is configured to redirect any http access to the
corresponding https: URL and RT itself is only configured to use port
443.  However, immediately after login, RT itself issues a redirect that
sends the user to an http: URL.  This is of course immediately directed
back to https: by the web server, but when that happens I see the
following:

[warning]: The requested port (80) does NOT match the configured WebPort (443). 
 Perhaps you should Set($WebPort, 80); in RT_SiteConfig.pm, otherwise your 
internal links may be broken. 
(/usr/share/perl5/vendor_perl/RT/Interface/Web.pm:1308

So far this is merely annoying; everything seems to function properly.
But I simply cannot figure out any way to keep RT from redirecting the
user to an http: URL after login.  I've played with
$CanonicalizeRedirectURLs and $WebBaseURL but they seem to make no
difference in this case.  $WebPort is set to 443 as indicated in the
message.

Is there some magical configuration setting I'm missing, or have I
perhaps messed something else up?

 - J<


[rt-users] RT Not Sending Autoreply E-Mails On Ticket Creation Via E-Mail

2015-09-23 Thread Tim Gustafson
I have an RT 4.2.11 instance that is not sending autoreply messages
when tickets are created via e-mail.  If you create a ticket on behalf
of a user through the web form, an autoreply is sent.  It's only when
a ticket is created via e-mail that an autoreply is not sent.  The
Sendmail log file shows no attempt to send an autoreply, and no
outbound e-mail is recorded in the ticket's transaction history.

My global scrips screen is attached.  There are no queue-specific scrips.

What would cause RT to not send autoreplys to requestors when tickets
are created via e-mail?

-- 

Tim Gustafson
t...@ucsc.edu
831-459-5354
Baskin Engineering, Room 313A


[rt-users] Change default queue in "Quick ticket creation" area

2015-09-23 Thread Russell Jones

Hi all,

How do I change the default queue that is selected in the quick ticket 
creation area? Doing some research led me to the "Default queue" drop 
down in user preferences, and this does indeed change the queue that is 
selected by default next to the "New ticket in" button at the top right, 
but it does not change the selected queue for the "Quick Ticket 
Creation" box.


Any help is greatly appreciated. Thanks!