View Full Version : InterWorx-CP Version 1.8.0 Released
IWorx-Paul
09-11-2004, 10:23 AM
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).
Instructions for this upgrade can be viewed here:
http://updates.interworx.info/iworx/scripts/171to180.txt
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 :)
Paul
timryberg
09-12-2004, 05:25 PM
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.
IWorx-Chris
09-12-2004, 06:56 PM
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.
Chris
eDixon
09-13-2004, 07:13 PM
Any known issues w/ extra things like coldfusion? If there are, guess we will find out on tudsday night :D .
Cant wait to upgrade, just need to finish my backups before Ivan hits.
IWorx-Chris
09-13-2004, 07:15 PM
Any known issues w/ extra things like coldfusion? If there are, guess we will find out on tudsday night .
Let us know how it goes eDixon.. I think you'll be the first to try so while I'll say "there's no known issues" it doens't mean much :).
Chris
eDixon
09-13-2004, 07:19 PM
I'll say "there's no known issues" :).
Chris
... DOH!
Coldfusion's documentation says it *should* handle apache upgrades w/ o an issue, im hoping they are right. :)
IWorx-Chris
09-13-2004, 07:24 PM
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 :).
Chris
eDixon
09-14-2004, 02:01 PM
Here goes nothing (all fingers crossed :S )
I got an error...
(moved to a more approperiate thread)
http://interworx.info/forums/showthread.php?p=855&posted=1#post855
Justec
09-14-2004, 04:44 PM
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)
--- Below this line is a copy of the message.
Return-Path: <root@server1.horn.com>
Received: (qmail 23947 invoked by uid 0); 14 Sep 2004 20:00:50 -0000
Date: 14 Sep 2004 20:00:50 -0000
Message-ID: <20040914200050.23946.qmail@server1.horn.com>
From: root@server1.horn.com
To: 180upgrade@interworx.info
1.8.0 upgrade performed
IWorx-Paul
09-14-2004, 04:47 PM
No problem, that e-mail obviously isn't critical :)
Paul
eDixon
09-14-2004, 06:19 PM
After a small error w/ jRun, (answered in the link im my previous post), its running fine.
Seems to be running faster, and using up less memory.
Now to play around for a bit :D
PaulK
09-15-2004, 05:59 PM
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 ;)
IWorx-Chris
09-15-2004, 06:05 PM
Paul,
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)
Chris
PaulK
09-16-2004, 12:58 AM
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!
IWorx-Chris
09-16-2004, 01:00 AM
Check back tomorrow for a major website update :) We'll have a bunch more docs on the site later this week and into the weekend as well.
Glad it's humming again :).
Chris
pascal
09-17-2004, 07:06 PM
Hi
When I launch the script 171to180.sh
I have these messages :
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.
Is there a pbm with these messages ?
Thanks
Pascal
IWorx-Chris
09-17-2004, 07:30 PM
squalito,
There may be, can you submit your root info: https://secure.interworx.info/iworx-cp/support/rootdrop.php and I'll take a look.
Chris
pascal
09-17-2004, 08:11 PM
ok thanks
Just done
Squalito
IWorx-Paul
09-18-2004, 02:12 AM
Hi Pascal,
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.
Paul
pascal
09-18-2004, 08:18 AM
Thanks Paul
My server show 1.8.
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.
AnyWay everything is fine now :)
A big thank yu to all of yu for your help
Pascal
aftermath
10-02-2004, 02:28 AM
i tried to upgrade my inetwrox to 1.8 and i did exactly what its been said but i got a number of erros and now my interworx from web doesnt work. these r the logs.
httpd-iworx 100 % done 20/87
Stopping InterWorx-web: [ OK ]
Stopping InterWorx-db: [ OK ]
Starting InterWorx-db: [ OK ]
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:2080
no listening sockets available, shutting down
Unable to open logs
Starting InterWorx-web: [FAILED]
interworx 100 % done 25/87
error: %post(interworx-1.8.0-2.iworx) scriptlet failed, exit status 0
Installing mysql-client
Unable to find pid
Restarting httpd and InterWorx-CP
Stopping httpd: [ OK ]
Starting httpd: httpd: module "mod_python.c" is not compatible with this version of Apache (found 20020628, need 20020903).
Please contact the vendor for the correct version.
[FAILED]
iworx: unrecognized service
iworx: unrecognized service
Restarting MySQL
Stopping MySQL: [FAILED]
Starting MySQL: [ OK ]
since i didnt have phyton in my server, the phyton error occured coz of that but what about the others and how can i fix all of these ?
regards
IWorx-Paul
10-02-2004, 04:43 PM
Aftermath,
Could you fill out the form here http://interworx.info/rootdrop and I'll figure out what the problem is. Unfortuntately just based on those errors I can't tell you exactly what to do.
Paul
Lhadatt
10-05-2004, 11:57 PM
Interworx guys -
I upgraded my RH 9 Sago box from 1.7.1 to 1.8 using the script in the first post of this thread. I later found out that PHP was not parsing in normal pages at all. PHP itself seemed to be working, though -- I could get it to respond to command line stuff and yum said it was there. Interworx itself still worked, but I did some searching and I see that you've given it a separate php daemon thingy (nice design choice, btw).
I fixed the problem by adding this to /etc/httpd/conf/httpd.conf:
AddType application/x-httpd-php .php .phtml
Now it recognizes PHP file exensions and parses them. I don't know if this was a fluke on my specific box, but you might want to take a look at that for your next upgrade.
The following problem could certainly be some other than with the new PHP version.
All I know is that up until yesterday morning, where I did the entire upgrade as described above, I was able to use PHP code to stream video files to surfers, using code similar to the below example, and now it streams absolutely nothing, actually it seems from from the receivers end that the content-lenght is zero.
function sendfile($sFilename){
$nFileSize = filesize($sFilename);
$sContentType = PAYC_GetContentType($sFilename);
header ("Content-type: $sContentType");
header ("Content-length: $nFileSize");
if (isset($_GET['saveas']) && ($_GET['saveas']==1))
header ("Content-Disposition: attachment; filename=". $sFilename);
else
header ("Content-Disposition: inline; filename=". $sFilename);
readfile($sFilename);
}
Somehow it is going wrong before it tries to output the file, but if I put in some test lines to echo the file lenght it echo's the file size correctly. All streaming worked perfectly unitl yesterday morning, and I have triple checked that the files to be delivered are on my server in the right location, so I suspect that this problem has to do with the upgrades.
Streaming pictures works fine, HOWEVER suddenly after the upgrade the content-lenght is now zero!?!
eDixon
11-18-2004, 11:39 AM
you may want to start a new thead for this problem, might get a little more traffic. I would suggest in: InterWorx > NodeWorx > General Discussion
I had some of my php scripts break as well, but all were fixed by using the php fix back then (this has been corrected in the newer versions of the upgrade / install).
Thanks I just did with a follow up...
bubbahall
12-04-2004, 09:24 AM
Hey. During the upgrade I got the following errors-
Running test transaction:
Errors reported doing trial run
file /usr/lib/libaprutil-0.so.0.9.4 conflicts between attempted installs of subversion-0.27.0-2 and apr-util-0.9.4-100.iworx
file /usr/lib/libapr-0.so.0.9.4 conflicts between attempted installs of apr-0.9.4-100.iworx and subversion-0.27.0-2
Starting httpd: httpd: module "mod_watch.c" is not compatible with this version of apache.
Please contact the vendor for the correct version.
[FAILED]
I have not seen anything about his particular SO problem here. Oddly, when I do apachectl -v I get 2.0.40. Maybe I'm misreading but I thought the upgrade bumped the version to 2.0.50.
Any ideas?
IWorx-Paul
12-04-2004, 12:46 PM
My guess is that the old redhat 9 subversion RPM was installed on your server. The first thing I would do is remove that package from your system and try the upgrade again - but it might be a bit of a struggle at this point, so it may be best for you to open a support ticket (https://secure.interworx.info/support/helpdesk/) with your server info, and we'll take a look at things.
Paul
vBulletin® v3.7.4, Copyright ©2000-2009, Jelsoft Enterprises Ltd.