Migrating to EasyApache3

[VeZoZ]

Well I'm looking at migrating to having all my servers use EasyApache 3 which means Apache 2.2 can be used soon so I've been testing on a non production machine. But obviously there are some concerns so I'm looking for other peoples experiences:

1) The first conversion to easyApache 3 did your apache go down for the entire migration? I ran the first build and apache was down for close to 30 minutes when this happened. Is this the experience for everyone else?

2) Has anyone found at random the start of the build apache goes offline and is unable to come back? I've been back and forth on a ticket about this but it's a tough one to reproduce. So I'm wondering if others have seen this same thing?


3) For those who experienced issues due to the number of virtual hosts were you able to solve the problems? I heard issues about SSL breaking and the solution was to upgrade openSSL. Can anyone confirm this was indeed the fix and there hasn't been an issue since that was done


Now something more related to doing migration of configurations.

Has anyone here moved from apache modules to suPHP? Any special scripts or tips on any issues you've had come up? I know about permissions and such related to this switch. But any other special surprises? Testing only shows you so much compared to having it happen in a production environment.


Thanks in advance

[VeZoZ]

I guess everyone is the same as me not brave enough to migrate?

[cPanelDavidG]

...
3) For those who experienced issues due to the number of virtual hosts were you able to solve the problems? I heard issues about SSL breaking and the solution was to upgrade openSSL. Can anyone confirm this was indeed the fix and there hasn't been an issue since that was done

See http://www.cpanel.net/support/docs/e...n_ssl_bug.html for official documentation regarding OpenSSL issues.

Now something more related to doing migration of configurations.

Has anyone here moved from apache modules to suPHP? Any special scripts or tips on any issues you've had come up? I know about permissions and such related to this switch. But any other special surprises? Testing only shows you so much compared to having it happen in a production environment.

...

This is permissions-related: I know e107 version 0.6.10 will moan and complain about certain files not having 777 permissions. Users may take the gloomy sounding advice of e107 and change the permissions to 777 (not required) and in the process prevent that .php file from being executed (as 777 permissions return a server 500 error if executed).

Additionally, the WordPress Upgrade Plugin doesn't work well in Su environments (phpSuExec, SuPHP etc.). It dies after it converts things to have privileges above 755 (again, server 500 error). It does result in a broken WordPress, but knowing that it is running in a Su environment helps a lot with fixing those WP installs.

Additionally, the umask setting for SuPHP may cause PHP scripts that need to create files with 644 permissions to create them as 600 permissions instead of 644. The 644 permissions are generally useful when create images and other non-PHP files via PHP.

[VeZoZ]

Ok what about the first time running a rebuild on the new apache system. I guess everyone is seeing apache go down for the entire process and it's normal or was this isolated incident when I was doing testing? That's my big concern here