The last few nights I've been practicing upgrading from OTRS 2.3.3 to 2.4.9, and I had been getting stuck at the same place each time. I typed this up as I worked out to a solution, so maybe this post will help someone in the future. I am trying to run the "migration script", the instructions say to run the script "as OTRS user". http://doc.otrs.org/2.4/en/html/x834.html Based on Robert Kehl's helpful post from long ago... http://www.mail-archive.com/otrs@otrs.org/msg04238.html ...I used su - otrs and successfully became otrs but when I run the script I get the following error... SuSEOTRS:/home/wes # su - otrs otrs@SuSEOTRS:~> whoami otrs otrs@SuSEOTRS:~> /opt/otrs/scripts/DBUpdate-to-2.4.pl Start migration of the system... ERROR: OTRS-DBUpdate-to-2.4-1 Perl: 5.10.0 OS: linux Time: Tue Nov 23 21:53:41 2010 Message: Can't remove shm for log: Operation not permitted Traceback (4730): Module: Kernel::System::Log::CleanUp (v1.62) Line: 254 Module: Kernel::System::Log::new (v1.62) Line: 105 Module: /opt/otrs/scripts/DBUpdate-to-2.4.pl (v1.8.2.1) Line: 63 Bad address at /opt/otrs/Kernel/System/Log.pm line 230. otrs@SuSEOTRS:~> Finally I read this post... http://lists.otrs.org/pipermail/otrs/2009-April/026353.html ...maybe not for the first time, but I finally realized I should have apache2 stopped. I turned off apache and then this command finally worked... otrs@SuSEOTRS:~> /opt/otrs/scripts/DBUpdate-to-2.4.pl Start migration of the system... NOTICE: Rebuild config... done. NOTICE: Clean up old cache files... done. NOTICE: Migrate queue based customer notifications... done. Migration of the system completed! otrs@SuSEOTRS:~> -- Wes Plate Automatic Duck, Inc. http://www.automaticduck.com