Re: [rt-users] Warning messages after upgrade to rt 4.2.10
On 27/02/2015 09:21, Arkady Glazov wrote: Hi, Today i upgrade my RT 4.2.9 to 4.2.10 successfully. But now i have in appache & rt logs next warning messages: [10373] [Fri Feb 27 09:00:02 2015] [info]: Using internal Perl HTML -> text conversion (/opt/rt4/sbin/../lib/RT/Interface/Email.pm:1818) from rt-email-dashbords, rt-fulltext-indexer scripts. How i can suprress it? Put: Set($LogToSTDERR, "warn"); In your site config. -- Best regards, Arkady Glazov http://globster.ru -- Regards, Giles Coochey, CCNP, CCNA, CCNAS NetSecSpec Ltd +44 (0) 8444 780677 +44 (0) 7584 634135 http://www.coochey.net http://www.netsecspec.co.uk gi...@coochey.net smime.p7s Description: S/MIME Cryptographic Signature
Re: [rt-users] error 401 Credentials required
On 07/11/2014 15:58, Payam Poursaied wrote: curl -u root:Nasim1414 http://192.168.1.201/rt/REST/1.0/ticket/33/comment but get me error : RT/4.0.19 401 Credentials required what to do? If that password is used elsewhere, then the first thing you should do is change it. smime.p7s Description: S/MIME Cryptographic Signature
Re: [rt-users] Incoming email address
On 19/05/2014 14:40, Flynn, Peter wrote: I am setting up a test instance of rt as part of our investigation of a replacement for our current helpdesk system. So far it's up and running nicely on a virtual host under Apache, and I've been adding some test users and queues. I can't find any documentation on how best to set up the email responder. There are descriptions of the variables in the docs, but there doesn't seem to be any description of what the receiver email address is or how/where to configure it. The server has sendmail configured, but what address would a customer send a query to? ///Peter Take a look at rt-mailgate: https://www.bestpractical.com/docs/rt/4.2/rt-mailgate.html -- Regards, Giles Coochey, CCNP, CCNA, CCNAS NetSecSpec Ltd +44 (0) 8444 780677 +44 (0) 7983 877438 http://www.coochey.net http://www.netsecspec.co.uk gi...@coochey.net smime.p7s Description: S/MIME Cryptographic Signature -- RT Training - Dallas May 20-21 http://bestpractical.com/training
Re: [rt-users] articles RTFM WYSIWYG
On 26/02/2014 16:19, Support wrote: Anyone, Any hints, direction, help, links anything trying to put a WYSIWYG to new create articles.. I will be appreciated if any one guide me to the right direccion rt 4.2.1 centos 6 Hi David, Sorry I can't help you, but I would like to have this functionality as well!! rt 4.2.3 centos 6.5 -- Regards, Giles Coochey, CCNP, CCNA, CCNAS NetSecSpec Ltd +44 (0) 8444 780677 +44 (0) 7983 877438 http://www.coochey.net http://www.netsecspec.co.uk gi...@coochey.net smime.p7s Description: S/MIME Cryptographic Signature -- RT Training London, March 19-20 and Dallas May 20-21 http://bestpractical.com/training
[rt-users] UNSUBSCRIBE
Re: [rt-users] Incompatibility with IE11?
On 27/11/2013 09:37, Rubén Sánchez-Pascuala Pérez wrote: Hi This is my configuration: Server: CentOS 6.4 (64x) / Apache 2 / mod_perl Request Tracker 4.2.0 Client: Windows 7 Ultimate (x64) Internet Explorer 11.0.9600.16428 When I clickreply on a ticket, it does nothing. If I do this with Firefox or Chrome, works perfectly. Is there some kind of incompatibility? Have you tried 4.2.1 ? Various IE bugs fixed in 4.2.1 -- Regards, Giles Coochey, CCNP, CCNA, CCNAS NetSecSpec Ltd +44 (0) 8444 780677 +44 (0) 7983 877438 http://www.coochey.net http://www.netsecspec.co.uk gi...@coochey.net smime.p7s Description: S/MIME Cryptographic Signature
Re: [rt-users] errors in upgrade to rt-4.2
On 14/09/2013 19:09, Ruslan Zakirov wrote: On Sat, Sep 14, 2013 at 5:28 PM, Xin, Qiao <mailto:q...@cio.sc.gov>> wrote: Thank both of you very much for the reply. According to the reply from Kevin: "I'm confused how you're running 4.0.5 with RTIR 2.6.1, since that version isn't compatible with RT 4 (RTIR 3.0.0 is the compatible version)." After I upgrade RT to 4.0.x but before I upgrade RTIR, I will end up with RT 4.0.x with RTIR 2.6.1. Will the system still be able to run? How can tell the RT part should be able to do basic things, RTIR has some hooks inserted into RT, but not so many to prevent everything from working. However, you should not use such setup in production. RT upgrade works fine? You can bring up RT web interface and play around with read only parts. Anyway, upgrades across major versions should be performed with test runs, do test run, document every step, play with every aspect important to you, repeat all steps during cut over. And as far as I am aware RT4.2 is still Beta, well - release candidate, but still Beta. Therefore you shouldn't really be upgrading to it as moving from release candidate to a higher version is not guaranteed possible. -- Regards, Giles Coochey, CCNP, CCNA, CCNAS NetSecSpec Ltd +44 (0) 8444 780677 +44 (0) 7983 877438 http://www.coochey.net http://www.netsecspec.co.uk gi...@coochey.net smime.p7s Description: S/MIME Cryptographic Signature -- RT Training in New York, October 8th and 9th: http://bestpractical.com/training
Re: [rt-users] Two Annoying Messages in the logs
On 26/07/2013 14:09, Kevin Falcone wrote: On Fri, Jul 26, 2013 at 01:23:32PM +0100, Giles Coochey wrote: I run RT (upgraded to 4.0.15 today), but this is a small issue I've always had with my set up. I always get the following in my apache errorlogs: You should get these once per process startup, yes? [Fri Jul 26 09:05:14 2013] [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/local/rt/sbin/../lib/RT/Interface/Web.pm:1232) [Fri Jul 26 09:05:14 2013] [warning]: The requested path (/ticket/) does NOT match the configured WebPath (/ticket). Perhaps you should Set($WebPath, '/ticket/'); in RT_SiteConfig.pm, otherwise your internal links may be broken. (/usr/local/rt/sbin/../lib/RT/Interface/Web.pm:1248) The first one is because RT sits behind a reverse proxy which strips SSL, therefore WebPort 443 is correct, as is setting the port to 80 locally in the web server configuration. So the warning is wrong in this case. The second one seems to be required, rt moans about the configured WebPath missing the trailing slash, but I seem to remember that I needed to configure it this way to correctly get the reverse proxy to fix up the links in responses. Would be nice to somehow eliminate these warnings from a future release or RT. What are you using to reverse proxy? These warnings imply that you've got something which isn't passing any headers that we would expect. In particular, if we detect proxying, we don't do the second check. OK, but I should still expect the warnings at startup? I've done a packet capture and noted that I have all these headers set: X-Forwarded-For: (a comma seperated list of IPs, original client and the squid server) X-Forwarded-Host: (a hostname matching the proxying host reverse lookup) X-Forwarded-Server: (a hostname matching the proxying host reverse lookup) I'm guessing that at startup there have not been any requests, so I will still get the warnings? -- Regards, Giles Coochey, CCNP, CCNA, CCNAS NetSecSpec Ltd +44 (0) 8444 780677 +44 (0) 7983 877438 http://www.coochey.net http://www.netsecspec.co.uk gi...@coochey.net smime.p7s Description: S/MIME Cryptographic Signature
Re: [rt-users] Two Annoying Messages in the logs
On 26/07/2013 14:09, Kevin Falcone wrote: On Fri, Jul 26, 2013 at 01:23:32PM +0100, Giles Coochey wrote: I run RT (upgraded to 4.0.15 today), but this is a small issue I've always had with my set up. I always get the following in my apache errorlogs: You should get these once per process startup, yes? Yes. What are you using to reverse proxy? These warnings imply that you've got something which isn't passing any headers that we would expect. In particular, if we detect proxying, we don't do the second check. You can see the relevant code and headers here: https://github.com/bestpractical/rt/blob/stable/lib/RT/Interface/Web.pm#L1226 -kevin OK, For info: 1. squid strips the SSL and does caching, it then gets passed to... 2. apache reverse proxy which does other things. I expect that they're both set up to not insert FORWARDED_FOR headers... I will check. Thanks for the info, I can probably fix that. -- Regards, Giles Coochey, CCNP, CCNA, CCNAS NetSecSpec Ltd +44 (0) 8444 780677 +44 (0) 7983 877438 http://www.netsecspec.co.uk giles.cooc...@netsecspec.co.uk -- Regards, Giles Coochey, CCNP, CCNA, CCNAS NetSecSpec Ltd +44 (0) 8444 780677 +44 (0) 7983 877438 http://www.coochey.net http://www.netsecspec.co.uk gi...@coochey.net smime.p7s Description: S/MIME Cryptographic Signature
[rt-users] Two Annoying Messages in the logs
Hi, I run RT (upgraded to 4.0.15 today), but this is a small issue I've always had with my set up. I always get the following in my apache errorlogs: [Fri Jul 26 09:05:14 2013] [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/local/rt/sbin/../lib/RT/Interface/Web.pm:1232) [Fri Jul 26 09:05:14 2013] [warning]: The requested path (/ticket/) does NOT match the configured WebPath (/ticket). Perhaps you should Set($WebPath, '/ticket/'); in RT_SiteConfig.pm, otherwise your internal links may be broken. (/usr/local/rt/sbin/../lib/RT/Interface/Web.pm:1248) The first one is because RT sits behind a reverse proxy which strips SSL, therefore WebPort 443 is correct, as is setting the port to 80 locally in the web server configuration. So the warning is wrong in this case. The second one seems to be required, rt moans about the configured WebPath missing the trailing slash, but I seem to remember that I needed to configure it this way to correctly get the reverse proxy to fix up the links in responses. Would be nice to somehow eliminate these warnings from a future release or RT. -- Regards, Giles Coochey, CCNP, CCNA, CCNAS NetSecSpec Ltd +44 (0) 7983 877438 http://www.coochey.net http://www.netsecspec.co.uk gi...@coochey.net smime.p7s Description: S/MIME Cryptographic Signature
Re: [rt-users] Tickets in a Nice Print Format
On 04/01/2013 17:12, Kevin Falcone wrote: On Fri, Jan 04, 2013 at 12:22:33PM +, Giles Coochey wrote: I would like to be able to Print or PDF tickets in a nice format. Is there a good way to do this? I currently print the ticket pages from a browser, but have various rendering issues and, in short, it isn't all that pretty. I also notice that Reminders for tickets don't appear to be on the print outs / PDFs. You forgot to mention your RT version. More recent versions ship with a print.css that provides a lot of improvements. -kevin 4.0.8 How precisely does that get used - is it automatic? -- Regards, Giles Coochey, CCNA, CCNAS NetSecSpec Ltd +44 (0) 7983 877438 http://www.coochey.net http://www.netsecspec.co.uk gi...@coochey.net smime.p7s Description: S/MIME Cryptographic Signature
[rt-users] Tickets in a Nice Print Format
I would like to be able to Print or PDF tickets in a nice format. Is there a good way to do this? I currently print the ticket pages from a browser, but have various rendering issues and, in short, it isn't all that pretty. I also notice that Reminders for tickets don't appear to be on the print outs / PDFs. -- Regards, Giles Coochey, CCNA, CCNAS NetSecSpec Ltd +44 (0) 7983 877438 http://www.coochey.net http://www.netsecspec.co.uk gi...@coochey.net smime.p7s Description: S/MIME Cryptographic Signature
Re: [rt-users] emails on ticket updates not being sent in 4.0.6
On 23/05/2012 12:01, Niall Wilson wrote: Hi, I've just updated to 4.0.6 and ticket updates are no longer being emailed. This does not seem to be related to the noted FCGI.pm problem as (1) I'm using mod_perl and (2) I updated the installed FCGI to v 0.74 just in case. If I revert to 4.0.5 email works fine. : `/usr/sbin/sendmail -oi -t` exited with code 1 (/opt/rt4/sbin/../lib/RT/Interface/Email.pm:465) [Wed May 23 10:52:07 2012] [crit]:: Could not send mail with command `/usr/sbin/sendmail -oi -t`:: `/usr/sbin/sendmail -oi -t` exited with code 1 at /opt/rt4/sbin/../lib/RT/Interface/Email.pm line 466. Interesting - I've just upgraded to 4.0.6 from 4.0.5 and just tested this (I'm on CentOS 6.2, with mod_perl setup). I couldn't replicate your issue. It seems to me that the /usr/sbin/sendmail command failed - have you checked this? Permissions, command line options etc... smime.p7s Description: S/MIME Cryptographic Signature
Re: [rt-users] Getting Request Tracker to stick to HTTPS
On 2012-05-17 13:47, Ruslan Zakirov wrote:
On Wed, May 16, 2012 at 8:50 PM, Matt Brennan
wrote:
This is how I do this. In my RT_SiteConfig.pm I have:
Set($WebBaseURL,
'https://'
. RT->Config->Get('WebDomain')
);
All traffic on my RT instance is done via HTTPS. I also have an
Apache
rewrite rule in case someone navigates to HTTP instead (as users
often do).
You don't need this. WebDomain, WebPort and WebPath is enough in most
cases.
As documentation in versions says you set WebBaseURL or other options
only
in very specific cases, for example when you want to server RT over
HTTPS
from port 1.
Topic starter needs CanonicalizeRedirectURLs option. He uses reverse
proxy. By
default for redirects RT guesses a few bits from ENV variables (set
by
web server).
This allows you to run the same RT instance with multiple entry
points. However,
if you have something in front of RT then this guessing doesn't work.
And just to confirm, for the reverse SSL offloading proxy case the:
Set($CanonicalizeRedirectURLs, 1);
Option in RT_SiteConfig.pm works just right, my pages stay on https
throughout the session.
Re: [rt-users] Getting Request Tracker to stick to HTTPS
On 16/05/2012 17:27, Darin Perusich wrote:
On 05/16/2012 11:20 AM, Giles Coochey wrote:
How can I force RT to HTTPS?
Have you tried use mod_rewrite to rewrite the all traffic for that
virtual host to https?
Stubs of the config's for your RT virtual host. They http vhost only
needs to have the basic's defined, the rewrite rules will push
everything to https.
...
...
RewriteEngine On
RewriteCond %{SERVER_PORT} !^443$
RewriteRule ^/(.*)https://%{SERVER_NAME}/$1 [L,R=301]
...
...
Order allow,deny
Allow from all
SetHandler modperl
PerlResponseHandler Plack::Handler::Apache2
PerlSetVar psgi_app /usr/sbin/rt-server
use Plack::Handler::Apache2;
Plack::Handler::Apache2->preload("/usr/sbin/rt-server");
...
...
I can't do that, the actual RT Apache Server runs on port 80, so the
rewrite condition is always false.
The Reverse Proxy Director runs on port 8080
The Squid SSL-offload caching proxy runs on 443 & 80
So RT needed to act as if it was running on 443, but it didn't do any
SSL itself.
The problem seemed to be this setting, as mentioned by Paul.
Set($CanonicalizeRedirectURLs, 1);
Now it appears to work. If I wanted to do what you suggested I'd need to do the
equivalent in Squid config, I think.
Also, I don't mind it being available on HTTP, I just don't want it bouncing
back to HTTP if I log in with HTTPS.
smime.p7s
Description: S/MIME Cryptographic Signature
Re: [rt-users] Getting Request Tracker to stick to HTTPS
On 16/05/2012 16:26, Paul Tomblin wrote: Further reading in RT_Config suggests you may need to look at this: =item C<$CanonicalizeRedirectURLs> Set C<$CanonicalizeRedirectURLs> to 1 to use C<$WebURL> when redirecting rather than the one we get from C<%ENV>. Apache's UseCanonicalName directive changes the hostname that RT finds in C<%ENV>. You can read more about what turning it On or Off means in the documentation for your version of Apache. If you use RT behind a reverse proxy, you almost certainly want to enable this option. =cut Set($CanonicalizeRedirectURLs, 0); Thanks!!! Just tried it and that looks a lot more promising. smime.p7s Description: S/MIME Cryptographic Signature
Re: [rt-users] Getting Request Tracker to stick to HTTPS
On 16/05/2012 16:24, Paul Tomblin wrote: In RT_Config, it looks like you shouldn't even have to specify WebBaseURL - it appears to look to see if WebPort is 443 and changes it to https accordingly. Yes, it is doing that automatically (I have not specified WebBaseURL). But it reverts me to http after logging in via https On Wed, May 16, 2012 at 11:20 AM, Giles Coochey wrote: I have the following set up: Clients --> Squid SSL Offload / Caching Reverse Proxy (HTTPS--->HTTP) --> Apache Routing Proxy (HTTP) --> RT (HTTP) RT (v4.0.5) itself is configured for HTTPS: Set($WebDomain, 'www.domain.net'); Set($WebPath, '/ticket'); Set($WebPort, 443); On going to Tools --> Configuration --> System Config I see that WebBaseURL is correctly listed as https://www.domain.net So if I navigate to https://www.domain.net/ticket/ and Login then next page reverts to http... What do you think I might be missing?? How can I force RT to HTTPS? smime.p7s Description: S/MIME Cryptographic Signature
[rt-users] Getting Request Tracker to stick to HTTPS
I have the following set up: Clients --> Squid SSL Offload / Caching Reverse Proxy (HTTPS--->HTTP) --> Apache Routing Proxy (HTTP) --> RT (HTTP) RT (v4.0.5) itself is configured for HTTPS: Set($WebDomain, 'www.domain.net'); Set($WebPath, '/ticket'); Set($WebPort, 443); On going to Tools --> Configuration --> System Config I see that WebBaseURL is correctly listed as https://www.domain.net So if I navigate to https://www.domain.net/ticket/ and Login then next page reverts to http... What do you think I might be missing?? How can I force RT to HTTPS? smime.p7s Description: S/MIME Cryptographic Signature
[rt-users] How to set a custom field on a user
I have created a new RT:User object and loaded it but I cannot see how to set one of it's custom fields. There seem to be methods for Tickets but I cannot find any for Users.
[rt-users] Basic question about running a perl script in RT
apologies for the v basic nature of this question. I have written a perl script to add some users to RT. Obviously when I run it straight from the linux command line it doesn't function because it isn't running in within the instance of RT. How do I run it within RT - ie with the @INC path set so perl can find all the libraries etc?
