Re: [otrs] Problem after upgrading from from 2.0 beta2 to 2.0 beta4

13 Jul 2005

      Yes, I had seen this in the upgrade script.  I was going to go through 
the script and run the things that I found were not already setup.  Then 
I remembered the -f which just ignores errors like "table exists".  This 
way it only made changes to what still needed changes.

The only other problem I ran into was after running the SetPermissions 
script.  I saw errors in my mail.log file about procmail[9911]: 
Suspicious rcfile.  This was being caused by the otrs dir being set to 
775.  Changed to 755 and now everything seems to be working fine.

Thank you all for such a great product.

Ken Kilgore
----------------------------------------------
When life hands you lemons just grab the salt and pass the Tequila.

Bryan Fullerton wrote:
...
On 7/13/05, Ken Kilgore  wrote:
...
OK, I have fixed this problem.  I ran DBUpdate-to-2.0.mysql.sql with a
-f.  This allowed it to run and ignore the errors.  All looks good so far.
...
From the bottom of the 2.0b4 Changes:
o added ticket free time feature - take care, you need to
 alter the ticket table:
  ALTER TABLE ticket ADD freetime1 DATETIME;
  ALTER TABLE ticket ADD freetime2 DATETIME;
If you don't do that update then the error you reported will occur and
OTRS will not work. At all. (which wasn't entirely clear in the
Changes, IMHO)
You effectively did the update by re-upgrading the entire schema,
which should be otherwise harmless I think.
Bryan
_______________________________________________
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
Support oder Consulting für Ihr OTRS System?
=http://www.otrs.de/