CentOS 6.0 + Interworx

Just seeing if anybody out there is running CentOS 6 (http://www.centos.org/) and having any issue with Interworx. We’re running on 4.9 and been holding off till now to upgrade till 6.0 came out.

Any issue? Smooth Upgrade? Any recommended strategies? Would be interested to hear…

Hi Digital Jesus,

Our preliminary testing has not revealed any serious incompatibilities. We did notice on a new install that:

A) CentOS 6 now has an httpd-libs package which will block the installation of the iworx-provided httpd until it is removed

B) CentOS 6 ships with MySQL 5.1 which does not have the old-password format enabled by default. You will want to manually add

old-passwords=1

to your my.cnf file if you choose to upgrade now.

In any case we are still testing and working towards making 4.8 fully compatible with it.

Excellent, so if I understand correctly you recommend I remove HTTPd pre-upgrade, then do the upgrade, remove CentOS 6’s flavor of Httpd, then install the iworx-httpd RPM.

And for MySQL 5.1 simply add the old-passwords=1 and then it should be good to go?

[QUOTE=digitaljesus;18159]Excellent, so if I understand correctly you recommend I remove HTTPd pre-upgrade, then do the upgrade, remove CentOS 6’s flavor of Httpd, then install the iworx-httpd RPM.

And for MySQL 5.1 simply add the old-passwords=1 and then it should be good to go?[/QUOTE]

Hmm… we have not tested upgrading existing servers yet. For upgrade you may not have to do that since hypothetically rpm/yum should leave your old config files intact. I also would not know if the upgrade would blow away the existing httpd - you may be fine.

Dan,

Thank you. I’d prefer naturally not to be the guinea pig for this as this is our live server. Any idea when you guys might give an existing server an attempted upgrade and let the community know of the results?

I’ll try to see if we can get a production server moved over within the week for testing.

Dan,

We’ll happily be your guinea pigs for moving a production server over to 6.0 if a couple concerns are taken care of, shoot me a PM if y’all would be interested in that. Thanks!

Dan A.

You are a braver man than I!

Every time I move to new CentOS installs (major release 4.0, 5.0 6.0), I just move to a new server. I have the new server setup fresh with the new CentOS, then use NodeWorx migration tools to move the sites over.

I do this for two reasons:

  1. To make sure all the sites work properly on the new server before making them live
  2. Because I’m not confident in the cleanness of doing an upgrade from a 4 to 5 or a 5 to 6.

Good luck! Let us know how it goes when you try it.

Need a test dummy?

I’ve got a brand new, shiny CentOS 6 server that’s begging for a control panel… I’ve been using InterWorx on two of my other servers, and plan on using it on this just as soon as it’s released… I’d be more than happy to play test dummy if it’s needed. :smiley:

CentOS 6 fully supported, and should be ready to go with new installs. Upgrading from CentOS 5 to 6 “in place” is not recommended.

Yay!!! Thank you!!!

Now I just have to wait for my key :frowning:

Just a question: Why old-passwords=1 is needed on new servers? old-passwords are coming from the MySQL 4.0 era. Also the new mysqlnd MySQL driver for PHP does not support this.

My question to Interworx: is it REALLY needed on new servers?

[QUOTE=gerwin;19034]Just a question: Why old-passwords=1 is needed on new servers? old-passwords are coming from the MySQL 4.0 era. Also the new mysqlnd MySQL driver for PHP does not support this.

My question to Interworx: is it REALLY needed on new servers?[/QUOTE]

Unfortunately the MySQL client used by InterWorx is still from the 4.0 era due to some legacy dependencies which we are working on resolving. For the time being, yes this is required if you wish to interface with the MySQL server from the panel. If not the panel will not be able to authenticate with your MySQL server.