I am running mod_perl 2. rt3 is not running. It's something from the old
RT_SiteConfig.pm. It's probably from some options that are not enabled or
are now deprecated. Once I just did that, I restarted the server and the
errors went away. So I guess the real answer is that you can use the
RT_Si
On Fri, Nov 18, 2011 at 01:15:49PM -0800, Jared Griffith wrote:
>I have switched over to the rt4 install that was not installed over rt3,
> and I am still
>getting those errors when restarting apache with a so far, slightly
> modified RT_SiteConfig.pm
Show your apache config and the erro
I have switched over to the rt4 install that was not installed over rt3,
and I am still getting those errors when restarting apache with a so far,
slightly modified RT_SiteConfig.pm
On Fri, Nov 18, 2011 at 11:17 AM, Alex Vandiver wrote:
> On Fri, 2011-11-18 at 11:07 -0800, Jared Griffith wrote:
>
On Fri, 2011-11-18 at 11:07 -0800, Jared Griffith wrote:
> Can I use the same RT_SiteConfig.pm from the 3 install?
Yes, though you will want to skim through the new RT_Config.pm to ensure
that there are no new configuration variables that you should be
setting.
- Alex
RT Training Sessio
Can I use the same RT_SiteConfig.pm from the 3 install?
On Fri, Nov 18, 2011 at 11:03 AM, Kevin Falcone
wrote:
> On Fri, Nov 18, 2011 at 10:46:04AM -0800, Jared Griffith wrote:
> >Odd number of elements in anonymous hash at
> /home/jared/rt-4.0.4/sbin/../lib/RT/Config.pm line
> >1071.
> >
On Fri, Nov 18, 2011 at 10:46:04AM -0800, Jared Griffith wrote:
>Odd number of elements in anonymous hash at
> /home/jared/rt-4.0.4/sbin/../lib/RT/Config.pm line
>1071.
>Use of uninitialized value $_[8] in anonymous hash ({}) at
>/home/jared/rt-4.0.4/sbin/../lib/RT/Config.pm line 1
users@lists.bestpractical.com
Subject: [rt-users] Upgrade from 3.6.11 to 4.0.4 More Errors
Here's the entire situation.
I have been tasked with migrating and upgrading our rt system to a new system,
complete with MySQL 5, CentOS 6, and all the latest and greatest. At this
point I have followed the READ
Here's the entire situation.
I have been tasked with migrating and upgrading our rt system to a new
system, complete with MySQL 5, CentOS 6, and all the latest and greatest.
At this point I have followed the README and the UPGRADING.mysql
documentation and followed everything there. When running m
