suPHP to mod_ruid2 migration - any considerations?

[kevinlevin]

Hello Everyone,

Can I expect some problems if I decide to migrate my server from suPHP to mod_php + mod_ruid2, some differences maybe? Permissions problems or anything else? Maybe someone already tried it?

There is many Joomla, forum, blog sites on the server - will it be safe to just make the migration?

I will be very thankful if you share any experience. Thanks in advance.

 

[cPanelTristan]

Hello,

I would highly suggest setting up a testing machine to test out DSO + mod_ruid2 prior to making the switch to see any possible issues that you might have happen. It isn't advisable to do testing on production machines. You could always ask [email protected] for any possible short-term license for that new server for testing purposes if necessary.

Having a clone of your existing box for testing purposes is typically a great way to check how any component will function prior to going live with it.

Thanks!

 

[actived]

I have the same issue:
If I switch to DSO + Ruid2 what extra steps do I have to take and what can be expected to go wrong?

The testing server idea is a good one - However I have no idea how to test with production loads and security issues.
The Siege tool and custom wget scripts can help only so much. I wonder how big sites test new configurations.

Since mod_ruid2 has practically zero publicly available documentation (in contrast to PHP, Apache, DSO, FCGI ) I am a little worried to test it out.

Also, should we keep SuEXEC = on along with Ruid2?

Finally, if things dont work out well, will everything be fixed if we simply change back to SuPHP, SuExec=On ?

Thanks in advance.
Regards,
Dave

 

[cPanelTristan]

Hello Dave,

You can always test using Apache ab tool on a test machine to try to mimic traffic. It isn't going to be exactly the same as what your production machine does, but you could always copy over the sites to that test machine and then internally run the ab tool to see the results.

You would keep SuEXEC on with mod_ruid2.

Thanks!

 

[dalem]

The migration should be quite painless just run below in the command line

find /home/*/public_html -name "php.ini" >> /root/phpini.txt

it may take a wile depending hoe many sites you have running then convert the text from the phpini.txt to .htaccess format
most modern scripts will run with folder permissions 755 there a few that may not since you have no idea which folders will need to be fixed, Just tail your error_log and fix the permissions as you find them. If it looks like its going to overwhelm you or its going to break this terribly you can do a quick change back to SuPHP

 

[actived]

Thanks Tristan, dalem.
This gives me the courage to test out DSO+ruid2.
I'll update if anything goes wrong or it works out well

Regards,
Dave

 

[Duplika]

Feedback on people that switched to ruid2 would be useful

 

[tiff2342]

not had any problems here after going ruid2

 

[AndyB78]

Hi,

I have 3 questions:

1. When jumping from suPHP to DSO + mod_ruid2 the only thing that needs to be done is to move & convert all PHP directives from php.ini local to .htaccess?

2. I see in cPanel's twiki that ruid2 is not compatible with shared SSL certificated. What would stop working in this case?

For instance https://site1.com:2083 and https://site2.com:2083 would be on a (self signed) shared SSL certificate and would stop working? Could we then access secure cPanel on https://hostname.com:2083 instead?
Anything else? Like SSL/TLS mail (used on ports 995, 993 and 465)?

3. Additionally has there been any progress or conclusion over the EasyApache installed DSO + ruid2 + mod_security issue?

Thanks!