Error running DBUpdate-to-2.4.pl [SOLVED]

[RichardT]

Hi,

I'm in the process of upgrading from 2.2.5 to 3, luckily I have the luxury of doing this on a new server, so this is a practice run with no downtime

So far I have restored the 2.2.5 db backup onto the new server and copied the contents of /opt/otrs and verified that the system is working (picking up email from a test account, automatic reply sent, manual reply and close ticket OK). Then I followed the instructions to upgrade to 2.3.6 (from tgz), and everything was still working.

I'm in the process of upgrading to 2.4.10 and have hit a snag. The first set of database updates went OK, but when I try to run DBUpdate-to-2.4.pl I get the following error:

Code: Select all

[otrs@centos scripts]$ ./DBUpdate-to-2.4.pl
Start migration of the system...

ERROR: OTRS-DBUpdate-to-2.4-10 Perl: 5.8.8 OS: linux Time: Thu Apr 28 10:19:01 2011

 Message: Can't remove shm for log: Operation not permitted

 Traceback (16601):
   Module: Kernel::System::Log::CleanUp (v1.62) Line: 254
   Module: Kernel::System::Log::new (v1.62) Line: 105
   Module: ./DBUpdate-to-2.4.pl (v1.8.2.1) Line: 63

Bad address at /opt/otrs/Kernel/System/Log.pm line 230.
[otrs@centos scripts]$

I am logged in as otrs (su from root) and ran SetPermissions.pl before the first db update script. Can somebody help me out with this error please?

Thanks in advance,

Richard

[RichardT]

I did a google search for that error message and found this page (yes, I had already searched this forum for "Log.pm" before my original question): http://permalink.gmane.org/gmane.comp.otrs.user/32965. That person fixed the problem by stopping apache, but my apache was already stopped. However, he links to this page http://lists.otrs.org/pipermail/otrs/20 ... 26353.html which suggests using ipcs to check for shared memory segments, and I found 2 belonging to apache. I removed these using ipcrm and the script runs fine.

Just a thought, but I think the upgrade instructions could be clearer. At the start it says to stop all services, but obviously you need mysql running to do the database updates...

[randy112]

Running the upgrade sounds like a scary proposition, especially when you consider what can go wrong, but once you get the hang of it, it becomes mere routine. I’m in the process of upgrading my database too.