InterWorx Version 5 beta 6 & 4.11.7 released!

General Interworx Control Panel Info News & Announcements
1

We’re happy to announce the release of 5 beta 6 (build 531) and 4.11.7 (build 483)! Both contain bug fixes as well as features that will enable a smooth transition to InterWorx 5 when it is out of beta.

[B]PLEASE NOTE: The builds released yesterday for 5 beta 6 and 4.11.7 (530 & 482) had a bug in them that caused Maintenance Mode to not exit correctly. If you see a Maintenance Mode page when logging into NodeWorx or SiteWorx, SSH into your system and run:

yum update interworx

[/B]
Below is a summary of changes made in 5 beta 6 and 4.11.7.

Version 5 beta 6 includes the following:
Improvements to InterWorx Upgrade Infrastructure

  • InterWorx now goes into "maintenance mode" when iworx updates are running (client websites/mail are of course unaffected)
  • Improved logging of success/failure of upgrade steps
  • Improved management of individual upgrade steps, and with ability to automatically "retry" if a step fails on the first try
  • Improved cluster-upgrade control, where cluster nodes will upgrade InterWorx immediately after the cluster manager is updated
[B]Bug Fixes[/B]
  • Fixed a problem with previously upgrade dns zones and their SOA nameserver entry
  • Made it possible to remove inactive system IPs from the database
  • Changed so IPs without relevant changes are not unnecessarily deactivated and re-activated
  • Fixed bug that made Maintenance Mode not exit correctly in some systems
[B]Other Changes[/B]
  • Added domain popup on IP management page
  • Made suphp the default php mode setting for new installs
  • Added web interface for IPv6 diagnostic tools
  • SiteWorx skel index now totally self contained, including images
[B]Interface Tweaks[/B]
  • Logviewer improvements in SiteWorx
  • Cleaned up DNS Records page
  • Cleaned up SSL management page SiteWorx
  • Cleaned up import page

Version 4.11.7 includes the following:

Improvements to InterWorx Upgrade Infrastructure

  • InterWorx now goes into "maintenance mode" when iworx updates are running (client websites/mail are of course unaffected)
  • Improved logging of success/failure of upgrade steps
  • Improved management of individual upgrade steps, and with ability to automatically "retry" if a step fails on the first try
  • Improved cluster-upgrade control, where cluster nodes will upgrade InterWorx immediately after the cluster manager is updated
[B]Big Fixes:[/B]
  • Fixed issue causing new SiteWorx account creation to return an internal server error
  • Fixed bug that made Maintenance Mode not exit correctly in some systems
All InterWorx servers that have auto-updates enabled will be updated according to their subscribed release channel over the next 24 hours. To see the full changelog for these and previous releases, head here: http://www.interworx.com/developers/changelog

Feel free to discuss this release or ask questions here, but for the serious issues, open a ticket at the support desk.

2

Thats awesome to hear up, that would really be going to rock on… Much informative information

3

Maintenance Mode

We have a Xen template with InterWorx-CP preinstalled (unlicensed). I just discovered that if I clone it and the run yum update before configuring InterWorx through the license / goiworx.pex step that it will become stuck in Maintenance Mode.

Does not work:
[LIST=1]

  • Clone Xen template with InterWorx-CP preinstalled.
  • yum update
  • Go to the :2443 InterWorx-CP webpage excepting to see "Welcome to InterWorx-CP" but instead see Maintenance Mode. [/LIST]

    Works as excepted:
    [LIST=1]

  • Clone Xen template with InterWorx-CP preinstalled.
  • Go to the :2443 InterWorx-CP webpage to setup and license InterWorx-CP.
  • yum update [/LIST]

    So it seems that upgrading an unlicensed InterWorx box (or maybe just one that is not setup yet) will get stuck in Maintenance Mode as well.