Many thanks to the testers of the 1.8.0 release candidate! By now, the folks who were testing have already had their servers automatically updated to the release version, along with a few other supporting packages, via NodeWorx’s update system.
For everyone still running InterWorx-CP 1.7.1 - check for the version number under “Server Setup” in NodeWorx - this new version revamps how the update system works. As a result, the upgrade from InterWorx-CP 1.7.1 to InterWorx-CP 1.8.0 must be performed manually, by logging into your server and issuing a couple commands as the root user. Future updates will be automatic (like they were for the 1.8.0 testers this time).
As of version 1.8.0, we have made a few key decisions regarding software updates. First of all, we will now be bundling the latest versions of key hosting related software for InterWorx-CP users. So we now provide all the RPMs for this software, including:
Apache Web Server: 2.0.50
MySQL Database: 4.0.20
PHP: 4.3.8
When you update your server to InterWorx-CP 1.8.0, these new Apache, MySQL, and PHP versions will automatically be installed.
We will continue to provide updated packages to these, and the other key hosting related packages, and we’re committed to updating the packages prompty - example: MySQL 4.0.21 was released yesterday, and it is already in testing.
As of this release, InterWorx-CP offically runs on the following distributions:
Red Hat 9.0
Red Hat Enterprise Linux 2.x, 3.x
CentOS 3.x
White Box Linux 3.x
Fedora Core 1
Fedore Core 2
There are also some new features in this version, including:
Themes - InterWorx-CP now comes with three default themes for you to choose from, and allows you to customize the NodeWorx and SiteWorx interface however you like.
SiteWorx SSL - A web based interface to assist in setting up SSL certificates.
New phpMyAdmin version
And finally, a number of small interface tweaks and bug fixes (thanks to all who reported them!) to make your life easier.
Thanks again to all the InterWorx-CP users, and especially to the 1.8.0 testers. This is our biggest update thus far, and we have LOTS planned for the future. Stay tuned
Thanks Paul, as one of the beta testers (now running the final code) I am very impressed with it. I advise anybody running the old code to upgrade, even though it has bo be done by hand. It’s really not that hard (just running a ssh script) and requires no real input from the user.
I’ve done about 10 upgrades and I’ve had troubles with 2. The only problems I’ve seen so far is with “extra” apache modules being loaded that aren’t compatible with the new Apache 2.0.50 that is distributed with iworx-cp.
The 2 I’ve seen probs with are mod_jk2 (java support) and mod_security (basic security support). We provide an updated mod_security here on the site and for mod_jk2 a recompile should fix things.
I’m sure it’ll be fine. The apache with 1.8 is vanilla. We made a few small mods to the config files but nothing unorthodox. If you run into problems just post here and we’ll try to help out. I’m curious to see it working myself :).
The email sent from the server on upgrade failed, just thought I’d let you know.
Justin
Hi. This is the qmail-send program at server1.horn.com.
I’m afraid I wasn’t able to deliver your message to the following addresses.
This is a permanent error; I’ve given up. Sorry it didn’t work out.
<180upgrade@interworx.info>:
Connected to 69.56.137.23 but sender was rejected.
Remote host said: 552 sorry, your envelope sender domain must exist (#5.7.1)
Well I ran the update script and everything went smoothly except this:
ERROR 1054 at line 2: Unknown column ‘Create_tmp_table_priv’ in ‘field list’
Stopping MySQL: [FAILED]
Running the /etc/init.d/mysqld script won’t stop mysql now. I ended up kill -9’ing the process and starting it up and everything is functioning fine, but obviously I’d like to know how to fix that
I’ve noticed this on 1 or 2 other servers where mysqld didn’t want to exit. It’s due to a bug in the init.d script for MySQL which is fixed in tonight’s release (see here: http://interworx.info/forums/showthread.php?t=181).
To fix the “uknown column” problem just copy / paste the following into a root shell session:
rtpass=`grep rootdsn /home/interworx/iworx.ini | sed 's/rootdsn="mysql:\/\/iworx://' | sed 's/@localhost\/mysql"//'`
/usr/bin/mysql_fix_privilege_tables --user=iworx --password=$rtpass
echo "use mysql;
update user set Create_tmp_table_priv='N', Lock_tables_priv='N' where User != 'root' and User != 'iworx';
flush privileges;" | mysql -u iworx -p$rtpass
It just runs the last bit of code that does the MySQL table fixes needed for the MySQL 3.x to 4.x upgrade.
NOTE, you will see “errors” but the output of the mysql tool states that you can safely ignore them. The will be of the type:
ERROR 1060 at line 1: Duplicate column name 'Grant_priv'
ERROR 1060 at line 2: Duplicate column name 'Grant_priv'
ERROR 1060 at line 3: Duplicate column name 'Grant_priv'
among some others (usually complaining of duplicate columns)
Thanks Chris. I just updated httpd, proftpd, and mysqld to the latest versions with the updates and everything works properly with /etc/init.d/mysqld now. I’m happy to see all these updates lately!
Package php needs httpd-mmn = 20020628, this is not available.
Package php needs httpd-mmn = 20020628, this is not available.
Package mod_python needs httpd-mmn = 20020628, this is not available.
Package mod_python needs httpd-mmn = 20020628, this is not available.
Package perl-DBD-MySQL needs libmysqlclient.so.10, this is not available.
Package ucspi-tcp-toaster needs libmysqlclient.so.10, this is not available.
Package vpopmail-toaster needs libmysqlclient.so.10, this is not available.
Package courier-imap-toaster needs libmysqlclient.so.10, this is not available.
and
Restarting MySQL
Stopping MySQL: [FAILED]
Starting MySQL: [ OK ]
Yum said that : mysql-client is installed and is the latest version.
It looks like your server’s RPM database got out of whack, perhaps the server crashed or something else went wrong while it was in the middle of updating a bunch of packages. The end result was that your server was “in the middle” of updating a handful of packages. I finished the upgrade on your server manually, so you should be all set now. Your server should say InterWorx version 1.8.0 now as well - you mentioned in another thread that it still reported 1.7.1.
Hmmm I understand what you’re talking about but I can’t figure out why as my server didn’t crash during the upgrade package (both beta and final release).
The only pbm I’ve had was the MySQL that didn’t stop well.
.
