On Feb 18, 2011, at 9:45 PM, Jesse Vincent wrote:
>
> It sure looks like something went wrong during your upgrades, as a
> "Lifecycle" column should have been added by the 3.9.7 upgrade script. Do you
> still have a log?
Jesse,
I think I figured it out.
I had been using UPGRADING.mysql and README as my principal stepwise guide.
Line 3 of UPGRADING.mysql got me to 3.7.87.
I'm not sure what lines 4,5,6 accomplish exactly but I assumed they got me
completely current (did all the rest). But clearly the schema was missing a lot
of stuff.
On a hunch, I re-ran:
/opt/rt4/sbin/rt-setup-database --dba root --prompt-for-dba-password
--action upgrade
with a start release of 3.7.87 and no end (apply all updates) and I have a much
healthier RT now. In fact, I can't find a single darn thing wrong with it!!
Very sexy new look. ;-)
(a little while later ....)
Well maybe I can find one thing ... I'm not able to get mailgate working any
longer:
Feb 18 21:59:03 rt postfix/local[13847]: 052E6C064D:
to=<[email protected]>, relay=local, delay=0.39,
delays=0.07/0/0/0.32, dsn=4.3.0, status=deferred (temporary failure. Command
output: An Error Occurred ================= 302 Found )
I'm not sure if you can hand-crank mailgate or not, but trying, I see:
[root@rt postfix]# /opt/rt4/bin/rt-mailgate --queue sales --action comment
--url http://rt4.ifax.com/ --debug
test
.
/opt/rt4/bin/rt-mailgate: temp file is '/tmp/D8IMPShIFr/6difOpAIKD'
/opt/rt4/bin/rt-mailgate: connecting to
http://rt4.ifax.com//REST/1.0/NoAuth/mail-gateway
An Error Occurred
=================
302 Found
/opt/rt4/bin/rt-mailgate: undefined server error
Which seems to be the same error as postfix was getting.
Apache log says:
[Fri Feb 18 22:06:32 2011] [error] Your request path is
'/1.0/NoAuth/mail-gateway' and it doesn't match your Location(Match)
'/opt/rt4/share/html/'. This should be due to the configuration error. See
perldoc Plack::Handler::Apache2 for details.
Thoughts?
-d