IW6 Officially EOL as of 6.14.2, and Automatic IW6 > IW7 Updates

InterWorx version 6.14.2 was released to the IW6 Beta channel this morning (5-17-2023). This version removes the opt-in flag for updating to IW7. IW6 has been deprecated since the beginning of the year, and 6.14.2 marks the point where it is officially EOL.

This means that, once a server updates to 6.14.2, the server will then automatically update to IW7 when the next daily cron runs.

Barring any bugs that may come up, we generally have a weekly release schedule. This means that, barring unforeseen circumstances, the ETA for the progression of 6.14.2 will be as follows:

• Release Candidate: Week of May 22
• Release: Week of May 29
• Stable: Week of June 5

The above is a rough estimate and is subject to change, but should give an idea as to when the update may occur on your server, so as to avoid any surprises.

How it works

For most servers, no interaction is needed. Your server will update to 6.14.2 when that version reaches the update channel that the server is on. This removes the opt-in flag. If all of the pre-flight checks pass, when the next daily cron runs, the server will be updated to IW7.

Things to Know

• Themes have been removed in IW7, however, it is possible to add custom branding and logos: https://appendix.interworx.com/…/add-custom-branding.html
• There are a lot of added features and improvements in IW7 which were not pushed to IW6. A list of some of these features, with related documentation can be found here: https://forums.interworx.com/…/what-s-new-with…/23174

Troubleshooting

As mentioned above, there is a pre-flight checklist that is addressed before the update to IW7 occurs. If any of the items on this checklist fail, the update will not happen. These items are:

• The httpd syntax is error free: If there are any syntax errors in Apache confs of vhosts, this will fail
• LiteSpeed is not enabled: This update cannot occur on Litespeed servers. Litespeed will either need to be disabled, or accounts will need to be migrated to a new server with IW7 installed
• CloudLinux is not enabled: This update cannot occur on servers running CloudLinux. Those accounts must be imported to a new server with IW7 installed
• The server is not part of a cluster: This update cannot occur on clustered servers. Clustering either has to be disabled/removed or accounts will need to be migrated to new servers with IW7 installed
• No custom themes are present: This item being marked as a failure should not stop the upgrade from occurring, it is just an alert that themes are removed in IW7
• The domain vhost files has not been customized: This is the preflight item most likely to fail. Because IW7 includes a new vhost template system, vhosts must be free of customization before converting to the new format can take place.
  • If this step is marked Fail, run the following script at the CLI. It will provide information on any vhosts with customization that cannot be converted, and the specific information that is being flagged:

~iworx/bin/template-adopt.pex --inspect

• Yum dry run: This checks to make sure that yum is up and running
• The server is up to date: This makes sure that the server is up to date
• Server is running EOL OS version: This checks to make sure that the server is on a supported OS. The update to IW7 will not work on EL6 servers. If this fails, accounts must be migrated to a new server with IW7 installed. Supported OSes can be found here: https://appendix.interworx.com/…/requirements-interworx…
• Server is using Dovecot Submission: Servers will using courier for port 587 cannot be updated to IW7. The Dovecot MSA must be in use. Information on how to check if the Dovecot MSA is in use on the server, can be found here: https://forums.interworx.com/…/dovecot-and-php…/23224

If your server is updated to 6.14.2 and does not automatically update itself to IW7 within 24 hours:

• Check to make sure that the daily cron has run. The easiest way to check is by looking at the timestamp on ~iworx/var/last_daily. This indicates the last time the daily cron ran successfully.
  • If it has been more than 24 hours since the last daily cron ran, there should be information about why it did not complete in the cron.log found under ~iworx/var/log

• Check the Preflight Checklist, which is located in NodeWorx under Server > Software Updates. Click the link for Go to Updates Page under Major Version Upgrade at the very bottom of the page. That will take you to the Preflight Checklist. Resolve any failure messages you may find there, if applicable.

If you have any questions, or run into any issues, don’t hesitate to reach out to us at https://support.interworx.com. We will be happy to assist.

Thanks,

-Jenna

Friendly Neighborhood InterWorx Support Manager