Upgrade path confirmation (2nd set of eyes)

[ptay]

Hi,
I wanted to get a confirmation of this upgrade path before I start any actual work. This will all be done on a test environment.

Here is starter system:
OTRS 3.2.5 on RHEL5.6 with PERL 5.8.8 and MySQL 5.5.40.

Temporary setup:
CentOS6.6 system with Perl 5.10.1 and MySQL 5.5.40. Install OTRS 3.2.5.

Backup OTRS 3.2.5 on RHEL5.6 and restore OTRS 3.2.5 on CentOS6.6.

On CentOS 6.6 upgrade 3.2.5 to 3.3.1. Then upgrade 3.3.1 to 4.0.3.

RHEL 7.0 with Perl 5.16.3 and MariaDB 5.5.40. Install OTRS 4.0.3.

Backup OTRS 4.0.3 on CentOS6.6 then restore on RHEL7.0.

Final system would be RHEL 7.0 with OTRS 4.0.3 MariaDB 5.5.40 and Perl 5.16.3.

[Rooobaaat]

Please upgrade on CentOS 6.6 upgrade 3.2.5 to 3.3.11. After this upgrade 3.3.11 to 4.0.3.

Please use RHEL 6.5 or CentOS 6.5 AFAIR on RHEL 7 and CentOS 7 you don't have mod_perl for apache2.4

[Giulio Soleni]

I made some tests on CentOS 7 some time ago and I posted here my considerations.

Please note that you might also have to take care to update the db engine from MyISAM to InnoDB; you may find here some further info.

[ptay]

I made some tests on CentOS 7 some time ago and I posted here my considerations.

Please note that you might also have to take care to update the db engine from MyISAM to InnoDB; you may find here some further info.

Thanks for sharing your post. My DB engines are InnoDB. What did you end up using in your production environment instead of mod_perl?

My setup is small. We have about 40 users and probably only 2 users would be using OTRS simultaneously.

Can I simply not use mod_perl? I can install it once mod_perl supports Apache 2.4.x.

[Giulio Soleni]

Hallo,
actually I did not move my prod system on CentOS 7 and I am still on CentOS 6.x.
However since from my tests on CentOS 7 and some other installations on OpenSuSE 13.1 (which also is released upon apache 2.4) let me use mod_perl without issues.
So probably the previous issues with mod_perl have been solved.