Hello -
Upgraded a test RT server from 4.0.22 to 4.2.9 yesterday. Upgrade went
smooth and I didn’t run into any real big issues.
The issue is now when logging in to RT. I get to the login just fine and I
enter my credentials. Upon hitting the Login button I immediately get
sent to a page that shows:
Not Found
The requested URL /HASH(0x7f632a4a2b98) was not found on this server.
With a URL of https://fqdn/HASH(0x7f632a4a2b98).
However, if I modify the URL to just the fqdn of my server, I am logged
in just fine to RT and all seems well. If I logout and attempt to login
again – I’ll get the same error with a different HASH number following.
The mason data cache was cleared after the upgrade.
What would cause such an error?
Thanks!
Max McGrath
Network Administrator
Carthage College
262-552-5512
mmcgrath@carthage.edu
Upgraded a test RT server from 4.0.22 to 4.2.9 yesterday. Upgrade went smooth
and I didn’t run into any real big issues.
The requested URL /HASH(0x7f632a4a2b98) was not found on this server.
With a URL of https://fqdn/HASH(0x7f632a4a2b98).
However, if I modify the URL to just the fqdn of my server, I am logged in just
fine to RT and all seems well. If I logout and attempt to login again – I’ll
get the same error with a different HASH number following.
A similar issue was caused by using older RT-Authen-ExternalAuth with
newer RTs. The version you’re upgrading from should have
exhibited the same bug (this was specific to versions prior to 4.0.8).
It’s worth checking your customizations and plugins to see if you have
stale versions around, especially if you’ve touched Login.
-kevin
Thanks!
That seems to have fixed it! I was still on version 0.10 of
RT-Authen-ExternalAuth. Got to 0.25 and the problem went away!
Thanks so much!
Max
Max McGrath
Network Administrator
Carthage College
262-552-5512
mmcgrath@carthage.eduOn Wed, Nov 26, 2014 at 1:29 PM, Kevin Falcone falcone@bestpractical.com wrote:
On Wed, Nov 26, 2014 at 10:47:13AM -0600, Max McGrath wrote:
Upgraded a test RT server from 4.0.22 to 4.2.9 yesterday. Upgrade went
smooth
and I didn’t run into any real big issues.
The requested URL /HASH(0x7f632a4a2b98) was not found on this server.
With a URL of https://fqdn/HASH(0x7f632a4a2b98).
However, if I modify the URL to just the fqdn of my server, I am logged
in just
fine to RT and all seems well. If I logout and attempt to login again
– I’ll
get the same error with a different HASH number following.
A similar issue was caused by using older RT-Authen-ExternalAuth with
newer RTs. The version you’re upgrading from should have
exhibited the same bug (this was specific to versions prior to 4.0.8).
It’s worth checking your customizations and plugins to see if you have
stale versions around, especially if you’ve touched Login.
-kevin