After upgrade to 3.8.1, can't view ticket details

Hey all,

CentOS 4.5
RequestTracker 3.8.1
Apache 1.3.37

I upgraded our installation from 3.6.3 to 3.8.1 over the weekend after
the users had tested it for about a week. The upgrade went without a
hitch, but now the users are coming to me with a major problem:

If a user clicks on a queue, then clicks on a ticket they are given
either a blank page (FireFox) or a standard “Internet Explorer cannot
display the webpage” error. What makes this worse is that the session
is now ruined. The user cannot click ‘back’ as they are prompted with
the same error. Even if the user tries to type the login page in the
browser, they are shown the same error. The only way to get back to the
login page is to clear out all the cached information like cookies.

Does this have anything to do with the previous post on 8/19 - “RT38 not
maintaining authentication (with RT::Authen::ExternalAuth)”

Or has anyone experienced this?

Thanks,

Adam

Adam Engel
Specialized Business Software
IT Manager
440.542.9145
adamengel@specializedbusinesssoftware.com

I would like to make an addition to this

I looked in the rt-error_log file and found a lot of OOM errors. The
server has at least 400MB of swap left. I guess Ill try increasing the
memory within VMWare. Maybe Apache is running out of available memory

Out of memory!
Callback called exit.
Out of memory!
Callback called exit.
Out of memory!
Callback called exit.
Out of memory!
Callback called exit.
Out of memory!
Callback called exit.
Out of memory!
Callback called exit.On 8/25/2008 2:14 PM, Adam Engel wrote:

Hey all,

CentOS 4.5
RequestTracker 3.8.1
Apache 1.3.37

I upgraded our installation from 3.6.3 to 3.8.1 over the weekend after
the users had tested it for about a week. The upgrade went without a
hitch, but now the users are coming to me with a major problem:

If a user clicks on a queue, then clicks on a ticket they are given
either a blank page (FireFox) or a standard “Internet Explorer cannot
display the webpage” error. What makes this worse is that the session
is now ruined. The user cannot click ‘back’ as they are prompted with
the same error. Even if the user tries to type the login page in the
browser, they are shown the same error. The only way to get back to
the login page is to clear out all the cached information like cookies.

Does this have anything to do with the previous post on 8/19 - “RT38
not maintaining authentication (with RT::Authen::ExternalAuth)”

Or has anyone experienced this?

Thanks,

Adam

Adam Engel
Specialized Business Software
IT Manager
440.542.9145
adamengel@specializedbusinesssoftware.com


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Adam Engel
Specialized Business Software
IT Manager
440.542.9145
adamengel@specializedbusinesssoftware.com