[rt-users] centos OS upgrade broke RT 3.8.2

[Jeff Blaine]

On 3/19/2012 1:54 PM, testwreq wreq wrote:
> What mime_name should I be looking for?

None.

I guess I was too terse.

CentOS "upgraded" your Perl "Encode" module for you and
the version that RH and CentOS push out breaks RT.  The
version they push out (which breaks things) is lacking
an attribute or function called mime_name.  You don't
need to know that to fix it, I am only telling you so
that if you see "mime_name" mentioned in an error some
time, you will have some context for it.

To fix, just do this:

     perl -MCPAN -e "install Encode"

> On Mon, Mar 19, 2012 at 1:47 PM, Jeff Blaine <jblaine at kickflop.net
> <mailto:jblaine at kickflop.net>> wrote:
>
>     On 3/19/2012 1:34 PM, testwreq wreq wrote:
>
>         Hi
>         I upgraded centos from 5.5 to 5.8 release on my development
>         server. I
>         cannot get RT to work. My RT installation is under data/rt3
>         folder. The
>         document rool is .../share/html; When we try to access the RT
>         host name
>         on the browser, it does not reach the index.html file location
>         in the
>         document root of RT, bur instead tries to open some file and is
>         looking
>         for a filetype to open it with
>         I ran ./rt-test-dependencies --with-modperl1 on both development and
>         production. there are following things missing on both
>           Apache::Request...MISSING
>         CORE missing dependencies:
>                  Encode >= 2.13...MISSING
>                          Encode version 2.13 required--this is only
>         version 2.12
>         However, the production centos  is not updgraded and it is
>         working. I
>         don't get any errors in the error log. Could anyone help us to
>         find what
>         the problem could be?
>         thanks much:)
>
>
>     perl -MCPAN -e "install Encode"
>
>     Red Hat / CentOS updates nearly always screw up something with
>     the "Encode" that RT expects.  The RH or CentOS one lacks mime_name
>     somewhere.
>
>